Good morning Cyberman. When first efforts don't quite succeed it becomes necessary to examine each item more closely. I don't mean to nit pick terminology, but non-standard terms may be misunderstood, so I'm going to tell you what I understood you to mean and let you correct me if I missed.
Quote:
|
Originally Posted by Cyberman
I just bought a new 320-GB disk and try to install Fedora 8.0 and FreeBSD.
|
Here was my fist error. I locked on this one drive, with two new installation and didn't pay close enough attention to the second problem, preferring to go after one problem at a time. But it wasn't a different problem. Further down you said:
Quote:
|
Originally Posted by Cyberman
And this time I got a new problem:
I have an old disk with Windows XP installed, this disk is sda and the newer disk is sdb. But GRUB recognized the new one as hd0 and the old one as hd1. First installation Fedora generated correct grub.conf but the second time it generated a error one with sda begin hd0, so it couldn't find the kernel file. Is that a but with Fedora 8.0? After I changed it, it can find the kernel but still stopped after print message with 'Red Hat nash'.
|
If I had been paying proper attention I would have cautioned you here. With both these disks attached it is not just an interaction between Fedora and BSD. It is Windows, Fedora and BSD.
Quote:
|
Originally Posted by Cyberman
First time:
I installed FreeBSD first with only one master partition (slice) using the first 40GB of the disk, without MBR installed.
|
I'm sorry, but you did not install anything without an MBR. The Master Boot Record must exist in order for you to have any partitions. I know you know this, but it needs stated to help us think clearly about what is happening. So instead of "without MBR installed," what was it that was not installed ? I have no guess as to what was not installed here.
Also, I am not familiar with either disk slices or master partitions. I believe the "slice" in question is clearly the 40 GB first partition of the 320 GB drive. But unless you were careful to tell it to put the boot loader on the new 320 GB drive, it went to the MBR of your Windows drive. That is dangerous. You would be much better to not involve the Windows drive and put the boot loader on the MBR of the new 320 GB drive.
Unless you are very aware of this kind of interaction your Windows installation is in grave danger. You should image your Windows installation before you do any more work on installations with it attached. This will give you the ability to restore it if things go badly, which all too often they do.
The last I heard you had Fedora running. You can use it to back up the MBR of your Windows drive. In a terminal window enter:
su -
(your root password)
dd if=sda of=/root/XP-MBR bs=512 count=1
This will disk dump the fist 512 bytes of the Windows drive to a file named XP-MBR in your Fedora /root folder. Then you should copy it to a floppy, a USB thumb drive or anything off the system. You want it to be available in the event Fedora fails to start.
In your BIOS you can usually select which drive is the boot drive. Please verify which it is, and post it. It is probably your old Windows XP drive. When you boot, do you get an option to boot into Fedora or BSD or Windows ? And if you select Windows, does it boot ?
Quote:
|
Originally Posted by Cyberman
Then I install Fedora use the other disk space. Every thing went fine, but after I rebooted the system, it couldn't continue after this printed:
Red Hat nash version 6.0.19 starting.
At that time I can still use root(hd0,0) under GRUB to boot FreeBSD.
|
Here Fedora cannot find its / partition. But there is no mention of Windows being one of the options. Is it?
[QUOT=Cyberman] Then I tried again:
I deleted all the diskpart, and installed Fedora with /boot at the beginning of the disk. This time it can boot normally. Then I installed FreeBSD on the free space, and when I tried to reboot it, the problem occurred again.[QUOTE
OK, /boot is the first partition, probably about 100 MB. The / or about 40 GB ?
And what are the disk labels? When Fedora installs it will label its partitions. If there is no partition labeled / it will label its / partition /. If there is already a partition labeled / it will label its / partition /1, etc. Does BSD label its partitions like this? Since Fedora boots to LABEL=/, what if BSD labeled its / partition /, leaving Fedora to possibly go to the wrong LABEL=/ ? I don't know what BSD does.
The last problem cited was FreeFSD failing to boot. So does "the problem occurred again" mean that FreeBSD again fails to boot but Fedora boots? Or does it mean that FreeBSD boots but Fedora fails ?
The last installation gets to provide the dual boot menu, because it puts its link in the MBR of the boot drive (probably the Windows drive). So with BSD being the last OS installed, it is responsible for booting itself, your Fedora and your Windows.
My preferences appear to run a little counter to the most common practice. I like to keep my drives working independent of one another. That means I don't let an installation of an OS on one drive write anything to the MBR of another drive, and I simply edit the grub.conf to provide the dual boot features I want.