xref: /aosp_15_r20/external/e2fsprogs/tests/f_crashdisk/expect.1 (revision 6a54128f25917bfc36a8a6e9d722c04a0b4641b6)
1*6a54128fSAndroid Build Coastguard Workerext2fs_open2: The ext2 superblock is corrupt
2*6a54128fSAndroid Build Coastguard Worker../e2fsck/e2fsck: Superblock invalid, trying backup blocks...
3*6a54128fSAndroid Build Coastguard Worker../e2fsck/e2fsck: The ext2 superblock is corrupt while trying to open test.img
4*6a54128fSAndroid Build Coastguard Worker../e2fsck/e2fsck: Trying to load superblock despite errors...
5*6a54128fSAndroid Build Coastguard Workerext2fs_open2: The ext2 superblock is corrupt
6*6a54128fSAndroid Build Coastguard Worker../e2fsck/e2fsck: Superblock invalid, trying backup blocks...
7*6a54128fSAndroid Build Coastguard Worker../e2fsck/e2fsck: The ext2 superblock is corrupt while trying to open test.img
8*6a54128fSAndroid Build Coastguard Worker
9*6a54128fSAndroid Build Coastguard WorkerThe superblock could not be read or does not describe a valid ext2/ext3/ext4
10*6a54128fSAndroid Build Coastguard Workerfilesystem.  If the device is valid and it really contains an ext2/ext3/ext4
11*6a54128fSAndroid Build Coastguard Workerfilesystem (and not swap or ufs or something else), then the superblock
12*6a54128fSAndroid Build Coastguard Workeris corrupt, and you might try running e2fsck with an alternate superblock:
13*6a54128fSAndroid Build Coastguard Worker    e2fsck -b 8193 <device>
14*6a54128fSAndroid Build Coastguard Worker or
15*6a54128fSAndroid Build Coastguard Worker    e2fsck -b 32768 <device>
16*6a54128fSAndroid Build Coastguard Worker
17*6a54128fSAndroid Build Coastguard WorkerExit status is 8
18