Actually the swap devices were also defined in fstab as "by-path", so they worked okay. But the the LVM device is set as /dev/vg1/lv1 which is not being created, I assume because of the changed device order.
On Tue, Apr 7, 2009 at 12:57 PM, Mark Pace <[email protected]> wrote: > Well that fixed the problem of the device not coming online at IPL. But > now all the dasd labels have been changed. > 0200 was dasda now dasdc > 0201 was dasdb now dasdd > 0202 was dasdc now dasda > 0203 was dasdd now dasdb > > root dasd mounts fine because it is mounted "by-path", but the swap disk > were by /dev/dasdx1 and now obviously that is incorrect. Also the LVM > doesn't mount as 0203 is no longer /dev/dasdd1. > > What, now, determines the order? > > On Tue, Apr 7, 2009 at 11:01 AM, Bruce Hayden <[email protected]>wrote: > >> I think, in SLES 11, you either must use Yast to add disks, or to use >> the scripts supplied by Novell that Yast calls. The script to add >> dasd is dasd_configure, and if you run it without any arguments, it >> shows this help: >> Usage: /sbin/dasd_configure <ccwid> <online> <use_diag> >> For your use, you'd enter: dasd_configure 0.0.0203 1 0 >> This will create the needed udev rules so that the device will be >> placed online at boot time. I don't think I'd recommend copying or >> editing the rules files directly. By the way, the dasd_configure >> script also exists in SLES 10, but it created the hardware >> configuration files in /etc/sysconfig/hardware instead. >> >> On Tue, Apr 7, 2009 at 10:24 AM, Mark Pace <[email protected]> wrote: >> > Hmmmm - new stuff in SLES11 - >> > Found /etc/udev/rules.d >> > copied 51-dasd-0.0.0202.rules to 51-dasd-0.0.0203.rules and then edited >> the >> > file and changed all occurances of 202 to 203, reboot, now difference. >> > udev is not bringing 203 online at IPL. >> > >> > On Tue, Apr 7, 2009 at 9:16 AM, Mark Pace <[email protected]> wrote: >> > >> >> Working on a new SLES11 install. >> >> I added a new disk as an LVM volume. After I had the LV setup and >> working >> >> I did an >> >> mkinitrd >> >> zipl >> >> >> >> When I reboot it does not find the disk and stops. >> >> I can do >> >> chccwdev --online 0.0.0203 >> >> mount -a >> >> and the disk comes online and mounts fine. I added dasd=0200-021f >> to >> >> the zipl parameters, another mkinitd and zipl, but the disk still is >> not >> >> online at boot time. >> >> >> >> What have I forgotten to do? >> >> >> >> -- >> >> Mark Pace >> >> Mainline Information Systems >> >> 1700 Summit Lake Drive >> >> Tallahassee, FL. 32317 >> >> >> > >> > >> > >> > -- >> > Mark Pace >> > Mainline Information Systems >> > 1700 Summit Lake Drive >> > Tallahassee, FL. 32317 >> > >> > ---------------------------------------------------------------------- >> > 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 >> > >> >> >> >> -- >> Bruce Hayden >> Linux on System z Advanced Technical Support >> IBM, Endicott, NY >> >> ---------------------------------------------------------------------- >> 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 >> > > > > -- > Mark Pace > Mainline Information Systems > 1700 Summit Lake Drive > Tallahassee, FL. 32317 > -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 ---------------------------------------------------------------------- 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
