nate wrote:

Found the root issue here I believe in /etc/rc.sysinit

if [ "${RHGB_STARTED}" != "0" -a -w /etc/rhgb/temp/rhgb-console ]; then fsck -T -t noopts=_netdev -A $fsckoptions >

After changing _netdev above to "noauto" the system boots normally. I'm not sure if I could specify noopts=_netdev,noauto or what the syntax is, can't find that syntax in the docs.

Before:

device-mapper: create ioctl failed: Device or resource busy Setting up Logical Volume Management: Volume group "san-p-mysql001a-db" is exported Volume group "san-p-mysql001a-log" is exported [FAILED] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda3 /1: clean, 80554/59834368 files, 2441697/59807986 blocks [/sbin/fsck.ext3 (1) -- /san/MrT/mysql/db] fsck.ext3 -a /dev/san-p-mysql001a-log/san-p-mysql001a-log fsck.ext3: No such file or directory while trying to open /dev/san-p-mysql001a-log/san-p-mysql001a-log /dev/san-p-mysql001a-log/san-p-mysql001a-log: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>

[/sbin/fsck.ext3 (1) -- /san/MrT/mysql/log] fsck.ext3 -a /dev/san-p-mysql001a-db/san-p-mysql001a-db fsck.ext3: No such file or directory while trying to open /dev/san-p-mysql001a-db/san-p-mysql001a-db /dev/san-p-mysql001a-db/san-p-mysql001a-db: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>

[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/sda1 /boot: clean, 35/26104 files, 17544/104388 blocks [FAILED]

*** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue):

after:

Setting up Logical Volume Management: Volume group "san-p-mysql001a-db" is exported Volume group "san-p-mysql001a-log" is exported [FAILED] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda3 /1: clean, 80554/59834368 files, 2441697/59807986 blocks [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/sda1 /boot: clean, 35/26104 files, 17544/104388 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] [..] Starting mount_san: Scanning and activating SAN-based volume groups PV /dev/dm-3 is in exported VG san-p-mysql001a-db [2.00 TB / 1.51 TB free] PV /dev/dm-2 is in exported VG san-p-mysql001a-log [1023.99 GB / 973.99 GB free] Total: 2 [3.00 TB] / in use: 2 [3.00 TB] / in no VG: 0 [0 ] Volume group "san-p-mysql001a-db" successfully imported Volume group "san-p-mysql001a-log" successfully imported Checking LVM SAN filesystems.. e2fsck 1.39 (29-May-2006) /dev/san-p-mysql001a-db/san-p-mysql001a-db: clean, 11/128000 files, 63258/131072000 blocks e2fsck 1.39 (29-May-2006) /dev/san-p-mysql001a-log/san-p-mysql001a-log: clean, 11/12800 files, 22733/13107200 blocks Finished checking LVM SAN filesystems.. Scanning and mounting multipathed filesystems.....[/san/MrT/mysql/db]....[/san/MrT/mysql/log]..done! [ OK ]

So will file a bug with RH I suppose to get them to tweak that so that "noauto" behaves as expected.

nate