Kernel update fails due to grub update

Bug #863134 reported by Matthew Wyneken
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LTSP5
Fix Released
Undecided
Alkis Georgopoulos
grub (Ubuntu)
Invalid
Undecided
Unassigned
ltsp (Ubuntu)
Fix Released
Undecided
Alkis Georgopoulos

Bug Description

LTSP client is running Ubuntu 11.04

I had problems during an update in the chroot that wanted to update to kernel 2.6.38-11.50. This was the first time a kernel update was performed on this image so it's the first time I could run into this problem.

The installation process runs /etc/kernel/postinst.d/zz-update-grub, which exits with an error because it can't find the root partition. There is no root partition mounted because the update is performed in chroot.

I had the same problem when I tried to perform the update on a running client system. In this case the problem was due to root being on an aufs disk rather than on an actual harddisk.

I came to the conclusion that an LTSP image doesn't have to have a working grub because it doesn't boot from disk. My solution: „chmod -x /etc/kernel/postinst.d/zz-update-grub“.

If my thinking is correct I suggest that zz-update-grub be removed from the directory when the LTSP client tree is first created.

Tags: grub kernel ltsp
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Fixed in LTSP 5.3. You can now use `ltsp-chroot -m` to have /dev mounted so that the grub postinst doesn't fail. I'm opening a task to the grub package though, as I think that it shouldn't fail when it doesn't detect any devices, it should consider it the same as not selecting any device at its debconf dialog.

Changed in ltsp (Ubuntu):
assignee: nobody → Alkis Georgopoulos (alkisg)
status: New → Fix Released
Changed in ltsp:
assignee: nobody → Alkis Georgopoulos (alkisg)
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This is no more a supported version; and grub legacy upstream is also stopped, only receiving possible random fixes locally

Changed in grub (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.