Date: Thu, 2 Mar 2000 18:52:02 +0100 From: Brad Knowles <blk@skynet.be> To: Clifton Royston <cliftonr@lava.net> Cc: freebsd-stable@freebsd.org Subject: Re: Crash on boot when disks are present? Message-ID: <v0422081cb4e459abf349@[195.238.1.121]> In-Reply-To: <20000302073558.A3582@lava.net> References: <v0422080bb4e401fc570d@[195.238.1.121]> <20000302073558.A3582@lava.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:35 AM -1000 2000/3/2, Clifton Royston wrote: > Have you tried installing a fresh master boot record on the new virtual > drives? They never had one to begin with (no OS is stored out there), so I don't understand how this could make a difference. > 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. That happens all the time. Any time I boot the machine while the drive array is turned off, or if I delete the logical units that are exported to the host, then the next time the machine boots it will try to boot from the external drives. I fix this by going into the BIOS each time something like this happens and re-ordering the disks that will be booted from. If I don't, then I get an error message to the effect of "No bootable image could be found. Insert a bootable disk and press any key." > 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. Up until now, I either haven't gotten the loader at all (when I haven't re-ordered the drives that it will try to boot from), or it has found the loader on the internal drive and worked fine. > 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. Terminators are installed externally, and haven't been moved. Termination status on the host controllers hasn't changed. I should also note that this problem appears to be sporadic -- sometimes I can boot up just fine. The problem happens much more frequently when I do a soft reboot, and happens less frequently when I hit the hardware reset switch after doing a proper "shutdown -h". -- These are my opinions and should not be taken as official Skynet policy ========================================================================= Brad Knowles, <blk@skynet.be> Sys. Arch., Mail/News/FTP/Proxy Admin Note: No Microsoft programs were used in the creation or distribution of this message. If you are using a Microsoft program to view this message, be forewarned that I am not responsible for any harm you may encounter as a result. See <http://i-want-a-website.com/about-microsoft/twelve-step.html>; for details. 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?v0422081cb4e459abf349>