John Wiersba
January 26th, 2009, 04:17 AM
I just installed quite a number of new packages on a completely up-to-date
Intrepid 8.10, using synaptic. Installation went without problems. When I
reboot, I see:
Boot from (hd0,0) ext3 ...<UUID>...
Starting up ...
Loading, please wait ...
<CLEAR SCREEN>
usb 2-1: device not accepting address 2, error -71
usb 2-0:1.0: unable to enumerate USB device on port 1
After rebooting from a rescue environment, I checked /boot and saw that
initrd.img-2.6.27-9-generic had been changed by synaptic. Luckily, I had
backed up the previous version of initrd.img-2.6.27-9-generic, so I renamed
the bad one and was able to boot from the previous version.
This error is completely repeatable. However, my hard disk is
luks-encrypted, so no logs are saved in /var/log. I do see other copies of
these same error messages in /var/log/syslog (from a successful boot into my
luks-envryped LVM root disk).
So, my questions:
What caused this error?
How can I help debug this error?
How can I fix it other than by using a previous version of initrd.img?
How can I tell which changes were made to initrd.img-2.6.27-9-generic
that caused it to fail to be able to boot? I presume the changes were made
because of newly loaded modules, but maybe it's something else. Is there
something I can diff between the two versions of initrd.img?
Thanks in advance!
Intrepid 8.10, using synaptic. Installation went without problems. When I
reboot, I see:
Boot from (hd0,0) ext3 ...<UUID>...
Starting up ...
Loading, please wait ...
<CLEAR SCREEN>
usb 2-1: device not accepting address 2, error -71
usb 2-0:1.0: unable to enumerate USB device on port 1
After rebooting from a rescue environment, I checked /boot and saw that
initrd.img-2.6.27-9-generic had been changed by synaptic. Luckily, I had
backed up the previous version of initrd.img-2.6.27-9-generic, so I renamed
the bad one and was able to boot from the previous version.
This error is completely repeatable. However, my hard disk is
luks-encrypted, so no logs are saved in /var/log. I do see other copies of
these same error messages in /var/log/syslog (from a successful boot into my
luks-envryped LVM root disk).
So, my questions:
What caused this error?
How can I help debug this error?
How can I fix it other than by using a previous version of initrd.img?
How can I tell which changes were made to initrd.img-2.6.27-9-generic
that caused it to fail to be able to boot? I presume the changes were made
because of newly loaded modules, but maybe it's something else. Is there
something I can diff between the two versions of initrd.img?
Thanks in advance!