Rebooting failed because the initramfs was incomplete. Turns out /boot was full because backup initrd.img files had been created.
The important problem is that package installation succeeded despite the initrd.img write failure. It seems to me that this is sufficiently serious that it might be release critical. I don't know exactly which package was responsible for ignoring the write error so I'm sending the report to this list. I note that the following packages are all in state "ii": # dpkg -l | grep mdadm | cut -b-60 ii mdadm 2.5.6-7 # dpkg -l | grep initramfs-tools | cut -b-60 ii initramfs-tools 0.85e # dpkg -l | grep linux-image | cut -b-60 ii linux-image-2.6-686 2.6.18+5 ii linux-image-2.6.18-3-686 2.6.18-7 # There may have been some kind of error logged to the console but if so it must have scrolled past without my noticing. I've been assuming that if a package has attained "ii" then it has installed successfully. According to /var/log/dpkg.log* both initramfs-tools and mdadm had been upgraded since the last reboot but there had been no changes to linux-image packages: 2006-12-12 14:07:09 upgrade initramfs-tools 0.85b 0.85c 2006-12-28 06:32:25 upgrade initramfs-tools 0.85e 0.85e 2006-12-30 11:31:37 upgrade mdadm 2.5.6-6 2.5.6-7 --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
