>>> On Tue, Apr 15, 2008 at 11:03 AM, in message <[EMAIL PROTECTED]>, "Kelly F. Hickel" <[EMAIL PROTECTED]> wrote: -snip- > That explains something, although fdasd doesn't think there are > partition tables either, I just tried again though, and I can still do a > "normal" load from DASD address D04D and it works right up to the point > where it panics after trying to activate the volume groups...
Right. The script on the ram disk is trying to get the real root file system ready, and when it can't the system dies. -snip- > Vgscan fails: > -/bin/sh-3.00# lvm > lvm> vgscan > Reading all physical volumes. This may take a while... > No volume groups found > lvm> I would say at this point that you are indeed out of luck. If pvscan and vgscan aren't finding any traces of the metadata that should be there, it's game over. Are these DASD volumes accessible from other LPARs? If so, it's entirely possible that some overzealous storage administrator reformatted them for you. Mark Post ---------------------------------------------------------------------- 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
