Which works fine - except that I am going to clone this machine
and this will fail on all the other disks, which have a different serial number. It needs to be
The part5 piece of this cannot be changed in yast. I selected that line, edited to /dev/sda5, and it came back the same way.
The part6 seems to be coming from /etc/fstab, changed it by hand to /dev/sda6, but it may not stay that way the next time yast runs. Similar changes to menu.lst did not survive a reboot, defaulting back to the “part5” syntax.
Is there some way to employ "/dev/sdX’ syntax using yast, or is this one of those cases where one must work around the “help” of the easy configuration tool?
Afaik that should of worked not actually tested, but I would confirm that the gui is actually changing the menu.lst(I have encountered similar not specifically this, but I do recall a manual edit sticking where a gui didn’t ). I’m not aware of a reason why a boot should be changing it back.
> Is there some way to employ "/dev/sdX’ syntax using yast, or is this one
> of those cases where one must work around the “help” of the easy
> configuration tool?
Go into the YaST partitioner and under settings change the default mount
by setting - that should take care of it for you.
Well that was strange. Did that, changed it to “by label”. and ended up with label mounts in fstab. This changed nothing in menu.lst. Went into the boatloader and selected the (now available) by label options, OK. Resulting menu.lst had
root=/dev/sda6
That is, not by label. Went into yast/bootloader again, reselected the same things, OK. On the second one it ended up with
root=/dev/disk/by-label/root
(root is the label of the partition). Which is fine. Will see now if it actually reboots.
Probably there should be a note in the bootloader section of Yast redirecting those of us without experience or ESP to the partitioner section to fix this. Normally I stay the heck away from GUI partition tools on working systems, since when they hiccup, those systems don’t usually work anymore!
> Probably there should be a note in the bootloader section of Yast
> redirecting those of us without experience or ESP to the partitioner
> section to fix this. Normally I stay the heck away from GUI partition
> tools on working systems, since when they hiccup, those systems don’t
> usually work anymore!
>
> Thanks.
That is bizarre - you may want to enter the details into a bug just so
it’s documented and can be fixed (assuming there isn’t a bug on it
already).
But glad that got you pointed in the right direction. I hadn’t thought
about the effects in menu.lst (which would be in the bootloader module
and not the partitioner). I went through something similar to this with
SLED in preparation for BrainShare, and had to (after the fact) fix this
on each system manually.