Hi!
I have a multiboot multidrive system with open Suse 11.0 on partition 11 and 12 of my first drive.(sda11 and sda12)
As I have encountered a major Ubuntu drive designation bug when re-installing Hardy after having installed Suse 11.0. (again) and not realising the problem until I installed Ubuntu’s grub on sdc1 to follow the “faulty” partitionner scheme. This caused me to be incapable of booting into any OS: Suse, Windows or Ubuntu (yet when I reverse my bios order it’s confirmed that windows still boots fine and my partitions appear to have things installed at least seen graphically in gparted).
My other linux OS were designated a /boot partition on the 1st drive (IDE) and in the past, Gutsy Ubuntu’s grub was able to list all my OS entries fine so that is why I prefer to install Ubuntu last. But now Ubuntu switched my drive sda to sdc and (second drive SCSI) sdb to sda and (3rd drive SCSI) sdc to sdb!!! I thought this was some new installation approach (since I am still a relative newbie) and I forgot that /boot and grub must be on the first drive, so I went along with the faulty alternate install of Hardy! Note: Suse designates the 1st drive as sdc as well not sda, and I put it’s grub on sdc1 during suse install but for some reason Suse on its own, could properly boot at that point!!
So a long story short, after I will try to re-install Ubuntu correctly (it seems the installer changes its designation of drives at each reinstall, so I might get the right one again!) is there a way of getting my Suse bootable again without re-installing a 3rd time??? I can’t count on Ubuntu’s grub or can I? since my /boot partition was automatically formatted during the ubuntu install in order to have it mounted as /boot … Is that what I am supposed to do? I am wondering if I did one step different a year back when I installed Suse 10.2 (JAD) and then Ubuntu Gutsy - everything went smooth back then…
Anyone had similar experiences or has advice esp. with Open Suse/Ubuntu/Windows - multiboot installation?