Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in:
I've got the same problem after I used gpart to adjust my space. I might
have changed the size of the swap partition after the operation. The
swap partition failed to mount after the machine resume from sleep.
Machine automatically restart with activating swap fail error... The
problem loops every
Swap partition failed to mount on resuming from hibernate with gutsy.
[EMAIL PROTECTED]:~$ sudo vol_id /dev/sda12
ID_FS_USAGE=other
ID_FS_TYPE=suspend
ID_FS_VERSION=s1suspend
ID_FS_UUID=50e4bada-e2bc-4cc4-b6a6-ce280decd803
ID_FS_UUID_ENC=50e4bada-e2bc-4cc4-b6a6-ce280decd803
ID_FS_LABEL=
I had the very same issue as kenw: the UUID in /etc/fstab didn't match
the vol_id on the swap partition
It is just after an upgrade from Xubuntu 7.04 to Xubuntu 7.10.
--
Swap fails to activate in gutsy
https://bugs.launchpad.net/bugs/133564
You received this bug notification because you are a
I had the problem where swap wasn't getting activated on boot, but my
issue was that the UUID in /etc/fstab didn't match the vol_id on the
swap partition.
How that happened I don't have any idea, but setting /etc/fstab to match
the vol_id fixed it.
--
Swap fails to activate in gutsy
Have the exact same problem. Its not a fstab/uuid issue. What I've
noticed is that when it fails and I do a sudo vol_id /dev/sda5. the
output has ID_FS_TYPE=suspend instead of ID_FS_TYPE=swap.
Once I do a mkswap and then add the new uuid to the fstab file, it
starts to work on reboot until for
Same here!
There's a thread in ubuntuforums too:
http://ubuntuforums.org/showthread.php?t=563265
[EMAIL PROTECTED]:~$ sudo fdisk -l
Disco /dev/sda: 80.0 GB, 80026361856 byte
255 heads, 63 sectors/track, 9729 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0x54e3cf5c
