Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- $ fsck /var
- fsck from util-linux 2.20.1
- e2fsck 1.42 (29-Nov-2011)
- fsck.ext2: Is a directory while trying to open /var
- The superblock could not be read or does not describe a correct ext2
- filesystem. If the device is valid and it really contains an ext2
- 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>
- #Comment created on pastebin. So, i decided to try e2fsck:
- $ e2fsck /var
- e2fsck 1.42 (29-Nov-2011)
- e2fsck: Is a directory while trying to open /var
- The superblock could not be read or does not describe a correct ext2
- filesystem. If the device is valid and it really contains an ext2
- 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>
- #I also applied sudo to see what happened:
- $ sudo fsck /var
- [sudo] password for ivan:
- fsck from util-linux 2.20.1
- e2fsck 1.42 (29-Nov-2011)
- fsck.ext2: Is a directory while trying to open /var
- The superblock could not be read or does not describe a correct ext2
- filesystem. If the device is valid and it really contains an ext2
- 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>
- #And sudo e2fsck:
- $ sudo e2fsck /var
- e2fsck 1.42 (29-Nov-2011)
- e2fsck: Is a directory while trying to open /var
- The superblock could not be read or does not describe a correct ext2
- filesystem. If the device is valid and it really contains an ext2
- 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>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
