Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Mar 2000 07:35:58 -1000
From:      Clifton Royston <cliftonr@lava.net>
To:        Brad Knowles <blk@skynet.be>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Crash on boot when disks are present?
Message-ID:  <20000302073558.A3582@lava.net>
In-Reply-To: <v0422080bb4e401fc570d@[195.238.1.121]>
References:  <v0422080bb4e401fc570d@[195.238.1.121]>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 02, 2000 at 12:45:35PM +0100, Brad Knowles wrote:
> 	I've gone in and made sure that the BIOS has been changed (yet 
> once again) to try to boot off the internal Quantum Atlas-IV drive 
> that is attached to the AIC-7890 controller, because the external 
> drive array does not have the OS installed, etc....  Unfortunately, 
> when I try to boot with the drive array turned on, it crashes hard 
> (during the bootloader phase, I think), displaying the following:
> 
> F1    DOS
> F2    FreeBSD
> F5    Drive 1
> 
> Default: F2
> 
> -
> int=00000000  err=00000000  efl=00030083  eip=00000004
> eax=000004e3  ebx=0000097f  ecx=0000dc00  edx=000034be
> esi=0000dc00  edi=00000004  ebp=00000000  esp=000004ce
> cs=c800  ds=c800  es=9e7d    fs=0000  gs=0000  ss=9e7b
> cs:eip=d4 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
> ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00

Have you tried installing a fresh master boot record on the new virtual
drives?

(I've found that booting to a DOS floppy and using the undocumented
FDISK /MBR is the simplest way to do this.)

It's possible that changing the RAID sets around has caused either the
BIOS or FreeBSD to try to boot off of those drives when they're
present.  I did have a hard time (for instance) getting FreeBSD to boot
off the internal drive on the second channel of the integrated 7896;
the BIOS would boot the loader off the internal drive, and then FreeBSD
would start trying to complete the boot from the first drive it saw,
which was one of the external ones.

Also, of course, all the usual rules about looking for new SCSI bus
termination problems before all else apply; possibly the firmware
upgrade changed some controller settings relating to termination.

Good luck.
  -- Clifton

-- 
 Clifton Royston  --  LavaNet Systems Architect --  cliftonr@lava.net
      The named which can be named is not the Eternal named.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000302073558.A3582>