Kernel panic and unable to boot Ubuntu 16.04 after updating
up vote
8
down vote
favorite
I have tried to update my Ubuntu version and after updating, my boot screen is displaying a kernel panic message and I'm unable to access my login screen.
kernel updates toshiba-satellite
edited Mar 30 '17 at 12:16
vijay
165
asked Mar 30 '17 at 11:08
user1900238
41127
add a comment |
up vote
8
down vote
favorite
I have tried to update my Ubuntu version and after updating, my boot screen is displaying a kernel panic message and I'm unable to access my login screen.
kernel updates toshiba-satellite
edited Mar 30 '17 at 12:16
vijay
165
asked Mar 30 '17 at 11:08
user1900238
41127
1
you may want to add which version you are updating from and to which version.
– saviour123
Mar 30 '17 at 11:28
And this is why I never do in-place upgrades, regardless of the OS. I always clean install instead of upgrade.
– Android Dev
Mar 30 '17 at 11:56
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I have tried to update my Ubuntu version and after updating, my boot screen is displaying a kernel panic message and I'm unable to access my login screen.
kernel updates toshiba-satellite
edited Mar 30 '17 at 12:16
vijay
165
asked Mar 30 '17 at 11:08
user1900238
41127
I have tried to update my Ubuntu version and after updating, my boot screen is displaying a kernel panic message and I'm unable to access my login screen.
kernel updates toshiba-satellite
kernel updates toshiba-satellite
edited Mar 30 '17 at 12:16
vijay
165
asked Mar 30 '17 at 11:08
user1900238
41127
edited Mar 30 '17 at 12:16
vijay
165
asked Mar 30 '17 at 11:08
user1900238
41127
edited Mar 30 '17 at 12:16
vijay
165
edited Mar 30 '17 at 12:16
vijay
165
edited Mar 30 '17 at 12:16
vijay
165
165
asked Mar 30 '17 at 11:08
user1900238
41127
asked Mar 30 '17 at 11:08
user1900238
41127
asked Mar 30 '17 at 11:08
user1900238
41127
41127
1
you may want to add which version you are updating from and to which version.
– saviour123
Mar 30 '17 at 11:28
And this is why I never do in-place upgrades, regardless of the OS. I always clean install instead of upgrade.
– Android Dev
Mar 30 '17 at 11:56
add a comment |
1
you may want to add which version you are updating from and to which version.
– saviour123
Mar 30 '17 at 11:28
And this is why I never do in-place upgrades, regardless of the OS. I always clean install instead of upgrade.
– Android Dev
Mar 30 '17 at 11:56
1
1
you may want to add which version you are updating from and to which version.
– saviour123
Mar 30 '17 at 11:28
you may want to add which version you are updating from and to which version.
– saviour123
Mar 30 '17 at 11:28
And this is why I never do in-place upgrades, regardless of the OS. I always clean install instead of upgrade.
– Android Dev
Mar 30 '17 at 11:56
And this is why I never do in-place upgrades, regardless of the OS. I always clean install instead of upgrade.
– Android Dev
Mar 30 '17 at 11:56
add a comment |
3 Answers
3
active
oldest
votes
up vote
8
down vote
You are missing the initramfs for kernel version 4.8.0-44.
It looks like you got a kernel panic error message after updating the kernel in Ubuntu 16.04.1 to 4.8.0-44-generic. To fix it enter a text-only console and either replace 4.8.0-44-generic with the more stable default kernel version or run sudo update-initramfs -u -k 4.8.0-44-generic && sudo update-grub.
After the boot stops at the black screen, open a text-only virtual console by using the keyboard shortcut Ctrl+Alt+F3
At the
login:prompt type your username and press Enter.At the
Password:prompt type your user password and press Enter.
After you have logged in in the console type:
sudo apt remove linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic linux-headers-4.8.0-44-generic
sudo apt install linux-image-4.4.0-71-generic linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic
sudo reboot
Alternatively you can run the following commands to update initramfs for kernel version 4.8.0-44-generic :
sudo update-initramfs -u -k 4.8.0-44-generic
sudo update-grub
Immediately after the BIOS/UEFI splash screen during boot, with BIOS, quickly press and hold the Shift key, which will bring up the GNU GRUB menu. (If you see the Ubuntu logo, you've missed the point where you can enter the GRUB menu.) With UEFI press (perhaps several times) the Esc key to get to the GRUB menu. Sometimes the manufacturer's splash screen is a part of the Windows bootloader, so when you power up the machine it goes straight to the GRUB screen, and then pressing Shift is unnecessary.
From the purple GRUB screen select Advanced options for Ubuntu with the ↑ and ↓ keys and press Enter.
A new purple screen will appear showing a list of kernels. Select Ubuntu, with Linux 4.4.0-71-generic and press Enter.
Ubuntu will load the selected kernel and proceed to the login screen as usual.
Don't let Ubuntu update the kernel to the 4.8.0-44 version that caused the black screen again, or else you'll get the same black screen problem that you got before.
answered Mar 30 '17 at 11:56
karel
54.8k11119138
1
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
|
show 4 more comments
up vote
1
down vote
Steps:
mount -o remount,rw /mkinitramfs -o /boot/initrd.img-{kerner_version}-generic {kernel_version}-generic update-grub Here {Kernel_version} is the kernel version number you take note of in step 5 (The Problematic kernel, latest installed one).
Reboot the System that is it, you're all set and ready to continue your work flow. Hopes That Helps.
answered Dec 22 '17 at 15:24
salafi
1263
add a comment |
up vote
0
down vote
You have a file system error that caused your kernel panic. Unable to mount root. It might be because you're trying to run kernel 4.8 on 16.04.1, or a failed 16.04.2 update, or it might even be a bad hard drive, or one that needs to be reinitialized... but lets try this first...
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode (from the prior 4.4 kernel)
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the fsck command if there were errors
- type
reboot
Let me know if you can't do this, and I'll give you another method.
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with@heynnemaor I may miss them.
– heynnema
Apr 1 '17 at 13:29
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
You are missing the initramfs for kernel version 4.8.0-44.
It looks like you got a kernel panic error message after updating the kernel in Ubuntu 16.04.1 to 4.8.0-44-generic. To fix it enter a text-only console and either replace 4.8.0-44-generic with the more stable default kernel version or run sudo update-initramfs -u -k 4.8.0-44-generic && sudo update-grub.
After the boot stops at the black screen, open a text-only virtual console by using the keyboard shortcut Ctrl+Alt+F3
At the
login:prompt type your username and press Enter.At the
Password:prompt type your user password and press Enter.
After you have logged in in the console type:
sudo apt remove linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic linux-headers-4.8.0-44-generic
sudo apt install linux-image-4.4.0-71-generic linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic
sudo reboot
Alternatively you can run the following commands to update initramfs for kernel version 4.8.0-44-generic :
sudo update-initramfs -u -k 4.8.0-44-generic
sudo update-grub
Immediately after the BIOS/UEFI splash screen during boot, with BIOS, quickly press and hold the Shift key, which will bring up the GNU GRUB menu. (If you see the Ubuntu logo, you've missed the point where you can enter the GRUB menu.) With UEFI press (perhaps several times) the Esc key to get to the GRUB menu. Sometimes the manufacturer's splash screen is a part of the Windows bootloader, so when you power up the machine it goes straight to the GRUB screen, and then pressing Shift is unnecessary.
From the purple GRUB screen select Advanced options for Ubuntu with the ↑ and ↓ keys and press Enter.
A new purple screen will appear showing a list of kernels. Select Ubuntu, with Linux 4.4.0-71-generic and press Enter.
Ubuntu will load the selected kernel and proceed to the login screen as usual.
Don't let Ubuntu update the kernel to the 4.8.0-44 version that caused the black screen again, or else you'll get the same black screen problem that you got before.
answered Mar 30 '17 at 11:56
karel
54.8k11119138
1
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
|
show 4 more comments
up vote
8
down vote
You are missing the initramfs for kernel version 4.8.0-44.
It looks like you got a kernel panic error message after updating the kernel in Ubuntu 16.04.1 to 4.8.0-44-generic. To fix it enter a text-only console and either replace 4.8.0-44-generic with the more stable default kernel version or run sudo update-initramfs -u -k 4.8.0-44-generic && sudo update-grub.
After the boot stops at the black screen, open a text-only virtual console by using the keyboard shortcut Ctrl+Alt+F3
At the
login:prompt type your username and press Enter.At the
Password:prompt type your user password and press Enter.
After you have logged in in the console type:
sudo apt remove linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic linux-headers-4.8.0-44-generic
sudo apt install linux-image-4.4.0-71-generic linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic
sudo reboot
Alternatively you can run the following commands to update initramfs for kernel version 4.8.0-44-generic :
sudo update-initramfs -u -k 4.8.0-44-generic
sudo update-grub
Immediately after the BIOS/UEFI splash screen during boot, with BIOS, quickly press and hold the Shift key, which will bring up the GNU GRUB menu. (If you see the Ubuntu logo, you've missed the point where you can enter the GRUB menu.) With UEFI press (perhaps several times) the Esc key to get to the GRUB menu. Sometimes the manufacturer's splash screen is a part of the Windows bootloader, so when you power up the machine it goes straight to the GRUB screen, and then pressing Shift is unnecessary.
From the purple GRUB screen select Advanced options for Ubuntu with the ↑ and ↓ keys and press Enter.
A new purple screen will appear showing a list of kernels. Select Ubuntu, with Linux 4.4.0-71-generic and press Enter.
Ubuntu will load the selected kernel and proceed to the login screen as usual.
Don't let Ubuntu update the kernel to the 4.8.0-44 version that caused the black screen again, or else you'll get the same black screen problem that you got before.
answered Mar 30 '17 at 11:56
karel
54.8k11119138
1
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
|
show 4 more comments
up vote
8
down vote
up vote
8
down vote
You are missing the initramfs for kernel version 4.8.0-44.
It looks like you got a kernel panic error message after updating the kernel in Ubuntu 16.04.1 to 4.8.0-44-generic. To fix it enter a text-only console and either replace 4.8.0-44-generic with the more stable default kernel version or run sudo update-initramfs -u -k 4.8.0-44-generic && sudo update-grub.
After the boot stops at the black screen, open a text-only virtual console by using the keyboard shortcut Ctrl+Alt+F3
At the
login:prompt type your username and press Enter.At the
Password:prompt type your user password and press Enter.
After you have logged in in the console type:
sudo apt remove linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic linux-headers-4.8.0-44-generic
sudo apt install linux-image-4.4.0-71-generic linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic
sudo reboot
Alternatively you can run the following commands to update initramfs for kernel version 4.8.0-44-generic :
sudo update-initramfs -u -k 4.8.0-44-generic
sudo update-grub
Immediately after the BIOS/UEFI splash screen during boot, with BIOS, quickly press and hold the Shift key, which will bring up the GNU GRUB menu. (If you see the Ubuntu logo, you've missed the point where you can enter the GRUB menu.) With UEFI press (perhaps several times) the Esc key to get to the GRUB menu. Sometimes the manufacturer's splash screen is a part of the Windows bootloader, so when you power up the machine it goes straight to the GRUB screen, and then pressing Shift is unnecessary.
From the purple GRUB screen select Advanced options for Ubuntu with the ↑ and ↓ keys and press Enter.
A new purple screen will appear showing a list of kernels. Select Ubuntu, with Linux 4.4.0-71-generic and press Enter.
Ubuntu will load the selected kernel and proceed to the login screen as usual.
Don't let Ubuntu update the kernel to the 4.8.0-44 version that caused the black screen again, or else you'll get the same black screen problem that you got before.
answered Mar 30 '17 at 11:56
karel
54.8k11119138
You are missing the initramfs for kernel version 4.8.0-44.
It looks like you got a kernel panic error message after updating the kernel in Ubuntu 16.04.1 to 4.8.0-44-generic. To fix it enter a text-only console and either replace 4.8.0-44-generic with the more stable default kernel version or run sudo update-initramfs -u -k 4.8.0-44-generic && sudo update-grub.
After the boot stops at the black screen, open a text-only virtual console by using the keyboard shortcut Ctrl+Alt+F3
At the
login:prompt type your username and press Enter.At the
Password:prompt type your user password and press Enter.
After you have logged in in the console type:
sudo apt remove linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic linux-headers-4.8.0-44-generic
sudo apt install linux-image-4.4.0-71-generic linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic
sudo reboot
Alternatively you can run the following commands to update initramfs for kernel version 4.8.0-44-generic :
sudo update-initramfs -u -k 4.8.0-44-generic
sudo update-grub
Immediately after the BIOS/UEFI splash screen during boot, with BIOS, quickly press and hold the Shift key, which will bring up the GNU GRUB menu. (If you see the Ubuntu logo, you've missed the point where you can enter the GRUB menu.) With UEFI press (perhaps several times) the Esc key to get to the GRUB menu. Sometimes the manufacturer's splash screen is a part of the Windows bootloader, so when you power up the machine it goes straight to the GRUB screen, and then pressing Shift is unnecessary.
From the purple GRUB screen select Advanced options for Ubuntu with the ↑ and ↓ keys and press Enter.
A new purple screen will appear showing a list of kernels. Select Ubuntu, with Linux 4.4.0-71-generic and press Enter.
Ubuntu will load the selected kernel and proceed to the login screen as usual.
Don't let Ubuntu update the kernel to the 4.8.0-44 version that caused the black screen again, or else you'll get the same black screen problem that you got before.
answered Mar 30 '17 at 11:56
karel
54.8k11119138
edited Nov 13 at 23:30
answered Mar 30 '17 at 11:56
karel
54.8k11119138
answered Mar 30 '17 at 11:56
karel
54.8k11119138
answered Mar 30 '17 at 11:56
karel
54.8k11119138
54.8k11119138
1
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
|
show 4 more comments
1
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
1
1
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
Remember that 16.04.2 (they weren't specific what version they installed, but it looks like .2) comes with kernel 4.8, not 4.4. It might be better to first try and boot the previous kernel from the GRUB menu and see if that works. Then I'd reinstall/update to 16.04.whatever they were trying to update to. Also, the last error message indicates a file system error.
– heynnema
Mar 30 '17 at 13:42
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
@heynnema The first line of the screenshot in the question says that user1900238 is using Ubuntu 16.04.1 which came with Linux kernel version 4.4, the same as the first 16.04 release.
– karel
Mar 30 '17 at 14:35
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
Ah, interesting... they're trying to run kernel 4.8 on 16.04.1... or trying to update to .2. It's not important, as they can't mount root due to a file system error.
– heynnema
Mar 30 '17 at 14:39
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
I got it working now. I went to grub options and than did update initramfs.. It even updated my kernel. Thanks guys, now it's working fine..
– user1900238
Apr 1 '17 at 13:18
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
@karel how did you determine that initramfs was missing? Inquiring minds want to know :-)
– heynnema
Apr 1 '17 at 13:27
|
show 4 more comments
up vote
1
down vote
Steps:
mount -o remount,rw /mkinitramfs -o /boot/initrd.img-{kerner_version}-generic {kernel_version}-generic update-grub Here {Kernel_version} is the kernel version number you take note of in step 5 (The Problematic kernel, latest installed one).
Reboot the System that is it, you're all set and ready to continue your work flow. Hopes That Helps.
answered Dec 22 '17 at 15:24
salafi
1263
add a comment |
up vote
1
down vote
Steps:
mount -o remount,rw /mkinitramfs -o /boot/initrd.img-{kerner_version}-generic {kernel_version}-generic update-grub Here {Kernel_version} is the kernel version number you take note of in step 5 (The Problematic kernel, latest installed one).
Reboot the System that is it, you're all set and ready to continue your work flow. Hopes That Helps.
answered Dec 22 '17 at 15:24
salafi
1263
add a comment |
up vote
1
down vote
up vote
1
down vote
Steps:
mount -o remount,rw /mkinitramfs -o /boot/initrd.img-{kerner_version}-generic {kernel_version}-generic update-grub Here {Kernel_version} is the kernel version number you take note of in step 5 (The Problematic kernel, latest installed one).
Reboot the System that is it, you're all set and ready to continue your work flow. Hopes That Helps.
answered Dec 22 '17 at 15:24
salafi
1263
Steps:
mount -o remount,rw /mkinitramfs -o /boot/initrd.img-{kerner_version}-generic {kernel_version}-generic update-grub Here {Kernel_version} is the kernel version number you take note of in step 5 (The Problematic kernel, latest installed one).
Reboot the System that is it, you're all set and ready to continue your work flow. Hopes That Helps.
answered Dec 22 '17 at 15:24
salafi
1263
answered Dec 22 '17 at 15:24
salafi
1263
answered Dec 22 '17 at 15:24
salafi
1263
answered Dec 22 '17 at 15:24
salafi
1263
1263
add a comment |
add a comment |
up vote
0
down vote
You have a file system error that caused your kernel panic. Unable to mount root. It might be because you're trying to run kernel 4.8 on 16.04.1, or a failed 16.04.2 update, or it might even be a bad hard drive, or one that needs to be reinitialized... but lets try this first...
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode (from the prior 4.4 kernel)
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the fsck command if there were errors
- type
reboot
Let me know if you can't do this, and I'll give you another method.
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with@heynnemaor I may miss them.
– heynnema
Apr 1 '17 at 13:29
add a comment |
up vote
0
down vote
You have a file system error that caused your kernel panic. Unable to mount root. It might be because you're trying to run kernel 4.8 on 16.04.1, or a failed 16.04.2 update, or it might even be a bad hard drive, or one that needs to be reinitialized... but lets try this first...
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode (from the prior 4.4 kernel)
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the fsck command if there were errors
- type
reboot
Let me know if you can't do this, and I'll give you another method.
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with@heynnemaor I may miss them.
– heynnema
Apr 1 '17 at 13:29
add a comment |
up vote
0
down vote
up vote
0
down vote
You have a file system error that caused your kernel panic. Unable to mount root. It might be because you're trying to run kernel 4.8 on 16.04.1, or a failed 16.04.2 update, or it might even be a bad hard drive, or one that needs to be reinitialized... but lets try this first...
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode (from the prior 4.4 kernel)
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the fsck command if there were errors
- type
reboot
Let me know if you can't do this, and I'll give you another method.
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
You have a file system error that caused your kernel panic. Unable to mount root. It might be because you're trying to run kernel 4.8 on 16.04.1, or a failed 16.04.2 update, or it might even be a bad hard drive, or one that needs to be reinitialized... but lets try this first...
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode (from the prior 4.4 kernel)
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the fsck command if there were errors
- type
reboot
Let me know if you can't do this, and I'll give you another method.
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
edited Apr 1 '17 at 13:41
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
answered Mar 30 '17 at 13:50
heynnema
17.1k22053
17.1k22053
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with@heynnemaor I may miss them.
– heynnema
Apr 1 '17 at 13:29
add a comment |
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with@heynnemaor I may miss them.
– heynnema
Apr 1 '17 at 13:29
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
Thanks for the tip. I did go through grub mention option and logged into previous version and updated initramfs.. It even updated my kernel. Thanks, now it's working fine..
– user1900238
Apr 1 '17 at 13:19
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with
@heynnema or I may miss them.– heynnema
Apr 1 '17 at 13:29
@user1900238 so what did you finally end up with? What version Ubuntu? What version kernel? Please begin comments directed to me with
@heynnema or I may miss them.– heynnema
Apr 1 '17 at 13:29
add a comment |
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%2f898449%2fkernel-panic-and-unable-to-boot-ubuntu-16-04-after-updating%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
1
you may want to add which version you are updating from and to which version.
– saviour123
Mar 30 '17 at 11:28
And this is why I never do in-place upgrades, regardless of the OS. I always clean install instead of upgrade.
– Android Dev
Mar 30 '17 at 11:56