tags 310368 = moreinfo unreproducible severity 310368 important thanks Danny,
On Mon, May 23, 2005 at 10:03:09AM +0200, dth wrote: > running debian unstable apt-get dist-upgrade: > Setting up mdadm (1.9.0-2.3) ... > Installing new version of config file /etc/init.d/mdadm-raid ... > update-rc.d: /etc/init.d/mdadm-raid exists during rc.d purge (continuing) > Removing any system startup links for /etc/init.d/mdadm-raid ... > /etc/rc0.d/S50mdadm-raid > /etc/rc6.d/S50mdadm-raid > /etc/rcS.d/S04mdadm-raid > Starting raid devices: mdadm: failed to add /dev/sdb to /dev/md/0: Device or > resource busy > mdadm: failed to add /dev/sda to /dev/md/0: Device or resource busy > mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array. > mdadm: failed to add /dev/sdb to /dev/md/0: Device or resource busy > mdadm: failed to add /dev/sda to /dev/md/0: Device or resource busy > mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array. > done. > Starting RAID monitor daemon: mdadm -F. > After this action /etc/mdadm/ subdir was totally EMPTY > ergo: no mdadm.conf > I restored that manually using mdadm -E /dev/sda1 > Tried it on several other machines, same problems! I've verified that there is no code path in this package that would cause /etc/mdadm/mdadm.conf to be removed on upgrade, so I don't really see how this can be the package's fault. It could be the fault of some previous, broken version of mdadm that you had installed before this upgrade. Other than the missing /etc/mdadm/mdadm.conf file, did the installation of the package actually fail? -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
