This sounds like some sort of bug/timing issue in SUSE's shutdown scripts. I suspect the vgchange command isn't being executed at the right time. Have you opened up a support request with Novell?
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wiggins, Mark Sent: Friday, February 18, 2005 3:59 PM To: [email protected] Subject: LVM volume group isn't available after a reboot We've got one test instance of SLES9 on z/VM 5.1 that has the following disk layout MDISK 200 3380 /dev/dasda1 /boot ext3 defaults MDISK 201 3380 /dev/dasdb1 / reiserfs acl,user_xattr MDISK 202 3380 /dev/dasdc1 /usr reiserfs acl,user_xattr MDISK 203 3380 /dev/dasdd1 swap swap pri=42 MDISK 204 3380 /dev/system/OPT /opt reiserfs defaults /dev/system/VAR /var reiserfs defaults /dev/system/SRV /srv reiserfs defaults You'll notice that the 204 disk is running LVM with opt, var and srv running on it. My question is that sometimes (and I mean about 80% of time), when you issue a reboot (either reboot or shutdown -r), the instance is unable to bring the LVM devices back up. If you shut it down all the way, it comes back fine, only rebooting has trouble. It's unable to find the volume group "system" and thus can't mount the lv's. Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 ---------------------------------------------------------------------- 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
