Can anyone help me out with the following problem? After ubuntu kernel update 4.15.0-76 to 4.15.0-88, I get in an emergency mode. I have to use the former kernel to be able to use the computer. Can´t find anything useful on current fora. I'm not sure what kind of information you need to solve this, and how to retrieve it from an emergency state system without uploading screenshots instead of plain text!?.
Asked
Active
Viewed 628 times
0
-
Did you install any grapphics drivers? Which and how? – Pilot6 Feb 22 '20 at 16:22
-
When going into emergency mode, does it give any error messages? Is it GRUB emergency mode, or Ubuntu Recovery mode? – heynnema Feb 22 '20 at 16:25
-
Thanks for responding! 1. No, I didn't install (new) graffic dirvers or other drivers – Bob Feb 23 '20 at 16:35
-
- I don know; The screen says; code; You are in emergency mode. After logging in, type ´journalctl -xb´ to view system logs code. I have a photo of blkid output and cat ..etc/fstab output but cannot upload it! Hope this helps.
– Bob Feb 23 '20 at 18:42
2 Answers
1
I lost wifi from the -88 kernel upgrade, so I went back to -76.
KITHMan777
- 11
-
1It would help OP if you tell how you went back to previous version. Also you should look at "pinning" the good kernel version so it doesn't get removed in a future update. Finally you should look at having grub automatically select the last boot option instead of most recent kernel: https://askubuntu.com/questions/1003079/how-to-change-the-order-on-my-dual-booting-distros/1003086#1003086 – WinEunuuchs2Unix Feb 23 '20 at 20:10
-
@ WinEunuuchs2Unix; your earlier suggestion/code is very helpful! sudo apt-mark hold linux-image-4.13.0-26-generic linux-headers-4.13.0-26-generic [https://askubuntu.com/questions/999529/pin-kernel-version] – Bob Feb 27 '20 at 13:40
0
I was able to resolve this by changing the options in my fstab for a 2nd drive that mounts at boot.
UUID= /mountpoint ext4 defaults 0 1
-
Thanks for responding, after trying different solutions, I finally did a clean install. I think a dual boot partition was the problem and had a conflict with the update. How I don know. I'm up and running again. – Bob Mar 09 '20 at 10:17