I am closing this as I have not experienced it since Edgy.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
--
"Command failed" when running update-initramfs on Edgy
https://bugs.launchpad.net/bugs/61122
You received this bug notification because you are a member
I also get the "command failed" message when update-initramfs is run,
this is occuring in the cryptroot hook script (/usr/share/initramfs-
tools/hooks) when it tries to get info about the dependent devices.
The system does not have an encrypted root partition, but does use LVM
and this is possibly
I should also note that there are two bugs here apparently. The "-v"
that mlind confirmed and the more major bug that the file refers to. I
didn't realize this when I initially submitted the bug.
--
"Command failed" when running update-initramfs on Edgy
https://launchpad.net/bugs/61122
--
ubu
Here is the output of "mkinitramfs -o /boot/initrd.img-2.6.17-5-686
2.6.17-5-686" when set -x is added to the script.
One consequence of this bug is that usplash doesn't use the proper
graphics on boot.
** Attachment added: "output of mkinitramfs"
http://librarian.launchpad.net/4416591/out
--
I also get this error without "-v". This is a box that was recently
upgraded from dapper.
Here is the output without "-v":
# update-initramfs -k 2.6.17-7-generic -u
update-initramfs: Generating /boot/initrd.img-2.6.17-7-generic
Command failed
--
"Command failed" when running update-initramfs o
Confirming, on initramfs-tools 0.69ubuntu13.
-v param seems to cause trouble although it shouldn't.
** Changed in: initramfs-tools (Ubuntu)
Status: Unconfirmed => Confirmed
--
"Command failed" when running update-initramfs on Edgy
https://launchpad.net/bugs/61122
--
ubuntu-bugs mailing
