Greetings.
I have a couple of Seagate Expansion USB drives which are not being auto mounted with the Vero V. I have other Seagate drives (not Expansion but Touch One) and WD which get successfully auto mounted. All these drives are EXT4 formatted and can be mounted successfully on my Linux-based NAS.
I am linking the log below, where I started the V with one of the problematic drives already connected and accessed Files - Auto mounted drives. Then I disconnected and connected also a Seagate drive, this time a Seagate Touch One and this one is auto-mounted successfully. Can also be ejected.
I just wanted to know if this issue is due to the quality of this model of Seagate drives. They were bought in separate occasions with a at least a few weeks, if not months, gap between each purchase. Thanks for your time in advance.
Jan 31 16:14:03 osmc-waldo kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (400)
Jan 31 16:14:03 osmc-waldo udisks-glue[2790]: Failed to automount /dev/sda1: Error mounting: mount: /media/188c19f7-e318-4576-94f1-680e0beed52c: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
So are you able to mount it manually and only auto mount not working?
@Winters Can you restart the Vero just with one of the problematic Seagate Expansion USB HDDs connected, log into the VeroV using ssh (user:osmc, password:osmc) and give here the output of
I didn’t mount it manually, or at least I don’t think I did. What I did was:
Connect the Seagate Expansion (one that can’t seem to be auto-mounted) and booted the V
Went to Files (usually any auto-mounted drives already appear here) and also checked Auto-mounted drives option but nothing was listed there
Disconnected the Seagate Expansion. Couldn’t see the option to Remove safely on the side menu
Connected another Seagate drive (model is One Touch) and accessed Files. Here this drive appears already mounted and I access the content with not issues
I did the above with the problematic drive and another which I had used in the past with auto-mount with no issues (although with my Vero 4K+ at the time), to rule out either issues with the auto-mount feature or issues with the drives themselves.
I’m not well-versed in command line tools but I am willing to give it a go, if you have any suggestions for further troubleshooting.
I used my Terramaster NAS. All the external drives that I used described in the steps above were formatted using the same NAS.
I share my USB drives in my network to be accessed by the Veros, via this same NAS, but recently their latest OS update which I did a few days ago has brought a few issues which I no longer have the patience to deal with, so I am looking for an alternative OS. In meantime, I was thinking of accessing my USB drives directly with the Vero.
I compared the features with the features of an ext4 file system I created with a Vero long time ago and the features ea_inode and uninit_bg are not shown. Might be there is an incompatibility, now.
Can you connect one of the working etxernal drives and show the output of dumpe2fs here again? Thx.
It appears that this feature is introduced in the 4.13 kernel as noted by @JimKnopf. Vero V is currently using the 4.9 kernel, with plans to move to the 5.15 kernel in the near future.
In the interim, I will see if this can be backported.
@JimKnopf Can you give me the necessary mkfs/tune2fs commands so that I can toggle this flag on a USB drive and verify if this can be backported? I don’t mind reformatting each time as I will be testing on a fresh disk and just verifying mounting.
Sure: tune2fs -O ea_inode <ext4 partition like /dev/sda1>
(You can only set this feature flag but you cannot clear/reset it like using tune2fs -O ^ea_inode)
(Just for later reference, how I prepare an hdd/ssd at /dev/sda just holding videos with OSMC:
sudo dd if=/dev/zero of=/dev/sda bs=1M count=32 (clean the drive, all data are lost)
sudo apt update && sudo apt install fdisk (install fdisk if not already done)
echo -e "g\nn\n\n\n\nw\n" | sudo fdisk /dev/sda(command line to create gpt partition table+partition on /dev/sda)
I just followed this workflow and the drive was successfully auto-mounted on the V after rebooting. I’ll do the same for the other drive. Thank you, @JimKnopf, @sam_nazarko and @fzinken for your help!