Ubuntu 16.04 had been working well for over a year. After a standard update, re-boot freezes on purple screen
up vote
0
down vote
favorite
Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.
I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)
I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there
16.04 boot grubrescue
asked Nov 20 at 10:48
Hugh
11
add a comment |
up vote
0
down vote
favorite
Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.
I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)
I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there
16.04 boot grubrescue
asked Nov 20 at 10:48
Hugh
11
try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.
I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)
I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there
16.04 boot grubrescue
asked Nov 20 at 10:48
Hugh
11
Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.
I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)
I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there
16.04 boot grubrescue
16.04 boot grubrescue
asked Nov 20 at 10:48
Hugh
11
asked Nov 20 at 10:48
Hugh
11
asked Nov 20 at 10:48
Hugh
11
asked Nov 20 at 10:48
Hugh
11
asked Nov 20 at 10:48
Hugh
11
11
try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51
add a comment |
try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51
try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51
try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I got the right verion of the vmlinuz file in the boot directory. Then I tried
grub> set root=(hd0,2)
grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
grub> boot
where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc
answered Nov 20 at 12:50
Hugh
11
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I got the right verion of the vmlinuz file in the boot directory. Then I tried
grub> set root=(hd0,2)
grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
grub> boot
where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc
answered Nov 20 at 12:50
Hugh
11
add a comment |
up vote
0
down vote
I got the right verion of the vmlinuz file in the boot directory. Then I tried
grub> set root=(hd0,2)
grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
grub> boot
where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc
answered Nov 20 at 12:50
Hugh
11
add a comment |
up vote
0
down vote
up vote
0
down vote
I got the right verion of the vmlinuz file in the boot directory. Then I tried
grub> set root=(hd0,2)
grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
grub> boot
where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc
answered Nov 20 at 12:50
Hugh
11
I got the right verion of the vmlinuz file in the boot directory. Then I tried
grub> set root=(hd0,2)
grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
grub> boot
where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc
answered Nov 20 at 12:50
Hugh
11
answered Nov 20 at 12:50
Hugh
11
answered Nov 20 at 12:50
Hugh
11
answered Nov 20 at 12:50
Hugh
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094481%2fubuntu-16-04-had-been-working-well-for-over-a-year-after-a-standard-update-re%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51