[Update-manager] Ubuntu 10.04 won't boot after kernel update (Sep. 23,2010)

Asked by DanD

Not sure if ubuntuforums would be the better place, but here goes, any help/direction is appreciated:

Sole ubuntu 10.04 lucid install on /sda1 (with some 0.5Gb /sda4 -extended and /sda5 -swap) grub2 loader. First updated kernel to 2.6.32-24. Rebooted, then went on to adding some ec2 and euca cloud tools and some exotic python dependencies. Upon subsequent reboot (needed apparently) system halts, even in recovery mode. No plain-jane black screen (doesnt seem to be X problem) - last lines on text screen are from fsck (appears to complete - no need for FS check). 'D' or 'M' don't work, just Ctrl-Alt-Del but no good feedback from that. /var/log/boot.log last line says 'SpamAssassin "disabled, see /etc/default/spamassassin' Well I tried spamassasin =1 and =0 (was 0 before) without success (after booting from a liveCD and changing the spamassasin variable on the HDD).

How can I catch where the hang is happening I guess is my question. What logs/files am I missing.

Thanks a lot

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu grub2 Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Hold shift at boot and try booting an older kernel (if you have one). Does it work ok?

Revision history for this message
DanD (dandrumea) said :
#2

I cleaned the old one after it restarted OK the first time around with the new krnl. :( I'm on a 16Gb SSD drive, so space is an issue. Shift only brings me to recovery - and it stalls somewhere before loading X and I still can't figure out where.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

16Gb is plenty. Keeping the older kernel for at least week is a good policy as you will have a fallback, each kernel also only uses 120Mb space.

If you boot now, what is onscreen. I suggest you remove the boot options to show the splash, so you can watch the boot happen.

Revision history for this message
DanD (dandrumea) said :
#4

Yes, I know, Im trusting QA testing so if it reboots OK I get rid of the old kernel (any tutorials to restore an older kernel onto a dead drive?). It's a good policy to keep at least a week and I'll enforce from now on. If I boot now it's what I said before - stuck prompt after fsck. Log file says it tried to load spamassassin after that. Then nothing.

Revision history for this message
delance (olivier-delance) said :
#5

I would be surprised spamassassin is the problem. Problems after update-manager install a new kernel are related to kernel itself.
Unfortunately, I'm not currently on a Ubuntu computer, so I can't provide you a verified solution.
1) Boot on Ubuntu Live CD
2) System->Administration->Synaptic
2.1) In search window, enter vmlinuz
2.2) Install the kernel you are interested
2.3) Do the same for initrd (not sure of name)
3) Check you have in /boot the needed files for previous kernel
4) Mount hard drive and copy these files in <mounting point>/boot
5) https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD
6) Check new file <mounting point>/boot/grub/grub.cfg
7) Reboot while holding shift key
8) Select previous kernel in Grub2 menu
9) If it works, remove latest kernel and run "sudo update-grub"
10) Reboot to check

@actionparsnip: How can we prevent update-manager to automatically install new kernel ?
@DanD: don't hesitate to post to ask explanation. As I said, I have not tested this process.

Revision history for this message
delance (olivier-delance) said :
#6

What is the status of your bug ? If it is solve, please mark the answer which solves the issue, or else provide your solution. If not, I will have some time this week to help.

Revision history for this message
DanD (dandrumea) said :
#7

Sorry to not have followed up sooner; ran into USB issues unrelated to this problem. I will be able to test the steps you provided tonight (I am on New York time). One thing is a bit unclear in step 5, specifically manually editing grub.cfg to add the now (old rather) kernel. I might have to do a kernel install twice and then diff the file to see the right places to change in the cfg on the mounted drive.

Revision history for this message
delance (olivier-delance) said :
#8

5) You are not supposed to edit file grub.cfg.
Commands to type are:
   sudo mount /dev/sda1 /mnt
   sudo grub-install --root-directory=/mnt/ /dev/sda

Can you help with this problem?

Provide an answer of your own, or ask DanD for more information if necessary.

To post a message you must log in.