Marist EDU wrote:
I see you're fixed, but to explain ...
This SLES8 guest under z/VM stopped responding and now when we log on
the guest we get the following messages.
Does anyone have any ideas on what I can do to fix this?
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 8Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
cryptoapi: loaded
RAMDISK: Couldn't find valid RAM disk image starting at 0.
Looks like a missing initial RAM disk.
Freeing initrd memory: 694k freed
kmod: failed to exec /sbin/modprobe -s -k block-major-94, errno = 2
VFS: Cannot open root device "dasdb1" or 5e:05
You don't have a driver for the root device. Commonly caused by no
initial ram disk, or one that's not created properly - you left
something out.
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 5e:05
Linux is getting concerned:-) I've seen it when I didn't have a correct
initial ram disk* and when I had hardware problems (peecee shit
motherboard).
* You gotta have the driver, but it dones't have to be in the initial
ram disk, it _can_ be build into the kernel though vendors tend not to
do it that way.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
