Re: SLES9, SP2 and zipl
Thanks again I ran mkinitrd and zipl and the system came up without a problem. I'll look into increasing /boot. Bob Bates -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Nix, Robert P. Sent: Monday, October 03, 2005 1:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9, SP2 and zipl We have support through IBM. The ETR was closed and has fallen off my radar, but the gist of the response was "make /boot bigger". They did say that they'd forward to Novell the fact that maintenance can fail without any error indication, but as the ETR was closed, we'll never know if this is addressed down the road... -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - "In theory, theory and practice are the same, but in practice, theory and practice are different." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, October 03, 2005 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9, SP2 and zipl On Monday, 10/03/2005 at 08:06 EST, "Nix, Robert P." <[EMAIL PROTECTED]> wrote: > Your initrd file is corrupted, possibly due to not having enough free space in > /boot while applying maintenance. We ran into this, and received the same error > message. Note that the install / maintenance process where the actual error > occurs produces no error messages or codes, and will happily say that initrd > was created successfully, even though the process failed miserably. If you haven't done so, I encourage you to open a bugzilla or report it to your Linux support provider. Alan Altmark z/VM Development IBM Endicott -- 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: SLES9, SP2 and zipl
We have support through IBM. The ETR was closed and has fallen off my radar, but the gist of the response was "make /boot bigger". They did say that they'd forward to Novell the fact that maintenance can fail without any error indication, but as the ETR was closed, we'll never know if this is addressed down the road... -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - "In theory, theory and practice are the same, but in practice, theory and practice are different." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, October 03, 2005 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9, SP2 and zipl On Monday, 10/03/2005 at 08:06 EST, "Nix, Robert P." <[EMAIL PROTECTED]> wrote: > Your initrd file is corrupted, possibly due to not having enough free space in > /boot while applying maintenance. We ran into this, and received the same error > message. Note that the install / maintenance process where the actual error > occurs produces no error messages or codes, and will happily say that initrd > was created successfully, even though the process failed miserably. If you haven't done so, I encourage you to open a bugzilla or report it to your Linux support provider. Alan Altmark z/VM Development IBM Endicott -- 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: SLES9, SP2 and zipl
On Monday, 10/03/2005 at 08:06 EST, "Nix, Robert P." <[EMAIL PROTECTED]> wrote: > Your initrd file is corrupted, possibly due to not having enough free space in > /boot while applying maintenance. We ran into this, and received the same error > message. Note that the install / maintenance process where the actual error > occurs produces no error messages or codes, and will happily say that initrd > was created successfully, even though the process failed miserably. If you haven't done so, I encourage you to open a bugzilla or report it to your Linux support provider. Alan Altmark z/VM Development IBM Endicott -- 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: SLES9, SP2 and zipl
Your initrd file is corrupted, possibly due to not having enough free space in /boot while applying maintenance. We ran into this, and received the same error message. Note that the install / maintenance process where the actual error occurs produces no error messages or codes, and will happily say that initrd was created successfully, even though the process failed miserably. If you can get a corrected initrd back on to /boot, you should be ok. At this point, being a pessimistic person, whenever I add maintenance that touches the kernel, I run mkinitrd and zipl afterward. -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - "In theory, theory and practice are the same, but in practice, theory and practice are different." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bates, Bob Sent: Friday, September 30, 2005 12:37 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES9, SP2 and zipl Hello all, I have a SLES9 31-bit image I installed a short while back un zVM. I am now trying to put the SP2 pack on it using YaST. After I finished I rebooted and it would not come up correctly, it appeared to be looking for a file in the previous kernel level name. Remembering discussions regarding mksles9root and zipl I thought to look for those. I can't find mksles9root but did locate zipl and the zipl.conf. When I ran zipl the system would not boot. Got this error: RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) VFS: Cannot open root device "dasda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop I am trying to figure out what I did wrong, and where I can find more information about zipl.conf. I see the options but not an explanation of things on the parameter = card. Any help? Thanks Bob Bates Citigroup Technology Infrastructure 916-374-5017 -- 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: SLES9, SP2 and zipl
What you're looking for is the mkinitrd command, not mksles9root. It looks as though the mkinitrd command died for some reason. Perhaps you ran out of space on your /boot file system: - - - - - RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) - - - - - I would use the starter kernel to re-IPL, point your root file system to your DASD and not an initrd (create a different kernel parmfile than the starter one), and check things out. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bates, Bob Sent: Friday, September 30, 2005 1:37 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES9, SP2 and zipl Hello all, I have a SLES9 31-bit image I installed a short while back un zVM. I am now trying to put the SP2 pack on it using YaST. After I finished I rebooted and it would not come up correctly, it appeared to be looking for a file in the previous kernel level name. Remembering discussions regarding mksles9root and zipl I thought to look for those. I can't find mksles9root but did locate zipl and the zipl.conf. When I ran zipl the system would not boot. Got this error: RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) VFS: Cannot open root device "dasda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop I am trying to figure out what I did wrong, and where I can find more information about zipl.conf. I see the options but not an explanation of things on the parameter = card. -- 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: SLES9, SP2 and zipl
On Sep 30, 2005, at 12:36 PM, Bates, Bob wrote: Any help? Try rerunning mkinitrd. 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
SLES9, SP2 and zipl
Hello all, I have a SLES9 31-bit image I installed a short while back un zVM. I am now trying to put the SP2 pack on it using YaST. After I finished I rebooted and it would not come up correctly, it appeared to be looking for a file in the previous kernel level name. Remembering discussions regarding mksles9root and zipl I thought to look for those. I can't find mksles9root but did locate zipl and the zipl.conf. When I ran zipl the system would not boot. Got this error: RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) VFS: Cannot open root device "dasda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop I am trying to figure out what I did wrong, and where I can find more information about zipl.conf. I see the options but not an explanation of things on the parameter = card. Any help? Thanks Bob Bates Citigroup Technology Infrastructure 916-374-5017 -- 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
