Bugzilla – Bug 216072
yast2 bootloader configuration not working properly
Last modified: 2007-10-09 10:47:38 UTC
I have no YaST logs because of but 216070, so I will describe the problem. Machine is an IBM R50p internal hdd + USB hdd. I tried a new installation. As always as bootloader location /dev/sda (internal hdd was chosen). I always change this to /dev/sdb (USB hdd), but this time, the menu did not offer /dev/sdb as boot loader location (only /dev/sdb1, /dev/sdb2 was possible). I was also not pssible the change the order of the disks (it complained about no bootloader location selected, even if it was selected or configured in the edit files dialog). I always used (hd1) /dev/sda (hd0) /dev/sdb This chenges were only possible by editing the configuration files (/boot/grub/menu.list, /etc/grub.conf and device.map). This is not a big problem for me, because I can edit the files by hand, but up to 10.2 alpha5 the yast module worked just fine.
mhorvath: If there is bug in bootloader, odabrunz is the correct assignee
Created attachment 104863 [details] yast2 logs The problem still exists in beta2
Yes, what you are trying to do isn't possible. You currently have to manually edit the device.map file and then you should be able to select as you wish.
Why not possible? It works with 10.1, why shouldn't it be possible in 10.2?
The bootloader configuration for grub was undergoing major internal changes for 10.2. For 10.2 we had to drop the device map expert editor. You need to use the generic editor in yast2-bootloader for bootloader files instead, and edit the device.map file manually there. For 10.3 and SLES10 SP1, we will see what we can do about this.
So we would need a way to let the user choose the MBR of which disk he likes to boot from. This makes sense in certain configurations.
Stefan, what's the status on this one? I sounds like a potential feature/FATE request to me.
Stefan, please transfer into FATEh
done: #302875 resolved wontfix for 10.3