Can't mount previously mounted USB HDD

My 5TB USB HDD will not automount on my Vero for some reason.
It was previously /dev/sdd1 but know it’s not even listed when using df.
If I plug it into my Windows 10 laptop I can read and write to it with no issues.
I eject it and plug it into the Vero and it doesn’t see.
Tried different cables, different USB ports, cold booted teh Vero with it plugged in, nothing works.
It does show up in lsblk.
Any ideas?

osmc@osmc:~$ df
Filesystem           1K-blocks       Used  Available Use% Mounted on
devtmpfs                774688          0     774688   0% /dev
tmpfs                   899236       8744     890492   1% /run
/dev/vero-nand/root   14499760    9533228    4206932  70% /
tmpfs                   899236          0     899236   0% /dev/shm
tmpfs                     5120          0       5120   0% /run/lock
tmpfs                   899236          0     899236   0% /sys/fs/cgroup
/dev/sdb1           7811937256      94240 7811826632   1% /media/Seagate8TB-2
/dev/sda1           7811937256 7735346200   76574672 100% /media/Seagate8TB
/dev/sdc1           3904735508 2662298808 1242420316  69% /media/Seagate4TB
tmpfs                   179844          0     179844   0% /run/user/1000
osmc@osmc:~$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    0  7.3T  0 disk
`-sda1         8:1    0  7.3T  0 part /media/Seagate8TB
sdb            8:16   0  7.3T  0 disk
`-sdb1         8:17   0  7.3T  0 part /media/Seagate8TB-2
sdc            8:32   0  3.7T  0 disk
`-sdc1         8:33   0  3.7T  0 part /media/Seagate4TB
sdd            8:48   0  4.6T  0 disk
`-sdd1         8:49   0  4.6T  0 part
mmcblk0      179:0    0 14.6G  0 disk
mmcblk0boot0 179:32   0    4M  0 disk
mmcblk0boot1 179:64   0    4M  0 disk
mmcblk0rpmb  179:96   0    4M  0 disk

Tried this with no luck:
osmc@osmc:~$ sudo mkdir /media/Seagate5TB
osmc@osmc:~$ sudo mount /dev/sdd1 /media/Seagate5TB
mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.

Whats the FS on it?
What does lsblk -f say?

It’s ext4.
Running fsck now, it found some issues it’s fixing.
I got a bunch of lines, more than I can count, that say something to this extent:
Group descriptor 37260 checksum is 0x0927, should be 0x4e64. FIXED.
Then it ended with this:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
fsck: Warning… fsck.ext4 for device /dev/sdd1 exited with signal 9.

Doesn’t sound healthy, what happens if you run it again?

osmc@osmc:~$ lsblk -f
NAME         FSTYPE LABEL        UUID                                 MOUNTPOINT
sda
-sda1       ext4   Seagate8TB   349bdea0-60d3-46bc-82f1-6a6a072f3f8e /media/Seagate8TB
sdb
-sdb1       ext4   Seagate8TB-2 7312e332-39af-41a7-8008-dfb04d370401 /media/Seagate8TB-2
sdc
-sdc1       ext4   Seagate4TB   8f130b50-ab0f-482f-bd60-ef5663ce2e53 /media/Seagate4TB
sdd
-sdd1       ext4   Seagate5TB   8f303397-fb67-4fe5-89f3-e5ea50d96ba2
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0rpmb

osmc@osmc:~$ sudo fsck /dev/sdd1
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
One or more block group descriptor checksums are invalid. Fix?

Not looking good, can you now mount it?

It’s still doing the second fsck.
Once it is complete how do you recomend I mount it, through CLI or reboot Vero and see if it automounts?

Try manually so that you see what is happening.
If mounting manually works suggest to backup the files and run smart test on the disk and then format it once more before recover the backup files.

Won’t mount…

osmc@osmc:~$ sudo mount /dev/sdd1 /media/Seagate5TB
mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

Does it still mount under Windows as you indicated earlier?
If so do the backup there and then do the steps for smart test and format.

Good thing I have an empty 8TB handy…

would get smartctl installed on vero and do a scan to see if the drive is healthy, this is why i dont have moving drives…

So you just run SSDs?

@fzinken
Backup completed.
SMART status good.
Any specific test you think should be ran to further check disk health or just go ahead and format the drive and transfer everything back?

SMART status good? Did you run a short/long smart test?
What are the error values? I think easiest is to use smartctl on the Vero and then paste-log the output.

Vero has smartctl preloaded?

I don’t think that it does, but just try running smartctl. If you get command not found then it’s not installed :grin:

if it’s not installed:

sudo apt install smartmontools

will install it.

1 Like
osmc@osmc:~$ sudo smartctl -i /dev/sdc1
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               Seagate
Product:              BUP BK
Revision:             0304
Compliance:           SPC-4
User Capacity:        5,000,981,077,504 bytes [5.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
Logical Unit id:      0x5000000000000001
Serial number:        NA9W6CCJ
Device type:          disk
Local Time is:        Wed Sep 25 20:38:11 2019 MST
SMART support is:     Available - device has SMART capability.
SMART support is:     Disabled
Temperature Warning:  Disabled or Not Supported

How do you enable SMART?

osmc@osmc:~$ sudo smartctl -c /dev/sdc
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdc: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Would this be because it’s on a USB HUB?