> Bad news, unfortunately. > > [...] > mdadm -W --wait-clean --stop $md > > by > > mdadm --stop $md ; sleep 5 > > I don't have that in build 68, I have > > &FAI::push_command( "mdadm -W --stop $md", "$pre_deps_cl", > "self_cleared_$md"); > > which I edited to > > &FAI::push_command( "mdadm --stop $md ; sleep 5", "$pre_deps_cl", > "self_cleared_$md"); > > Which still failed. Format.log and mdadm-from-examine.conf tarred and > attached. >
Damn. May I ask you to further edit the very same line to &FAI::push_command( "mdadm -W --stop $md ; sleep 2 ; cat /proc/mdstat", "$pre_deps_cl", "self_cleared_$md"); i.e., add the wait, change the sleep to a smaller value (to speed things up), and print /proc/mdstat? I have absolutely no idea why the kernel claims some device is still busy, and even less so would I know how to figure out what is still trying to access the device. Many thanks for your help, Michael
pgpNhD8GowJCA.pgp
Description: PGP signature
