I was moving my LibreElec setup to a better computer... I got all the drives installed and the machine boots up just fine..
I have 3 HDs hooked up.. A 2TB, a 4TB and a 6TB... The 2 and 4 drives show up fine.. The 6TB is no where to be found...
I have tried different cabling, different SATA ports, JUST the boot drive and the 6TB... Nothing helps.. 6TB worth of TV Shows.. Gone..
Any assistance in getting them back would be GREATLY appreciated...
HOLODECK:~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 1978400 201360 1777040 10% /dev
/dev/sda1 499656 213980 275192 44% /flash
/dev/sda2 152228792 2182252 150030156 1% /storage
/dev/loop0 201472 201472 0 100% /
tmpfs 2014080 0 2014080 0% /dev/shm
tmpfs 2014080 7328 2006752 0% /run
tmpfs 2014080 0 2014080 0% /sys/fs/cgroup
tmpfs 2014080 12 2014068 0% /tmp
tmpfs 2014080 384 2013696 0% /var
/dev/sdd 1921803544 67609312 1756502120 4% /var/media/2TB
/dev/sdc 3844641608 1557931120 2091343176 43% /var/media/4TB
I know there is an easy way to post DMESG etc etc etc without cut n pasting the whole listing...
Anyone wanna throw me a quick reminder??
I am seeing a lot of this in DMESG
[ 10.139699] EXT4-fs (sdb): ext4_check_descriptors: Block bitmap for group 32250 overlaps superblock
[ 10.139700] EXT4-fs (sdb): ext4_check_descriptors: Inode bitmap for group 32250 overlaps superblock
[ 10.139700] EXT4-fs (sdb): ext4_check_descriptors: Inode table for group 32250 overlaps superblock
[ 10.139701] EXT4-fs (sdb): ext4_check_descriptors: Block bitmap for group 32251 overlaps superblock
[ 10.139701] EXT4-fs (sdb): ext4_check_descriptors: Inode bitmap for group 32251 overlaps superblock
/dev/sdb being the 6TB drive...
Forgive the random spewage... I don't use LINUX console much so it's kinda coming back to me in fits and spurts...
OK I am in parted...
(parted) print devices
print devices
/dev/sdb (6001GB)
/dev/sda (250GB)
/dev/sdc (4001GB)
/dev/sdd (2000GB)
(parted)
The 6TB is being seen...
Is there a way to use parted to fix the disk
Also check any errors on your drive(s), including the SMART log on the drive itself. Linux can even be very picky with diskdrives/ssds that are still in hibernation or suspend mode.
For 'real' errors, I would use a Live Session of Gparted. A gui is just that easier to work with in case of errors.
Thanx for the reply..... I got it fixed..
I ran fsck.ext4 -vy and, after a bit of access, it fixed all the errors..
Whew!!!! I did NOT want to have to try and find 6TB worth of TV shows!!
It all depends on how valuable you consider "your" data, and whether or not making backups is in order.