I can confirm that adding Before=local-fs.target to blk-
availability.service solved the issue for me. Now everything happens in
the correct order. I attached the shutdown journal for reference.
** Attachment added: "shutdown.txt"
(I wrote the comment before realizing that I could only attach one file
. Journal.txt contains both shutdown and boot sequence.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during
Thank you for looking into this. I have attached the journal of one
shutdown and boot. It seems like during boot, everything happens in the
correct order. As you pointed out, this is as expected due to the
"After" parameter in the service-files.
However, as you can see from the shutdown.txt file,
Public bug reported:
When using automatic suspend at reboot/shutdown, it makes sense to store
the suspend data on a separate partition to ensure there is always
enough available space. However this does not work, as the partition
gets unmounted before or during libvirt suspend.
Steps to
