wakeup from suspend mounts nvme disk as readonly and system crashes

[Filip Procházka]

Hi, I've bought a new NVMe and just finished a fresh install on my desktop of Ubuntu 20.04.2 LTS, I've previously had 18.04.something on the same hardware. On 18.04 suspend worked, on 20.04.2 it does not.

The normal suspend button did not work at all. The system went to sleep, but wakeup showed only error logs and after about a minute it auto-restarted. After some googling, I've found this command https://askubuntu.com/a/1237199/642027 and tried it. With that, the system showed the GUI after wakeup, and it looked like it might have worked, but the apps started crashing and I had to do a hard reboot.

I've configured my system to stream syslog to external storage which I believe helped me to capture the logs. I am attaching them, but I've stripped some parts. The "Failed to write entry, ignoring: Read-only file system" message is duplicated many times, alongside rsyslogd errors that it cannot write the logs to disk. Apart from that, most of the relevant logs should be there.

Motherboard: ROG STRIX X299-E GAMING, 90MB0U50-M0EAY0
CPU: Intel Core i7-7820X, BX80673I77820X
GPU: EVGA GeForce GTX 1060 GAMING, 06G-P4-6262-KR, 6GB GDDR5

I have no idea if this is the right place to report it. If not - sorry! https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate sent me here.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-48-generic 5.8.0-48.54~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 4 16:00:18 2021
InstallationDate: Installed on 2021-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

[Filip Procházka (fprochazka)]

I've just discovered https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889306/comments/12, and it looks like it **might** be related.

I have Seagate FireCuda 510 SSD, ZP2000GM30001 https://www.seagate.com/internal-hard-drives/ssd/firecuda-ssd/#specs

The drive claims it has "Storage Work Group Security Subsystem Class: Opal, Version 2.00" and according to https://wiki.archlinux.org/index.php/Self-encrypting_drives#Waking_up_from_suspend, this might not be supported out-of-the-box

[Filip Procházka (fprochazka)]

This https://askubuntu.com/a/576342/642027 made me check if I have the latest BIOS for my motherboard and it turns out I didn't.

I've upgraded my BIOS and the problem with the disk disappeared. Now suspend+wakeup works as expected.

This issue can be closed now.