Hi List,<br><br>A few weeks ago I created a Raid 5 set for my data partition using mdadm.<br><br>This works fine, but last week a short power outage caused the server to reboot.<br><br>When I came home the server was in need of maintainance because it couldn't check all his filesystems. <br><br>Strange fact was that the md device wasn't start...<br>mdadm --assemble /dev/md1 works fine, the /etc/mdadm.conf is read the the raid device is started...<br><br>But why doesn't start it at boot?<br><br>A piece of output from dmesg: <br><br><pre>md: Autodetecting RAID arrays.<br>md: autorun ...<br>md: considering hdb1 ...<br>md: adding hdb1 ...<br>md: created md1<br>md: bind<hdb1><br>md: running: <hdb1><br>raid5: device hdb1 operational as raid disk 0 <br>raid5: not enough operational devices for md1 (2/3 failed)<br>RAID5 conf printout:<br> --- rd:3 wd:1 fd:2<br> disk 0, o:1, dev:hdb1<br>raid5: failed to run raid set md1<br>md: pers->run() failed ...<br>md: do_md_run() returned -5 <br>md: md1 stopped.<br>md: unbind<hdb1><br>md: export_rdev(hdb1)<br>md: ... autorun DONE.</pre>It tell's me that 2/3 devices failed, but after I assemble it.. the ouput of mdadm --detail /dev/md1 is:<br><br><font size="1"> /dev/md1:<br> Version : 00.90.03<br> Creation Time : Fri Sep 22 22:28:43 2006<br> Raid Level : raid5<br> Array Size : 625137152 (596.18 GiB 640.14 GB)<br> Device Size : 312568576 (298.09 GiB 320.07 GB)<br> Raid Devices : 3<br> Total Devices : 3<br>Preferred Minor : 1<br> Persistence : Superblock is persistent<br><br> Intent Bitmap : Internal<br><br> Update Time : Wed Nov 15 10:56:36 2006<br> State : active <br> Active Devices : 3<br>Working Devices : 3<br> Failed Devices : 0<br> Spare Devices : 0<br><br> Layout : left-symmetric<br> Chunk Size : 64K<br><br> UUID : 82544aad:a2e92ea2:72ca2d55:716dada0<br> Events : 0.1486768<br><br> Number Major Minor RaidDevice State<br> 0 3 65 0 active sync /dev/hdb1<br> 1 22 1 1 active sync /dev/hdc1<br> 2 22 65 2 active sync /dev/hdd1 <br></font><br>No failed devices!<br><br>How it this possible?<br>I rebooted aferwards, but still the same issue! :-(<br><br>Anybody any clue's?!<br>Any help is appriciated....<br><br>-- <br>Met vriendelijke groet / With kind regards, <br><br>H. van Wees<br>---<br>If UNIX isn't the solution, you've got the wrong problem.