UUID can change onswap breaking swap mount and Hibernation

[Andrew Waldram]

Binary package hint: linux-source-2.6.20

There appears to be a number of reported bugs that skirt round this issue
bug 103672 could be related

in a nutshell

normal linux maintenance activity can result in the UUID of the swap partition altering this leads to various symptoms

such as

unable to enter hibernation (pc returns to password prompt)
unable to resume from hibernation
swap partition doesn't mount on boot
machine appears hung with flashing cursor

I have seen reports in the forum of swap UUID changing with reboots

The swap UUID can change
a) If you use uswsusp
b) If you install another Linux distribution (swap is often reformatted).
c) sharing swap windows/linux

It might be possible to do something about by making it recreate the swap with the same UUID as it had before.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[Andrew Waldram (andrew-waldram)]

Ok

Linux sidney 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

The logs you've requested will show that I'm not using UUID for my swap as why would I when I know its broke.??

Note my system is configured to NOT exhibit this issue.(not using UUID for swap)

I raised the Bug report so there was a place holder to correct this behavior for other users who may not be as savvy as me and not know why their swap wont mount any more. Fixing this will also give you Folks a break next time you swap ATA drivers mid release cycle

[Andrew Waldram (andrew-waldram)]

and lspci

[Andrew Waldram (andrew-waldram)]

actually having done a google search against launchpad

there has been a multitude of bugs reported for this dating back to dapper/edgy upgrade

bug 66637
bug 105490
bug 67437
bug 65798
and maybe
bug 48514

also
https://answers.launchpad.net/ubuntu/+question/7434
http://ubuntuforums.org/showthread.php?p=1683612
http://ubuntuforums.org/showthread.php?p=2740699

Worryingly the state varies from confirmed/undecided to confirmed/high

Scott James Remnant is working on 66637

This looks like the hidden bug from hell...;-)

[Andrew Waldram (andrew-waldram)]

and
bug 90526
bug 104789
bug 70626

And I'm sure many more this doesn't include those that don't explicitly mention swap and UUID.

[taj (othertaj)]

The same thing happened to me, after a dapper-edgy-feisty upgrade swap was not mounted at all at first, then I managed to set it right, and it was mounted twice. (see https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/96715).
Then yesterday I suddenly did not have a swap anymore (just out of the blue, I had not changed anything). The UUID appeared to have changed for some reason (this bug).
Have to mention that I also suffer from another system that unpredictably hangs at bootup, with message /bin/sh: can't access tty; job control turned off (initramfs), (see https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/96084).

All major problems point to linux-source-2.6.20. My faith in this kernel version for ubuntu has been totally lost. I think that someone has to have a serious look at this kernel and the UUID system. I wish I could do this mself.

[Sitsofe Wheeler (sitsofe)]

The more I think about this the more I think that mounting swap by label makes more sense...

[Sitsofe Wheeler (sitsofe)]

Setting back to New because information was provided.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!