projects / thirdparty / e2fsprogs.git / blame
| Commit | Line | Data |
|---|---|---|
| c8b20b40 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 | ||
| 14 | test.img contains a xfs file system labelled 'test_filsys' | |
| 15 | *** debugfs | |
| 16 | *** tune2fs | |
| 17 | ../misc/tune2fs: Bad magic number in super-block while trying to open test.img | |
| 18 | test.img contains a xfs file system labelled 'test_filsys' | |
| 19 | *** mke2fs | |
| a23b50cd | 20 | 128-byte inodes cannot handle dates beyond 2038 and are deprecated |
| c8b20b40 DW |
21 | Creating filesystem with 16384 1k blocks and 4096 inodes |
| 22 | Superblock backups stored on blocks: | |
| 23 | 8193 | |
| 24 |