Description of problem: Inintrds created by dracut won't resume from disk if they're host-only. Setting "hostonly=no" in /etc/dracut.conf has no effect; only the command-line option works. It's possible to make the system resume from disk if the device is added manually to a .conf snippet in /etc/dracut.conf.d. Version-Release number of selected component (if applicable): dracut-034-19.git20131021.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Run 'systemctl hibernate' and wait until it saves the image to disk 2. Power on the computer Actual results: Hibernation image is completely ignored on boot. Expected results: The system should at least check if there's a hibernation image on the swap device and resume from it, if applicable. Additional info: * Workaround 1: dracut -f --no-hostonly --regenerate-all * Workaround 2: add the swap partition manually to a .conf snippet in /etc/dracut.conf.d (add_device+=" /dev/<swap partition> ") * Partition table is GPT (not sure if this matters)
please attach your /etc/fstab please attach the output of: # dracut -f --debug
Created attachment 825569 [details] fstab
Created attachment 825570 [details] dracut-debug.log
The swap entry is commented out because systemd tries to enable it twice, slowing down boot by 20 seconds or so.
(In reply to enthymeme from comment #4) > The swap entry is commented out because systemd tries to enable it twice, > slowing down boot by 20 seconds or so. Well, dracut wants that entry. No swap -> no resume.
So I have to choose between snail-slow boot and working resume from disk? I wouldn't even care about boot times if hibernation wasn't half-broken.