I was glad I’ve found your site in the hope of getting my hdd going again. If it’s not, repeat the steps, but restore a different backup superblock 🙂 Now reboot, and your superblock should be fixed. Finally, restore the superblock from the backup, again replacing the x’s with your partition name, and block_number with the first backup superblock. Now lets find where your superblock backups are kept. Is corrupt, and you might try running e2fsck with an alternate superblock: If the device is valid and it really contains an ext4įilesystem (and not swap or ufs or something else), then the superblock The superblock could not be read or does not describe a correct ext4įilesystem. trying backup blocks.įsck.ext4: Bad magic number in super-block while trying to open /dev/sda5 If your superblock is corrupt, the output will look like this fsck /dev/sda5įsck.ext4: Group descriptors look bad. Here, you can change ext4 to ext3, or ext2 to suit the filesystem. Now, make sure your superblock is the problem, by starting a filesystem check, replacing xxx with your partition name. For this though, we just need the partition number, such as /dev/sda3 or /dev/hdb1. Testdisk is included in Parted Magic, and there’s a great guide on their site. To recover a lost partition, your going to need Testdisk. The above will list all the partitions on all the drives in your computer. Boot from that, and you’ll access to a number of useful tools.įirst, figure out what partition we’re dealing with. The easiest way to carry all this out, seeing as your computer probably won’t boot at this stage, is to download and burn a copy of Parted Magic.
This guide is for ext4, though I’ll explain how other filesystems can be cured along the way. You computer won’t boot, all your filesystem checks tell you you’ve a bad superblock, but you cant seem to find how to fix it. This has happened to me a few times, and it’s not a nice problem to find yourself in.
0 kommentar(er)
