From owner-freebsd-hackers Wed Jan 3 10:27:30 2001 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 3 10:27:25 2001 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from rush.telenordia.se (mail.telenordia.se [194.213.64.42]) by hub.freebsd.org (Postfix) with SMTP id 84EF637B402 for ; Wed, 3 Jan 2001 10:27:24 -0800 (PST) Received: (qmail 437 invoked from network); 3 Jan 2001 19:27:23 +0100 Received: from bb-62-5-7-17.bb.tninet.se (HELO web1.tninet.se) (62.5.7.17) by mail.telenordia.se with SMTP; 3 Jan 2001 19:27:23 +0100 From: Mark Rowlands Reply-To: mark.rowlands@minmail.net To: nathan@vidican.com, Nathan Vidican , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Server will not recognize boot record for some reason Date: Wed, 3 Jan 2001 19:20:30 +0100 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" References: <3A524BF2.E2E1F3BF@wmptl.com> In-Reply-To: <3A524BF2.E2E1F3BF@wmptl.com> MIME-Version: 1.0 Message-Id: <01010319203000.04014@web1.tninet.se> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG do you have bios translation set to 2gb? On Tuesday 02 January 2001 22:45, Nathan Vidican wrote: > This machine is an Intel Pentium Pro based system, (not a DEC Alpha), it > currently has one 200mhz 512K CPU, 196megs RAM, (4 x 32edo simms, 4 x > 16edo simms), and two 4.5Gig SCSI disks in hot-swappable drive carriages > configured using RAID 1 (mirrored), attached to a Mylex DAC960P/PD > dual-channel controller. I have flashed the firmware of the controller > card to 3.52, as reccomended during the dmesg prompts (the card > initially had < 3.51). The problem seems to be with booting, I have > tried several installs; all seem to partition fine except for > 'dangerously dedicated'. After an install using a 4.4Gig root, and an > 80meg swap, (leaving 20megs un-partitioned at the end of the drive), the > system will not boot. If I boot off of the installation floppies, I can > mount/view the files on the drive. This leaves me thinking it's got to > have something to do with FreeBSD's MBR. > Having problems booting; the system installs to the mylex system drive > fine, but when I reboot, I get the FreeBSD boot MGR, and it only beeps > when I press F1 for FreeBSD. If I install using a normal boot record, > the system reports 'No operating system found'. I'm thinking it may be > an issue with the Mylex card, but I don't know for sure if the system's > bios could cause this either. I cannot attempt to install the mylex card > in another machine; as the drives attached to it are in a hot-swap > carriage which is part of the system's chassis. > On a hunch, I tried re-partitioning and installing MsDos; maybe the > RAID configuration isn't bootable at all I figured; but it partitioned > fine, and booted properly. I then tried installing NT, and now Linux. > All three had no problems, and all three booted fine. Seeing as how the > other O/S's all installed/worked fine; I'm assuming this is just a > software issue. Maybe with the bios of the Raid controller, or maybe > with the system bios, has anyone else run into similar problems? Am I > just missing something blatenly obvious? Does FreeBSD not boot from a > mirrored volume (if so... why not)? > I've only ever done one other server install with FreeBSD, and a Mylex > Raid controller; it booted fine. It was using an AcceleRAID PCI 150 > card, with foud 9.1gig SCSIUW's in a RAID 5 configuration. It went fine > with no hitches, (cept that it took like 1hr to newfs). However, this is > a different controller, and having little to no experience working with > RAID controllers I figured I'd ask. > Baring no absolute solutions, or better partial ones from this mailing > list, I'm going to install Linux on a 200meg partition, and attempt to > install FreeBSD on the rest and boot it using Lilo (don't know if it's > going to work...but it's worth a try). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message