Ubuntu on NVMe SSD, many errors after ‘apt upgrade’


  • Did update BIOS (MB: Asus Z390-F)
  • Did update NVMe SSD firmware (Samsung 970 EVO Plus, 500G)
  • Did run memtest86 for hours (after the problems happened: is OK)
  • The MB (motherboard) has nothing else (no CD, no graphic card…)

Ubuntu install ( The SSD was supposed to be dedicated to Ubuntu 18.04 )

  • Installed fresh Ubuntu 18.04.3
  • Selected “Update while installing” + “Install 3rd party drivers…”
  • Did manual partitioning, all ext4 (then tried also “Erase disk and install”)
  • → Install had a “crash”, is “sorry” and “click to reboot”

So, tried again, the whole thing, without “Update while installing” & “Install 3rd party drivers…” (removed the network to be sure)

  • this time it went through
  • Then did apt update ; apt upgrade
  • Reboot
  • Then after a while, using Ubuntu GUI, suddenly pages and pages of that

enter image description here

get displayed. Had to reset the PC.

My thoughts were for the NVMe SSD… but…

Windows 10 trial-install. So I installed Windows 10 (the free ISO) to confirm the problem is the SSD (Samsung supports only Windows)

  • taking the whole disk,
  • creating as many partitions as what was on Ubuntu
  • did the MS updates
  • did a stress test on all partitions, copying files over and over, filling the partitions
  • rebooted many times
  • → No errors anywhere, nothing in the s.m.a.r.t log (Samsung magician)

Therefore, it seems hard to blame the SSD.

Ubuntu 19.04 install. Then, on the data partitions created in Windows (except the one where Windows is) I installed Ubuntu 19.04 (not 18.04), thus these parts went from ntfs to ext4.

  • All went fine
  • Did apt update && apt upgrade
  • Reboot
  • Using Ubuntu,
  • → then same as before, pages and pages of the same pic above
  • → Reboot: goes to Grub “shell”

Booting (from BIOS) to Windows is OK. Ubuntu boot goes to grub shell.

Not sure what to do next …

  • could be that the Ubuntu upgrade affects Grub (due to NVMe SSD)?
  • could be a bad SSD, but in that case why Windows has no problem?
  • both 18.04.3 and 19.04 use the kernel 5.0.x, could that be linked to the problem?