Everything except /boot is in the LVM. That's the way the install set it up and I didn't bother to change it. Next time I'll know better!
>>> [EMAIL PROTECTED] 6/22/2006 11:57 AM >>> From: Richard Pinion <[EMAIL PROTECTED]> > I am running Centos 4.3 under Hercules, kernel 2.6.9. I recompiled the > kernel source and installed it. I forgot to do the zipl command. Now my > image fails during boot. Luckily I backed up the Hercules disk images before > any of my changes. I have re-ipled using the good images. I would like to > mount the corrupted disks and run zipl. I've attached the bad dasd images > and varied the new devices addresses online. My problem is the corrupted > disk images belong to a logical volume group. I'm not sure how to build > another lv group with the existing dasd images with a new lv group name. The > good lv group names is /dev/VolGroup00. I've done a pvscan and lvscan and > the newly attached devices are showing up. But again, how do I form the new > vg???? Richard, is the root FS really in the LVM you talk about? I.e you have the whole zLinux in LVM? Assuming not, i.e. you have "/", "/boot", "/etc" in a non LVM FS, then you can forget the LVM disks, attach the disk with the root FS and mount the root FS on /mnt. Then run command chroot /mnt zipl I'm doing this from my head, so can someone confirm :-) Mark ---------------------------------------------------------------------- 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
