Nigel Henry wrote: > Hi. I have on my old Gateway 500, 3 harddrives, and 3 ROM drives. > hda, and hdb (both harddrives) are on the first IDE controller on the mobo. > hdc, and hdd (cdrom, and cdwriter) are on the 2nd IDE controller on the mobo. > hde (harddrive) is on the first IDE controller of the PCI adaptor card, and. > hdg (dvdrom) is on the 2nd IDE controller of the PCI adaptor card. > > FC2's (hdb) Grub is in the MBR of hda, (Win ME is on hda). FC3, and 2 > instances of FC5 are on other partitions of hda, and hdb, with their Grub > bootloaders in their respective / partitions, and I can chainload from Grub > in the MBR to these other Grub's, and everyone boots up ok. > > The problem is with FC1 (hde) on the IDE PCI adaptor card. Again it's Grub is > in FC1's / partition, but I cannot set up a chainloader to it like the other > OS's. When I bootup, and select FC1 on Grubs menu, I get a "no such disc" > returned. Incidentally I can boot FC1 from a floppy ok, and is the way I've > been booting it since 2003. > > Also when any of the other OS's is booted up, I have no problem with the > dvdrom drive, or hde, and can mount it, transfer files back and forth from > it, and so on. > > I saw some posts about Grubs drive map, but there is hardly any info about it > on the Grub site. Anyway I looked at the drive map of Grub (in the MBR) and > see that it only has 3 entries. fd0, hda, and hdb (no hde). I admit i'm > poking around in the dark, but added and entry for hde to the drive map. > Rebooted, but still getting a "no such disc" for FC1 on hde. > > If this missing hde from the drive map is the problem, am I supposed to > reinstall Grub to the MBR after making changes to the map? > > Any help is really appreciated. > > Nigel. > Yes, you have to run grub-install after updating the drive map. But this may not solve the problem. If your BIOS does not know how to access the drives on the Silicon Graphics card, and you chainload the copy of Grub on the MBR of hde, that first stage tries to use the BIOS to load the second stage. The reason the floppy boot works is that both the first and second stages are on the floppy, so Grub can use its own code to access the drive. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
