From owner-freebsd-current Thu Feb 17 7:39:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 6919237B751; Thu, 17 Feb 2000 07:39:35 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id KAA94708; Thu, 17 Feb 2000 10:39:34 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000217103709.01c2f7b0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 17 Feb 2000 10:37:09 -0500 To: Mike Smith From: Mike Tancsa Subject: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Cc: current@FreeBSD.ORG In-Reply-To: <200002170304.TAA03502@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:04 PM 2/16/00 -0800, Mike Smith wrote: >> At 05:15 PM 2/16/2000 -0800, Mike Smith wrote: >> > > Hi, >> > > I have been trying to get a PERC 2 (aka MegaRAID 466) working with >> > > Current. The box worked fine with the 428, but seems to barf with only the >> > > controller swapped. >> > >> >I don't think the two controllers share on-disk configuration formats; >> >you'll probably need to re-initialise the array (I could be wrong about >> >that). >> >> Yes, I did that. I blew away the old config, created a new set, and >> initialized the array. >> >> >> You probably don't want to do that with a valid slice table installed; >> >the slice code does silly things. Try nuking it first: >> > >> ># dd if=/dev/zero of=/dev/amrd0 count=16 >> >> newmail# dd if=/dev/zero of=/dev/amrd0 count=16 >> 16+0 records in >> 16+0 records out >> 8192 bytes transferred in 0.006427 secs (1274613 bytes/sec) >> newmail# disklabel -Brw amrd0 auto >> newmail# disklabel -e amrd0 >> disklabel: ioctl DIOCGDINFO: Invalid argument > >Hmm. I should have paid more attention to the fdisk output the first >time; you already had the whole-disk label in place. > >What's the output from 'disklabel mlxd0'? > OK, I took a chance and flashed the card's BIOS to the latest from the AMI site.... I had been suspecting BIOS, as the readme.txt mentioned problems with newer motherboards. Lo and Behold, it seems to have done the trick amr0: mem 0xe9000000-0xe93fffff irq 11 at device 12.1 on pci0 amr0: firmware GH6D bios 1.43 32MB memory amrd0: on amr0 amrd0: 17522MB (35885056 sectors) RAID 5 (optimal) As I mentioned, the card came as a Dell unit. I tried the latest BIOS from Dell, but that was a year old. The BIOS from megaraid.com 1.43, which is in there now *seems* to work so far.... At least I can now get a disklable on the drive and newfs the drive newmail# disklabel amrd0 # /dev/ramrd0c: type: SCSI disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2233 sectors/unit: 35885056 rpm: 7200 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 35885056 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 2233*) ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message