Sample Header Ad - 728x90

ext2fs_open2: Bad magic number in super-block

5 votes
1 answer
21469 views
I'm trying to resize a Linux partition, but after tweaking a lot with this disk I don't know If I have totally corrupted it. Device Boot Start End Sectors Size Id Type /dev/sdd1 * 64 5913631 5913568 2.8G 17 Hidden HPFS/NTFS /dev/sdd2 5913632 5915039 1408 704K 1 FAT12 /dev/sdd3 5915040 17578125 11663086 5.6G 83 Linux /dev/sdd4 17578126 28320312 10742187 5.1G 83 Linux Using dd deleting partitions and creating new ones I get Device Boot Start End Sectors Size Id Type /dev/sdd1 * 64 5913631 5913568 2.8G 17 Hidden HPFS/NTFS /dev/sdd2 5913632 5915039 1408 704K 1 FAT12 /dev/sdd3 5915040 40000000 34084961 16.3G 83 Linux /dev/sdd4 40000001 62521343 22521343 10.8G 83 Linux Then following some tutorial I do $ e2fsck -f /dev/sdd1 $ e2fsck 1.43.7 (16-Oct-2017) $ ext2fs_open2: Bad magic number in super-block $ e2fsck: Superblock invalid, trying backup blocks... $ e2fsck: Bad magic number in super-block while trying to open /dev/sdd1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 or e2fsck -b 32768 /dev/sdd1 contains a iso9660 file system labelled 'Kali Live' (And so on for the rest of the next 3 partitions) Trying to resize makes the same effect: $ resize2fs /dev/sdd3 resize2fs 1.43.7 (16-Oct-2017) resize2fs: Bad magic number in super-block while trying to open /dev/sdd3 Couldn't find valid filesystem superblock. I've followed a tutorial in internet but is not working, titled: HOWTO: Repair a broken Ext4 Superblock in Ubuntu . $ mke2fs -n /dev/sdd4 $ e2fsck -b block_number /dev/sdd4 $ e2fsck 1.43.7 (16-Oct-2017) e2fsck: Bad magic number in super-block while trying to open /dev/sdd4 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 or e2fsck -b 32768 So I definitely run out of ideas of what to do. Is it totally wasted or shall I just reinstall everything from the scratch?
Asked by Manuela Perez Pimentel (51 rep)
Jul 17, 2018, 02:10 PM
Last activity: May 13, 2025, 06:06 PM