Drove to Encinitas this morning to check on the server. it was sitting there waiting for someone to do something.
For reasons unknown, the machine had been power cycled and it was stuck part way through the boot process. Seems it had trouble with the superblock on one of the raid devices. and it was waiting for someone to run a manual check on the device.
After a bit of time -- while I was trying to remember anything about the raid tools on that old RedHat machine -- I finally go the system to reboot.
There was nothing wrong with the raid arrays. There was nothing wrong with any of the disks in the arrays. There was nothing wrong at all EXCEPT that the raidtab didn't have an entry for /dev/md2.
So, when the checks were made, md2 failed with a misleading error. Fix the raidtab and all is well.
Sigh.
For reasons unknown, the machine had been power cycled and it was stuck part way through the boot process. Seems it had trouble with the superblock on one of the raid devices. and it was waiting for someone to run a manual check on the device.
After a bit of time -- while I was trying to remember anything about the raid tools on that old RedHat machine -- I finally go the system to reboot.
There was nothing wrong with the raid arrays. There was nothing wrong with any of the disks in the arrays. There was nothing wrong at all EXCEPT that the raidtab didn't have an entry for /dev/md2.
So, when the checks were made, md2 failed with a misleading error. Fix the raidtab and all is well.
Sigh.