Can't write on some partition after suspend.

I’m not sure if it is the right section. Sorry if is not.

Some partitions are acting like SJW’s and are questioning my privilege as a user.rotfl! And I can’t write or copy sometime. I did an upgrade to 15.2 and the problem is still present.

And any program to test the health of a drive to suggest?

I bit more information might be useful. What were you doing? What persuaded you that there was a problem?

If possible, give enough information so that people can test whether they are having the same problem.

My drives are becoming read-only after a suspend. And after reboot everything come back to the normal. If you are excluding the fact that the suspend mode is useless, everything else is ok.

Fair enough.

Everything was okay here on the one time where I accidentally used suspend. But I normally avoid it. I don’t trust it.

I use resume regularly since 2014. It’s really great:

erlangen:~ # journalctl  -b -q --no-hostname -o short-monotonic -u systemd-suspend.service 
[34982.301408] systemd[1]: Starting Suspend...
[34982.310391] systemd-sleep[17742]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
[34982.311134] systemd-sleep[17733]: Suspending system...
[34983.499236] systemd-sleep[17733]: System resumed.
[34983.500135] systemd-sleep[17794]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
[34983.501157] systemd[1]: systemd-suspend.service: Succeeded.
[34983.501392] systemd[1]: Finished Suspend.
erlangen:~ # 

I only wish the monitor would resume as fast as the system does.:wink:

This command do nothing on my system.

I used suspend and hibernate in the past without any problem. But hibernate need a generous swap space to work properly.

Is it normal?

sinatra@linux-t4sq:~> systemctl hibernate
Failed to hibernate system via logind: Sleep verb not supported

Run the above as root.

Show output of

cat /sys/power/state
cat /sys/power/disk