boot loader crashes

Jeremy Chadwick freebsd at jdc.parodius.com
Thu Aug 12 12:46:20 PDT 2004


This sounds related to the "boot2" madness we went through about a
week ago.  There's too many threads to point you to, but as it stands
now, things work.  I can confirm that at one time there was a problem
with the loader breaking (i.e. when boot2 loaded, it would quickly
panic/spit out exceptions, then immediately reboot the machine), but
that was taken care of as well.

I would recommend rebuilding the bootblocks and re-applying them.  In
addition, reinstall the boot0 blocks as well, just to be safe.  A quick
walkthrough:

# cd /usr/src/sys/boot
# make clean
# make
# make install
# disklabel -B <drive><slice>  (i.e. "ad0s1")
# boot0cfg -B <drive>          (i.e. "ad0")

-- 
| Jeremy Chadwick                                 jdc at parodius.com |
| Parodius Networking                        http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, USA |
| Making life hard for others since 1977.                             |

On Thu, Aug 12, 2004 at 09:11:56PM +0300, Petri Helenius wrote:
> 
> I updated a machine with ABIT VP6 (dual S370) motherboard from -CURRENT 
> in May to recent -CURRENT and since then the boot crashes with a message 
> which is visible for only a fraction of a second until the BIOS message 
> shows again. This is reproduceable with recent CD's. I´m able to boot 
> the system using 5.2.1 release CD and then just switching over to the HD.
> 
> The bootloader seems to gone through multiple changes so I couldn´t 
> immediately locate a place which could be at fault.
> 
> Any ideas or suggestions would be appreciated, I would hate to have to 
> ditch the board.
> 
> Pete
> 
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"


More information about the freebsd-current mailing list