I'm getting the following error upon fsck in server reboot.
The superblock could not be read or does not describe a correct ext2 file system. 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 8199
I am a recent Linux user so this question has probably a trivial answer. I have dual boot on my pc with opensuse 11.1 and windows xp, each system being installed on different hard-drives.
The drive containing opensuse is currently divided as follows:
Device Size F Type FS Type Label Mount Point
I am playing with LVM and while doing lvreduce. I now get this error:
[root@localhost raja]# e2fsck -f /dev/vg1/lvol2
e2fsck 1.41.12 (17-May-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/vg1/lvol2
The superblock could not be read or does not describe a correct ext2
I am using Debian wheezy AMD64 7.0 and at present I am unable to resume after hibernation. When I issue the command update-initiates -u I am getting the following error
failed to detect canonical device of /dev/sda2(swap partition).
please help me to resolve this issue like adding an entry to crypttab etc.,
Please explain the process in detail because I am new to Linux.
I wouldn't use 'resume=/dev/mapper/cryptroot', at least for me it seems to lead to a kernel panic on resume.If I use 'resume=UUID=xxxxxxxxx' where xxxxxxxxx is the uuid of my swap partition then it works fine.
Check your resume entries for GRUB_CMDLINE_LINUX or GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub are pointing to the correct swap partition. After correcting you will need to write the changes to your grub.conf:sudo update-grubIt should output that it found the swap partition.