[Ubuntu] New /boot/grub/menu.lst after `apt-get upgrade`?

June 8, 2018 2.4k views
Docker Linux Basics DigitalOcean Ubuntu 16.04

Hi there!

Just started a new droplet with Docker.

I wanted to make sure I have the newest version, so I ran apt-get update and apt-get upgrade after which I got the following in Terminal:

A new version of /boot/grub/menu.lst is available, but the version
     │ installed currently has been locally modified.

     │ What would you like to do about menu.lst?

     │      install the package maintainer's version
     │      keep the local version currently installed
     │      show the differences between the versions
     │      show a side-by-side difference between the versions
     │      show a 3-way difference between available versions
     │      do a 3-way merge between available versions (experimental)   
     │      start a new shell to examine the situation

I've never edited the menu.lst file, I imagine this is something done by DO.

What exactly is happening here, and what option should I select?

Thanks!

Dillon

5 Answers

Update: after finding this discussion, I chose to keep the current version (prompted twice). After that, I rebooted my server and crossed fingers and it looks like it survived the reboot.

So I suppose the “keep current version” is not an entirely bad option.

Also hitting the same situation and would love some clarification.

The third option doesn’t show any non-whitespace differences between the two files, and as far as I can see, neither does the fourth one.

The fifth option, however, shows a change in root device from root=/dev/hda1 to root=LABEL=cloudimg-rootfs.

Which would be the right option to choose?

Hey @DigitalOcean, can we have an official answer on this? I'm getting the same warning and the changes between the two versions of /run/grub/menu.lst show that the new version is for Ubuntu 16.04.5.

Line by line differences between versions                                 

--- /run/grub/menu.lst root.root 0644 2018-08-05 09:53:42     
+++ /tmp/filenNNsEF root.root 0600 2018-08-05 09:53:42
@@ -1,11 +1,31 @@                    
 ## ## End Default Options ##
-title Ubuntu 16.04.4 LTS, kernel 4.4.0-127-generic
+title Ubuntu 16.04.5 LTS, kernel 4.4.0-131-generic
+root (hd0)                       
+kernel /boot/vmlinuz-4.4.0-131-generic root=LABEL=cloudimg-rootfs ro console=hvc0                             
+initrd /boot/initrd.img-4.4.0-131-generic
+
+title Ubuntu 16.04.5 LTS, kernel 4.4.0-131-generic (recovery mode)
+root (hd0)
+kernel /boot/vmlinuz-4.4.0-131-generic root=LABEL=cloudimg-rootfs ro single
+initrd /boot/initrd.img-4.4.0-131-generic
+                                
+title Ubuntu 16.04.5 LTS, kernel 4.4.0-130-generic
+root (hd0)                       
+kernel /boot/vmlinuz-4.4.0-130-generic root=LABEL=cloudimg-rootfs ro console=hvc0
+initrd /boot/initrd.img-4.4.0-130-generic
+
+title Ubuntu 16.04.5 LTS, kernel 4.4.0-130-generic (recovery mode)
+root (hd0)
+kernel /boot/vmlinuz-4.4.0-130-generic root=LABEL=cloudimg-rootfs ro single     
+initrd /boot/initrd.img-4.4.0-130-generic    
+                                
+title Ubuntu 16.04.5 LTS, kernel 4.4.0-127-generic root (hd0) kernel /boot/vmlinuz-4.4.0-127-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /boot/initrd.img-4.4.0-127-generic
-title Ubuntu 16.04.4 LTS, kernel 4.4.0-127-generic (recovery mode)
+title Ubuntu 16.04.5 LTS, kernel 4.4.0-127-generic (recovery mode)
 root (hd0)       
 kernel /boot/vmlinuz-4.4.0-127-generic root=LABEL=cloudimg-rootfs ro single initrd /boot/initrd.img-4.4.0-127-generic
  • Hello there,

    I used the first option just to try and it seems like everything is ok. I mean, I restarted the server and I was able to continue working on it. Honestly I'm not sure about the implications but there was no error for me.

Doing sudo rm /boot/grub/menu.lst before apt-get upgrade -y fixed the issue for me.

Have another answer? Share your knowledge.