Bug 128702

Summary:	suspend broken by selecting the wrong swap partition: "swsusp: FATAL: cannot find swap device"
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Martin Vidner <mvidner>
Component:	Update Problems	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	vicere
Version:	RC 4
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs.tgz - the update was performed on Oct 13

Description Martin Vidner 2005-10-17 13:27:58 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

Comment 1 Martin Vidner 2005-10-17 13:29:20 UTC

Created attachment 54318 [details]
y2logs.tgz - the update was performed on Oct 13

Comment 2 Jiri Srain 2005-10-21 10:38:48 UTC

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.

Comment 3 Martin Vidner 2005-12-13 13:19:18 UTC

*** Bug 138231 has been marked as a duplicate of this bug. ***