[opensuse] kernel HEAD version boot stops with fsck.ext3: No such file... messages

Hello:

This question might bee too specific here but I give a try before I subscribe to opensuse-kernel list.

I have openSUSE 11.2 with kernel version 2.6.31.14-0.6-desktop (i586) which works OK.
Recently I have installed kernel kernel-desktop-2.6.37-35.1.i586 from kernel-HEAD repo.
When I try to boot this kernel the boot process stops with the following messages:

"fsck.ext3: No such file or directory while trying to open /dev/mapper/nvidia_xxxx_part12
/dev/mapper/nvidia_xxxx_part12:
The superblock could not be read or does not describe a corect ext2
filesystem. If the device is valid and it really contains an ext2
filessystem (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 get the same maessage for all of the softraid devices (dev/mapper/nvidia_xxxx_partxx)
(The root partition is not located on a raid device.)

Finally I get:

"fsck failed for at least one filesystem (not /).
Please repair manually and reboot.
The root filesystem is is already mounted read-write.
...
Give root password for login."


When I give the root password and enter the the shell
all the /dev/mapper/nvidia_xxx devices are there (ls -l /dev/mapper)
I can mount manually all the devices for which the above error messages were given
with no problem. (The normal kernel, 2.6.31 also mounts these devices with no problem
at boot.)

Why aren't these devices mounted when the new kernel is booted?
How could I fix this?

Thanks,
Istvan

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: New to Linux (Fedora Core 3) - help with network error message
    ... kernel (usually the longer line and usuallyt the second line) and press e ... You will be asked for root password. ... If you are willing ot deal with command line, ...
    (alt.os.linux)
  • Re: corrupt superblock
    ... The superblock could not be read or does not describe a correct ext2 ... filesystem, ... errors went away when I compiled and used a newer kernel. ...
    (comp.os.linux.misc)
  • Re: SOLVED, maybe: mail no longer vanishes, but new problems abound.
    ... >> The big clue to the problem came when someone changed my root password. ... Start with the kernel:) ... That's what I'm doing -- first the kerhel upgrade. ...
    (Debian-User)
  • root or openssh exploited?
    ... *) loads of user accounts, user auth is against a local passwd file ... "expected" root password worked until at least 5 days ago. ... PID 20: not in readdir output ... Since I have a running kernel I can do a few things: ...
    (comp.os.linux.security)
  • dont know root password
    ... In the thread on X programming, I mentioned that I have a laptop running ... Ubuntu 4.1.2-0, with kernel 2.6.20-15-generic. ... I have an account on it, so I can log in, but I don't know the root password ...
    (comp.os.linux.misc)