If the system is up, and you're able to enter maintenance mode (by entering the root password), I would do a cat /proc/dasd/devices to see if, as Ed mentioned, your kernel "knows" about all your DASD.
If not, and a "#cp q dasd" command shows them, then there's a major disconnect between Linux and z/VM. In this case, I don't know if a "chccwdev -e devicenumber" command would help or not. If it does, then enable the second device, and then run "vgscan". If that works, then "vgchange -a y books" followed by a "mount -a" command. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim Moling Sent: Wednesday, January 24, 2007 9:49 AM To: [email protected] Subject: Lost an LVM under SLES9 64-bit ... -snip- fsck failed for at least one filesystem (not /). Please repair manually and reboot. So I am wondering if anybody has any ideas how this might have happened, and more importantly, how can I go about fixing this? Any help would be greatly appreciated. Jim Moling ---------------------------------------------------------------------- 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
