Richard R
asked on
Linux ext4 error, hard drive partition is missing and hdd is not mounting
Hey experts, I've been with this error for the past 2 days trying to find a way around it, but so far nothing seems to be working for me.
Basically, after a reboot (shutdown -r now), the server is not recognizing the second and third HDD's partition, it cannot be mount. The /dev/sdb1 partition is not present anymore and it's where I had about 600GB of data, and /dev/sdc1 was the backup hard-drive which has the partition present but it does not mount. Check the error message:
Same happens for the /dev/sdc device
I tried running the following for each superblock:
But it didn't seem to work.
Has anyone encountered the same error and found a fix or a work around? I'm running out of options here and since both drives are not mounting and 600GB of data short.
Hard Drives are healthy, reporting no errors.
SATA cable was changed to new ones, and still nothing.
Would really appreciate your input.
Thank you!
Basically, after a reboot (shutdown -r now), the server is not recognizing the second and third HDD's partition, it cannot be mount. The /dev/sdb1 partition is not present anymore and it's where I had about 600GB of data, and /dev/sdc1 was the backup hard-drive which has the partition present but it does not mount. Check the error message:
[root@jumbo ~]# fsck -fy /dev/sdb
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Group descriptors look bad... trying backup blocks...
fsck.ext4: Bad magic number in super-block when using the backup blocks
fsck.ext4: going back to original superblock
fsck.ext4: Device or resource busy while trying to open /dev/sdb
Filesystem mounted or opened exclusively by another program?Same happens for the /dev/sdc device
I tried running the following for each superblock:
fsck.ext4 -p -b <superblock> -B 4096 /dev/sdbBut it didn't seem to work.
Has anyone encountered the same error and found a fix or a work around? I'm running out of options here and since both drives are not mounting and 600GB of data short.
Hard Drives are healthy, reporting no errors.
SATA cable was changed to new ones, and still nothing.
Would really appreciate your input.
Thank you!
look at your command...you are running fsck on the device itself, not a partition
you need to run on /dev/sdb1, not /dev/sdb
how is your fstab defined?
sometimes with sata drives if you have external drives connected at startup then your device names are moved around so your boot might be sdc instead of sda the next time or something to that effect though it still boots because the UUID is specified for mounting and not the explicit device. if you run fdisk -l are the device names what it was before?
you need to run on /dev/sdb1, not /dev/sdb
how is your fstab defined?
sometimes with sata drives if you have external drives connected at startup then your device names are moved around so your boot might be sdc instead of sda the next time or something to that effect though it still boots because the UUID is specified for mounting and not the explicit device. if you run fdisk -l are the device names what it was before?
ASKER
I did run smart health check on the HDD, they are healthy.
Yes, fdisk -l shows the exact devices as they were before, except the missing partition sdb1
my /etc/fstab has this:
As I mentioned, /dev/sdb1 is not present after reboot... while /dev/sdc1 is present, this is the output I had for it from previous SSH session screen:
Also before I did get this:
Also, looking through SSH session screens, this is on of the DMESG tail message I have:
Yes, fdisk -l shows the exact devices as they were before, except the missing partition sdb1
my /etc/fstab has this:
/dev/sdb1 /storage ext4 defaults 1 2
/dev/sdc1 /backup ext4 defaults 1 2As I mentioned, /dev/sdb1 is not present after reboot... while /dev/sdc1 is present, this is the output I had for it from previous SSH session screen:
[root@jumbo ~]# fsck -p /dev/sdc1
fsck from util-linux-ng 2.17.2
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc1
/dev/sdc1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>Also before I did get this:
[root@jumbo ~]# fsck -y /dev/sdc1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
/dev/sdc1 has unsupported feature(s): FEATURE_C17 FEATURE_C22 FEATURE_C25 FEATURE_C28 FEATURE_C29 FEATURE_C30 FEATURE_C31 compression FEATURE_I5 FEATURE_I10 FEATURE_I13 FEATURE_I19 FEATURE_I20 FEATURE_I21 FEATURE_I23 FEATURE_I24 FEATURE_R2 FEATURE_R10 FEATURE_R13 FEATURE_R19 FEATURE_R20 FEATURE_R21 FEATURE_R23 FEATURE_R24
e2fsck: Get a newer version of e2fsck!Also, looking through SSH session screens, this is on of the DMESG tail message I have:
[root@jumbo ~]# dmesg | tail
readahead-collector: starting delayed service auditd
readahead-collector: sorting
readahead-collector: finished
EXT4-fs (sdb): ext4_check_descriptors: Checksum for group 880 failed (61921!=0)
EXT4-fs (sdb): group descriptors corrupted!
EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
udev: starting version 147
EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
when you do fdisk and check for partition is that drive is there if yes what is file system it showing, i will suggest go manually and do fidisk and delete the partition and check filesystem flag for the same
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No other valid answer.
How did you come up with a conclusion that the the disk is heathy? Have you run a disk check utility?