Have a VM guest running SLES 11 - has been working fine for months - rebooted several times. Over the weekend there was a problem with the SAN switch and the guest lost it's paths to disk. Now when we try to boot the guest, we see the following.
Waiting for device /dev/sda3 to appear: ok fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda3 fsck.ext3: Device or resource busy while trying to open /dev/sda3 Filesystem mounted or opened exclusively by another program? fsck failed. Mounting root device read-only. Mounting root /dev/sda3 mount -o ro,acl,user_xattr -t ext3 /dev/sda3 /root mount: /dev/sda3 already mounted or /root busy could not mount root filesystem -- exiting to /bin/sh We've booted the guest in repair mode. I initially used the "Repair Installed System" tool to repair the file system and it came back clean. I then logged onto the system using ssh and manually mounted /dev/sda3 to /mnt and looked around - everything looks good. I umounted /mnt and manually ran "fsck -t ext3 /dev/sda3" again, it was clean. Still, when the system is booted, the above messages appear. Also, I've used both the /dev/sdax aliases and the /dev/disk/by-path/xxx full names in the fstab with the same result. inst-sys:/mnt/etc # cat fstab /dev/sda1 /boot ext3 acl,user_xattr 1 2 /dev/sda2 swap swap defaults 0 0 /dev/sda3 / ext3 acl,user_xattr 1 1 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701000000000000-part2 swap swap defaults 0 0 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701000000000000-part3 / ext3 acl,user_xattr 1 1 #/dev/disk/by-path/ccw-0.0.d000-zfcp-0x5006048ad52cea89:0x0701000000000000-part1 /boot ext3 acl,user_xattr 1 2 Looking for ideas on what to look at next. Thanks, Joe ---------------------------------------------------------------------- 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
