Some users reported that they cannot boot after latest updates.
Reopened, because it has happened again. From a user:
today when turn on my Librem 13 it showed 30 updates to install. I gave permission to "restart and Install" the picture attached is what appears now when I turn on my laptop. I can access in safe mode...
Waiting for further info from the user.
I believe this is an isolated issue which was fixed, and is surfacing for users who didn't update for a long time (it happens for people who update via GNOME Software Center, AFAIK update via apt doesn't trigger the bug).
That's … odd. They should be calling the exact same thing. Can you provide the background etc. for your rationale?
Can you provide the background etc. for your rationale?
Well, the user managed to boot into rescue mode, from there they issued sudo apt update && sudo apt full-upgrade and got the following:
282 packages can be updated to see run 'apt list' upgradable E: dpkg was interrupted, you must manually run 'sudo dpkg -- configure -a' to correct the problem.
After they run sudo dpkg -- configure -a and right after that sudo apt update && sudo apt full-upgrade, the system started normally after restart.
Something happened while updating via GNOME Software Center to cause the interruption. This hasn't happened to users who update via apt (at least I didn't get any reports).
I did experience the same kernel panic as described above with brand new laptop at several occasion:
- When rebooting after setting up PureOS on a Librem 13 v2, out of the box
- When rebooting after upgrade to latest updates (kernel4.18) via Software Center
- When rebooting after setting up PureOS following fresh install
- When rebooting after upgrade to latest updates (kernel4.18) via apt with sudo apt update && sudo apt remove libavcodec-extra57 && sudo apt upgrade
At every occasion I just had to force shutdown and switch it back on. No need for any other action.
I have removed the 128 GB Intel SATA SSD and replaced it with a 500 GB Samsung 970 Evo NVMe M.2.
I did install PureOS from scratch and did not encounter any kernel panic.
Issue related to Intel SATA SSD?
I'm also experiencing this problem. After showing the Purism logo, the screen remains black for a couple minutes, then displays the same kernel panic.
I have a Librem13v4 with the 128GB SATA SSD.
Also, the kernel panic does not happen all the time! I'd say it happens 30% of the time. The rest of the time, the system boots normally.
I tried the multiple update commands in this thread, to no avail.
@mladen I reproduced the bug again while booting in verbose mode. The system sometimes hangs at Loading Linux 4.19.0-5-amd64, sometimes at Loading initial ramdisk.... Then after a couple minutes, the following line is shown:
error: failure reading sector 0x802 from `hd0'
and then the stack trace described above.
I ran some checks with the Disks utility, but the disk is looking ok.
So I reinstalled PureOS on the Librem13v4 again using the OEM usb key, and this time went for a apt full-upgrade directly, and the issue still occurs. I also tried installing PureOS using the live version and no swap, and after the installation, the problem occurs at every boot, without the couple minutes hanging time. Finally, I tried installing with the live version and hibernate swap (I think it's the default option when installing from the OEM usb key), and the behaviour is the same as originally (happens 30-40% of the time).
@mladen Is this still being investigated? It's kind of a disappointment to have to start a brand new laptop multiple times before it actually boots.
@mladen I just installed Ubuntu 19.04, sporting kernel version 5.0.0-25 and the issue persists!! The laptop fails to boot intermittently, the only difference is that the following error message is displayed before the panic stack trace
error: failure reading sector 0x802 from `hd0' Press any key to continue...
which was also displayed with PureOS when quiet mode was disabled.
This may indicate that your disk is failing. Start a live media (PureOS or Ubuntu) and check it for errors:
If you run "Self-Test" from GNOME Disks then I do not see any other course but to try another disk. If your device is still under warranty contact Purism support, we'll handle there. (I see that your laptop is Librem.)