Cannot open root device, Kernel panic

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

Re: Cannot open root device, Kernel panic

Do yo have another SLES8 guest available? Try LINKing to the failing guests root file system from it and see if you can mount it. Marist EDU wrote: 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

Re: Cannot open root device, Kernel panic

I booted into the install partition and was successfully able to mount dasda1 and view the contents. Should I try to ZIPL it again? Josh -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Posted At: Wednesday, July 05, 2006 7:34 AM Posted

Re: Cannot open root device, Kernel panic

Was there any recent maintenance done? After maintenance (especially kernel maintenance) usually mkinitrd and zipl does need to be run before rebooting. Do you have a backup of this disk? Marist EDU wrote: I booted into the install partition and was successfully able to mount dasda1 and view

Re: Cannot open root device, Kernel panic

I think you're right it did have to do with maintenance. I booted to the install partition and re-ran zipl and now it ipl's fine. Thanks for your help! Josh -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Posted At: Wednesday, July 05,

Re: Cannot open root device, Kernel panic

Excellent. Glad to be of assistance. Marist EDU wrote: I think you're right it did have to do with maintenance. I booted to the install partition and re-ran zipl and now it ipl's fine. Thanks for your help! Josh -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans

Re: Cannot open root device, Kernel panic

Just a simple hint for everybody interested... To rescue a x86 server, you can boot from the installation CD and enter in a rescue console mode. You can do the same with z/VM, but without a CD (you guessed it...) This works with SLES8 and SLES9, but I assume it should work with other

Ned with 2.6.9 Linux Kernel

Has anyone run UTS Global's Ned with the 2.6 kernel? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit

Re: SLES 10 Parmfile Encoding

Hello list, I finally got SLES10 RC 3 installed. Thanks to William Scully for recommending to take out the InstNetDev, OsaInterface and OsaMedium parameters. That was the only way I was able to get out of the starting gate. Hopefully SuSE will fix that before GA. It did install with the iso

Re: Cannot open root device, Kernel panic

Actually, you can go through the complete dialog for the install system, creating the network and using the IP address of the failing system. This allows you to start up a (much more comfortable) ssh session. You can even run yast and begin the GUI install, up through activating the disk

Re: SLES 10 Parmfile Encoding

Here's the parmfile I've been using, which includes the Osa definition, but not the InstNetDev entry. You're problem may be with that single entry, instead of the entire three. I still do FTP installs, as I haven't learned to trust NFS yet. ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc

Re: Cannot open root device, Kernel panic

Of course! It is definitely more easy to edit a broken fstab with vi on a ssh console... But TN3270 is a good way to learn sed! :-) On 7/5/06, Nix, Robert P. [EMAIL PROTECTED] wrote: Actually, you can go through the complete dialog for the install system, creating the network and using

So what are the major points of improvement in SLES10?

Seems every major release adds function and makes things better or faster or more stable, but are there any new things that z/Series can exploit well? -- For LINUX-390 subscribe / signoff / archive access instructions, send

Re: So what are the major points of improvement in SLES10?

James, Very good question. I would also like to know if there's any reason to seriously look at SLES10 on our mainframe. I have not gotten any value-add feedback from Novell about this issue. James Melin wrote: Seems every major release adds function and makes things better or faster or

Re: Websphere Information Integrator

Just out of curiousity, how much effort is generally involved in porting an application such as this to z? Is it just a matter of building it from source on z and making sure everything works? (Not that even that is in any way a small efford.) Or are there generally code changes required as

Re: Cannot open root device, Kernel panic

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