Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

OS: Ubuntu 8.04 LTS Server Edition

We just rolled back an kernel update using the following command:

sudo apt-get remove linux-image-2.6.24-24-server

The uninstallation was successful, but it had the following message before apt-get exited:

The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
 you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
 you may need to re-run your boot loader[grub]

Should we be worrying about this message? Do we need to re-run GRUB? How do we go about doing this if we have to re-run GRUB?

Thanks in advance.

share|improve this question
up vote 30 down vote accepted

Those messages are nothing to worry about. The symlinks that are being complained about are only needed if you're using lilo as your bootloader, because it uses those symlinks to find your "current" kernel. Grub, being more flexible, has it's own way of doing things, and doesn't need the symlinks.

share|improve this answer
    
That's weird, I do not have lilo. I have grub and still getting those messages. – Zlatko Apr 15 at 8:54
1  
Yeah, my explanation was a little misleading. I've edited it to clarify. – womble Apr 18 at 8:08

You shouldn't need to re-run grub. You would, but after a kernel change you may need to run /usr/sbin/update-grub.

Those messages probably do not indicate an issue. The real test would be to simply reboot the computer. If it boots fine, then nothing bad happened.

You may want to update your /etc/kernel-img.conf and disable the do_symlinks option, and you shouldn't see this message again.

share|improve this answer
    
Thank you for the extra details and file paths – Paul Gregoire Jul 27 '14 at 12:48
    
I am sorry but rebooting the computer to check whether it can reboot is not good advice. What if it can't? – Cookie Feb 4 at 11:03
    
If you can't schedule a reboot of a system to test if you have broken the boot setup, then it almost certainly means you have a single point of failure in your network, that you should be fixing. I have no idea how you expect test if your computer boots properly, without testing that it boots properly. Obviously you should be prepared when you do this to fix your system, if it fails. – Zoredache Feb 4 at 19:21

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.