UML - Kernel Panic after fresh installation of UML

[netboy1977]

Hi!
I installed UML according to Gentoo UML Howto.

Unfortunately I get the error message:

VFS: Cannot open root device "98:0" or unknown-block(98,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)

EIP: 0073:[<a022f618>] CPU: 0 Not tainted ESP: 007b:a04156ac EFLAGS: 00000246
Not tainted
EAX: 00000000 EBX: 00000001 ECX: a0415754 EDX: a04156d4
ESI: 00000008 EDI: 00000000 EBP: a04156bc DS: 007b ES: 007b
Call Trace:
a041bb20: [<a0040aad>] notifier_call_chain+0x2d/0x50
a041bb30: [<a0183b36>] bust_spinlocks+0x46/0x50
a041bb40: [<a002e3c1>] panic+0x71/0x120
a041bb60: [<a0002f19>] mount_block_root+0xb9/0x120
a041bb9c: [<a00111e0>] init+0x0/0x110
a041bbb0: [<a0002fb6>] mount_root+0x36/0x40
a041bbc0: [<a0002fef>] prepare_namespace+0x2f/0x110
a041bbcc: [<a00111e0>] init+0x0/0x110
a041bbd0: [<a000d80a>] sock_init+0x2a/0x40
a041bbe8: [<a00111e0>] init+0x0/0x110
a041bbf0: [<a00112e6>] init+0x106/0x110
a041bc08: [<a00111e0>] init+0x0/0x110
a041bc10: [<a0014ac8>] run_kernel_thread+0x78/0x80
a041bc28: [<a00111e0>] init+0x0/0x110
a041bc38: [<a0014a90>] run_kernel_thread+0x40/0x80
a041bcd4: [<a00111e0>] init+0x0/0x110
a041bce0: [<a001b85b>] new_thread_handler+0x15b/0x190
a041bce4: [<a00111e0>] init+0x0/0x110
a041bd20: [<a022f5a8>] __restore+0x0/0x8
a041bd60: [<a022f618>] __sigprocmask+0x38/0xb0

What can that mean?? /dev/ubd exist!

Thanks!

[destiney]

# linux --showconfig | grep UBD
CONFIG_BLK_DEV_UBD=y

[netboy1977]

It says:

CONFIG_BLK_DEV_UBD=y
CONFIG_BLK_DEV_UBD_SYNC=y


It must be a problem with the root_fs.

This is the latest error message when I try to boot:

* Remounting root filesystem read-only (if necessary)... [ ok ]
* Checking root filesystem...ext2fs_check_if_mount: No such file or directory while determining whether /dev/ubd/0 is mounted.
fsck.ext2: No such file or directory while trying to open /dev/ubd/0
/dev/ubd/0:
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>

* Filesystem couldn't be fixed
[ !! ]