I’ve created some new leap 42.2 partitions on a secondary disc and hence need to reinstall the boot loader to get at them. The new configuration file does not get written. It appears as if the boot loader software fails to get to the point where it actually writes the file. I’ve had a look in /var/log/YaST2 and found this:
bootloader/udev_mapping.rb:72 Cannot find udev link to satisfy mount by for /dev/sdc
/dev/sdc is the disc holding the main partition I use, but not the one the configuration file is being written to.
It’s some time since I installed 42.2, so I cant remember if I’m using a clean install or if it’s a clone of another partition; so it’s possible that the UUID of /dev/sdc has been changed since installation. I’ve tried to find a configuration file containing the current UUID - in addition to grub.cfg - but can’t find one.
Anyone have any ideas?
First – I am unclear what the boot loader has to do with getting at partitions. Normally, one would mount the partitions manually, or add an entry to “fstab” so that they are automatically mounted at boot.
Second – perhaps that “/dev/sdc” actually refers to the USB installer that you used to install 42.2 (assuming that you used a USB). Assuming MBR booting, the Yast bootloader screen should have a place you can click to change the order of disks during booting. Try using that.
Sorry, I should have said; the partitions are alternative Leap 42.2 installations
/dev/sdc6 is my current active partition. I have just cloned this partition to 2 partitions on a new disk (/dev/sdb).
The problem is the configuration file isn’t being written when using the Yast boot loader module.
The grub configuration file in use was produced by a 42.1 installation (on a third disc, /dev/sda). The disk order in that is different to what would be produced by the 42.2 installation on /dev/sdc6. I have changed the default boot partition so that if I boot unattended then the /dev/sdc6 partition is the one booted, but I would like to produce a boot configuration file from /dev/sdc6.