>>> On 11/16/2015 at 12:23 PM, Michael Weiner <[email protected]> >>> wrote: > Hi Dan > > I don't seem to have a zipl.conf when I am running in recovery mode.
Of course not, you don't have any DASD volumes activated so nothing is mounted. If, as Dan suggested, you don't have an old kernel entry to select, then you'll need to be a little more inventive. If this is a z/VM guest, you can try doing an "ipl #### parm dasd=0.0.1234,0.0.1235,0.0.1236" and so on. That _might_ override the parms that have been written to disk with zipl. If not, then you'll need to either: 1. Boot from the installation media and use that to recover. 2. Attach the DASD to another z/VM guest and use that to fix things. 3. When in recovery mode, activate all the DASD that should be activated and then try "systemctl default" (E.g., echo 1 > /sys/bus/ccw/devices/0.0.1234/online ) There are probably other ways to get around this if one of those doesn't work. Due to my own internal testing of things, I'm on the verge of creating a rescue system comprised of an NSS and xip2fs file system in a DCSS. I get tired of doing this over and over again. 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/
