Date: Thu, 17 Mar 2005 11:23:18 -0500 (EST) From: Jerry McAllister <jerrymc@clunix.cl.msu.edu> To: FreeBSD@euro.net.mk (Perica Veljanovski) Cc: freebsd-questions@freebsd.org Subject: Re: dual boot two disk Message-ID: <200503171623.j2HGNJV03641@clunix.cl.msu.edu> In-Reply-To: <42399C85.9000000@euro.net.mk> from "Perica Veljanovski" at Mar 17, 2005 04:04:37 PM
next in thread | previous in thread | raw e-mail | index | archive | help
> > Jerry McAllister wrote: > > >>Hi > >> > >>I have a problem booting the second disk with fbsd's boot manager. I > >>installed a new disk as pri/master (ad0) and moved my old disk to > >>sec/master (ad2). Then devided ad0 (40GB) with fbsd's fdisk in 10G (ufs) > >>and 30G (fat) and installed FreeBSD 5.3 with a boot manager on the first > >>10G. When I boot the system I get: > >> > >>F1 FreeBSD (the fbsd on ad0s1) > >>F2 DOS (the 30G fat, ad0s2) > >>F5 Other (again the fbsd) > >> > >>So there is no option to boot from the second disk!? > >>Allso when I unlplug ad0 or change the BIOS to boot from ad2 (hd1 as he > >>sees it), WinXP boots just fine, meaning, there is no problem with the > >>mbr on ad2. > > > >Hmmm. I am not exactly clear from your description, but... > > > >I would expect that when you hit F5, you would be presented with > >a new menu that included the ad2 disk. Maybe that disk does not > >really have an MBR, but only a boot block (the second part of > >the disk boot process [or third if you count BIOS]). I believe > >each disk that has bootable slices (which have boot blocks/sectors) > >also needs to have an MBR for it to work right. If you are brave, > >try using fdisk to write the MBR to ad2 as well. I don't think > >that would mess up anything and might be what is missing. > > > >Something like: fdisk -BI -b /boot/boot0 ad2 > > > >I don't know if FreeBSD 5.3 still keeps its MBR in /boot/boot0. > >You may have to check that. > > > >////jerry > > > That's what I thought. F5 should move on to the next disk, or more > precise the next disk's mbr. But it does not. > Anyways, the second disk has a MBR on it. As I said, when I unplug the > fist dis and boot the box with the old disk (second disk) only, I get a > normal boot menu from Widows XP (which has it's own boot loader = WinXP > and Win2k Pro). So the problem is not that the second disk has bad or no > MBR, rather that FreeBSD's boot manager "boot0" doesn't give me a chance > to boot from the second disk. > > I thought about overwriting the mbr on the second disk (ad2), but I > don't feel very brave :P I think that will most defenetly remove WinXP > boot manager and probably remove some partitioning info, thus I'll loose > the data. And since I'm not familiar with WinXP boot process, and don't > know if FreeBSD's boot manager will pick up where WinXP/MBR left off, I > rather not do that without any assurance. I think it would be OK. I don't think it will change the slicing info unless you tell it to. On any multi boot installs I have done, it has been smart enough to only change what it needed. But, it's your machine - doesn't harm me if it screws up, so... so it is up to you. Ted M seems to think there are some situations in which rewriting the MBR can screw things up. I haven't run in to one yet, but probably he knows of more such situations that I do. > > >>I read the man for boot0cfg, but I can't make heads or tails of ti!!! > >>how do I configure/install the boo0 to show the second disk ni the boot > >>menu? > > > >I generally use fdisk and not boot0cfg, but I think it is basically > >the same for what you are trying to do here. > > > >Something like: boot0cfg -B -b /boot/boot0 -o packet ad2 > > > >You might want to add -f some_file_name if you want it to save whatever > >was in the sector0 before the command. You can put it back if you need. > > > >You may also need -m 0x1 or -m 0x3 or -m 0x7 or -m 0xf depending > >on if you have 1, 2, 3 or 4 slices actively bootable. I think it > >is supposed to figure it out, but if it doesn't, then try those. > > > >You migh also want to include the -v flag to make it print out more > >stuff when it runs. > > > >You might also want to do the exactly the same or the same fdisk to ad0 > >as well. > > > I got that part :P What I didn't understand is how the hell I'm I > suppose to let him know about the other disk :) I think it is supposed to figure it out itself by looking at which slices are marked active - eg bootable. The -m 0x3 etc marks them active. You can also tell it which is the default one or the active slices to boot from. If you have the -o packet option set, then it will automatically set the default to whatever you select and the next time that will be it if you don't select anything else in the time allowed (set by -t ticks). > > >By the way, what happened to ad1? (I don't muck with IDE - I have SCSI > >so, I am not up on its device naming schemes) > > > >Good luck, > > > >////jerry > > > BIOS names disks as hdN, and bsd as adN (as you already know). The main > difference is that BIOS just increments N for the next disk (example: > pri/master=hd0, pri/slave=cdrom, sec/master=hd1) and fbsd decides N by > IDE position (example: pri/master=ad0, pri/slave=acd0, sec/master=ad2) Sort of what I guessed. ////jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503171623.j2HGNJV03641>