I think you were supposed to remove the dasd= - not the root= Scott Rohling
On Wed, Aug 15, 2012 at 7:16 AM, Dean, David (I/S) <[email protected]>wrote: > Mark, here you go. > > Original zipl.conf > > [ipl] > image = /boot/image > target = /boot/zipl > ramdisk = /boot/initrd,0x4000000 > parameters = "root=/dev/dasda1 dasd=202,700-730 TERM=dumb" > > run zipl > > Server comes up fine. > > Now: > > CHANGE zipl.conf to remove parameter root=/dev/dasda1 and run zipl > > Now I get this during boot > > dasd(eckd): 0.0.0202: 3390/0C(CU:3990/01) Cyl:8016 Head:15 Sec:224 > dasd(eckd): 0.0.0202: (4kB blks): 5771520kB at 48kB/trk compatible disk > layout > dasda:VOL1/ 0X0202: dasda1 > Loading dasd_fba_mod > Loading jbd > Loading ext3 > Waiting for device /dev/dasdb1 to appear: > ..............................not fou > d -- exiting to /bin/sh > > > > > > > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Mark Post > Sent: Tuesday, August 14, 2012 4:28 PM > To: [email protected] > Subject: Re: zipl > > >>> On 8/14/2012 at 03:59 PM, "Dean, David (I/S)" <[email protected]> > wrote: > > We have gotten in to trouble twice now with zipl.conf. We are on > > 10.3, upgrading to 10.4 then to 11.2. We have removed DASD in the > > past - USER DIRECTORY - and when we boot again without running zipl we > > get problems with it trying to load the old DASD def. I do not have, > > I recently discovered, an adequate knowledge of zipl - working on > > that - but if anyone has directions to a good explanation (I like > > flow charts.) > > > > Now the real question. A friend asked the question, "why not run zipl > > at boot?" and I said "hmmmmmm". > > > > Good? Bad? Ugly? > > I don't understand what is meant by running "zipl at boot," but I don't > think that matters much. There is no reason to update /etc/zipl.conf at > all when adding/removing DASD on SLES10 or SLES11 systems. Just don't do > it. In fact, I would recommend removing any "dasd=" parameters from > zipl.conf and then rebuilding your initrd and re-running zipl. To test > that out > - Duplicate one of your menu entries in zipl.conf > - Rename the menu entry to something unique > - Add the new menu entry to the :menu list > - Remove the "dasd=" list from the "parameters-" line > - Re-run mkinitrd and zipl > - Reboot and select the new menu entry. > > If things work as expected, do it for the rest of your menu entries. If > not, come back here with details. > > > 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 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit http://wiki.linuxvm.org/ > ----------------------------------------------------- > Please see the following link for the BlueCross BlueShield of Tennessee > E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm > > ---------------------------------------------------------------------- > 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/
