Ubuntu 16.04 won't start with linux-image-4.4.0-119-generic
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
My ubuntu 16.04 computer has stopped booting following an update, which updated to linux-image-4.4.0-119-generic. It will only start if I go into advanced grub options and select the previous linux image version, linux-image-4.4.0-116-generic.
Has anybody else encountered this problem, and does anyone know how to fix it?
boot grub2 kernel
asked Apr 17 at 16:54
samfrances
1011
add a comment |Â
up vote
0
down vote
favorite
My ubuntu 16.04 computer has stopped booting following an update, which updated to linux-image-4.4.0-119-generic. It will only start if I go into advanced grub options and select the previous linux image version, linux-image-4.4.0-116-generic.
Has anybody else encountered this problem, and does anyone know how to fix it?
boot grub2 kernel
asked Apr 17 at 16:54
samfrances
1011
If you press the left or right arrow key right after grub, what is displayed as the last few lines of the boot log before it hangs?
– sbergeron
Apr 17 at 17:03
2
If you hit e in your grub menu on linux-image-4.4.0-116-generic and remove the flags like 'quiet, splash, loglevel =0' and boot your system with hitting F10 you could maybe see a failure happening and find some explanations. I don't know if you are using the 'nomodeset' option, but I'd give it a try with both - set and not set and maybe you could set loglevel =7 to get some more information.
– starkus
Apr 17 at 17:07
Changingquietandsplashmake no difference. It just hangs on a grey screen for a while, no text, then reboots.
– samfrances
Apr 17 at 18:06
1
In the end, uninstallingimage-4.4.0-119-genericand the reinstallinglinux-generic.
– samfrances
Apr 17 at 18:29
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My ubuntu 16.04 computer has stopped booting following an update, which updated to linux-image-4.4.0-119-generic. It will only start if I go into advanced grub options and select the previous linux image version, linux-image-4.4.0-116-generic.
Has anybody else encountered this problem, and does anyone know how to fix it?
boot grub2 kernel
asked Apr 17 at 16:54
samfrances
1011
My ubuntu 16.04 computer has stopped booting following an update, which updated to linux-image-4.4.0-119-generic. It will only start if I go into advanced grub options and select the previous linux image version, linux-image-4.4.0-116-generic.
Has anybody else encountered this problem, and does anyone know how to fix it?
boot grub2 kernel
boot grub2 kernel
asked Apr 17 at 16:54
samfrances
1011
asked Apr 17 at 16:54
samfrances
1011
asked Apr 17 at 16:54
samfrances
1011
asked Apr 17 at 16:54
samfrances
1011
asked Apr 17 at 16:54
samfrances
1011
1011
If you press the left or right arrow key right after grub, what is displayed as the last few lines of the boot log before it hangs?
– sbergeron
Apr 17 at 17:03
2
If you hit e in your grub menu on linux-image-4.4.0-116-generic and remove the flags like 'quiet, splash, loglevel =0' and boot your system with hitting F10 you could maybe see a failure happening and find some explanations. I don't know if you are using the 'nomodeset' option, but I'd give it a try with both - set and not set and maybe you could set loglevel =7 to get some more information.
– starkus
Apr 17 at 17:07
Changingquietandsplashmake no difference. It just hangs on a grey screen for a while, no text, then reboots.
– samfrances
Apr 17 at 18:06
1
In the end, uninstallingimage-4.4.0-119-genericand the reinstallinglinux-generic.
– samfrances
Apr 17 at 18:29
add a comment |Â
If you press the left or right arrow key right after grub, what is displayed as the last few lines of the boot log before it hangs?
– sbergeron
Apr 17 at 17:03
2
If you hit e in your grub menu on linux-image-4.4.0-116-generic and remove the flags like 'quiet, splash, loglevel =0' and boot your system with hitting F10 you could maybe see a failure happening and find some explanations. I don't know if you are using the 'nomodeset' option, but I'd give it a try with both - set and not set and maybe you could set loglevel =7 to get some more information.
– starkus
Apr 17 at 17:07
Changingquietandsplashmake no difference. It just hangs on a grey screen for a while, no text, then reboots.
– samfrances
Apr 17 at 18:06
1
In the end, uninstallingimage-4.4.0-119-genericand the reinstallinglinux-generic.
– samfrances
Apr 17 at 18:29
If you press the left or right arrow key right after grub, what is displayed as the last few lines of the boot log before it hangs?
– sbergeron
Apr 17 at 17:03
If you press the left or right arrow key right after grub, what is displayed as the last few lines of the boot log before it hangs?
– sbergeron
Apr 17 at 17:03
2
2
If you hit e in your grub menu on linux-image-4.4.0-116-generic and remove the flags like 'quiet, splash, loglevel =0' and boot your system with hitting F10 you could maybe see a failure happening and find some explanations. I don't know if you are using the 'nomodeset' option, but I'd give it a try with both - set and not set and maybe you could set loglevel =7 to get some more information.
– starkus
Apr 17 at 17:07
If you hit e in your grub menu on linux-image-4.4.0-116-generic and remove the flags like 'quiet, splash, loglevel =0' and boot your system with hitting F10 you could maybe see a failure happening and find some explanations. I don't know if you are using the 'nomodeset' option, but I'd give it a try with both - set and not set and maybe you could set loglevel =7 to get some more information.
– starkus
Apr 17 at 17:07
Changing
quiet and splash make no difference. It just hangs on a grey screen for a while, no text, then reboots.– samfrances
Apr 17 at 18:06
Changing
quiet and splash make no difference. It just hangs on a grey screen for a while, no text, then reboots.– samfrances
Apr 17 at 18:06
1
1
In the end, uninstalling
image-4.4.0-119-generic and the reinstalling linux-generic.– samfrances
Apr 17 at 18:29
In the end, uninstalling
image-4.4.0-119-generic and the reinstalling linux-generic.– samfrances
Apr 17 at 18:29
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
I have noticed the sames issue today. After the question "A new version of boot/grub/menu.lst is available...." you can choice to "keep the local version" or "the package maintainer´s version".
I have tried both options, but either way after the first reboot of UBUNTU OS there is an issue! :(
Also related with upgrade to kernel 4.4.0-119 (but only from 4.4.0-112).
"
...
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-112-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-112-generic
"
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
answered Apr 20 at 15:03
Pieter
1
add a comment |Â
up vote
0
down vote
If we skip the "cloud-init" updates, we still get the question about the /boot/grub/men.lst, but if we choose the first option (maintainer's version) we have no issues anymore!
See also https://forums.aws.amazon.com/thread.jspa?messageID=844280&tstart=0
answered Apr 24 at 7:32
user821528
1
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I have noticed the sames issue today. After the question "A new version of boot/grub/menu.lst is available...." you can choice to "keep the local version" or "the package maintainer´s version".
I have tried both options, but either way after the first reboot of UBUNTU OS there is an issue! :(
Also related with upgrade to kernel 4.4.0-119 (but only from 4.4.0-112).
"
...
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-112-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-112-generic
"
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
answered Apr 20 at 15:03
Pieter
1
add a comment |Â
up vote
0
down vote
I have noticed the sames issue today. After the question "A new version of boot/grub/menu.lst is available...." you can choice to "keep the local version" or "the package maintainer´s version".
I have tried both options, but either way after the first reboot of UBUNTU OS there is an issue! :(
Also related with upgrade to kernel 4.4.0-119 (but only from 4.4.0-112).
"
...
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-112-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-112-generic
"
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
answered Apr 20 at 15:03
Pieter
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I have noticed the sames issue today. After the question "A new version of boot/grub/menu.lst is available...." you can choice to "keep the local version" or "the package maintainer´s version".
I have tried both options, but either way after the first reboot of UBUNTU OS there is an issue! :(
Also related with upgrade to kernel 4.4.0-119 (but only from 4.4.0-112).
"
...
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-112-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-112-generic
"
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
answered Apr 20 at 15:03
Pieter
1
I have noticed the sames issue today. After the question "A new version of boot/grub/menu.lst is available...." you can choice to "keep the local version" or "the package maintainer´s version".
I have tried both options, but either way after the first reboot of UBUNTU OS there is an issue! :(
Also related with upgrade to kernel 4.4.0-119 (but only from 4.4.0-112).
"
...
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-119-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-119-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-119-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro console=hvc0
initrd /initrd.img-4.4.0-112-generic
title Ubuntu 16.04.4 LTS, kernel 4.4.0-112-generic (recovery mode)
root (hd0)
kernel /vmlinuz-4.4.0-112-generic root=LABEL=cloudimg-rootfs ro single
initrd /initrd.img-4.4.0-112-generic
"
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
answered Apr 20 at 15:03
Pieter
1
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
edited Apr 20 at 15:11
WinEunuuchs2Unix
35.7k759133
35.7k759133
answered Apr 20 at 15:03
Pieter
1
answered Apr 20 at 15:03
Pieter
1
answered Apr 20 at 15:03
Pieter
1
1
add a comment |Â
add a comment |Â
up vote
0
down vote
If we skip the "cloud-init" updates, we still get the question about the /boot/grub/men.lst, but if we choose the first option (maintainer's version) we have no issues anymore!
See also https://forums.aws.amazon.com/thread.jspa?messageID=844280&tstart=0
answered Apr 24 at 7:32
user821528
1
add a comment |Â
up vote
0
down vote
If we skip the "cloud-init" updates, we still get the question about the /boot/grub/men.lst, but if we choose the first option (maintainer's version) we have no issues anymore!
See also https://forums.aws.amazon.com/thread.jspa?messageID=844280&tstart=0
answered Apr 24 at 7:32
user821528
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
If we skip the "cloud-init" updates, we still get the question about the /boot/grub/men.lst, but if we choose the first option (maintainer's version) we have no issues anymore!
See also https://forums.aws.amazon.com/thread.jspa?messageID=844280&tstart=0
answered Apr 24 at 7:32
user821528
1
If we skip the "cloud-init" updates, we still get the question about the /boot/grub/men.lst, but if we choose the first option (maintainer's version) we have no issues anymore!
See also https://forums.aws.amazon.com/thread.jspa?messageID=844280&tstart=0
answered Apr 24 at 7:32
user821528
1
answered Apr 24 at 7:32
user821528
1
answered Apr 24 at 7:32
user821528
1
answered Apr 24 at 7:32
user821528
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025876%2fubuntu-16-04-wont-start-with-linux-image-4-4-0-119-generic%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
If you press the left or right arrow key right after grub, what is displayed as the last few lines of the boot log before it hangs?
– sbergeron
Apr 17 at 17:03
2
If you hit e in your grub menu on linux-image-4.4.0-116-generic and remove the flags like 'quiet, splash, loglevel =0' and boot your system with hitting F10 you could maybe see a failure happening and find some explanations. I don't know if you are using the 'nomodeset' option, but I'd give it a try with both - set and not set and maybe you could set loglevel =7 to get some more information.
– starkus
Apr 17 at 17:07
Changing
quietandsplashmake no difference. It just hangs on a grey screen for a while, no text, then reboots.– samfrances
Apr 17 at 18:06
1
In the end, uninstalling
image-4.4.0-119-genericand the reinstallinglinux-generic.– samfrances
Apr 17 at 18:29