Hi Alvin, I had a chance to think over the problem, and it looks much closer to solution now. I had tried to mount the array on /home after boot, but the complaints suggested to me that the array didn't exist as far as the mounter was concerned. So I ran mdadm --assemble (with --scan, IIRC), left it to cook for ages, then did "mount -a". It was up and working. "df" showed /dev/md0 mounted, and a size in line with what I expected. Plus, the files that were in the 'home' directory on the root partition suddenly disappeared, as did my regular user's home directory! I assume that, having now assembled the array, I can activate it in future with "mdadm -As /dev/md0" - this is what http://www.linuxdevcenter.com/pub/a/linux/2002/12/05/RAID.html?page=2 suggests, although I've only skimmed it so far.
> that would than imply that you need to have mdadm assemble > your raid system, before the system boots ( fsck's your > systems ) > - you're missing the sniplet that assembles the raid5 system Yes, I see what you mean now. The problem that I see is that if I want to turn on the array before the fsck, I need to load the SATA drivers as well, and they seem to be loading long after the fsck. What would be the disadvantages of removing the fstab entry for /dev/md0, and creating a script to activate and mount the array after boot? I assume I could do this by messing around in the /etc/init.d files. I guess it's possible to load the SATA drivers earlier and assemble the array before fsck, which would be ideal, but I think I'd be a bit out of my depth. Thanks again for your help, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
