Thank you Mark, I had actually headed down this path as you explained
below just before I got this E-mail. The idea or thought came to me based
on my Gentoo Linux background. Anyhow, thank you for your help and so
everyone knows this procedure did fix the problem.
Thank you!
Eric Sammons
(804)697-3925
FRIT - Infrastructure Engineering
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/08/2003 03:27 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Urgent, receiving panic on my guest
In that case, it sounds like you re-ran zipl, but the contents of
/etc/zipl.conf are bad.
Re-IPL your system from the reader, using the three starter files. Do:
insmod dasd dasd=addr1,addr2,addr3
mount /dev/dasda1 /mnt
chroot /mnt
cd /etc
cat zipl.conf
Does the "parameters=" value specify all the disks you want? Does it
specify the correct "root=" value? If not, start the installation
process,
but when you telnet/ssh in, do this:
chroot /mnt
vi /etc/zipl.conf
zipl
exit
During the vi editing session, make sure the parms are correct. When you
reboot your system, make sure the parameters are reflected in the messages
put out by the system.
Mark Post
-----Original Message-----
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 3:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Urgent, receiving panic on my guest
How would one fix this if it was working prior to the addition of a new
disk?
Eric Sammons
(804)697-3925
FRIT - Infrastructure Engineering
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/08/2003 02:39 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Urgent, receiving panic on my guest
It looks like you punched an install kernel to the virtual reader, but not
the initrd. Device "01:00" is a ram disk.
Mark Post
-----Original Message-----
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 2:31 PM
To: [EMAIL PROTECTED]
Subject: Urgent, receiving panic on my guest
Importance: High
Anyone seen this error before? If so how do you resolve it?
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Cannot open root device "" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00
HCPGIR450W CP entered; disabled wait PSW 000A0000 802A04F0
Thanks!
Eric Sammons
(804)697-3925
FRIT - Infrastructure Engineering
