On Thursday February 8, [EMAIL PROTECTED] wrote: > I'm running an FC4 system. I was copying some files on to the server > this weekend, and the server locked up hard, and I had to power > off. I rebooted the server, and the array came up fine, but when I > tried to fsck the filesystem, fsck just locked up at about 40%. I > left it sitting there for 12 hours, hoping it was going to come > back, but I had to power off the server again. When I now reboot the > server, it is failing to mount my raid5 array.. > > mdadm: /dev/md0 assembled from 3 drives and 1 spare - not enough to > start the array.
mdadm -Af /dev/md0 should get it back for you. But you really want to find out why it died. Where there any kernel messages at the time of the first failure? What kernel version are you running? > > I've added the output from the various files/commands at the bottom... > I am a little confused at the output.. According to /dev/hd[cgh], > there is only 1 failed disk in the array, so why does it think that > there are 3 failed disks in the array? You need to look at the 'Event' count. md will look for the device with the highest event count and reject anything with an event count 2 or more less than that. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
