update-manager fails - requires at least kernel version 2.6.17

Bug #231075 reported by Sam Brightman on 2008-05-16
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: update-manager

udev gives the message, but says to report against update-manager. I was attempting to upgrade up-to-date dapper to hardy through ssh as described here: http://ubuntu-tutorials.com/2008/04/03/dapper-to-hardy-direct-server-upgrade-works/ (although I still had to use the -d switch for development distribution upgrade - surely this needs fixing?)

the failure:

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.15-51-686
W: udev hook script requires at least kernel version 2.6.17
W: not generating requested initramfs for kernel 2.6.15-51-686
Errors were encountered while processing:
 linux-ubuntu-modules-2.6.24-16-generic
/etc/fstab.pre-uuid already exists
remove this file before running the script again

Could not install the upgrades

The upgrade aborts now. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

Please report this bug against the 'update-manager' package and
include the files in /var/log/dist-upgrade/ in the bugreport.
installArchives() failed

dpkg: dependency problems prevent configuration of linux-ubuntu-modules-2.6.24-16-generic:
 linux-ubuntu-modules-2.6.24-16-generic depends on linux-image-2.6.24-16-generic; however:
  Package linux-image-2.6.24-16-generic is not installed.
dpkg: error processing linux-ubuntu-modules-2.6.24-16-generic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-ubuntu-modules-2.6.24-16-generic
/etc/fstab.pre-uuid already exists
remove this file before running the script again

I tried removing fstab.pre-uuid and running sudo do-release-upgrade -d again just in case but it seems to be "already on" hardy.

sudo dpkg --configure -a just prints the dependency problems

Sam Brightman (sambrightman) wrote :
Sam Brightman (sambrightman) wrote :

I should add that I didn't have the dapper-proposed repository enabled. Perhaps I would otherwise have a more up-to-date kernel installed? Seems to me the upgrader should be intelligent enough to deal with this.

Richard Seguin (sectech) wrote :

Thank you for reporting this issue... The issue you reported does need to be addressed because it shouldn't have crashed when upgrading but I think I have a solution to your problem. Try apt-get -f install and report back if it fixed it or not...

So if I understand you correctly you had an up to date dapper system and you did an upgrade via upgrade manager? I might have to test this to see if I can recreate the problem...

Richard Seguin (sectech) wrote :

* Marking as incomplete pending enough information to complete triage

Changed in update-manager:
status: New → Incomplete
Richard Seguin (sectech) wrote :

* Marking as confirmed as reporter clearly states that the message "W: udev hook script requires at least kernel version 2.6.17" is displayed.

Changed in update-manager:
status: Incomplete → Confirmed
Sam Brightman (sambrightman) wrote :

richard, thanks for the quick response. I didn't see it before I started playing myself. It was up-to-date dapper server upgrade to hardy as described in the link. I started playing around with sudo aptitude dist-upgrade/remove and eventually managed to get everything installed (and not broken). It just failed to come up from a reboot though, and without ssh access I can't do anything until I get local access on Monday. This bug should still be fixed - what other information can I provide? Would you expect my system to be stable and "properly" upgraded after fixing whatever is the current problem? i.e. what is the upgrade tool doing that I might not have done using aptitude?

Changed in update-manager:
importance: Undecided → Medium
status: Confirmed → Triaged
Download full text (5.4 KiB)

BTW running
  dpkg-reconfigure -a
fixed the problem for me. (It also asked me lots of questions, and I'm not sure what I misconfigured.)

Here's the end of the update messages [with my comments in square brackets]:

-- snip --
Cleaning up font configuration of pango...
Cleaning up category xfont..
Cleaning up font configuration of pango...
Cleaning up category xfont..
Updating font configuration of pango...
Cleaning up category xfont..
Updating category xfont..
udev active, devices will be created in /dev/.static/dev/
Cleaning up font configuration of libwmf0.2-7...
Cleaning up category type1..
Cleaning up category truetype..
Updating font configuration of libwmf0.2-7...
Cleaning up category type1..
Cleaning up category truetype..
Updating category truetype..
Updating category type1..
update-initramfs: Generating /boot/initrd.img-2.6.15-26-server
W: udev hook script requires at least kernel version 2.6.17
W: not generating requested initramfs for kernel 2.6.15-26-server
Not touching initrd symlinks since we are being reinstalled (2.6.15-26.47)
Not updating image symbolic links since we are being updated (2.6.15-26.47)
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz
Found kernel: /boot/vmlinuz-2.6.24-19-server
Found kernel: /boot/vmlinuz-2.6.15-52-server
Found kernel: /boot/vmlinuz-2.6.15-51-server
Found kernel: /boot/vmlinuz-2.6.15-29-server
Found kernel: /boot/vmlinuz-2.6.15-28-server
Found kernel: /boot/vmlinuz-2.6.15-26-server
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done
[4 repeats from line "update-initramfs: Generating..." above]

Running depmod.
[another repeat]

update-initramfs: Generating /boot/initrd.img-2.6.24-19-server
Generating locales...
  de_DE.ISO-8859-15@euro... up-to-date
  de_DE.ISO-8859-1... up-to-date
  de_DE.UTF-8... up-to-date
  en_US.UTF-8... up-to-date
Generation complete.
Generating locales...
  de_DE.ISO-8859-15@euro... up-to-date
  de_DE.ISO-8859-1... up-to-date
  de_DE.UTF-8... up-to-date
  en_US.UTF-8... up-to-date
Generation complete.
Backing up any LVM2 metadata that may exist...done.
[back to "too old kernel" mode]
update-initramfs: Generating /boot/initrd.img-2.6.15-29-server
W: udev hook script requires at least kernel version 2.6.17
W: not generating requested initramfs for kernel 2.6.15-29-server
udev active, devices will be created in /dev/.static/dev/
udev active, devices will be created in /dev/.static/dev/
 * Stopping MD monitoring service mdadm --monitor [ OK ]
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs: Generating /boot/initrd.img-2.6.15-29-server
W: udev hook script requires at least kernel version 2.6.17
W: not generating requested initramfs for kernel 2.6.15-29-server
 * Starting MD monitoring service mdadm --monitor [ OK ]
[back to "it works" mode]
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /b...

Read more...

I found out another detail:
  update-initramfs -u -k 2.6.24-19-server
will work without an error message; it is
  update-initramfs -u -k 2.6.15-52-server
that will fail with the udev hook script message. So the udev message is just misleading about which kernel it is talking about (kernel being updated instead of running kernel).

So I suggest changing the message
  udev hook script requires at least kernel version 2.6.17
to
  udev hook script cannot process kernels before version 2.6.17

What remains to be checked is whether the boot machinery is in a usable state in the current situation. If yes, the error can be downgraded to a warning, and a message as in
  The kernel was not changed and should still be usable
could be issued.
If no, the message should be
  The kernel is not bootable anymore. However, a new kernel is being installed and *should* be bootable. You can uninstall the old kernel(s).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments