Re: Buggered up zipl.conf file
To all those who replied to my distress call on Friday... Thank You, Thank You, Thank You. I went to section 12.4.2 Entering a rescue environment as described by Mike MacIsaac, then followed the suggestions from Robert Nix and I was able to successfully execute mkinitrd and zipl after updating (correctly this time around) zipl.conf. What a learing experience this has been. Thanks again. David Rakoczy Operating Systems Programmer Thermo Fisher Scientific "He who laughs last probably made a backup." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Friday, August 29, 2008 3:07 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Buggered up zipl.conf file Boot up your install system, and define the network. Get things up to the point that ssh is started. Then log in via ssh, mount your real Linux system's filesystem and once everything is in place beneath this mount point, do a chroot to the mountpoint. Then edit your zipl.conf file, and re-run mkinitrd and zipl. Shutdown and try to boot again. My assumption here is that this is your first linux image. If you have others, you could attach the necessary disks to a running image, mount them and chroot to there. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 8/29/08 1:51 PM, "Rakoczy, Dave" <[EMAIL PROTECTED]> wrote: > > All, > > Being a zLinux Newbie I'm following Chapter 7. (installing and > configuring SLES10) in the 'z/VM and Linux on IBM System z The > Virtualization Cookbook' > > Step 7.5.13 identifies modifications to make to the zipl.conf file. > > Well... Here's where the problem lies... I fat fingered the parameter > line and went ahead and executed the zipl command. Now when I try to > IPL I get the following message. > > Waiting for device /dev/dasd1 to appear: > ..not found > -- exiting to /bin/sh > > $ > > > The device I should be looking for is /dev/dasda1not > /dev/dasd1. > > Can anyone offer any insight on how I can save this install without > starting all over again? > > This is just a sandbox system I'm playing with for the time being, I > was hoping this was going to become my "Gold" system eventually. > > Thanks in advance for any assistance. > > And yes... I do have a backup of the zipl.conf file, I just have no > idea on how to restore it and re-run the zipl command without the > actual system. > > David Rakoczy > Operating Systems Programmer > Thermo Fisher Scientific > > "He who laughs last probably made a backup." > > > > -- > 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 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 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
Re: Buggered up zipl.conf file
If you have another zLinux guest running, you can link the disk from the DOA image and repair your zipl.conf, chroot and run zipl. "Rakoczy, Dave" <[EMAIL PROTECTED]> wrote: All, Being a zLinux Newbie I'm following Chapter 7. (installing and configuring SLES10) in the 'z/VM and Linux on IBM System z The Virtualization Cookbook' Step 7.5.13 identifies modifications to make to the zipl.conf file. Well... Here's where the problem lies... I fat fingered the parameter line and went ahead and executed the zipl command. Now when I try to IPL I get the following message. Waiting for device /dev/dasd1 to appear: ..not found -- exiting to /bin/sh $ The device I should be looking for is /dev/dasda1not /dev/dasd1. Can anyone offer any insight on how I can save this install without starting all over again? This is just a sandbox system I'm playing with for the time being, I was hoping this was going to become my "Gold" system eventually. Thanks in advance for any assistance. And yes... I do have a backup of the zipl.conf file, I just have no idea on how to restore it and re-run the zipl command without the actual system. David Rakoczy Operating Systems Programmer Thermo Fisher Scientific "He who laughs last probably made a backup." -- 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 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
Re: Buggered up zipl.conf file
Boot up your install system, and define the network. Get things up to the point that ssh is started. Then log in via ssh, mount your real Linux system's filesystem and once everything is in place beneath this mount point, do a chroot to the mountpoint. Then edit your zipl.conf file, and re-run mkinitrd and zipl. Shutdown and try to boot again. My assumption here is that this is your first linux image. If you have others, you could attach the necessary disks to a running image, mount them and chroot to there. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 8/29/08 1:51 PM, "Rakoczy, Dave" <[EMAIL PROTECTED]> wrote: > > All, > > Being a zLinux Newbie I'm following Chapter 7. (installing and > configuring SLES10) in the 'z/VM and Linux on IBM System z The > Virtualization Cookbook' > > Step 7.5.13 identifies modifications to make to the zipl.conf file. > > Well... Here's where the problem lies... I fat fingered the parameter > line and went ahead and executed the zipl command. Now when I try to > IPL I get the following message. > > Waiting for device /dev/dasd1 to appear: > ..not found > -- exiting to /bin/sh > > $ > > > The device I should be looking for is /dev/dasda1not > /dev/dasd1. > > Can anyone offer any insight on how I can save this install without > starting all over again? > > This is just a sandbox system I'm playing with for the time being, I was > hoping this was going to become my "Gold" system eventually. > > Thanks in advance for any assistance. > > And yes... I do have a backup of the zipl.conf file, I just have no idea > on how to restore it and re-run the zipl command without the actual > system. > > David Rakoczy > Operating Systems Programmer > Thermo Fisher Scientific > > "He who laughs last probably made a backup." > > > > -- > 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 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
Re: Buggered up zipl.conf file
Dave, See section 12.4 - Rescuing a Linux system. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 -- 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
Re: Buggered up zipl.conf file
On Aug 29, 2008, at 11:51 AM, Rakoczy, Dave wrote: Can anyone offer any insight on how I can save this install without starting all over again? Boot from a rescue system, chroot to the new disk, edit, run zipl. Adam -- 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
Buggered up zipl.conf file
All, Being a zLinux Newbie I'm following Chapter 7. (installing and configuring SLES10) in the 'z/VM and Linux on IBM System z The Virtualization Cookbook' Step 7.5.13 identifies modifications to make to the zipl.conf file. Well... Here's where the problem lies... I fat fingered the parameter line and went ahead and executed the zipl command. Now when I try to IPL I get the following message. Waiting for device /dev/dasd1 to appear: ..not found -- exiting to /bin/sh $ The device I should be looking for is /dev/dasda1not /dev/dasd1. Can anyone offer any insight on how I can save this install without starting all over again? This is just a sandbox system I'm playing with for the time being, I was hoping this was going to become my "Gold" system eventually. Thanks in advance for any assistance. And yes... I do have a backup of the zipl.conf file, I just have no idea on how to restore it and re-run the zipl command without the actual system. David Rakoczy Operating Systems Programmer Thermo Fisher Scientific "He who laughs last probably made a backup." -- 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
