My system won't boot in multi mode. I get the following in Maintenance Mode. (none):/dev # e2fsck -b 8193 /dev/dasda e2fsck -b 8193 /dev/dasda e2fsck 1.28 (31-Aug-2002) e2fsck: Bad magic number in super-block while trying to open /dev/dasda 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> (none):/dev # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2365444 2203616 41668 99% / (none):/dev #
On Monday, 4 October 2004 23.23, Patrick B. O'Brien wrote:
My system won't boot in multi mode. I get the following in Maintenance Mode.
(none):/dev # e2fsck -b 8193 /dev/dasda e2fsck -b 8193 /dev/dasda e2fsck 1.28 (31-Aug-2002) e2fsck: Bad magic number in super-block while trying to open /dev/dasda
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>
(none):/dev # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2365444 2203616 41668 99% /
If the device is dasda1, then that is what you should be running fsck on, not dasda Also, note that it's usually a bad idea to let your root file system get to 99% use
participants (2)
-
Anders Johansson
-
Patrick B. O'Brien