The Ryzen 7 based machine has a 2TB Maxio NVME SSD and nothing else, no HDD bay, thus necessitating exclusive use of the NVME for root, swap and home.
I have been experiencing a rather irritating problem, which detracts somewhat from the pleasure I am deriving from the sheer speed of the system.
If I attempt to use the ACPI sleep function, either by closing the lid, or by issuing the command:
- Code: Select all
systemctl sleep
when I try to use the system again, I find that the NVME drive does not "wake up". I get a console full of errors beginning with:
Aborting journal on device nvme0n1p2-0
followed by a whole series of errors all of which imply that the device is not being read as a result of an "io error". These are not really io errors but rather a situation whereby the device is not becoming available for normal rw access after the sleep is terminated.
I am not very familiar with the inner workings of ACPI and so on, but I was wondering if there is a way of running a script or other executable as part of the "waking up" procedure which ensures that the NVME drive is in the proper state, ie. mounted in read/write mode. I suspect that it is either in some sort of static state or else mounted in readonly mode, thus preventing normal resumption of services.
At the moment the only recourse I have is to shut the machine down instead of use the sleep function. Fortunately, the machine boots up very quickly, so I can live with it. However it would be great if I could resolve this issue.
The only other problem I found with this new machine was to do with the Realtek RTL8852 wifi adapter, but I seem to have resolved that one. (see another post I made on this forum.)
Does anyone have any bright ideas about this one? I have tried various additions to the kernel boot parameters as suggested in various Ubuntu, Arch and Fedora forums, but they seem to have no bearing on the issue, which I have been led to conclude is a case of the partitions being mounted in readonly mode on waking.