"Aaron D. Turner" wrote:
>Ok, how do you fsck a raid 1 partition? You know how after X reboots the
>system fsck's your partitions? Well it doesn't because they're raid1, and
>hence it complains. But I can't seem to figure out how to fsck them. I
>can't:
>
>raidstop /dev/md5
>umount /dev/md5
>fsck.ext2 /dev/md5
The manual operation you list above won't work, because you've just stopped
the raid device. You can't fsck an md device that isn't "running". You also
can't raidstop a devices thats mounted. Unmount your /dev/md5 partition
_then_ fsck it.
I guess that boot-time fsck being unable to run against the raid1 device might
be caused by the md device not being started when fsck runs through /etc/fstab
to check it. If you're using the kernel raid autostart doohickey (and a
wonderful doohickey it is) then this should already have been done.
If you're not using autostart, then check that (under RH52) the
/etc/rc/rc.sysinit script is checking for and running the correct raid command
(the "raidadd" included as part of the RH52 release has become "raidstart").
Failing that, post the relevant console messages you're getting.
E&OE,
-michael
--
St michael (mainly) Erroneous http://goliath.mersinet.co.uk/~ishamael/
"This message was brought to you by three Linux boxen, 768Mb RAM, 59Gb
disc space and one Oracle dba with no life. Expecting sense in such a
circumstance was woefully optimistic."
