Description of problem: Mageia 4.1 fails to boot when swap UUID is changed. Another Linux Distribution may reformt the swap UUID. Usually in another Linux Distribution this is solved by running $ blkid, to obtain the corrected UUID for the swap partition, then changing the UUID in etc/fstab, then updating the grub bootloader from the distro that controls grub bootloader/grub menu. However, on Mageia 4...the boot still fails with the former swap UUID being called (even after changes made in fstab). I do have two HDDs with a swap partition on each. Mageia etc/fstab lists both of these partitions. The UUIDs in fstab are correct due to my correcting the one altered by another distro. (I expect that having two HDDs and two swap partitions is not relevant to the problem). Version-Release number of selected component (if applicable):4.1 How reproducible: I have seen other people with this problem online, but complicated soltutions and lengthy discussions for what would be a normal and regular occurrence with multi-boot systems. Steps to Reproduce: 1. Install Mageia 4.1 with a root partition & swap partition 2. Install another Linux distribution allocating the same swap partition as Mageia installation has used. 3. run $ blkid from terminal of any distro to find the correct UUID for swap partition, then alter /etc/fstab with correct UUID, $ sudo update-grub from the distro that controls grub 4. reboot Mageia 4.1 from grub2 menu... Reproducible: Steps to Reproduce:
CC: (none) => zayd_depaor
There are two solutions: 1. Re-build initrd by running dracut -f in the affected installation. (You may need to chroot into it if you can't boot it) 2. Change the UUID of your swap partition back to what it should be. (The distribution that changed it is to blame not Mageia) Mageia does not change existing swap UUIDs on install. You can change the swap UUID with: mkswap -U $swapuuid /dev/sdXY
CC: (none) => zen25000
(In reply to Barry Jackson from comment #1) > There are two solutions: > 1. Re-build initrd by running dracut -f in the affected installation. (You > may need to chroot into it if you can't boot it) > > 2. Change the UUID of your swap partition back to what it should be. (The > distribution that changed it is to blame not Mageia) Mageia does not change > existing swap UUIDs on install. > > You can change the swap UUID with: > mkswap -U $swapuuid /dev/sdXY Yes thanks Barry, I did this mkswap -U method of changing the UUID back to the previous and now is booting fine again after sorting fstab and running grub, I firt had to learn that tune2fs command only works on ext files though! ...but I think Mageia developers need to sort this out so people don't have jump through these hoops. It is resolved for me, but I say the bug still remains until you don't have to go through this process.
(In reply to Zayd Depaor from comment #2) > It is resolved for me, but I say the bug still remains until you don't have > to go through this process. Good - glad it's working again. The other distro is mainly to blame as it should not change the UUID of an existing swap, however it's not ideal as you say for this to break the boot of Mageia. Re-assigning to Colin (at his suggestion ;)
Assignee: bugsquad => mageia
Whiteboard: (none) => MGA5TOOSeverity: major => normal
I have a similar problem. On sdb mag4 is installed with its / , swap, home and a 2nd swap on sda5. I replace sda with a new disk and mga5 alpha. I remove the 2nd swap in /mga4/etc/fstab I could boot on mga5 or mga4 with grub installed on sda by mga5, everything was fine until I discover that grub2 had replaced grub. Then it was impossible to boot on mga4. The system is claiming for a swap UUID=6240e-.... I have searched in /etc/* and /boot/* and mga4/etc/* and mga4/boot/*... The only file where I have found UUID=6240e-... is /mga4/etc/fstab.old Is there another file where this uuid is hidden? The 3 last lines of the log file are: [ 4.050994] hid-generic 0003:045E:0040.0001: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.2-1/input0 [ 33.725488] dracut Warning: Could not boot. [ 33.739785] dracut Warning: /dev/disk/by-uuid/6240e08f-87f0-4cd2-8eb2-3d0f83461545 does not exist + '[' -f /run/initramfs/init.log ']' With the option rd.debug, I can see dracut looping to search this non existing swap file. I have removed all the swap files from /mga4/etc/fstab: Same result.
CC: (none) => jarillon
I have already reported this in https://bugs.mageia.org/show_bug.cgi?id=14035#c2
I have reported how it is installed in https://bugs.mageia.org/show_bug.cgi?id=14759#c4 I have found 2 symbolic links broken in /mga4/boot lrwxrwxrwx 1 root root 29 févr. 10 2014 config -> config-3.10.28-desktop-1.mga3 lrwxrwxrwx 1 root root 33 févr. 10 2014 System.map -> System.map-3.10.28-desktop-1.mga3 This mga4 is an update of mga3 and these 2 links have not been updated! I have vmlinuz, config, System-map... with these releases: config-3.12.13-desktop-2.mga4 config-3.12.18-desktop-1.mga4 config-3.12.20-desktop-1.mga4 config-3.12.21-desktop-2.mga4 config-3.12.25-desktop-3.mga4 config-3.14.18-desktop-3.mga4 config-3.14.23-desktop-1.mga4 I have recreated the 2 links with -3.14.23 releases: Always the same problem... Nothing seems wrong in /boot/grub2/grub.cfg
Version: 4 => CauldronWhiteboard: MGA5TOO => MGA4TOO
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=12305
*** Bug 14861 has been marked as a duplicate of this bug. ***
CC: (none) => fri
possibly dup of bug 12305
CC: (none) => eeeemail
I think it's fixed now (see bug 12305). Please reopen if it's not.
Status: NEW => RESOLVEDResolution: (none) => FIXED