OK Here's zipl,conf:
wasi01:/ # cat /etc/zipl.conf
# Modified by YaST2. Last modification on Fri Mar 20 12:25:03 EDT 2009
[defaultboot]
defaultmenu = menu
###Don't change this comment - YaST2 identifier: Original name: linux###
[SLES_10_SP1]
image = /boot/image-2.6.16.54-0.2.12-default
target = /boot/zipl
ramdisk = /boot/initrd-2.6.16.54-0.2.12-default,0x1000000
parameters = "root=/dev/dasdc1 TERM=dumb"
[SLES_10_SP1_2]
image = /boot/image-2.6.16.54-0.2.5-default
target = /boot/zipl
ramdisk = /boot/initrd-2.6.16.54-0.2.5-default,0x1000000
parameters = "root=/dev/dasdc1 TERM=dumb"
:menu
default = 1
prompt = 1
target = /boot/zipl
timeout = 10
1 = SLES_10_SP1
2 = SLES_10_SP1_2
3 = ipl
###Don't change this comment - YaST2 identifier: Original name: ipl###
[ipl]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x1000000
parameters = "root=/dev/dasdc1 TERM=dumb"
lsdasd shows /dev/dasdc1 to be unit 200.
VM Directory shows 200 to be a dedicated DASD device.
Any ideas why something would fail to initialize? Is it a timing thing?
From: Pat Carroll <[email protected]>
To: [email protected]
Date: 06/29/2010 10:19 AM
Subject: Re: PSW 000A0000 00000100
Sent by: Linux on 390 Port <[email protected]>
Looks OK...take a look at zipl.conf...the wait state 100 is a device
failing initialization (see s390-tools)
Patrick Carroll | Technology Architect II
L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033
http://www.llbean.com | [email protected] | 207.552.2426
CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain
confidential information that is legally privileged. The information is
solely for the use of the intended recipient(s). Any disclosure,
copying, distribution, or other use of this information is strictly
prohibited. If you have received this e-mail in error, please notify the
sender by return e-mail and delete this message.
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Tuesday, June 29, 2010 9:59 AM
To: [email protected]
Subject: Re: PSW 000A0000 00000100
Here's what's in /boot.
wasi01:~ # ls -l /boot
total 25160
-rw-r--r-- 1 root root 218072 Nov 3 2008
Kerntypes-2.6.16.54-0.2.12-default
-rw-r--r-- 1 root root 218048 Jan 24 2008
Kerntypes-2.6.16.54-0.2.5-default
-rw-r--r-- 1 root root 652908 Nov 3 2008
System.map-2.6.16.54-0.2.12-default
-rw-r--r-- 1 root root 644457 Jan 24 2008
System.map-2.6.16.54-0.2.5-default
-rw-r--r-- 1 root root 20126 Nov 3 2008
config-2.6.16.54-0.2.12-default
-rw-r--r-- 1 root root 20102 Jan 24 2008
config-2.6.16.54-0.2.5-default
lrwxrwxrwx 1 root root 30 Mar 20 2009 image ->
image-2.6.16.54-0.2.12-default
-rwxr-xr-x 1 root root 7130696 Nov 3 2008
image-2.6.16.54-0.2.12-default -rwxr-xr-x 1 root root 6072136 Jan 24
2008 image-2.6.16.54-0.2.5-default
lrwxrwxrwx 1 root root 31 Mar 20 2009 initrd ->
initrd-2.6.16.54-0.2.12-default
-rw-r--r-- 1 root root 3047312 Mar 20 2009
initrd-2.6.16.54-0.2.12-default
-rw-r--r-- 1 root root 3045519 Jun 27 2008
initrd-2.6.16.54-0.2.5-default
-rw-r--r-- 1 root root 60223 Nov 3 2008
symsets-2.6.16.54-0.2.12-default.tar.gz
-rw-r--r-- 1 root root 56149 Jan 24 2008
symsets-2.6.16.54-0.2.5-default.tar.gz
-rw-r--r-- 1 root root 164297 Nov 3 2008
symtypes-2.6.16.54-0.2.12-default.gz
-rw-r--r-- 1 root root 164284 Jan 24 2008
symtypes-2.6.16.54-0.2.5-default.gz
-rw-r--r-- 1 root root 46840 Nov 3 2008
symvers-2.6.16.54-0.2.12-default.gz
-rw-r--r-- 1 root root 46904 Jan 24 2008
symvers-2.6.16.54-0.2.5-default.gz
-rwxr-xr-x 1 root root 2039224 Nov 3 2008
vmlinux-2.6.16.54-0.2.12-default.gz
-rwxr-xr-x 1 root root 2004734 Jan 24 2008
vmlinux-2.6.16.54-0.2.5-default.gz
drwxr-xr-x 2 root root 4096 Mar 20 2009 zipl
wasi01:~ #
When I found it down, all I did was log into the guest machine and issue
an "IPL 200" which z/Linux ipled as if there was nothing wrong.
From: Pat Carroll <[email protected]>
To: [email protected]
Date: 06/29/2010 09:56 AM
Subject: Re: PSW 000A0000 00000100
Sent by: Linux on 390 Port <[email protected]>
What's in /boot?
Patrick Carroll | Technology Architect II L.L.Bean, Inc.(r) | Double
L St. | Freeport ME 04033 http://www.llbean.com | [email protected] |
207.552.2426
CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain
confidential information that is legally privileged. The information is
solely for the use of the intended recipient(s). Any disclosure,
copying, distribution, or other use of this information is strictly
prohibited. If you have received this e-mail in error, please notify the
sender by return e-mail and delete this message.
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Tuesday, June 29, 2010 9:39 AM
To: [email protected]
Subject: PSW 000A0000 00000100
Got a call from one of our operators over the weekend. Apparently
one
of our linux machines failed to start.
Posted this on the IBMVM list but figured I'd post this here as it
involves IPLing z/Linux.
So, looking at the log, I see the guest machine went into a disabled
wait state.
00: zIPL v1.6.0 interactive boot menu
00:
00: 0. default (SLES_10_SP1)
00:
00: 1. SLES_10_SP1
00: 2. SLES_10_SP1_2
00: 3. ipl
00:
00: Note: VM users please use '#cp vi vmsg <number> <kernel-parameters>'
00:
00: Please choose (default will boot in 10 seconds):
00: Booting default (SLES_10_SP1)...
00: HCPGIR450W CP entered; disabled wait PSW 000A0000 00000100
I've been able to IPL the guest machine into Linux with no issues.
Nothing
I know of has been changed. I'm seeing a lot of messages related to
the
000A0000 but none for 00000100. What's going on? Is the linux guest
somehow getting corrupted? Do I need to run a zipl to rebuild the boot
record information?
We're running SLES10 under z/VM 5.3
Thanks
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
