On 05.11.2010 22:16, Mark Post wrote:
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of koray
Sent: Friday, November 05, 2010 9:24 AM
Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct
-snip-
- 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.
Did you have all your file systems mounted the same way as they are "normally"
and did you have /sys, /dev, and /proc bind mounted as well before doing the chroot?
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:
This is to be expected, and not at all weird. The naming of the devices is
going to depend on what order they are brought online by the kernel. In your
production initrd, that order is determined by /linuxrc. On the rescue system,
that order is not available (or you didn't use it. I forget how the rescue
system brings up DASD or if it is done manually.).
-snip-
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
I don't see an entry in there for /boot. To me that means you aren't using a
separate /boot file system, and your kernel and initrds are in the /boot
directory _on_the_root_filesystem_,
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"
-snip-
As you can see, it seems there is nothing wrong.But when i try to boot
from Minidisk100, i see;
See above. I suspect you should be IPLing from 102, not 100. Or, make sure
that /boot on 100 and /boot on 102 are synchronized and mkinitrd and zipl
re-run with them in the proper arrangement, as well as /etc/fstab being updated
to point /boot to 100 if that's what you really want.
Thanks Mark for your explanation, i noticed it with Eddie's mail. I dont
know how it changed, it's really weird. Now i need to change the default
boot minidisk from 100 to 102.
Regards
----------------------------------------------------------------------
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/
