Good morning,
For context…
I wanted to wipe my SSD so I can add anime, music, TV Shows, & ROMs
I used the ‘shred’ command to do so after searching around a while.
I followed this tutorial (3min long video): https://www.youtube.com/watch?v=shSrFbyCAzs
It was still mounted, the SSD.
After doing this it was still okay, but I saw I had the endeavorOS in the SSD still. Was going to delete the files, but cancelled. Figured there has to be a better way going at it. Then it became unmountable. This is the problem. I do not know why/how it did that after I pressed ‘cancel’ after changing my mind on the matter.
I’ll now share how it looks…
e2fsck 1.47.2 (1-Jan-2025)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks…
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb
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
Solutions I’ve tried…
I. sudo fsck.ext4 -y /dev/sdb----------(Did not work, same above result)
II. sudo e2fsck -b 8193 /dev/sdb-----(Did not work, same above result)
III. sudo e2fsck -b 32768 /dev/sdb—(Did not work, same above result)
IIII. sudo fsck -f /dev/sdb----------------(Slightly different result, same outcome however)
fsck from util-linux 2.41
e2fsck 1.47.2 (1-Jan-2025)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks…
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
V. sudo fsck.ext2 -f /dev/sdb -------(Did not work, same above result)
VI. sudo dumpe2fs /dev/sdb | grep superblock
[sudo] password for usr:
dumpe2fs 1.47.2 (1-Jan-2025)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb
Couldn’t find valid filesystem superblock.
VII. sudo e2fsck -C0 -p -f -v /dev/sdb (Did not work, same above result)
VIII. sudo mke2fs -n /dev/sdb
mke2fs 1.47.2 (1-Jan-2025)
Creating filesystem with 244190646 4k blocks and 61054976 inodes
Filesystem UUID: db12adc0-6f40-4dd5-ae15-8f3e53191473
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848
I feel defeated & worthless, my mommy gonna kill me. Bigger brothers & smarter brothers please help me ! Also I love you for taking time to help in advance ^o^)./)
