Hard Drive won't mount, fsck didn't fix it
by thethinker from LinuxQuestions.org on (#54T00)
Hey all. I've got a hard drive that I can't get into. It's where /home is(was) mounted, so I still have access to the system. I'll attach a full log, with highlights here.
Code:# mount /dev/sdb1 /home
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
bash-4.3# dmesg | tail
[ 666.452010] ata7.00: status: { DRDY ERR }
[ 666.452013] ata7.00: error: { UNC }
[ 666.554514] ata7.00: configured for UDMA/133
[ 666.554534] sd 6:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 dri
verbyte=0x08
[ 666.554540] sd 6:0:0:0: [sdb] tag#0 Sense Key : 0x3 [current] [descriptor]
[ 666.554544] sd 6:0:0:0: [sdb] tag#0 ASC=0x11 ASCQ=0x4
[ 666.554549] sd 6:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 08 08 00 00
08 00
[ 666.554553] blk_update_request: I/O error, dev sdb, sector 2056
[ 666.554576] ata7: EH complete
[ 666.554688] EXT4-fs (sdb1): can't read group descriptor 0Ok, let's try fsck:
Code:# fsck /dev/sdb1
fsck from util-linux 2.27.1
e2fsck 1.43.1 (08-Jun-2016)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while
trying to open /dev/sdb1
Could this be a zero-length partition?Def not zero-length, it's got all my user files in it. fdisk can see it:
Code:# fdisk -l
Disk /dev/sdc: 74.5 GiB, 80000000000 bytes, 156250000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e618f55
Device Boot Start End Sectors S
ize Id Type
/dev/sdc1 2048 31250431 31248384 14.9G 82 Linux swap
/dev/sdc2 31250432 156248063 124997632 59.6G 83 Linux
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa4b57300
Device Boot Start End Sectors Siz
e Id Type
/dev/sdb1 2048 976773167 976771120 465.8G 83 LinuxThose are my two linux disks, / is the first one and /home is the second. Ok fine, I'll run fsck to copy over whatever bad superblocks it finds:
Code:# e2fsck -b 32768 /dev/sdb1
e2fsck 1.43.1 (08-Jun-2016)
/dev/sdb1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 87556187 (Attempt to read block from filesystem resulted in
short read) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
...
/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 210795/30531584 files (1.3% non-contiguous), 30718932/122096390 blocksThose dots indicate many many lines of changes. After a restart.....no change to any of those commands.
It's not really a matter of data recovery, since I do weekly backups. I just wanted to know if anyone has any thoughts before I try something like repartitioning/reformat with fdisk - and also if people think that's unlikely and the drive is totally unusable.
Attached Files
Code:# mount /dev/sdb1 /home
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
bash-4.3# dmesg | tail
[ 666.452010] ata7.00: status: { DRDY ERR }
[ 666.452013] ata7.00: error: { UNC }
[ 666.554514] ata7.00: configured for UDMA/133
[ 666.554534] sd 6:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 dri
verbyte=0x08
[ 666.554540] sd 6:0:0:0: [sdb] tag#0 Sense Key : 0x3 [current] [descriptor]
[ 666.554544] sd 6:0:0:0: [sdb] tag#0 ASC=0x11 ASCQ=0x4
[ 666.554549] sd 6:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 08 08 00 00
08 00
[ 666.554553] blk_update_request: I/O error, dev sdb, sector 2056
[ 666.554576] ata7: EH complete
[ 666.554688] EXT4-fs (sdb1): can't read group descriptor 0Ok, let's try fsck:
Code:# fsck /dev/sdb1
fsck from util-linux 2.27.1
e2fsck 1.43.1 (08-Jun-2016)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while
trying to open /dev/sdb1
Could this be a zero-length partition?Def not zero-length, it's got all my user files in it. fdisk can see it:
Code:# fdisk -l
Disk /dev/sdc: 74.5 GiB, 80000000000 bytes, 156250000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e618f55
Device Boot Start End Sectors S
ize Id Type
/dev/sdc1 2048 31250431 31248384 14.9G 82 Linux swap
/dev/sdc2 31250432 156248063 124997632 59.6G 83 Linux
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa4b57300
Device Boot Start End Sectors Siz
e Id Type
/dev/sdb1 2048 976773167 976771120 465.8G 83 LinuxThose are my two linux disks, / is the first one and /home is the second. Ok fine, I'll run fsck to copy over whatever bad superblocks it finds:
Code:# e2fsck -b 32768 /dev/sdb1
e2fsck 1.43.1 (08-Jun-2016)
/dev/sdb1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 87556187 (Attempt to read block from filesystem resulted in
short read) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
...
/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 210795/30531584 files (1.3% non-contiguous), 30718932/122096390 blocksThose dots indicate many many lines of changes. After a restart.....no change to any of those commands.
It's not really a matter of data recovery, since I do weekly backups. I just wanted to know if anyone has any thoughts before I try something like repartitioning/reformat with fdisk - and also if people think that's unlikely and the drive is totally unusable.
Attached Files
 | logfile.txt (130.8 KB) |