15 Jul
2018
15 Jul
'18
2:32 p.m.
Hello,
On Sun, Jul 15, 2018 at 03:14:53PM +0100, Ian Hobson wrote:
ian@hobsoni:~$ dpkg -l | grep grub
ii grub-pc 2.02~beta2-36ubuntu3.18 amd64
GRand Unified Bootloader, version 2 (PC/BIOS version)
So, you're using Grub 2.x, and the config file will be
/boot/grub/grub.cfg…
/boot/grub/grub.cfg: linux
/boot/vmlinuz-4.4.0-127-generic
root=/dev/xvda1 ro console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-127-generic
root=/dev/xvda1 ro console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-127-generic
root=/dev/xvda1 ro recovery nomodeset console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-124-generic
root=/dev/xvda1 ro console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-124-generic
root=/dev/xvda1 ro recovery nomodeset console=hvc0
I assume that it failed to boot the /boot/vmlinuz-4.4.0-127-generic
entry and you're now running in the /boot/vmlinuz-4.4.0-124-generic
entry?
(uname -a to comfirm)
ian@hobsoni:~$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
It's not a problem at all but you might like to comment out the two
lines starting "GRUB_HIDDEN_" so that you do actually get a grub
boot menu.
Don't forget to run "update-grub" after changing this file.
As far as I can see then, the kernel file isn't there for some
reason. Have you checked that /boot/vmlinuz-4.4.0-127-generic is
actually present?
If it's not there, and you run update-grub, does the entry for it in
/boot/grub/grub.cfg go away?
What does:
$ dpkg -l | grep '^ii.*linux-image'
say?
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting