Ubuntu 19.10 to 20.04 upgrade getting stuck with fsck check

Bug #1888372 reported by Martin Goik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The bug among with ist underlying system is being described in detail at https://askubuntu.com/questions/1260677/ubuntu-20-04-upgrade-getting-stuck-with-fsck-check.

The system is currently only bootable in rescue mode. As being described a regular boot shows an endless spinner following the grub menu stage during the boot process.

All packages are current to 20.04.

Revision history for this message
Martin Goik (goik) wrote :

Additional info: On a fresh 20.04 re-install rebooting works fine based on the installation kernel 5.4.0-26. After upgrading the current 5.4.0-42 kernel fails to boot with the described behavior.

But after interrupting using the power-off button and choosing the still installed 5.4.0-26 installation kernel after power-on from the grub menu the boot process continues flawlessly.

I thus suspect a kernel related problem. Off-distribution kernels e.g. 5.7.9 don't work either.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1888372/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1888372

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: eoan
Revision history for this message
Martin Goik (goik) wrote :

Problem vanished after second re-install. Unable to reproduce.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.