Hi again to all,
after doing lots of research i found the problem is somewhere in linux,
let me explain.
- I checked all dasds, there were no offline or unattached.
- No overlap in diskmap file.
- I compared direct user file with the old backup and i saw there is no
change with disk mappings.
- I did all similar checks on Z/VM side, no problems found.
- I ipled from SLES11 DVD and choosed boot installed system, it boots!
So i thought it's about ZIPL configuration but there was nothing wrong
there. I regenerated the bootmap again by running /sbin/zipl, and tried
to reipl from Minidisk100, but no luck.
Now lets see what's weird;
When i first installed SLES, the disk mapping was:
Minidisk100 - dasda - /boot
Minidisk101 - dasdb - swap
Minidisk102 - dasdc - /
Minidisk110 - dasdd - LVM Member
...
Minidisk209 - dasdn - LVM Member
But when i boot with cd, and activate the DASD's i see
Minidisk100 - dasda
Minidisk101 - _dasdn_
Minidisk102 - dasdb
Minidisk110 - dasdc
...
It seems the mapping has changed somehow. But when i run the installed
system from DVD menu, i see DASD's as they supposed to be:
linux101:~ # more /proc/dasd/devices
0.0.0100(ECKD) at ( 94: 0) is dasda
0.0.0101(ECKD) at ( 94: 4) is dasdb
0.0.0102(ECKD) at ( 94: 8) is dasdc
0.0.0110(ECKD) at ( 94: 12) is dasdd
0.0.0200(ECKD) at ( 94: 16) is dasde
0.0.0201(ECKD) at ( 94: 20) is dasdf
0.0.0202(ECKD) at ( 94: 24) is dasdg
0.0.0203(ECKD) at ( 94: 28) is dasdh
0.0.0204(ECKD) at ( 94: 32) is dasdi
0.0.0205(ECKD) at ( 94: 36) is dasdj
0.0.0206(ECKD) at ( 94: 40) is dasdk
0.0.0207(ECKD) at ( 94: 44) is dasdl
0.0.0208(ECKD) at ( 94: 48) is dasdm
0.0.0209(ECKD) at ( 94: 52) is dasdn
linux101:~ # more /etc/fstab
/dev/disk/by-path/ccw-0.0.0101-part1 swap swap
/dev/disk/by-path/ccw-0.0.0102-part1 / ext3
/dev/system/home /home
/dev/system/opt /opt
/dev/system/tmp /tmp
/dev/system/usr /usr
/dev/system/var /var
proc /proc
sysfs /sys
debugfs /sys/kernel/debug
devpts /dev/pts
linux101:~ # more /etc/zipl.conf
# Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010
[defaultboot]
defaultmenu = menu
###Don't change this comment - YaST2 identifier: Original name: linux###
[Linux]
image = /boot/image-2.6.27.19-5-default
target = /boot/zipl
ramdisk = /boot/initrd-2.6.27.19-5-default,0x2000000
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb"
:menu
default = 1
prompt = 1
target = /boot/zipl
timeout = 10
1 = Linux
2 = ipl
3 = Failsafe
###Don't change this comment - YaST2 identifier: Original name: ipl###
[ipl]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x2000000
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb"
###Don't change this comment - YaST2 identifier: Original name: failsafe###
[Failsafe]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x2000000
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb
x11failsafe"
As you can see, it seems there is nothing wrong.But when i try to boot
from Minidisk100, i see;
Mounting root _/dev/disk/by-path/ccw-0.0.0100-part1_
Unknown filesystem type 'LVM2_member'
Kernel panic - not syncing: Attemted to kill init!
HCPGIR450W ...
I re-run ZIPL but, no change, it still searches 0.0.0100 for root fs. I
think the reason is same with the first DASD activation menu with DVD.
Linux somehow sees diskmaps different and i cant change the ZIPL behaviour.
Now, i need to change ZIPL to mount root-fs from Minidisk102.
And then research why the Minidisk-Linux Dasd mapping is changing.
Sorry for the long mail and thanks for your patient.
Regards
On 05.11.2010 15:30, martin roby wrote:
I have seen this happen as well; when trying to boot from san disks.
Do you have your root filesystem on a san disk? Can you post your user
direct entry for a user that fails?
When you logged all the way out of your Linux guests you reset that
user. A lot of different things could have happened at that point.
Do any of your Linux guests still work? When they boot do they go
straight to the
CPU errors? I am assuming you don't get the zipl boot menu.
One thing to look for is an overlaps in your disk map.
{from maint}
diskmap user {generates a new disk map}
x user diskmap {opens the new map in the wonderful z/os editor}
{then search for overlaps}
{I usually use "right 10" first so I can see the "gap' messages"}
/over
If you have an overlap that would be the issue.
Otherwise either you are not finding your disk at boot or your zipl
boot was corrupted.
If you a working system you can move the disk to the new system and
try to mount it from the working Linux , if it mounts then you can try
to rewire the zipl boot block.
Martin
On Thu, Nov 4, 2010 at 3:31 PM, koray<nixst...@gmail.com> wrote:
Hello all,
We have 14 Sles Guests running on Z/VM 5.4. We edited the user direct
file and changed the memory settings of Linux guests.For example;
linux001 - 2048M 4096M
linux002 - 2048M 4096M
has changed to
linux001 - 3072M 6144M
linux002 - 1024M 2048M
Now, i cant ipl my guest's. When i try to ipl from minidisk 100,
linux 001 says:
HCPGIR453W CP Entered, program interrupt loop.
linux002 says:
HCPGIR450W CP entered, disabled wait PSW 00020001 80000000 00000000 001536B0
It seems disk mapping are broken but i'm totally sure that i only
changed Memory settings, not touched minidisk settings.
Need your help please.
Regards
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
