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?
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?[/QUOTE]
Have you looked what ‘tune2fs -l [dev name]’ returns? Curious in which filesystem state it is and what next check have been set.
A list of messages and errors during boot would be interesting to see.
Any chance this might be due to something else that happened prior to the reboot (like kernel reconfiguration / updates / etc…) and do LVM functions function normally?
No. I did reset the fstab to reflect 0 in the 6th field and have booted with option fastboot with no different results.
Strangely (I’ve never seen this before) the data LVMs are mounted as usual as are two of the local partition mounts.
The remaining partitions are mounted but show the file system as “-” in the first field of a df command such as df -h /var.
I would expect “/dev/sda5” in a normally mounted file system on that server.
I no longer trust this server OS and there is no longer any support.
I will recommend to upgrade to a supported version.
Which version of suse enterprise would anyone suggest to upgrade/install to if the app is currently running on 9.4?
Probably the wrong forum at this point so I apologize but it is a segway.