On Thursday July 7, molle.bestefich@xxxxxxxxx wrote: > Mitchell Laks wrote: > > However I think that raids should boot as long as they are intact, as a matter > > of policy. Otherwise we lose our ability to rely upon them for remote > > servers... > > It does seem wrong that a RAID 5 starts OK with a disk missing, but a > RAID 1 fails. > > Perhaps MD is unable to tell which disk in the RAID 1 is the freshest > and therefore refuses to assemble any RAID 1's with disks missing? This doesn't sound right at all. "--run" is required to start a degraded array as a way of confirming to mdadm that you really have listed all the drives available. The normal way of starting an array at boot time is by describing the array (usually by UUID) in mdadm.conf and letting mdadm find the component devices with "mdadm --assemble --scan". This usage does not require --run. The only time there is a real reluctance to start a degraded array is when it is raid5/6 and it suffered an unclean shutdown. A dirty, degraded raid5/6 can have undetectably data corruption, and I really want you to be aware of that and not just assume that "because it started, the data must be OK". NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
