Created attachment 253602 [details] dmesg I believe there is a problem with USB devices not being properly handled when waking the system after using /usr/sbin/zzz. My experience has been that the system behaves as if the device has been unplugged -- it can no longer access it. And when trying to use the device on a subsequent reboot, the system complains that the device was improperly dismounted. I do a fsck when this happens, which finds no problems. In my case, the device is a 7200 rpm 2TB Seagate SATA drive, with a SATA to USB adapter. It has the GPT partitioning scheme. The partition I keep having trouble with is a vanilla UFS partition that I use to back up my home directory with rsync to avoid having just one copy of a lot of recent work. The workaround is to umount the drive before putting the system to sleep and remount it after awakening the system.
(In reply to donaldcallen from comment #0) Did you collect the dmesg after resuming from S3? If not, please attach that, so we can see what's happening with the device. I'd expect to see USB devices being detached during suspend to S3.
(In reply to Mark Johnston from comment #1) I didn't and I'm afraid that I no longer can. After experiencing this problem plus too frequent system crashes due to problem with the AMD gpu driver plus a softdep bug that surfaced due to those crashes, I restored Arch Linux on the system in question. Sorry.