On Tuesday 11 October 2005 04:40 pm, Guy Rouillier wrote: > However, when I reboot, I get a message that the superblock is > corrupted. If I drop into repair mode and comment out the line in > /etc/fstab, I can boot. Then I have to start the RAID creation all over > again. > > What step am I missing? I found a post just like this one in the > archives, but no solution was ever provided. Thanks for any pointers.
Please keep in mind that it is extremely hard to troubleshoot something that you don't have in front of you to try out and I don't have your setup in front of me. My guess would be that going through the process of creating the raid setup with diskdrake is causing a kernel module to be loaded that, upon reboot, is no longer present in your setup. And that causes the raid device to fail at mount. So, my suggestion would be to restart the computer and then get a listing of all modules "lsmod" that you have loaded. Then, go through the process of creating the raid mount point and at the point that you have it loaded and working, you should do another lsmod and check for any new modules that have been loaded. Make sure that module is set to start on boot. You may also want to check the chkconfig list "chkconfig --list" to see if you have any new startup packages that are not set to start on boot. I am thinking of something along the lines of an evm virtual disk manager tools, or mdtools which may be started by diskdrake but may not be set to start automatically even though it is needed for raid support. That may also be responsible for losing the raid device on reboot.
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
