*** Reply to note of Tue, 01 Jun 2004 14:27:06 -0400 (EDT) *** by [EMAIL PROTECTED]
I have been able to recover them by IPLing a recovery system (a single minidisk system) and then running: vgexport, vgimport and then vgscan (you may need vgchange to inact/act, and vgmknodes if they are not on /dev). At other times I had to run /sbin/fsck.reiserfs or /sbin/fsck.ext2 to fix the filesystems before the mount. sal "Ferguson, Neale" <[EMAIL PROTECTED]> writes: >Well, this another fine mess I've got me in! > >I was updating the kernel and my system crashed. I was left with neither = >a valid /boot/image file nor initrd. No problem you say? Just boot the = >install disk? Good idea but my installed system uses lvm (not the root = >or boot devices but /usr etc.). Thus, while I can mount /dev/dasdxx = >/mnt/ etc and chroot. I cannot get the lvm devices up and running. = >lvscan etc. show that the devices are recognized but I can't get them = >mounted (at which point I can rerun mkinitrd etc. and recover). Ideas? > >Neale > >---------------------------------------------------------------------- >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
