Advertisement
Guest User

Untitled

a guest
Nov 23rd, 2017
86
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.63 KB | None | 0 0
  1. [root@archlinux one]# fsck.ext4 -f -v /dev/mapper/cryptofs
  2. e2fsck 1.43.7 (16-Oct-2017)
  3. ext2fs_open2: Bad magic number in super-block
  4. fsck.ext4: Superblock invalid, trying backup blocks...
  5. fsck.ext4: Bad magic number in super-block while trying to open /dev/mapper/cryptofs
  6.  
  7. The superblock could not be read or does not describe a valid ext2/ext3/ext4
  8. filesystem. If the device is valid and it really contains an ext2/ext3/ext4
  9. filesystem (and not swap or ufs or something else), then the superblock
  10. is corrupt, and you might try running e2fsck with an alternate superblock:
  11. e2fsck -b 8193 <device>
  12. or
  13. e2fsck -b 32768 <device>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement