Either the superblock or the partition table is likely to be corrupt!

graysky · 2009-12-25 00:21:46

How should I handle this? The HDD partition was fine the last time I used it. Now I can't even mount it to get at my data

If I try to mount the ext4 partition, I get:

# mount /dev/sdb1 /mnt
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

So looking at dmesg shows:

# dmesg | tail -n 10
sky2 eth1: enabling interface
sky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth1: no IPv6 routers present
EXT4-fs (sdb1): bad geometry: block count 153356482 exceeds size of device (151035089 blocks)
EXT4-fs (sdb1): bad geometry: block count 153356482 exceeds size of device (151035089 blocks)
EXT4-fs (sdb1): bad geometry: block count 153356482 exceeds size of device (151035089 blocks)
EXT4-fs (sdb1): bad geometry: block count 153356482 exceeds size of device (151035089 blocks)
EXT4-fs (sdb1): bad geometry: block count 153356482 exceeds size of device (151035089 blocks)

WTF is going on with this?

If I attempt a repair, I get:

# fsck /dev/sdb1
fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
The filesystem size (according to the superblock) is 153356482 blocks
The physical size of the device is 151035089 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no

Repo contains a file system with errors, check forced.
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
Error reading block 151519232 (Invalid argument) while reading inode and block bitmaps.  Ignore error<y>? no

fsck.ext4: Can't read an block bitmap while retrying to read bitmaps for Repo
e2fsck: aborted
[root@novelty]# fsck /dev/sdb1
fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
The filesystem size (according to the superblock) is 153356482 blocks
The physical size of the device is 151035089 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no

Repo contains a file system with errors, check forced.
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
Error reading block 151519232 (Invalid argument) while reading inode and block bitmaps.  Ignore error<y>? no

fsck.ext4: Can't read an block bitmap while retrying to read bitmaps for Repo
e2fsck: aborted

Last edited by graysky (2014-11-03 08:39:19)

Dheart · 2009-12-25 08:13:52

Ignore that block in order for the chech to try to continue.
Also how old is your HDD? Mine started fucking up bout five years into use...

graysky · 2009-12-25 08:29:00

If I answer yes to ignoring it, fsck just exits and I can't continue. The HDD is a refurbished unit I got from Seagate when the original started clicking on idle. It's a 640 gig older 7200.11 series drive. The refurb'ed hdd only has 200 hours on it. The solution was to just wipe the drive and restore a backup set. It's working fine now but I have no idea why it just went bad.

Arch Linux

#1 2009-12-25 00:21:46

Either the superblock or the partition table is likely to be corrupt!

#2 2009-12-25 08:13:52

Re: Either the superblock or the partition table is likely to be corrupt!

#3 2009-12-25 08:29:00

Re: Either the superblock or the partition table is likely to be corrupt!

Board footer