Hello all,

I'm setting up a storage server running Suse 9.1 running (currently) three SATA 200 gig drives in RAID 5 for storage on a Promise SATA150 TX4 controller and a 10 gig PATA for boot/OS.

The problem is this: all went fine installing Suse, setting up the partitions for the RAIDed drives and starting RAID, however after a reboot Suse would not start completely, giving a message the fsck had failed and needed to be run manually. After some trial and error I found that deleting the RAID entry from /etc/fstab allowed Suse to start up normally without RAID. If I start RAID and mount the array manually it seems to work.

A work around would be to manually start RAID and mount the drives after a reboot, but Suse should be doing that. Is there a setup step I've missed?

I'm guessing that Suse is trying to do so a test on the RAID drive before software RAID actually starts and fails since there are no RAID drives present. If this is the case how can Suse be told not to check RAIDed drives?

Thanks...