projects / thirdparty / e2fsprogs.git / blame
| Commit | Line | Data |
|---|---|---|
| b291c11f DW |
1 | *** e2fsck |
| 2 | ext2fs_open2: Bad magic number in super-block | |
| 3 | ../e2fsck/e2fsck: Superblock invalid, trying backup blocks... | |
| 4 | ../e2fsck/e2fsck: Bad magic number in super-block while trying to open test.img | |
| 5 | ||
| 6 | The superblock could not be read or does not describe a valid ext2/ext3/ext4 | |
| 7 | filesystem. If the device is valid and it really contains an ext2/ext3/ext4 | |
| 8 | filesystem (and not swap or ufs or something else), then the superblock | |
| 9 | is corrupt, and you might try running e2fsck with an alternate superblock: | |
| 10 | e2fsck -b 8193 <device> | |
| 11 | or | |
| 12 | e2fsck -b 32768 <device> | |
| 13 | ||
| b291c11f | 14 | *** debugfs |
| b7454eb8 | 15 | debugfs: Bad magic number in super-block while trying to open test.img |
| b291c11f DW |
16 | *** tune2fs |
| 17 | ../misc/tune2fs: Bad magic number in super-block while trying to open test.img | |
| b291c11f DW |
18 | *** mke2fs |
| 19 | Creating filesystem with 16384 1k blocks and 4096 inodes | |
| 20 | Superblock backups stored on blocks: | |
| 21 | 8193 | |
| 22 |