Hello:
Systems were fine, until I recently rebooted. Now they will not start
declaring: "VFS: Cannot open root device "ubd/0" or unknown-block(0,0)"
I am guessing that the new glibc 2.4-11 is what is causing the issue. I
have removed /lib/tls (which was empty) with no avail.
What is causing the kernel to be unable to find the device?
Here is my config:
Host Kernel: 2.6.17.8-skas3-v9-pre9
UML Kernel: 2.6.15.7-bs3-tls
UML fstab: /dev/ubd/0 / ext3 defaults 0 0
+--------------------------------+
| Boot Command
+--------------------------------+
LD_ASSUME_KERNEL=2.4.1 /backup/uml/linux mem=64M root=/dev/ubd/0
devfs=mount ubd0=/path/to/uml/Debian-3.1.ext3 uml_dir=/backup/uml/916
umid=916 eth0=tuntap,,,207.230.28.10
+--------------------------------+
| Boot Log
+--------------------------------+
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking PROT_EXEC mmap in /tmp...OK
Checking for the skas3 patch in the host:
- /proc/mm...found
- PTRACE_FAULTINFO...found
- PTRACE_LDT...found
UML running in SKAS3 mode
Linux version 2.6.15.7-bs3-tls ([EMAIL PROTECTED]) (gcc version 4.1.1
20060525 (Red Hat 4.1.1-1)) #1 Sat Dec 2 14:11:55 CST 2006
Built 1 zonelists
Kernel command line: mem=64M root=/dev/ubd/0 devfs=mount
ubd0=/backup/uml/916/Debian-3.1.ext3 uml_dir=/backup/uml/916
eth0=tuntap,,,207.230.28.10
PID hash table entries: 512 (order: 9, 8192 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 60896k available
Mount-cache hash table entries: 512
Checking for host processor cmov support...Yes
Checking for host processor xmm support...No
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
Checking for /dev/anon on the host...Not available (open failed with
errno 2)
/usr/include/linux/aio_abi.h not present during build
2.6 host AIO support not used - falling back to I/O thread
NET: Registered protocol family 16
mconsole (version 2) initialized on /backup/uml/916/916/mconsole
Initializing Cryptographic API
io scheduler noop registered
Initialized stdio console driver
Console initialized on /dev/tty0
VFS: Cannot open root device "ubd/0" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
EIP: 0073:[<a0145f91>] CPU: 0 Not tainted ESP: 007b:b7ff5fb4 EFLAGS:
00000296
Not tainted
EAX: 00000000 EBX: 00003983 ECX: 00000013 EDX: 00003983
ESI: 0000397f EDI: 00000011 EBP: 00000000 DS: 007b ES: 007b
a035fb84: [<a003b6a4>] notifier_call_chain+0x34/0x40
a035fba0: [<a002ce65>] panic+0x75/0x110
a035fbc0: [<a0001a4c>] mount_block_root+0xbc/0x140
a035fbe8: [<a0002930>] huft_build+0x350/0x5f0
a035fbec: [<a0043620>] autoremove_wake_function+0x0/0x60
a035fc08: [<a0001b2b>] mount_root+0x5b/0x60
a035fc1c: [<a0001b52>] prepare_namespace+0x22/0xf0
a035fc38: [<a000d1b0>] init+0x0/0x160
a035fc3c: [<a000d2ef>] init+0x13f/0x160
a035fc50: [<a0021eab>] run_kernel_thread+0x3b/0x50
a035fc64: [<a000d1b0>] init+0x0/0x160
a035fc70: [<a0021e94>] run_kernel_thread+0x24/0x50
a035fcd0: [<a002967a>] schedule_tail+0x2a/0x180
a035fcf4: [<a000d1b0>] init+0x0/0x160
a035fcfc: [<a001a50e>] new_thread_handler+0x9e/0xd0
a035fd00: [<a000d1b0>] init+0x0/0x160
a035fd5c: [<a0145f91>] kill+0x11/0x20
--
eTecc Support
eTecc Communications, Inc.
www.eTecc.net
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
