Bugzilla – Bug 128702
suspend broken by selecting the wrong swap partition: "swsusp: FATAL: cannot find swap device"
Last modified: 2005-12-13 13:19:18 UTC
I updated from 9.3 GM to 10.0 GM. powersave -U had worked before but did not work after, reporting "swsusp: FATAL: cannot find swap device". With some luck and Google help I noticed that the Grub entry for the system had been changed from resume=/dev/hda4 to resume=/dev/hda3. After I changed the boot menu entry and rebooted, suspend worked. My disk layout is as follows, with the 10.0 system on hda1 and swapping on hda4, and another SL on hda2 and swapping to hda3. Disk /dev/hda: 6495 MB, 6495068160 bytes 255 heads, 63 sectors/track, 789 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 522 4192933+ 83 Linux /dev/hda2 * 523 718 1574370 83 Linux /dev/hda3 719 755 297202+ 82 Linux swap / Solaris /dev/hda4 756 789 273105 82 Linux swap / Solaris
Created attachment 54318 [details] y2logs.tgz - the update was performed on Oct 13
The problem is that YaST recreates the bootloader sections from scratch. And it sets the largest swap partition to be used for suspending. I changed it in SVN so that largest used swap partition is used.
*** Bug 138231 has been marked as a duplicate of this bug. ***