Undocumented so far. /etc/default/grub has a line GRUB_CMDLINE_LINUX="resume=UUID=192aa59f-0741-4236-b2e4-32d6d32e019a rhgb quiet radeon.dpm=1" #sda2 On a system with more than one disk and more than one Linux system the swap file on the other disk is pointed to by the resume=UUID. This same resume=UUID is pasted from the /etc/default/grub/ is within the /boot/grub2/grub.cfg What happens is the following. If the other swap file becomes reformatted, renamed or missing, The system will wait 1.5 minutes for that swap file to be mounted, and then continues. Because it existed, and is now missing, the system has not taken note of this situation and the result is corruption of the installation.
As an aside On my computer, the corruption included the Microcode update to the quad core processors.
Bugzilla 1632799 /etc/default/grub resume /boot/grub2/grub.cfg example line linux16 /vmlinuz-4.18.12-200.fc28.x86_64 root=UUID=1690219b-8858-4c31-9789-e0f6a122aeaf ro resume=UUID=192aa59f-0741-4236-b2e4-32d6d32e019a rhgb quiet radeon.dpm=1 LANG=en_CA.UTF-8
Leslie, this is the Release Notes repository. You already (correctly) opened a bug in Bugzilla for this, there's no need to also open a docs issue - we don't cover known bugs in the Release Notes.
Metadata Update from @pbokoc: - Issue status updated to: Closed (was: Open)
No documention exists to state that a second swap file is used and when or how it is used.. It should be documented. I have F29 Gnome and F29KDE, if I cleanup one, I kill the other. I have not read in the install guide or release notes anything about this second swap file. I have already posted on other forums, an explanation of how to fix the problem. Where does that User guide explain about Anaconda using a second swap file?
Its closed, so one does not have to write about it.