I have a production server which DBAs requested a sanity reboot (slow response).
When it rebooted it went to Root FSCK Prompt (all ext3).
On entry the local disk file systems were all mounted and the fs looked healthy but the lvm data drive was not ready.
I did an fsck -n on each of the partitions and it reported no corruption or problems.

I did an fsck on all partitions using a rescuecd without issues and I removed the data lvm from /etc/fstab

Every time it rebooted to single user prompt for root to fsck

I finally removed all but root file system after copying /usr /opt /var /home /oracle and /tmp to the / dir.

It booted

So. What is the problem?

Is this an mdsetup /dev/mapper issue or an ext3 suse issue?