[RAID] GParted resizing has corrupted a partition

Asked by ohad

Hi All,

I was running Karmic 64bit, and wanted to install a 32 bit version.
I've resized a partition with GParted, shrank it with 20GB. It was previously mounted to /home.

All partitions are ext4, and I'm on RAID0 using my Intel's ICH9R.

After shrinking and installing the 32 bit karmic on the new partition, the old /home partition isn't accessible.

fsck.ext4 /dev/mapper/isw_bahdiiijae_Volume06 (the problematic partition) returned:

The filesystem size (according to the superblock) is 46026217 blocks
The physical size of the device is 40905498 blocks
Either the superblock or the partition table is likely to be corrupt!

I know that the physical size is "right", since it's after the shrink. The superblocks see the data before the shrink.

I have done many tryings and google searches, and nothing helped.
I didn't manage getting testdisk, fsck, fsck.ext4, resize2fs nor e2fsck to work.
Also, all my tries to find how to change the size of the disk as the filesystem thinks it is, have failed.

Please, help me save my dear /home!

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu gparted Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Curtis Gedak (gedakc) said :
#1

More information about this problem with older versions of GParted and solutions can be found at the following link:

WARNING! Problem Resizing File Systems with GParted
http://gparted-forum.surf4.info/viewtopic.php?id=13777

Can you help with this problem?

Provide an answer of your own, or ask ohad for more information if necessary.

To post a message you must log in.