Kernel Panic after reboot because no new kernel was installed during the upgrade
Bug #96196 reported by
Harish Naik
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
High
|
Michael Vogt |
Bug Description
Binary package hint: update-manager
Everything went smoothly until the cleanup stage. During the clean up stage, it gave an error and a 'Report Bug' option. When I clicked it the system froze. I had to terminate the application. Then I launched Adept again and ran Full-Upgrade, Fetch Updates Full Upgrade again. At reboot, I get "Kernel Panic : cannot mount fs" or something.
Harish Naik
description: | updated |
Changed in update-manager: | |
importance: | Undecided → High |
status: | Needs Info → Confirmed |
Changed in update-manager: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I had the same problem. The update tool showed a dpkg error in subprocess while removing old packages such as old kernel etc. Then it crashed. In fact old kernel 2.6.17-11 was removed, but GRUB was not amended accordingly.
Booting with 2.6.17-10 was possible, perhaps the update tool was crashed before removing 2.6.17-10. But, restricted-modules for 2.6.17-10 were not installed. I was a bit in trouble to fix this, because WLAN was not working and manuals for editing GRUB are usually found in the web.
Since I´m lazy I installed the restricted-modules for 2.6.17-10 from the Install-CD of 6.10 and thereafter with working WLAN I reinstalled the new kernel 2.6.20 whereas GRUB was updated correctly.