Public bug reported:
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!
** Affects: ubuntu
Importance: Undecided
Status: New
--
GParted resizing has corrupted a partition - ext4, RAID0 w/ICH9R
https://bugs.launchpad.net/bugs/483859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
