tags 385017 confirmed thanks also sprach Paul Slootman <[EMAIL PROTECTED]> [2006.08.28.1655 +0200]: > Firstly, it's not clear where I specified this... I now see (upon manual > inspection of the debconf-show output, which reportbug somehow failed to > obtain) that I at some point apparently had entered it (I can't recall > this, BTW). Here's the debconf-show output: > > $ debconf-show mdadm > debconf: DbDriver "passwords" warning: could not open > /var/cache/debconf/passwords.dat: Permission denied > * mdadm/autostart: false > mdadm/autocheck: true > * mdadm/warning: > mdadm/mail_to: root > mdadm/initrdstart: /dev/md3
without the asterisk, this means you did not actually see the question due to your debconf priority. Aye. My fault. > Perhaps the /proc/cmdline info could be queried? Mine contains: > root=/dev/md3 ro vga=6 > No hint of an initrd there. > > Additionally the further output is a bit confusing: > > W: unable to determine MD arrays needed for boot. > W: falling back to starting all of them... This is something I can definitely address by differentiating between the when the user chooses to ignore the fact that the array cannot be found in the config, and the system running in such a way that it just simply failed. Anyway, the problem is not as easy as it may sound as I have no reliable way to find out whether no initrds are being used. In case there is one used, I have to prepare for it. Do you think that it would be enough if I added a statement to the question of whether it's okay to go on even though the array is not listed in the configuration file if kernel autostart is being used? Other than that, I don't really know what to do, especially since I explicitly state that mdadm.conf is now required in multiple places. I realise that's painful for people who use kernel autostart, but there's really no other way. > Starting MD monitoring service: mdadm --monitor. > Assembling MD arrays...done (disabled in /etc/default/mdadm). > > As the assembling is disabled, why first say you're going to assemble... > and then say "done". I'll have to ponder about this. There are three scripts involved: postinst, config, init. Each is trying to be smarter than the other two. :) Please confirm that other than this being a nuisance, your system still works and mdadm installs properly. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck http://debiansystem.info `- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
