>>> On 3/29/2010 at 09:29 AM, Christian Paro <[email protected]> wrote: > I believe that for SLES 11 zipl.conf is no longer used to determine which > dasd to online at boot. Instead, however, you can run `dasd_configure > 0.0.0210 1` before you run mkinitrd and zipl, and the specified disk should > be set online and come back online on subsequent boots.
I would be more accurate to say that /etc/zipl.conf is not the _sole_ way to define which DASD volumes come online at boot time. The parameters there are used if they exist, but YaST uses a different method when setting this up. This is true for SLES10 as well as SLES11. If a DASD volume is needed to mount the root file system (whether a single partition or an LVM LV spanning many DASD volumes), the main startup script in the initrd gets dasd_configure commands added for each one of them. For any DASD volumes that are unrelated to the root file system, the only thing that gets looked at is (for SLES10) /etc/sysconfig/hardware/hwcfg-dasd-*, and (for SLES11) /etc/udev/rules.d/51-dasd-*. The thing about the dasd_configure command is that it will create those files for you, whether in /etc/sysconfig/hardware, or /etc/udev/rules.d/, depending on what version of the distribution you're running. So, the easiest way to add a volume to your system via the command line is: dasd_configure busid online diag/notdiag dasdfmt fdasd if ECKD and not FBA mkinitrd zipl Mark Post ---------------------------------------------------------------------- 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
