15 Jul
2018
15 Jul
'18
12:26 p.m.
Hi Guys,
I'm out of my depth. Help needed.
Running Ubuntu.
After applying changes, including those "Held back" by Apt-get, it
reported that it needed a restart.
The restart failed. Finally got onto the console and saw it was failing
with
error: file `/boot/vmlinuz-4.4.0-127-generic' not found.
So tried the other (older) versions listed and an old version is now
running. Now running is
ian@hobsoni:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
ian@hobsoni:~$
How can I recover, and get grub set up so default boot works again please?
Just in case it removes "disk full" questions...
ian@hobsoni:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.5G 0 1.5G 0% /dev
tmpfs 300M 4.4M 296M 2% /run
/dev/xvda1 14G 4.9G 7.6G 40% /
tmpfs 1.5G 0 1.5G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.5G 0 1.5G 0% /sys/fs/cgroup
tmpfs 300M 0 300M 0% /run/user/1000
ian@hobsoni:~$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 381064 358 380706 1% /dev
tmpfs 383485 525 382960 1% /run
/dev/xvda1 884736 252470 632266 29% /
tmpfs 383485 1 383484 1% /dev/shm
tmpfs 383485 5 383480 1% /run/lock
tmpfs 383485 16 383469 1% /sys/fs/cgroup
tmpfs 383485 4 383481 1% /run/user/1000
ian@hobsoni:~$
Thanks
Ian
--
Ian Hobson
Tel (+351) 910 418 473
15 Jul
15 Jul
1:44 p.m.
Hi Ian,
On Sun, Jul 15, 2018 at 01:26:13PM +0100, Ian Hobson wrote:
The restart failed. Finally got onto the console and
saw it was failing
with
error: file `/boot/vmlinuz-4.4.0-127-generic' not found.
This suggests that the bootloader configuration is wrong, at least
if /boot/vmlinuz-4.4.0-127-generic isn;t actually present in the VM.
What do these commands output?
$ dpkg -l | grep grub
$ ls -la /boot/grub/menu.lst /boot/grub/grub.cfg
$ grep vmlinuz /boot/grub/menu.lst /boot/grub/grub.cfg
$ cat /etc/default/grub
It may be as simple as running update-grub.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
2:14 p.m.
Hi Andy,
Thanks for your reply.
On 15/07/2018 14:44, Andy Smith wrote:
What do these commands output?
$ dpkg -l | grep grub
$ ls -la /boot/grub/menu.lst /boot/grub/grub.cfg
$ grep vmlinuz /boot/grub/menu.lst /boot/grub/grub.cfg
$ cat /etc/default/grub
ian@hobsoni:~$ dpkg -l | grep grub
ii grub-common 2.02~beta2-36ubuntu3.18
amd64 GRand Unified Bootloader (common files)
ii grub-gfxpayload-lists 0.7
amd64 GRUB gfxpayload blacklist
ii grub-legacy-ec2 18.2-4-g05926e48-0ubuntu1~16.04.2
all Handles update-grub for ec2 instances
ii grub-pc 2.02~beta2-36ubuntu3.18
amd64 GRand Unified Bootloader, version 2 (PC/BIOS version)
ii grub-pc-bin 2.02~beta2-36ubuntu3.18
amd64 GRand Unified Bootloader, version 2 (PC/BIOS binaries)
ii grub2-common 2.02~beta2-36ubuntu3.18
amd64 GRand Unified Bootloader (common files for version 2)
ian@hobsoni:~$ ls -la /boot/grub/menu.lst /boot/grub/grub.cfg
-r--r--r-- 1 root root 15829 May 22 20:22 /boot/grub/grub.cfg
-rw-r--r-- 1 root root 5560 May 19 16:08 /boot/grub/menu.lst
ian@hobsoni:~$ grep vmlinuz /boot/grub/menu.lst /boot/grub/grub.cfg
/boot/grub/menu.lst:# kernel /vmlinuz root=/dev/hda2 ro
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-121-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-121-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro single
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-119-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-119-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro single
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-116-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-116-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro single
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-112-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/menu.lst:kernel /boot/vmlinuz-4.4.0-112-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro single
/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
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-116-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-116-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro recovery nomodeset
console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-112-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-112-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 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: menuentry 'Ubuntu (on /dev/xvda1)' --class
gnu-linux --class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot
vmlinuz-4.4.0-124-generic--80731626-dbd6-4aff-8e17-1d741b7d2c73' {
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-124-generic
root=/dev/xvda1 ro console=hvc0
/boot/grub/grub.cfg: menuentry 'Ubuntu, with Linux 4.4.0-124-generic
(on /dev/xvda1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-4.4.0-124-generic--80731626-dbd6-4aff-8e17-1d741b7d2c73'
{
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-124-generic
root=/dev/xvda1 ro console=hvc0
/boot/grub/grub.cfg: menuentry 'Ubuntu, with Linux 4.4.0-124-generic
(recovery mode) (on /dev/xvda1)' --class gnu-linux --class gnu --class
os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-4.4.0-124-generic-root=/dev/xvda1 ro
recovery nomodeset console=hvc0-80731626-dbd6-4aff-8e17-1d741b7d2c73' {
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-124-generic
root=/dev/xvda1 ro recovery nomodeset console=hvc0
/boot/grub/grub.cfg: menuentry 'Ubuntu, with Linux 4.4.0-116-generic
(on /dev/xvda1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-4.4.0-116-generic--80731626-dbd6-4aff-8e17-1d741b7d2c73'
{
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-116-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/grub.cfg: menuentry 'Ubuntu, with Linux 4.4.0-116-generic
(recovery mode) (on /dev/xvda1)' --class gnu-linux --class gnu --class
os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-4.4.0-116-generic-root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73
ro recovery nomodeset console=hvc0-80731626-dbd6-4aff-8e17-1d741b7d2c73' {
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-116-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro recovery nomodeset
console=hvc0
/boot/grub/grub.cfg: menuentry 'Ubuntu, with Linux 4.4.0-112-generic
(on /dev/xvda1)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-4.4.0-112-generic--80731626-dbd6-4aff-8e17-1d741b7d2c73'
{
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-112-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro console=hvc0
/boot/grub/grub.cfg: menuentry 'Ubuntu, with Linux 4.4.0-112-generic
(recovery mode) (on /dev/xvda1)' --class gnu-linux --class gnu --class
os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-4.4.0-112-generic-root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73
ro recovery nomodeset console=hvc0-80731626-dbd6-4aff-8e17-1d741b7d2c73' {
/boot/grub/grub.cfg: linux /boot/vmlinuz-4.4.0-112-generic
root=UUID=80731626-dbd6-4aff-8e17-1d741b7d2c73 ro recovery nomodeset
console=hvc0
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
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="console=hvc0"
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
ian@hobsoni:~$
--
Ian Hobson
Tel (+351) 910 418 473
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
2:59 p.m.
Hi Andy,
On 15/07/2018 15:32, Andy Smith wrote:
ian@hobsoni:~$ dpkg -l | grep '^ii.*linux-image'
ii linux-image-4.4.0-112-generic 4.4.0-112.135
amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-116-generic 4.4.0-116.140
amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-130-generic 4.4.0-130.156
amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-virtual 4.4.0.130.136
amd64 This package will always depend on the latest
minimal generic kernel image.
ian@hobsoni:~$
Thanks for your help.
Ian
--
Ian Hobson
Tel (+351) 910 418 473
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:~$ uname -a
Linux hobsoni 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
ian@hobsoni:~$
So no. 124 also failed to boot, but 116 did.
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'
3:08 p.m.
Hello,
On Sun, Jul 15, 2018 at 03:59:41PM +0100, Ian Hobson wrote:
ian@hobsoni:~$ dpkg -l | grep
'^ii.*linux-image'
ii linux-image-4.4.0-112-generic 4.4.0-112.135 amd64 Linux
kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-116-generic 4.4.0-116.140 amd64 Linux
kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-130-generic 4.4.0-130.156 amd64 Linux
kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-virtual 4.4.0.130.136 amd64 This
package will always depend on the latest minimal generic kernel image.
So you appear to have 4.4.0-112.135, 4.4.0-116.140, 4.4.0-130.156,
but your grub.cfg doesn't feature anything for 4.4.0-130.156 and the
one you're booted into is 4.4.0-116.140.
If you do "update-grub" does it find the 4.4.0-130.156 one?
Which kernel files do you actually have present?
$ ls /boot/vmlinuz*
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
3:07 p.m.
Hi Andy,
On 15/07/2018 15:32, Andy Smith wrote:
(uname -a to comfirm)
I did this, and afterwards "sudo reboot". and it rebooted into....
Linux hobsoni 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Which I think is the latest.
Regards
Ian
--
Ian Hobson
Tel (+351) 910 418 473
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.
3:10 p.m.
Hello,
On Sun, Jul 15, 2018 at 04:07:11PM +0100, Ian Hobson wrote:
On 15/07/2018 15:32, Andy Smith wrote:
Yes, it seems so. It seems like the only thing that went wrong is
that update-grub wasn't run for some reason. It normally happens
when kernel packages are installed/removed.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Don't forget to run "update-grub"
after changing this file.
I did this, and afterwards "sudo reboot". and it rebooted into....
Linux hobsoni 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Which I think is the latest.
2110
days inactive
2110
days old
7 comments
2 participants
participants (2)
-
Andy Smith -
Ian Hobson