Jim, If your system is back to where it was before, why can't you start your network and come in via SSH? Not that learning to use ed or sed isn't a good idea, but still...
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim Moling Sent: Thursday, January 25, 2007 11:17 AM To: [email protected] Subject: Re: Lost an LVM under SLES9 64-bit ... First, I'd like to say thanks for all of the great ideas/suggestions, and second, I'd like to apologize for not responding sooner. Also, just so everyone knows - I am working with a SLES9 SP3 based server. So, what I have figured out at this point is that I definitely did not make the LVM persistent via updating zipl.conf & doing a mkinitrd & zipl, and since I hadn't IPLed the server since creating the LVM, it was just waiting to "get me" - I guess I assumed to much from Yast as that is what I used to create the LVM. At this point I have been working with the "cippled" server to see what I could figure out & then accomplish based on everyone's feedback and so haven't taken the recovery system route yet ... Here's what I have been able to do so far: After bringing the 2 volumes online (chccwdev) and re-establishing the LVM (vgchange) and then mounting it (mount /pathname), it looks like I'm back to were I was before - the directories & data appear to be intact within the LVM space as well. -snip- ---------------------------------------------------------------------- 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
