Last active
May 22, 2023 20:01
-
-
Save KenwoodFox/a60add1ac9b6e8228874eb42612f4a3a to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e2fsck -b 8193 /dev/sda1 | |
e2fsck 1.47.0 (5-Feb-2023) | |
e2fsck: Bad magic number in super-block while trying to open /dev/sda1 | |
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 <device> | |
or | |
e2fsck -b 32768 <device> | |
/dev/sda1 contains a ext2 file system labelled 'ROOT_FS' | |
last mounted on Tue Mar 8 14:40:47 2022 | |
# Keeps doing this when i try and mount? | |
mount -t ext2 -o sb=8193 /dev/sda1 rescue/ | |
mount: /mnt/rescue: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. | |
dmesg(1) may have more information after failed mount system call. | |
Journalctl: | |
May 22 16:00:13 Hydroxonium kernel: EXT4-fs (sda1): VFS: Can't find ext4 filesystem | |
May 22 16:00:23 Hydroxonium kernel: EXT4-fs (sda1): VFS: Can't find ext4 filesystem | |
# Im not trying to mount ext4? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment