Paul Hampson wrote: > The issues arises when apt-install mdadm installs mdadm, > "mdadm --monitor" is run without debconf asking questions, > as it does if it's installed with apt-get install. In > particular, mdadm/start_daemon is skipped, and defaults to > "true". > Now that I've found the process being undertaken for this > menu option, I can either manually simulate it myself, or > try and stop mdadm starting mdadm --monitor... > > It looks to me like a change in mdadm caused this, in > particular 1.6.0-1's changelog lists: > * Changed default to autostart RAID array. > (closes: Bug#250792) Of course the bug there was that without this change, mdadm did not start when booting the installed system, so we didn't get raid at all then. Kinda damned if we do and damned if we don't. It sounds as if we need to arrange for mdadm to not be started when the installer is run, but do continue to let it be started afterwards. > My ideal preference would be for mdadm --monitor to not run > during the install, irrespective of whether the user wants it > when the system's running. But short of adding 'killall mdadm' > after apt-install mdadm in base-install's postinst, I dunno > how else to do that. Well, I think that would be a good quick fix. Note there's no killall in the installer, but you can probably instead add this: chroot /target /etc/init.d/mdadm stop If that works for you well enough we can look for a better fix.. such as applying the patch in bug #264451. -- see shy jo
Attachment:
signature.asc
Description: Digital signature