Boot loader messed up - How do I fix?

Kevin Oberman oberman at es.net
Thu Aug 18 18:18:08 GMT 2005


> Date: Thu, 18 Aug 2005 11:02:07 -0700
> From: Rudy Rucker <crapsh at monkeybrains.net>
> Sender: owner-freebsd-current at freebsd.org
> 
> 
> I did a cvsup & made a new kernel & world  on August 9th but now I can't 
> boot.
> 
> This was on my second drive.  When I boot, I get this menu:
> 
>   F1: ??
>   F2: FreeBSD   (old, May 31st FreeBSD 6.0 CURRENT)
>   F5: Drive 2   (newer, Aug 9th FreeBSD - CURRENT)
> 
> F2 works fine.  F5 _used_ to go to my other drive and boot FreeBSD just 
> fine.  I have updated along the CURRENT branch many times, so I sort of 
> know what I am doing ;)
> 
> If I edit the fstab file on Drive 1 to mount only points on Drive 2, the 
> boot loader will load the kernel from the first drive, but then 
> everything else works fine on Drive 2.
> 
> Here are my questions:
>   Why is the boot code on Drive 1 unable to load the kernel on Drive 2?
>   How do I fix my computer to boot the kernel on Disk 2?
> 
> (Would changing my supfile to grab RELENG_6 resolve this problem?
>   I am trying that right now...)

OK. I am guessing that the system beeps or does nothing when you hit
F5. Is that correct?

If so you need to sue boot0cfg to write a new boot to Drive 2. If I
understand all of this, pressing F5 causes the boot block on the other
drive to be run and, if there is no valid boot block, nothing
interesting happens.

So to make this work, you need a valid boot on both disks.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634


More information about the freebsd-current mailing list