LinuxQuestions.org - Size in superblock is different from the physical size of the partition

Page 2 of 2

Show 50 post(s) from this thread on one page

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Size in superblock is different from the physical size of the partition (https://www.linuxquestions.org/questions/linux-hardware-18/size-in-superblock-is-different-from-the-physical-size-of-the-partition-298175/)

The shepherd

10-31-2011 01:48 AM

A lightning stroke damaged my disk. I dd'ed the image to another disk an ran fsck on the image. I got:

Code:

$ fsck.ext3 -v -y  ./copy.iso 

e2fsck 1.41.14 (22-Dec-2010)

Error reading block 13858 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes



Force rewrite? yes



Superblock has an invalid journal (inode 8).

Clear? yes



*** ext3 journal has been deleted - filesystem is now ext2 only ***



The filesystem size (according to the superblock) is 15912374 blocks

The physical size of the device is 12900 blocks

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

Abort? yes

Is there anything that is likely to work that I can do to rescue data from the disk?

BobJam

08-12-2012 01:40 PM

Quote:

Originally Posted by Hailey's_Comet (Post 4418424)

I just typed:

Code:

resize2fs -f /dev/sdb1

I have had EXACTLY the same issue as others in this thread, AND my compliments to Mr. Hailey's_Comet . . . the only thing I would add to the line is sudo. But the resize2fs command IS the one that SOLVED my problem. Compliments again to HC.

I found this solution by searching on the clause "Either the superblock or the partition table is likely to be corrupt" . . . the message from a forced fsck. I had tried TestDisk and a few other remedies that DIDN'T work.

For those of us that mess around with GParted trying to shrink partitions and screw up, this is a likely solution (or at least it was for me and a few others here.) Thanks very much HC.

tsester

11-17-2015 06:55 AM

i also did:

Code:

fsck -y /dev/sdd1

and then

Code:

resize2fs -p /dev/sdd1 48839725

and it WORKED. many thanx.

On a sidenote: my problem appeared on a ,now, faulty external case. so after i took the disk out and into my pc i restored the partition with gparted to max size. Apparently the external case saw the disk of less capacity than the partition, and even so many errors occured later on on transfers. i found in the past that using ext2 works quite well, (journals get dropped). Nevermind, i guess its time has come, so i'm now using that disk as an internal one.

davidleosam

09-11-2016 08:48 AM

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

I make a resize of my logical disc, /dev/mapper and I found the error:

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

Ok the solution is to make this order with the corrupt partition:

[root@localhost]# mke2fs -S /dev/mapper/VolGroup-lv_home && fsck /dev/mapper/VolGroup-lv_home

and that's all...

source:

novell support

All times are GMT -5. The time now is 01:20 AM.

Page 2 of 2

Show 50 post(s) from this thread on one page