Failure to boot due OS or SWAP uuid mismatch: workaround if using grub legacy
 

This is NOT a [solved]

It's been discussed ad infinitum on usenet as well as in web hosted groups that for example when another distro is installed and that installation RE-creates the swap and thus gives it a new UUID the next boot of Mageia will likely fail because it cannot do a resume or such. There seems to be no shiortage of other related problems especually on multi-OS boxes or when using dd [as I do ALL THE TIME]. In my case I'm tinkering with v-5a2 but I've seen this on 4.x as well but only on Mageia systems. It has to do with the use of uuid but it probably also involves the way it is used in service.

The short of the long is that I found a quick workaround *IF* using grub legacy, something similar might be devisable with other loaders, I use only grub legacy.


- bail out of the grub menu [hit 'c']

- do [i use partition 5 on this one]

grub > root (hd0,4)
grub > kernel /boot/vmlinuz root=/dev/sda5
grub > boot

this completely sidesteps the initrd command & argument and worked on MY setup

HTH

I hope all distros stop making this uuid crap mandatory instead of an option

you are really barking up the wrong tree here.
simply don't create a swap partition when installing; you can add it to your /etc/fstab manually later.
no need to mess with grub or any other bootloader.