Date: Sat, 13 Nov 2004 13:54:47 -0800 From: Jay O'Brien <jayobrien@att.net> To: FreeBSD - questions <questions@freebsd.org> Subject: Re: Help with boot0 Message-ID: <419682A7.6090904@att.net> In-Reply-To: <419578AC.30702@att.net> References: <419578AC.30702@att.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Henrik and Ruben, Good input from you both. To be sure which HD I'm on, I made (empty) directories in the root of each drive, called (either) ..AD0 or ..AD1. In this way the HD's aren't completely identical, and I can see which one boots. I agree that boot0 shouldn't be on the second drive and I fixed that. However, I couldn't restore the standard mbr until I went to /stand/sysinstall, selected Configure, selected fdisk, ad1, set bootable, write changes, yes, standard mbr, ok. This worked fine. If I interrupt the boot process, at the command prompt I can use the ls command to list files and see the empty directory that confirms which drive has booted. If I boot from the second drive, ad1, then fstab and other files point to ad0, not ad1, and I wind up on ad0, regardless of which drive actually boots. It seems to me that the boot0cfg -o option should force the drive in use to be referred to the boot0cfg option -b 0x80, and then the second drive would be used but called 0x80. This doesn't seem to be the case. Apparently I will have to make some changes to the files on the second drive so that the first drive won't be used at all when the system is booted from the second drive. Which files? To recap, I can use boot0 to boot from either HD. However, when the boot is on the second HD, it still points to (and uses) the first drive as if it was booted there. I have identical files on ad0 and ad1. I would like to be able to boot from (and use the files on) either ad0 or ad1. Help? Jay O'Brien Rio Linda, CA, USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?419682A7.6090904>