** Description changed: - Binary package hint: ubiquity - I installed Ubuntu Intrepid on a machine, and then made a second installation (the second time using a Hardy Live CD, I was not able to use Intrepid the second time due to bug 333584 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/333584 ). The second installation involved repartitioning, and when I returned to my first installation, the UUID of the swap partition had been changed, which meant that swap was no longer available, and hibernate no longer worked. The original UUID was: 441b1300-b765-4600-813b-fd2c03e917e6 The new UUID is: 441b13b7-6546-813b-fd2c-03e917e617e6 The striking similarities between these number make me think something funny is going on, which is why I bothered to post them. Assuming the hexadecimal digits correspond to a simple array of bytes, it looks like you can generate the second UUID by this algorithm: 1) create a buffer containing the first UUID 2) set pointer1 and pointer2 to position 0 3) if byte at pointer1 == 0, increment pointer1, and go to step 3 4) copy byte at pointer1 to pointer2 5) increment pointer1 and pointer2 6) go to step 3. The other UUID on my first installation system, i.e. for the root partition, was not changed, but it did not contain a '00' in it either, so by the above process you would not expect it to change. (Also the - root partition didn't change its starting cyclinder, only the end + root partition didn't change its starting cylinder, only the end cylinder, whereas the swap partition probably had to be created from scratch). As mentioned above, this happened in Hardy, not Intrepid, and it looks like it could well be a libparted bug or something like that. + + + This was fixed in partman-basicfilesystems 62ubuntu2 in jaunty: + + http://bazaar.launchpad.net/~ubuntu-core-dev/partman- + basicfilesystems/ubuntu/revision/574 + + I've backported this change to hardy-proposed: + + http://bazaar.launchpad.net/~ubuntu-core-dev/partman-basicfilesystems + /hardy-proposed/revision/562 + + TEST CASE: Perform an installation on a blank disk, then set the UUID of + the swap partition to one containing at least one zero byte; the UUID + provided by the reporter of this bug will do fine. You can do that like + this, assuming that the swap partition is /dev/sda5: + + sudo swapoff /dev/sda5 + sudo mkswap -U 441b1300-b765-4600-813b-fd2c03e917e6 /dev/sda5 + + Having done this, reboot and do another installation overwriting the + previous one's root filesystem and just using the existing swap + partition; you'll need to use the manual partitioner to do this + properly. After rebooting, run 'sudo vol_id -u /dev/sda5' and confirm + that the UUID shown is exactly that which you set previously. + + REGRESSION POTENTIAL: It might be worth making sure that installations + with a fresh swap partition (i.e. no UUID to preserve) keep on working.
-- UUID of existing swap partitions are changed https://bugs.launchpad.net/bugs/336992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
