Hi all, For those who've not yet seen this yet, Neil Brown has reported a nasty bug in the MD software RAID driver introduced into 3.4-rc1 and fixed in 3.4-rc5, but unfortunately the bad commit was copied to the stable@ address and so got backported into the 3.2.14 release (and fixed in 3.2.17) and the 3.3.1 release (fixed in 3.3.4). http://neil.brown.name/blog/20120615073245 # The bug will only fire if, while the machine is shutting down, # and array is partially assembled but not yet started. If the # array is started and running it is safe ... as long as it stays # that way. # # The typical way that an array can get into this "partially # assembled by not started" start is for "mdadm --incremental" # to have been run on some, but not all, of the devices in the # array. If it had been run on all it would have started the # array, but until then it is assembled but not started and this # is the dangerous situation. It won't toast your data, but will toast the MD metadata and break your array. Your best way to recover is to have an already existing copy of the output of "mdadm -Evvvvs" for your arrays. See Neils blog for more info. cheers, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC