Package: dracut Version: 043-4 Severity: grave I'm not sure whether dracut or systemd is really the right place to take care of this issue. I can't fully prove that my recent experiences of ext4 corruptions with ro-remount shortly after resuming from hibernate are related to this.
But here is a journalctl log out of dracut which seems to show that we should make sure that no fsck takes place before the potential process of resuming from hibernation is started. In the Unit section of the service files the rules of Before and After somehow make sense to me, but I have no trust right now, specially if the systemd-fsck@[diskid] is the one run or systemd-fsck-root… Anyway I think that no fsck for any device should be done before trying to resume from hibernation, because the memory image might have mounted it already with open files. Workaround would be chaning passno value from 1 to 0 in /etc/fstab for root or passing fsck.mode=skip as kernel cmdline or masking of systemd-fsck* services. I would be pleased to get responses how to go on with this, even if I'm not right with my suspicion. Regards, Kai Oct 23 18:35:39 hn systemd[1]: Started Cryptography Setup for sda1_crypt. Oct 23 18:35:39 hn systemd[1]: Reached target Encrypted Volumes. Oct 23 18:35:39 hn systemd[1]: Found device /dev/mapper/sda1_crypt. Oct 23 18:35:40 hn dracut-initqueue[228]: Scanning devices dm-0 for LVM logical volumes hn/root hn/swap_1 Oct 23 18:35:40 hn dracut-initqueue[228]: inactive '/dev/hn/root' [109.78 GiB] inherit Oct 23 18:35:40 hn dracut-initqueue[228]: inactive '/dev/hn/swap_1' [4.70 GiB] inherit Oct 23 18:35:40 hn systemd[1]: Found device /dev/mapper/hn-root. Oct 23 18:35:40 hn systemd[1]: Starting File System Check on /dev/mapper/hn-root... Oct 23 18:35:40 hn systemd-fsck[756]: /dev/mapper/hn-root: recovering journal Oct 23 18:35:40 hn systemd[1]: Found device /dev/disk/by-uuid/c92c9791-09c1-4745-a685-ff9dc41c20b9. Oct 23 18:35:40 hn systemd[1]: Starting Resume from hibernation using device /dev/disk/by-uuid/c92c9791-09c1-4745-a685-ff9dc41c20b9... Oct 23 18:35:40 hn systemd-hibernate-resume[773]: Could not resume from '/dev/disk/by-uuid/c92c9791-09c1-4745-a685-ff9dc41c20b9' (252:2). Oct 23 18:35:40 hn systemd[1]: Started Resume from hibernation using device /dev/disk/by-uuid/c92c9791-09c1-4745-a685-ff9dc41c20b9. Oct 23 18:35:40 hn systemd[1]: Reached target Local File Systems (Pre). Oct 23 18:35:40 hn systemd[1]: Reached target Local File Systems. Oct 23 18:35:40 hn systemd[1]: Reached target System Initialization. Oct 23 18:35:40 hn kernel: PM: Starting manual resume from disk Oct 23 18:35:40 hn kernel: PM: Hibernation image partition 252:2 present Oct 23 18:35:40 hn kernel: PM: Looking for hibernation image.
