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 devices. At
that point, switch back to your ssh session and perform the recovery tasks
necessary, as described in Dominic's post.
This allows you a bit more flexibility, in that many programs will not work
well with a 3270 console.
(I saw the penguin in the original Marist EDU post, and couldn't resist
stealing it. Sorry.)
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OC-1-13 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Dominic Coulombe
Sent: Wednesday, July 05, 2006 8:30 AM
To: [email protected]
Subject: 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
distributions...
Just run the installation procedure from the beginning (punch some files,
ipl and so on), then when the startup script asks you to configure the
network, choose 0) no network.
You will be moved to a rescue console, logged in as root.
----------------------------------------------------------------------
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
