Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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 tries 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.
... I didn't manage getting testdisk, fsck, fsck.ext4, resize2fs nor e2fsck to work. ...
According to the FAQ, resize2fs or ext2resize were the programs that could have resized the logical structures to prepare the file system for the change of physical size. What happened when you tried resize2fs?
Others can/should chime in and deliver lectures on backing up your data, but IMHO you can now only try to fsck your way through /home and cross your fingers that most of your data was not in the far end of the file system. Since you have already reallocated and reused the space I don't know of any way to back out of where you are now.