From owner-freebsd-scsi@FreeBSD.ORG Sun Jan 2 18:02:29 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 827C616A4CE for ; Sun, 2 Jan 2005 18:02:29 +0000 (GMT) Received: from delicious.stderror.at (stdin.stderror.at [213.229.63.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB1FA43D1F for ; Sun, 2 Jan 2005 18:02:28 +0000 (GMT) (envelope-from pinhead@delicious.stderror.at) Received: by delicious.stderror.at (Postfix, from userid 501) id 127041A221D; Sun, 2 Jan 2005 19:02:59 +0100 (CET) Date: Sun, 2 Jan 2005 19:02:59 +0100 From: Toni Schmidbauer To: freebsd-scsi@freebsd.org Message-ID: <20050102180259.GC18802@stderror.at> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w7PDEPdKQumQfZlR" Content-Disposition: inline Phone: +43 664 3502198 X-WWW-Home-Page: http://stderror.at X-PGP-Fingerprint: 53F2 28AE 8070 83E0 AFEC 0ABC BBF9 A34A 3ED1 3287 X-Operating-System: Darwin User-Agent: Mutt/1.5.6i Subject: 5.3-REL and icp gdt6523rs boot0 problems X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: toni@stderror.at List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2005 18:02:29 -0000 --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi, i'm trying to install 5.3-REL on a system with an icp vortex gdt6523rs raid controller. problem is, i'm getting some kind of a register dump when booting from the 5.3-REL cd. this happens very early in the boot process (boot0?), because i can't even see the daemon splash screen. - if i pull the controller out of the system, booting works - if i boot from an old 4.10 cd, booting + installation works - booting the 5.3 cd on another system works, so the cd is ok - booting with an 5.2.1 cd doesn't work either, same problem - updating to the latest icp firmware doesn't help - it doesn't matter if there are disks connected to the controller or not i can't post the exact output, because the text is scrolling to fast... is there anything i can do to get this beast booting? any help would be appreciated regards toni --=20 Wer es einmal so weit gebracht hat, dass er nicht | toni at stderror dot at mehr irrt, der hat auch zu arbeiten aufgehoert | Toni Schmidbauer -- Max Planck | --w7PDEPdKQumQfZlR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFB2DdTu/mjSj7RMocRAjySAJ9SLqZoLqgQ5kDPBhazVvT2ogoVNACeKu8W wrRlBBycExgBwpF/NacfPe4= =tsBF -----END PGP SIGNATURE----- --w7PDEPdKQumQfZlR-- From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 3 11:02:06 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 470D616A4D9 for ; Mon, 3 Jan 2005 11:02:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF14C43D45 for ; Mon, 3 Jan 2005 11:02:05 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j03B25jE006189 for ; Mon, 3 Jan 2005 11:02:05 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j03B25wK006183 for freebsd-scsi@freebsd.org; Mon, 3 Jan 2005 11:02:05 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 3 Jan 2005 11:02:05 GMT Message-Id: <200501031102.j03B25wK006183@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 11:02:06 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2000/08/18] kern/20689 scsi Newbusified version of ncr driver does no f [2001/05/03] kern/27059 scsi (symbios) SCSI subsystem hangs under heav o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug f [2002/09/15] kern/42796 scsi NCR/SYM 53C825 driver detects scsi cdrom f [2002/11/25] kern/45713 scsi If you use the amr driver, it is impossib f [2002/12/09] kern/46152 scsi Panic in adw dumping to tape f [2003/05/16] kern/52331 scsi 4.7 to 4.8-REL upgrade: SCSI disks on sym f [2003/09/14] kern/56759 scsi [hang] System freezes when writing CD Adv f [2003/09/14] kern/56760 scsi [hang] system hangs at boot with adaptec f [2003/09/14] kern/56871 scsi dd can't write variable length data block f [2003/09/18] kern/56973 scsi SCSI errors from on-board Adaptec (AIC7xx s [2003/09/30] kern/57398 scsi Current fails to install on mly(4) based o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with a [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/09/15] kern/71778 scsi 5.3 BETA3 doesnt see Adaptec 2015S FW Rev o [2004/12/02] kern/74607 scsi FreeBSD 5.3 install CD crashes on SCSI de 18 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2001/08/15] kern/29727 scsi [amr] [patch] amr_enquiry3 structure in a o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57468 scsi [patch] Quirk for Quantum LPS540S o [2003/10/01] kern/57469 scsi [patch] Quirk for Conner CP3500 o [2004/09/22] kern/72010 scsi [patch] mt -f /dev/rsa0.ctl comp off, or 8 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 3 13:13:02 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 333DF16A4CE for ; Mon, 3 Jan 2005 13:13:02 +0000 (GMT) Received: from zep1.it-austria.net (zep1.it-austria.net [213.150.1.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id D597143D45 for ; Mon, 3 Jan 2005 13:13:01 +0000 (GMT) (envelope-from pinhead@delicious.stderror.at) Received: from delicious.stderror.at (unknown [10.24.28.114]) by zep1.it-austria.net (Postfix) with ESMTP id 32E4633CD4 for ; Mon, 3 Jan 2005 14:13:00 +0100 (CET) Received: by delicious.stderror.at (Postfix, from userid 501) id 880361A3954; Mon, 3 Jan 2005 14:13:03 +0100 (CET) Date: Mon, 3 Jan 2005 14:13:03 +0100 From: Toni Schmidbauer To: freebsd-scsi@freebsd.org Message-ID: <20050103131303.GA25291@stderror.at> Mail-Followup-To: toni@stderror.at, freebsd-scsi@freebsd.org References: <20050102180259.GC18802@stderror.at> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20050102180259.GC18802@stderror.at> Phone: +43 664 3502198 X-WWW-Home-Page: http://stderror.at X-PGP-Fingerprint: 53F2 28AE 8070 83E0 AFEC 0ABC BBF9 A34A 3ED1 3287 X-Operating-System: Darwin User-Agent: Mutt/1.5.6i Subject: [SOLVED] 5.3-REL and icp gdt6523rs boot0 problems X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: toni@stderror.at List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 13:13:02 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 02, 2005 at 07:02:59PM +0100, Toni Schmidbauer wrote: > i'm trying to install 5.3-REL on a system with an icp vortex > gdt6523rs raid controller. problem is, i'm getting some kind of a > register dump when booting from the 5.3-REL cd. this happens > very early in the boot process (boot0?), because i can't even see > the daemon splash screen. booting from floppy works. has to be a problem with cdboot. finding a floppy drive is not so easy these days... thanks toni --=20 Wer es einmal so weit gebracht hat, dass er nicht | toni at stderror dot at mehr irrt, der hat auch zu arbeiten aufgehoert | Toni Schmidbauer -- Max Planck | --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFB2UTfu/mjSj7RMocRAv5NAKCHKHbJWaNLINi1t1juyr4wqrQVJgCbBZVq 99dl0ocu3hbsTgTBTl5I+XY= =3swo -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 4 05:06:18 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF8BB16A4CE for ; Tue, 4 Jan 2005 05:06:18 +0000 (GMT) Received: from eagle.uvm.edu (eagle.uvm.edu [132.198.101.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7869143D2F for ; Tue, 4 Jan 2005 05:06:18 +0000 (GMT) (envelope-from jflemer@uvm.edu) Received: from [192.168.2.15] (c-24-9-89-237.client.comcast.net [24.9.89.237]) (authenticated bits=0) by eagle.uvm.edu (8.12.11/8.12.11) with ESMTP id j0456FBs016500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jan 2005 00:06:17 -0500 Message-ID: <41DA2475.90509@uvm.edu> Date: Mon, 03 Jan 2005 22:07:01 -0700 From: "James E. Flemer" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040918) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: jflemer@uvm.edu Subject: mtio/sa device response to bad blocks X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 05:06:19 -0000 I have a SCSI DAT drive and have had some problems reading tapes with bad blocks. It seems that a read(2) from the sa device returns 0 when a bad block is read from the tape. Note that read(2) also correctly returns 0 when a filemark is read. A userland application (see below) can tell the difference between a filemark and a read error by looking at the io_sense part of the scsi_tape_errors struct (via the MTIOCERRSTAT ioctl). However this is cumbersome and requires the knowledge of the scsi_sense_data struct. It would seem more appropriate for the read to return -1 and set errno to EIO when a bad block is read. With such a change "dd conv=noerror,sync" could be used to dump a tape with bad blocks. Unfortunately, I'm not familiar enough with the SCSI/CAM layers to know where make this change, could someone point me where to look? Thanks, -James /* This code will check the real reason for read to return 0 * and change the return code to -1 and set errno to EIO if there * was a MEDIUM_ERROR. Other non-SSD_FILEMARK/SSD_EOM flags * should probably also be handled via -1/errno. */ num_read = read(mtfd, buf, blk_size); if (num_read == 0) { ioctl(mtfd, MTIOCERRSTAT, &tape_err); sense_data = (struct scsi_sense_data *)&tape_err.io_sense; if (sense_data->flags & SSD_KEY_MEDIUM_ERROR) { num_read = -1; errno = EIO; } } From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 4 07:45:31 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46C5416A4CE for ; Tue, 4 Jan 2005 07:45:31 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7DB343D2F for ; Tue, 4 Jan 2005 07:45:30 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so85377rne for ; Mon, 03 Jan 2005 23:45:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KN9FOyJWDWyPrbmr8JJ0A6fhl4Z56w/rjKA0ACP6p6PXtQUpPBgY8y4QhKWGpJx6OrIBryhtUL6Z1Dyht3mI2sUug+rPq+Xz5I6n5xoNVTAT8iKbLp/DSIfkcpgRHcjPtepay7abXp0fXxR5K+GSQPpO8N6okVyxcauD1Qf0mqE= Received: by 10.38.11.31 with SMTP id 31mr239785rnk; Mon, 03 Jan 2005 23:45:30 -0800 (PST) Received: by 10.38.104.73 with HTTP; Mon, 3 Jan 2005 23:45:30 -0800 (PST) Message-ID: <7579f7fb05010323457bab1899@mail.gmail.com> Date: Mon, 3 Jan 2005 23:45:30 -0800 From: Matthew Jacob To: "James E. Flemer" In-Reply-To: <41DA2475.90509@uvm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41DA2475.90509@uvm.edu> cc: freebsd-scsi@freebsd.org Subject: Re: mtio/sa device response to bad blocks X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Matthew Jacob List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 07:45:31 -0000 Are you using fixed block or variable block mode? I believe that errors propagate correctly for variable but can't for fixed block mode. On Mon, 03 Jan 2005 22:07:01 -0700, James E. Flemer wrote: > I have a SCSI DAT drive and have had some problems reading tapes with > bad blocks. It seems that a read(2) from the sa device returns 0 when a > bad block is read from the tape. Note that read(2) also correctly > returns 0 when a filemark is read. A userland application (see below) > can tell the difference between a filemark and a read error by looking > at the io_sense part of the scsi_tape_errors struct (via the > MTIOCERRSTAT ioctl). However this is cumbersome and requires the > knowledge of the scsi_sense_data struct. It would seem more appropriate > for the read to return -1 and set errno to EIO when a bad block is read. > With such a change "dd conv=noerror,sync" could be used to dump a tape > with bad blocks. Unfortunately, I'm not familiar enough with the > SCSI/CAM layers to know where make this change, could someone point me > where to look? > > Thanks, > -James > > /* This code will check the real reason for read to return 0 > * and change the return code to -1 and set errno to EIO if there > * was a MEDIUM_ERROR. Other non-SSD_FILEMARK/SSD_EOM flags > * should probably also be handled via -1/errno. > */ > num_read = read(mtfd, buf, blk_size); > if (num_read == 0) { > ioctl(mtfd, MTIOCERRSTAT, &tape_err); > sense_data = (struct scsi_sense_data *)&tape_err.io_sense; > if (sense_data->flags & SSD_KEY_MEDIUM_ERROR) { > num_read = -1; > errno = EIO; > } > } > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 4 08:31:53 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDD2616A4CE for ; Tue, 4 Jan 2005 08:31:53 +0000 (GMT) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 7B81B43D1D for ; Tue, 4 Jan 2005 08:31:52 +0000 (GMT) (envelope-from janm-freebsd-scsi@transactionware.com) Received: (qmail 9798 invoked from network); 4 Jan 2005 08:32:12 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 4 Jan 2005 08:32:12 -0000 Received: (qmail 87628 invoked by uid 1001); 4 Jan 2005 08:32:12 -0000 Date: 4 Jan 2005 08:32:12 -0000 Message-ID: <20050104083212.87627.qmail@new.transactionware.com> From: janm-freebsd-scsi@transactionware.com To: freebsd-scsi@freebsd.org Subject: ips, IBM Serveraid and failed disks X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 08:31:54 -0000 Hi, I've been looking at how to detect a failed disk in a machine with an IBM Serveraid controller using the ips driver. It doesn't seem to be supported out of the box, and others seem to have asked this question in the past without a solution being posted. How are people dealing with this problem? Do the users of ips controllers just check the LEDs on the front of the drives occasionally? There is a user command ioctl in the source, which I'll try out to see whether it does what I want. Has anyone else tried to use it? Thanks, Jan Mikkelsen From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 4 14:05:16 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7CF416A4CE for ; Tue, 4 Jan 2005 14:05:16 +0000 (GMT) Received: from eagle.uvm.edu (eagle.uvm.edu [132.198.101.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 494F943D39 for ; Tue, 4 Jan 2005 14:05:16 +0000 (GMT) (envelope-from jflemer@uvm.edu) Received: from [192.168.2.15] (c-24-9-89-237.client.comcast.net [24.9.89.237]) (authenticated bits=0) by eagle.uvm.edu (8.12.11/8.12.11) with ESMTP id j04E5Dsa022940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jan 2005 09:05:15 -0500 Message-ID: <41DAA2C8.7030303@uvm.edu> Date: Tue, 04 Jan 2005 07:06:00 -0700 From: "James E. Flemer" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040918) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <41DA2475.90509@uvm.edu> <7579f7fb05010323457bab1899@mail.gmail.com> In-Reply-To: <7579f7fb05010323457bab1899@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: James Flemer Subject: Re: mtio/sa device response to bad blocks X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 14:05:16 -0000 I am using fixed block mode. Why is it that errors cannot propagate for fixed block? After a little more looking in the code, perhaps this patch in saerror() will do what I want. I have not tried this patch yet though, since I compiled SCSI into the kernel (not module) and cannot reboot the box at the moment. -James --- sys/cam/scsi/scsi_sa.c 16 Jun 2004 09:46:31 -0000 1.101 +++ sys/cam/scsi/scsi_sa.c 4 Jan 2005 13:56:50 -0000 @@ -2415,6 +2415,8 @@ } else { error = EIO; } + } else if (sense_key == SSD_KEY_MEDIUM_ERROR) { + error = EIO; } else if (sense->flags & SSD_FILEMARK) { if (softc->flags & SA_FLAG_FIXED) { error = -1; Matthew Jacob wrote: > Are you using fixed block or variable block mode? I believe that > errors propagate correctly for variable but can't for fixed block > mode. > > > On Mon, 03 Jan 2005 22:07:01 -0700, James E. Flemer wrote: > >>I have a SCSI DAT drive and have had some problems reading tapes with >>bad blocks. It seems that a read(2) from the sa device returns 0 when a >>bad block is read from the tape. Note that read(2) also correctly >>returns 0 when a filemark is read. A userland application (see below) >>can tell the difference between a filemark and a read error by looking >>at the io_sense part of the scsi_tape_errors struct (via the >>MTIOCERRSTAT ioctl). However this is cumbersome and requires the >>knowledge of the scsi_sense_data struct. It would seem more appropriate >>for the read to return -1 and set errno to EIO when a bad block is read. >> With such a change "dd conv=noerror,sync" could be used to dump a tape >>with bad blocks. Unfortunately, I'm not familiar enough with the >>SCSI/CAM layers to know where make this change, could someone point me >>where to look? >> >>Thanks, >>-James >> >>/* This code will check the real reason for read to return 0 >> * and change the return code to -1 and set errno to EIO if there >> * was a MEDIUM_ERROR. Other non-SSD_FILEMARK/SSD_EOM flags >> * should probably also be handled via -1/errno. >> */ >>num_read = read(mtfd, buf, blk_size); >>if (num_read == 0) { >> ioctl(mtfd, MTIOCERRSTAT, &tape_err); >> sense_data = (struct scsi_sense_data *)&tape_err.io_sense; >> if (sense_data->flags & SSD_KEY_MEDIUM_ERROR) { >> num_read = -1; >> errno = EIO; >> } >>} >>_______________________________________________ >>freebsd-scsi@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >>To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" >> From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 5 01:01:46 2005 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DDE416A4CE; Wed, 5 Jan 2005 01:01:46 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B0443D31; Wed, 5 Jan 2005 01:01:46 +0000 (GMT) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (kris@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0511ktk015144; Wed, 5 Jan 2005 01:01:46 GMT (envelope-from kris@freefall.freebsd.org) Received: (from kris@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0511kbK015140; Wed, 5 Jan 2005 01:01:46 GMT (envelope-from kris) Date: Wed, 5 Jan 2005 01:01:46 GMT From: Kris Kennaway Message-Id: <200501050101.j0511kbK015140@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-scsi@FreeBSD.org Subject: Re: kern/75603: 5.3 kernel crash X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 01:01:46 -0000 Synopsis: 5.3 kernel crash Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: kris Responsible-Changed-When: Wed Jan 5 01:01:30 GMT 2005 Responsible-Changed-Why: Assign to SCSI mailing list for evaluation http://www.freebsd.org/cgi/query-pr.cgi?pr=75603 From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 5 12:38:24 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C788D16A4CE for ; Wed, 5 Jan 2005 12:38:24 +0000 (GMT) Received: from mail.squidge.com (mail0.squidge.com [195.10.252.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04C4E43D48 for ; Wed, 5 Jan 2005 12:38:24 +0000 (GMT) (envelope-from henry@jot.to) Received: from TOSHIBA (toshiba.netcraft.com [195.92.95.86]) (authenticated bits=0) by mail.squidge.com (8.13.1/8.12.9) with ESMTP id j05CcJB7039723 for ; Wed, 5 Jan 2005 12:38:19 GMT From: "henry" To: Date: Wed, 5 Jan 2005 12:37:12 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Virus-Scanned: by AMaViS at mail.squidge.com X-Spam-Level: 0.0 Subject: 5.3-Stable panics on boot after detecting mpt1 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 12:38:25 -0000 5.3-Stable as of 3rd Jan 2005. Hardware known good previously. 2 Scsi controllers, one onboard Adaptec, one 64bit PCI card LSI Logic 1030 (correctly identified below) No devices attached to the LSI card (there was but I am trying to make the environment simpler for debugging). Boot messages snipit: mpt0: port 0xe000-0xe0ff mem 0xfeb40000-0xfeb5ffff,0xfeb60000-0xfeb7ffff irq 24 at device 1.0 on pci1 mpt0: Reserved 0x20000 bytes for rid 0x14 type 3 at 0xfeb60000 mpt0: [GIANT-LOCKED] mpt0: soft reset mpt1: port 0xe400-0xe4ff mem 0xfeb80000-0xfeb9ffff,0xfeba0000-0xfebbffff irq 25 at device 1.1 on pci1 mpt1: linking with peer (mpt0) mpt1: Reserved 0x20000 bytes for rid 0x14 type 3 at 0xfeba0000 panic: pmap_mapdev: Couldn't alloc kernel virtual memory I can also provide backtrace from KDB but would like to know what is "interesting" to people here first because I will be copying by hand (time to setup a serial console?). Any pointers? Partial (but fuller than the above) verbose boot message captured from a subsequent boot map[10]: type 1, range 32, base fe5fc000, size 12, enabled map[14]: type 4, range 32, base 0000c000, size 6, enabled map[18]: type 1, range 32, base fe200000, size 20, enabled pcib0: slot 4 INTA routed to irq 22 found-> vendor=0x8086, dev=0x1229, revid=0x08 bus=0, slot=4, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=22 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fe5fd000, size 12, enabled map[14]: type 4, range 32, base 0000c400, size 6, enabled map[18]: type 1, range 32, base fe400000, size 20, enabled pcib0: slot 6 INTA routed to irq 31 found-> vendor=0x8086, dev=0x1229, revid=0x08 bus=0, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=31 powerspec 2 supports D0 D1 D2 D3 current D0 map[90]: type 4, range 32, base 00000580, size 4, enabled found-> vendor=0x1166, dev=0x0200, revid=0x50 bus=0, slot=15, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x1166, dev=0x0211, revid=0x00 bus=0, slot=15, func=1 class=01-01-8a, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base fffff000, size 12, memory disabled found-> vendor=0x1166, dev=0x0220, revid=0x04 bus=0, slot=15, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=255 pci0: at device 3.0 (no driver attached) fxp0: port 0xc000-0xc03f mem 0xfe200000-0xfe2fffff,0xfe5fc000-0xfe5fcfff irq 22 at device 4.0 on pci0 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe5fc000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1229 8086 100c 0008 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:30:48:11:b6:ab fxp0: [MPSAFE] fxp1: port 0xc400-0xc43f mem 0xfe400000-0xfe4fffff,0xfe5fd000-0xfe5fdfff irq 31 at device 6.0 on pci0 fxp1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe5fd000 fxp1: using memory space register mapping fxp1: PCI IDs: 8086 1229 8086 100c 0008 fxp1: Dynamic Standby mode is disabled miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: bpf attached fxp1: Ethernet address: 00:30:48:11:b6:aa fxp1: [MPSAFE] isab0: port 0x580-0x58f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=20 ostat1=30 ata0-master: stat=0x20 err=0x20 lsb=0x20 msb=0x20 ata0-slave: stat=0x30 err=0x30 lsb=0x30 msb=0x30 ata0: reset tp2 stat0=20 stat1=30 devices=0x0 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1-master: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1-slave: stat=0x00 err=0x01 lsb=0x7f msb=0x7f ata1: reset tp2 stat0=10 stat1=00 devices=0x4 ata1: [MPSAFE] ohci0: mem 0xfffff000-0xffffffff at device 15.2 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfffff000 pcib0: unable to route slot 15 INTA ohci0: Could not allocate irq device_attach: ohci0 attach returned 6 pcib1: pcibus 1 on motherboard pci1: on pcib1 pci1: physical bus=1 map[10]: type 4, range 32, base 0000e000, size 8, enabled map[14]: type 1, range 64, base feb60000, size 17, enabled map[1c]: type 1, range 64, base feb40000, size 17, enabled pcib1: slot 1 INTA routed to irq 24 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=1, slot=1, func=0 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x48 (2160 ns), mingnt=0x10 (4000 ns), maxlat=0x06 (1500 ns) intpin=a, irq=24 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 0000e400, size 8, enabled map[14]: type 1, range 64, base feba0000, size 17, enabled map[1c]: type 1, range 64, base feb80000, size 17, enabled pcib1: slot 1 INTB routed to irq 25 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=1, slot=1, func=1 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x48 (2160 ns), mingnt=0x10 (4000 ns), maxlat=0x06 (1500 ns) intpin=b, irq=25 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 0000e800, size 8, enabled map[14]: type 1, range 64, base febff000, size 12, enabled pcib1: slot 3 INTA routed to irq 28 found-> vendor=0x9005, dev=0x008f, revid=0x02 bus=1, slot=3, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x28 (10000 ns), maxlat=0x19 (6250 ns) intpin=a, irq=28 powerspec 2 supports D0 D3 current D0 mpt0: port 0xe000-0xe0ff mem 0xfeb40000-0xfeb5ffff,0xfeb60000-0xfeb7ffff irq 24 at device 1.0 on pci1 mpt0: Reserved 0x20000 bytes for rid 0x14 type 3 at 0xfeb60000 mpt0: [GIANT-LOCKED] mpt0: soft reset mpt1: port 0xe400-0xe4ff mem 0xfeb80000-0xfeb9ffff,0xfeba0000-0xfebbffff irq 25 at device 1.1 on pci1 mpt1: linking with peer (mpt0) mpt1: Reserved 0x20000 bytes for rid 0x14 type 3 at 0xfeba0000 panic: pmap_mapdev: Couldn't alloc kernel virtual memory cpuid = 0 KDB: enter: panic From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 5 21:53:39 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C526016A4CF for ; Wed, 5 Jan 2005 21:53:39 +0000 (GMT) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A67243D48 for ; Wed, 5 Jan 2005 21:53:38 +0000 (GMT) (envelope-from janm@transactionware.com) Received: (qmail 19151 invoked from network); 5 Jan 2005 21:53:57 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 5 Jan 2005 21:53:57 -0000 Received: (qmail 10069 invoked by uid 1026); 5 Jan 2005 21:53:57 -0000 Received: from 192.168.2.2 by new.transactionware.com (envelope-from , uid 1003) with qmail-scanner-1.23 ( Clear:RC:1(192.168.2.2):. Processed in 1.87358 secs); 05 Jan 2005 21:53:57 -0000 Received: from unknown (HELO mosm1) (192.168.2.2) by new.transactionware.com with SMTP; 5 Jan 2005 21:53:55 -0000 From: "Jan Mikkelsen" To: "'Scott Long'" , "'Jeroen Molinger'" Date: Thu, 6 Jan 2005 08:51:21 +1100 Organization: Transactionware Message-ID: <000001c4f370$b3cb7a40$0202a8c0@mosm1> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <41D6C7BF.7030405@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: Normal cc: stable@freebsd.org cc: 'Rong-En Fan' cc: scsi@freebsd.org Subject: RE: IBM ServeRAID 7k & 5.3 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 21:53:40 -0000 Hi, I'm looking at the same issue with a Serveraid 6i in an xSeries x226. In hindsight, I should have specified an iir controller, possibly with some machine other than an IBM! There seems to be an ioctl where a user mode program can issue a command to the controller to find out what is going on. Is there any documentation available for this? I've started to experiment, but I haven't done much yet. Regards, Jan Mikkelsen. > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Scott Long > Sent: Sunday, 2 January 2005 2:55 AM > To: Jeroen Molinger > Cc: stable@freebsd.org; Rong-En Fan; scsi@freebsd.org > Subject: Re: IBM ServeRAID 7k & 5.3 > > > Jeroen Molinger wrote: > > Rong-En Fan wrote: > > > >> [just for a record] > >> > >> Hi all, > >> > >> It seems ips(4) doesn't support ServeRAID 7k, however I just > >> installed 5.3-RELEASE/i386 on IBM x236 which has ServeRAID > >> 7k installed. Everything looks fine here (I'm running RAID-5 over > >> 4 HDDs). > >> > >> A little problem is that once a HDD fails, FreeBSD doesn't > >> know that unless I reboot it and saw the ips state is DEGRADED. > >> > >> > >> pciconf & dmesg are listed as below: > >> > >> ips0@pci3:14:0: class=0x010400 card=0x028e1014 chip=0x02509005 > >> rev=0x07 hdr=0x00 > >> vendor = 'Adaptec Inc' > >> class = mass storage > >> subclass = RAID > >> > >> ips0: mem > 0xcfffd000-0xcfffdfff irq 38 at > >> device 14.0 on pci3 > >> ips0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xcfffd000 > >> ips0: [GIANT-LOCKED] > >> ips0: logical drives: 1 > >> ips0: Logical Drive 0: RAID5 sectors: 430116864, state OK > >> ipsd0: on ips0 > >> ipsd0: Logical Drive (210018MB) > >> > >> Regards, > >> Rong-En Fan > >> _______________________________________________ > >> freebsd-scsi@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > >> To unsubscribe, send any mail to > "freebsd-scsi-unsubscribe@freebsd.org" > >> > >> > >> > >> > > Hai Scott, > > > > Do you know when the 7K will be fully supported. I got a > note from IBM > > that they will discontinue the ServerRAID 6M series. > > > > Best Regards > > > > Jeroen Molinger > > I guess that by 'support' that you are referring to the > problem with it > not seeing a failed drive? I really have no idea how that is supposed > to work, if at all. > > Scott > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 6 03:43:21 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20E5E16A4CE for ; Thu, 6 Jan 2005 03:43:21 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DE0E43D48 for ; Thu, 6 Jan 2005 03:43:20 +0000 (GMT) (envelope-from kc.somaratne@gmail.com) Received: by rproxy.gmail.com with SMTP id y7so182rne for ; Wed, 05 Jan 2005 19:43:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding; b=em1CL8VW9GPQ8aTKBQjrprDKt3s40SdVTeZYOF+43moFlyoorId2LcOPB2NQcAcoQmGpf/1umfnje5XzlAQ7UsuNPiqbeFvG4DdlW7hF16YRohWU2NPRNt2rCHeFqcC3rze8qmciVECfAwOakkG0uS1uMkduO3rayOP15ZJa0CY= Received: by 10.38.11.49 with SMTP id 49mr334583rnk; Wed, 05 Jan 2005 19:43:19 -0800 (PST) Received: by 10.38.79.61 with HTTP; Wed, 5 Jan 2005 19:43:19 -0800 (PST) Message-ID: <9967ef0705010519435b6bbd66@mail.gmail.com> Date: Thu, 6 Jan 2005 11:43:19 +0800 From: KC Somaratne To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: scottl@freebsd.org Subject: Re: Recommended RAID controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KC Somaratne List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 03:43:21 -0000 >>Walter Vaughan wrote: >> >> I am looking to build two new servers, and >> plan on using freeBSD. I've read the last >> 5 months of this list and while I haven't seen >> anything to scare me, I'm looking for advice on >> something that'll work pretty much out of the block >> with 5.2.1 that has pretty good tools support. >> I was all fired up about a Zero-channel Adaptec, >> but after reading it's only 4.* tools supported >> I not so sure. >> I liked what I've read about Intel's SATA >> raid that uses the iir driver, but again >> I am worried about administrative tools. >> >> Thanks >> -- > >Let me go through the list: > >Adaptec: > - There are two families of controller here. The 2010/2015 > ZCR cards are all that is left of the old family. It is > supported under 4.x and 5.x, though there are issues with > the management tools that require a few tricks to overcome > in 5.x. I'm also not terribly happy with the driver, but > I recently started cleaning it up. Adaptec provides no > support nor updates for the driver. If you have a strong > desire to use Adaptec ZCR, this is the only choice right now, > but a lot of people use it and are happy with it. > - The newer family of cards is a bit better in my opinion. > Adaptec hasn't released a newer version of the management > app for FreeBSD in several years, but the one that shipped > with the 5400S will work for all cards in the family. > Alternatively, the Linux CLI tool that Adaptec does ship > will work under FreeBSD in linux emulation mode. The driver > is well maintained. > >Intel: > - The ICP/Vortex/Intel controllers are actually owned and > produced by Adaptec now. The driver is fairly good and is > actively maintained by the vendor. A management app is > available for FreeBSD, but it will not work with FreeBSD 5.2.x > due to an inadvertent IOCTL incompatibility. I have changes > from the vendor pending right now that should hopefully fix > this for 5.3. In the mean time, the patch that I committed to > 5.2-CURRENT last month should work ok. > >AMI/LSI MegaRAID: > - This hardware used to be well supported, but the vendor no > longer provides regular updates. I don't know whether a > management app exists or not, though I doubt that it does. > >3Ware: > - Both the 6xxx/7xxx/8xxx and the 9xxx generation cards are > actively supported on FreeBSD by the vendor and are used by a > large, well-known web portal company. Not sure what the > status of management apps are. > >Compaq CISS: > - Driver is well supported by the FreeBSD community and is popular > amoung users. > >IBM ServeRAID: > - IBM provided an initial driver, and work has gone on over the > past year to clean it up and make it more robust. It only exists > for 5.x, but backporting it to 4.x would only take a few days. > No management app exists, nor can the Linux apps run on FreeBSD. > This hardware is owned and produced by Adaptec also. > >If I were to go the ZCR route right now, it would likely be with the >Intel card. I've just started playing with them, and it has been a >generally positive experience. The fact that they actively support >FreeBSD is a big plus. For SATA, it would be a toss-up between 3ware >and Adaptec. For U320 SCSI that you can buy in the channel (as opposed >to only buying from the vendor), Adaptec probably wins. > >Scott Hi, With respect to the support for the IBM ServeRAID cards, has there been a change of status since then. I am looking at getting two IBM servers with ServeRAID-6M cards to run 5.3-R. Also, are there any management apps available in 5.3 for the ServeRAID-6M card? thanks n rgds, -kc. From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 6 19:27:30 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 009D216A4CE for ; Thu, 6 Jan 2005 19:27:30 +0000 (GMT) Received: from miramanee.icarz.com (miramanee.icarz.com [207.99.22.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A29A43D1F for ; Thu, 6 Jan 2005 19:27:29 +0000 (GMT) (envelope-from kenm@icarz.com) Received: from kenxp (netb-138.icarz.com [209.123.219.138]) by miramanee.icarz.com (8.13.1/8.13.1) with SMTP id j06JRSRu026720 for ; Thu, 6 Jan 2005 14:27:28 -0500 (EST) (envelope-from kenm@icarz.com) Message-ID: <2a1f01c4f425$c2fc04c0$8adb7bd1@icarz.com> From: "Ken Menzel" To: Date: Thu, 6 Jan 2005 14:27:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: management apps for U320 RAID controllers on 5.3 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 19:27:30 -0000 Hi, We have always used adaptec asr style controllers with asr-utils package and scripts written to remotely monitor the raid using the command line raidutil program. We are now looking to do this with Ultra320 drives and FreeBSD 5.3. Can anyone recommend a controller that has or will have U320 support and tools to monitor/manage the arrays in FreeBSD 5.x? We have a database application, that updates often and needs a high speed caching RAID controller. We have used RAID 10 in the past. I was considering an Adaptec 39320A-R, it uses the 'ahd' driver but I can't seem to find a toolset for managing and monitoring.Will the LINUX "Adaptec Storage manager v2.12" RPM run under FreeBSD? What is the difference between "HostRAID" and "non-HostRAID"?! I am open to suggestions, I can't find much info on the Adaptec web site, except that FreeBSD is not a supported OS. I am also considering one of Dell's PERC controllers which I assume would use the aac-cli tool set. I saw some-one already asked similar questions about IBM serveRAID with regards to ZCR, I am not sure it would be wise to assume all things to be equal with U320 controllers! Thanks in advance for any advice on 5.3 and U320 tools! Ken ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 6 20:53:35 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 748BC16A4CE for ; Thu, 6 Jan 2005 20:53:35 +0000 (GMT) Received: from beck.quonix.net (beck.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBCB443D5C for ; Thu, 6 Jan 2005 20:53:34 +0000 (GMT) (envelope-from john@essenz.com) Received: from beck.quonix.net (localhost [127.0.0.1]) by beck.quonix.net (8.12.11/8.12.11) with ESMTP id j06KrTv8025296; Thu, 6 Jan 2005 15:53:29 -0500 (EST) Received: from localhost (essenz@localhost)j06KrSPR025293; Thu, 6 Jan 2005 15:53:28 -0500 (EST) X-Authentication-Warning: beck.quonix.net: essenz owned process doing -bs Date: Thu, 6 Jan 2005 15:53:28 -0500 (EST) From: John Von Essen X-X-Sender: essenz@beck.quonix.net To: Ken Menzel In-Reply-To: <2a1f01c4f425$c2fc04c0$8adb7bd1@icarz.com> Message-ID: <20050106153735.D24930@beck.quonix.net> References: <2a1f01c4f425$c2fc04c0$8adb7bd1@icarz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamAssassin-3.0.1-Score: -2.82/6 ALL_TRUSTED X-MimeDefang-2.48: beck.quonix.net X-Scanned-By: MIMEDefang 2.48 on 146.145.66.90 cc: freebsd-scsi@freebsd.org Subject: Re: management apps for U320 RAID controllers on 5.3 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 20:53:35 -0000 Ken, If you want RAID then dont use the 39320, use something like the 2200S or 2120S U320 Raid Controllers. The 2200S supports an optional battery module. Those cards use the new aac driver. The olrder U160 Raid cards used the asr, but they the new U320 use the aac. I forget which one worked with the raid utilities, but I have a felling its the aac. -john On Thu, 6 Jan 2005, Ken Menzel wrote: > Hi, > We have always used adaptec asr style controllers with asr-utils > package and scripts written to remotely monitor the raid using the > command line raidutil program. We are now looking to do this with > Ultra320 drives and FreeBSD 5.3. Can anyone recommend a controller > that has or will have U320 support and tools to monitor/manage the > arrays in FreeBSD 5.x? We have a database application, that updates > often and needs a high speed caching RAID controller. We have used > RAID 10 in the past. > > I was considering an Adaptec 39320A-R, it uses the 'ahd' driver but I > can't seem to find a toolset for managing and monitoring.Will the > LINUX "Adaptec Storage manager v2.12" RPM run under FreeBSD? What is > the difference between "HostRAID" and "non-HostRAID"?! I am open to > suggestions, I can't find much info on the Adaptec web site, except > that FreeBSD is not a supported OS. I am also considering one of > Dell's PERC controllers which I assume would use the aac-cli tool set. > I saw some-one already asked similar questions about IBM serveRAID > with regards to ZCR, I am not sure it would be wise to assume all > things to be equal with U320 controllers! > > Thanks in advance for any advice on 5.3 and U320 tools! > > Ken > > > > ----------------------------------------------------- > Ken Menzel ICQ# 9325188 > www.icarz.com kenm@icarz.com > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 07:15:43 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 780EA16A4CE for ; Fri, 7 Jan 2005 07:15:43 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06FE343D2D for ; Fri, 7 Jan 2005 07:15:43 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j077IlYL025348; Fri, 7 Jan 2005 00:18:47 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41DE36BE.8050205@freebsd.org> Date: Fri, 07 Jan 2005 00:14:06 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: KC Somaratne References: <9967ef0705010519435b6bbd66@mail.gmail.com> In-Reply-To: <9967ef0705010519435b6bbd66@mail.gmail.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: Recommended RAID controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 07:15:43 -0000 KC Somaratne wrote: >>>Walter Vaughan wrote: >>> >>>I am looking to build two new servers, and >>>plan on using freeBSD. I've read the last >>>5 months of this list and while I haven't seen >>>anything to scare me, I'm looking for advice on >>>something that'll work pretty much out of the block >>>with 5.2.1 that has pretty good tools support. >>>I was all fired up about a Zero-channel Adaptec, >>>but after reading it's only 4.* tools supported >>>I not so sure. >>>I liked what I've read about Intel's SATA >>>raid that uses the iir driver, but again >>>I am worried about administrative tools. >>> >>>Thanks >>>-- >> >>Let me go through the list: >> >>Adaptec: >> - There are two families of controller here. The 2010/2015 >> ZCR cards are all that is left of the old family. It is >> supported under 4.x and 5.x, though there are issues with >> the management tools that require a few tricks to overcome >> in 5.x. I'm also not terribly happy with the driver, but >> I recently started cleaning it up. Adaptec provides no >> support nor updates for the driver. If you have a strong >> desire to use Adaptec ZCR, this is the only choice right now, >> but a lot of people use it and are happy with it. >> - The newer family of cards is a bit better in my opinion. >> Adaptec hasn't released a newer version of the management >> app for FreeBSD in several years, but the one that shipped >> with the 5400S will work for all cards in the family. >> Alternatively, the Linux CLI tool that Adaptec does ship >> will work under FreeBSD in linux emulation mode. The driver >> is well maintained. >> >>Intel: >> - The ICP/Vortex/Intel controllers are actually owned and >> produced by Adaptec now. The driver is fairly good and is >> actively maintained by the vendor. A management app is >> available for FreeBSD, but it will not work with FreeBSD 5.2.x >> due to an inadvertent IOCTL incompatibility. I have changes >> from the vendor pending right now that should hopefully fix >> this for 5.3. In the mean time, the patch that I committed to >> 5.2-CURRENT last month should work ok. >> >>AMI/LSI MegaRAID: >> - This hardware used to be well supported, but the vendor no >> longer provides regular updates. I don't know whether a >> management app exists or not, though I doubt that it does. >> >>3Ware: >> - Both the 6xxx/7xxx/8xxx and the 9xxx generation cards are >> actively supported on FreeBSD by the vendor and are used by a >> large, well-known web portal company. Not sure what the >> status of management apps are. >> >>Compaq CISS: >> - Driver is well supported by the FreeBSD community and is popular >> amoung users. >> >>IBM ServeRAID: >> - IBM provided an initial driver, and work has gone on over the >> past year to clean it up and make it more robust. It only exists >> for 5.x, but backporting it to 4.x would only take a few days. >> No management app exists, nor can the Linux apps run on FreeBSD. >> This hardware is owned and produced by Adaptec also. >> >>If I were to go the ZCR route right now, it would likely be with the >>Intel card. I've just started playing with them, and it has been a >>generally positive experience. The fact that they actively support >>FreeBSD is a big plus. For SATA, it would be a toss-up between 3ware >>and Adaptec. For U320 SCSI that you can buy in the channel (as opposed >>to only buying from the vendor), Adaptec probably wins. >> >>Scott > > > Hi, > > With respect to the support for the IBM ServeRAID cards, has there been a change > of status since then. I am looking at getting two IBM servers with ServeRAID-6M > cards to run 5.3-R. > > Also, are there any management apps available in 5.3 for the ServeRAID-6M card? > > thanks n rgds, > -kc. There really is no way to monitor or manage a serveraid card under FreeBSD. IBM/Adaptec seems to have no interest in releasing specs or porting their apps, and there is no way to make the linux apps work. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 07:17:59 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B814116A4CE; Fri, 7 Jan 2005 07:17:59 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3859543D1D; Fri, 7 Jan 2005 07:17:59 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j077KtGj025368; Fri, 7 Jan 2005 00:20:56 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41DE373E.8090805@freebsd.org> Date: Fri, 07 Jan 2005 00:16:14 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jan Mikkelsen References: <000001c4f370$b3cb7a40$0202a8c0@mosm1> In-Reply-To: <000001c4f370$b3cb7a40$0202a8c0@mosm1> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: 'Rong-En Fan' cc: stable@freebsd.org cc: scsi@freebsd.org Subject: Re: IBM ServeRAID 7k & 5.3 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 07:17:59 -0000 Jan Mikkelsen wrote: > Hi, > > I'm looking at the same issue with a Serveraid 6i in an xSeries x226. In > hindsight, I should have specified an iir controller, possibly with some > machine other than an IBM! > > There seems to be an ioctl where a user mode program can issue a command to > the controller to find out what is going on. Is there any documentation > available for this? I've started to experiment, but I haven't done much > yet. > > Regards, > > Jan Mikkelsen. > There is no documentation on anything related to this that I know of. Sorry. These are decent cards, but there seems to be little chance that Adaptec or IBM will support online management under FreeBSD. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 07:37:41 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE16716A4CE for ; Fri, 7 Jan 2005 07:37:41 +0000 (GMT) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 00B6A43D3F for ; Fri, 7 Jan 2005 07:37:40 +0000 (GMT) (envelope-from janm@transactionware.com) Received: (qmail 27774 invoked from network); 7 Jan 2005 07:37:59 -0000 Received: from new.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 7 Jan 2005 07:37:59 -0000 Received: (qmail 27092 invoked by uid 1026); 7 Jan 2005 07:37:59 -0000 Received: from 192.168.1.32 by new.transactionware.com (envelope-from , uid 1003) with qmail-scanner-1.23 ( Clear:RC:1(192.168.1.32):. Processed in 1.887183 secs); 07 Jan 2005 07:37:59 -0000 Received: from janm.transactionware.com (HELO ?192.168.1.32?) (192.168.1.32) by new.transactionware.com with SMTP; 7 Jan 2005 07:37:57 -0000 Message-ID: <41DE3CC6.7010803@transactionware.com> Date: Fri, 07 Jan 2005 18:39:50 +1100 From: Jan Mikkelsen User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <000001c4f370$b3cb7a40$0202a8c0@mosm1> <41DE373E.8090805@freebsd.org> In-Reply-To: <41DE373E.8090805@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: 'Rong-En Fan' cc: stable@freebsd.org cc: scsi@freebsd.org Subject: Re: IBM ServeRAID 7k & 5.3 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 07:37:41 -0000 Hi, Scott Long wrote: > There is no documentation on anything related to this that I know of. > Sorry. These are decent cards, but there seems to be little chance that > Adaptec or IBM will support online management under FreeBSD. Thanks for the reply. I looked through the driver code and wrote an "ipsstat" utility that uses the user command ioctl to query what is going on. The output isn't pretty; my main purpose is to have someone be notified if a logical drive goes into degraded mode. Example output below. The implementation is pretty straightforward; I'm happy to hand out the source. Regards, Jan. janm@serv: src $ sudo ./ipsstat /dev/ips0 ips adaptor info for /dev/ips0 drivecount: 1 miscflags: 6 SLTflags: 0 BSTflags: 0 pwr_chg_count: 0 wrong_addr_count: 0 unident_count: 0 nvram_dev_chg_count: 0 codeblock_version: 7.00.17 bootblock_version: 7.00.17 max_concurrent_cmds: 64 max_phys_devices: 30 flash_prog_count: 0 defunct_disks: 0 rebuildflags: 15 offline_drivecount: 0 critical_drivecount: 0 config_update_count: 41 blockedflags: 0 psdn_error: 0 drivecount: 1 host_id: Null Config rebuild_rate: 15 board_desc: TMB 4 Ch processor: PPC-750 Info for logical drive 0: user_field: 5132 state: OK raid_cache_param: 1 chunk_unit_count: 2 stripe_size: 4 params: 0 logical_drive_size: 286746624 Details of chunk 0 for logical drive 0: channel: 1 target: 0 starting sector: 0 sector count: 286746624 Details of chunk 1 for logical drive 0: channel: 1 target: 1 starting sector: 0 sector count: 286746624 Device at channel 1, target 0: initiator: 0 params: 0 misc_flag: 0 state: 137 block_count: 286747728 device_id: IBM-ESXSDTN146C3S29CECWGBXTC Device at channel 1, target 1: initiator: 0 params: 0 misc_flag: 0 state: 137 block_count: 286747728 device_id: IBM-ESXSDTN146C3S29CECWDSDGE Device at channel 1, target 8: initiator: 0 params: 3 misc_flag: 0 state: 1 block_count: 0 device_id: IBM 02R0980a1 000 From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 11:42:18 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D75916A4CE for ; Fri, 7 Jan 2005 11:42:18 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDE1F43D1D for ; Fri, 7 Jan 2005 11:42:17 +0000 (GMT) (envelope-from kc.somaratne@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so207457rne for ; Fri, 07 Jan 2005 03:42:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=f11uR0Nn24FS0PUapbcmTHARgdxzmlrY0eN0TECRPKQEuYaDk6ezR4o8QQ4TzIA9MkjNwZpsA6edWaMiqn+CpN6rbzj/G2LbK/1f5BWIpdK15Q/BJPc/FMzApiT4ymDYLvqCavERhmvhDgcyX0rFAavGAUF7j2i1sEmd7tcOm4o= Received: by 10.38.15.49 with SMTP id 49mr288557rno; Fri, 07 Jan 2005 03:42:17 -0800 (PST) Received: by 10.38.79.61 with HTTP; Fri, 7 Jan 2005 03:42:17 -0800 (PST) Message-ID: <9967ef0705010703424e9081a0@mail.gmail.com> Date: Fri, 7 Jan 2005 19:42:17 +0800 From: KC Somaratne To: Scott Long In-Reply-To: <41DE36BE.8050205@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <9967ef0705010519435b6bbd66@mail.gmail.com> <41DE36BE.8050205@freebsd.org> cc: freebsd-scsi@freebsd.org Subject: Re: Recommended RAID controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KC Somaratne List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 11:42:18 -0000 On Fri, 07 Jan 2005 00:14:06 -0700, Scott Long wrote: > KC Somaratne wrote: > >>>Walter Vaughan wrote: > >>> > >>>I am looking to build two new servers, and > >>>plan on using freeBSD. I've read the last > >>>5 months of this list and while I haven't seen > >>>anything to scare me, I'm looking for advice on > >>>something that'll work pretty much out of the block > >>>with 5.2.1 that has pretty good tools support. > >>>I was all fired up about a Zero-channel Adaptec, > >>>but after reading it's only 4.* tools supported > >>>I not so sure. > >>>I liked what I've read about Intel's SATA > >>>raid that uses the iir driver, but again > >>>I am worried about administrative tools. > >>> > >>>Thanks > >>>-- > >> > >>Let me go through the list: > >> > >>Adaptec: > >> - There are two families of controller here. The 2010/2015 > >> ZCR cards are all that is left of the old family. It is > >> supported under 4.x and 5.x, though there are issues with > >> the management tools that require a few tricks to overcome > >> in 5.x. I'm also not terribly happy with the driver, but > >> I recently started cleaning it up. Adaptec provides no > >> support nor updates for the driver. If you have a strong > >> desire to use Adaptec ZCR, this is the only choice right now, > >> but a lot of people use it and are happy with it. > >> - The newer family of cards is a bit better in my opinion. > >> Adaptec hasn't released a newer version of the management > >> app for FreeBSD in several years, but the one that shipped > >> with the 5400S will work for all cards in the family. > >> Alternatively, the Linux CLI tool that Adaptec does ship > >> will work under FreeBSD in linux emulation mode. The driver > >> is well maintained. > >> > >>Intel: > >> - The ICP/Vortex/Intel controllers are actually owned and > >> produced by Adaptec now. The driver is fairly good and is > >> actively maintained by the vendor. A management app is > >> available for FreeBSD, but it will not work with FreeBSD 5.2.x > >> due to an inadvertent IOCTL incompatibility. I have changes > >> from the vendor pending right now that should hopefully fix > >> this for 5.3. In the mean time, the patch that I committed to > >> 5.2-CURRENT last month should work ok. > >> > >>AMI/LSI MegaRAID: > >> - This hardware used to be well supported, but the vendor no > >> longer provides regular updates. I don't know whether a > >> management app exists or not, though I doubt that it does. > >> > >>3Ware: > >> - Both the 6xxx/7xxx/8xxx and the 9xxx generation cards are > >> actively supported on FreeBSD by the vendor and are used by a > >> large, well-known web portal company. Not sure what the > >> status of management apps are. > >> > >>Compaq CISS: > >> - Driver is well supported by the FreeBSD community and is popular > >> amoung users. > >> > >>IBM ServeRAID: > >> - IBM provided an initial driver, and work has gone on over the > >> past year to clean it up and make it more robust. It only exists > >> for 5.x, but backporting it to 4.x would only take a few days. > >> No management app exists, nor can the Linux apps run on FreeBSD. > >> This hardware is owned and produced by Adaptec also. > >> > >>If I were to go the ZCR route right now, it would likely be with the > >>Intel card. I've just started playing with them, and it has been a > >>generally positive experience. The fact that they actively support > >>FreeBSD is a big plus. For SATA, it would be a toss-up between 3ware > >>and Adaptec. For U320 SCSI that you can buy in the channel (as opposed > >>to only buying from the vendor), Adaptec probably wins. > >> > >>Scott > > > > > > Hi, > > > > With respect to the support for the IBM ServeRAID cards, has there been a change > > of status since then. I am looking at getting two IBM servers with ServeRAID-6M > > cards to run 5.3-R. > > > > Also, are there any management apps available in 5.3 for the ServeRAID-6M card? > > > > thanks n rgds, > > -kc. > > There really is no way to monitor or manage a serveraid card under > FreeBSD. IBM/Adaptec seems to have no interest in releasing specs or > porting their apps, and there is no way to make the linux apps work. > > Scott > Hi, Do I have any other choices of well supported SCSI RAID cards that I can use on a IBM eServer xSeries255 that you can recommend to use with FreeBSD 5.3-R? Thnks in advance, -kc. From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 15:19:47 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D58E516A4CE for ; Fri, 7 Jan 2005 15:19:47 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65CA143D3F for ; Fri, 7 Jan 2005 15:19:47 +0000 (GMT) (envelope-from kc.somaratne@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so255537rne for ; Fri, 07 Jan 2005 07:19:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=hk40lSgU/YrY+s/loLRwilG6+DblJ5UhNm8m67IMwFbQRWZwlZO78BrhArItAYk+tXZH3HHpTi+7MZxR/8WpOKicIDr7RL6fflCQakiNEvRLZF6GjxHYHjoudLZeVFduYY31XB2/v8PtmqXBJS1pWxGHYWE+cEiWV3QvM7rhX38= Received: by 10.38.99.16 with SMTP id w16mr61394rnb; Fri, 07 Jan 2005 07:19:46 -0800 (PST) Received: by 10.38.79.61 with HTTP; Fri, 7 Jan 2005 07:19:46 -0800 (PST) Message-ID: <9967ef0705010707196cf0434b@mail.gmail.com> Date: Fri, 7 Jan 2005 23:19:46 +0800 From: KC Somaratne To: scottl@freebsd.org In-Reply-To: <9967ef0705010703424e9081a0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <9967ef0705010519435b6bbd66@mail.gmail.com> <41DE36BE.8050205@freebsd.org> <9967ef0705010703424e9081a0@mail.gmail.com> cc: freebsd-scsi@freebsd.org Subject: Fwd: Recommended RAID controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KC Somaratne List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 15:19:48 -0000 On Fri, 07 Jan 2005 00:14:06 -0700, Scott Long wrote: > > Hi, > > > > With respect to the support for the IBM ServeRAID cards, has there been a change > > of status since then. I am looking at getting two IBM servers with ServeRAID-6M > > cards to run 5.3-R. > > > > Also, are there any management apps available in 5.3 for the ServeRAID-6M card? > > > > thanks n rgds, > > -kc. > > There really is no way to monitor or manage a serveraid card under > FreeBSD. IBM/Adaptec seems to have no interest in releasing specs or > porting their apps, and there is no way to make the linux apps work. > > Scott > Hi, Do I have any other choices of well supported SCSI RAID cards that I can use on a IBM eServer xSeries255 that you can recommend to use with FreeBSD 5.3-R? Thnks in advance, -kc. PS: A card that has good management apps support. What is the management app support for the Adaptec SCSI RAID 2230SLP like? From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 15:30:57 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FFCF16A4CE for ; Fri, 7 Jan 2005 15:30:57 +0000 (GMT) Received: from miramanee.icarz.com (miramanee.icarz.com [207.99.22.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1F4643D1F for ; Fri, 7 Jan 2005 15:30:56 +0000 (GMT) (envelope-from kenm@icarz.com) Received: from kenxp (netb-138.icarz.com [209.123.219.138]) by miramanee.icarz.com (8.13.1/8.13.1) with SMTP id j07FUdja080655; Fri, 7 Jan 2005 10:30:43 -0500 (EST) (envelope-from kenm@icarz.com) Message-ID: <011b01c4f4cd$d97a4b00$8adb7bd1@icarz.com> From: "Ken Menzel" To: "John Von Essen" References: <2a1f01c4f425$c2fc04c0$8adb7bd1@icarz.com> <20050106153735.D24930@beck.quonix.net> Date: Fri, 7 Jan 2005 10:30:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 cc: freebsd-scsi@freebsd.org Subject: Re: management apps for U320 RAID controllers on 5.3 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 15:30:57 -0000 Thanks John, Yes there is /usr/ports/sysutils/aaccli !!! Looks like the 2200S is what I want, thanks! Ken ----- Original Message ----- From: "John Von Essen" To: "Ken Menzel" Cc: Sent: Thursday, January 06, 2005 3:53 PM Subject: Re: management apps for U320 RAID controllers on 5.3 > Ken, > > If you want RAID then dont use the 39320, use something like the > 2200S or > 2120S U320 Raid Controllers. The 2200S supports an optional battery > module. Those cards use the new aac driver. The olrder U160 Raid > cards > used the asr, but they the new U320 use the aac. I forget which one > worked > with the raid utilities, but I have a felling its the aac. > > -john > > > On Thu, 6 Jan 2005, Ken Menzel wrote: > >> Hi, >> We have always used adaptec asr style controllers with asr-utils >> package and scripts written to remotely monitor the raid using the >> command line raidutil program. We are now looking to do this with >> Ultra320 drives and FreeBSD 5.3. Can anyone recommend a controller >> that has or will have U320 support and tools to monitor/manage the >> arrays in FreeBSD 5.x? We have a database application, that >> updates >> often and needs a high speed caching RAID controller. We have used >> RAID 10 in the past. >> >> I was considering an Adaptec 39320A-R, it uses the 'ahd' driver but >> I >> can't seem to find a toolset for managing and monitoring.Will the >> LINUX "Adaptec Storage manager v2.12" RPM run under FreeBSD? What >> is >> the difference between "HostRAID" and "non-HostRAID"?! I am open to >> suggestions, I can't find much info on the Adaptec web site, >> except >> that FreeBSD is not a supported OS. I am also considering one of >> Dell's PERC controllers which I assume would use the aac-cli tool >> set. >> I saw some-one already asked similar questions about IBM serveRAID >> with regards to ZCR, I am not sure it would be wise to assume all >> things to be equal with U320 controllers! >> >> Thanks in advance for any advice on 5.3 and U320 tools! >> >> Ken >> >> >> >> ----------------------------------------------------- >> Ken Menzel ICQ# 9325188 >> www.icarz.com kenm@icarz.com >> >> _______________________________________________ >> freebsd-scsi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >> To unsubscribe, send any mail to >> "freebsd-scsi-unsubscribe@freebsd.org" >> From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 18:42:18 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DEAE16A4CE for ; Fri, 7 Jan 2005 18:42:18 +0000 (GMT) Received: from hm61.locaweb.com.br (hm61.locaweb.com.br [200.213.197.161]) by mx1.FreeBSD.org (Postfix) with SMTP id 6525943D39 for ; Fri, 7 Jan 2005 18:42:17 +0000 (GMT) (envelope-from gustavo.hideyuki@hideyuki.eng.br) Received: (qmail 12678 invoked from network); 7 Jan 2005 18:42:10 -0000 Received: from unknown (10.1.10.145) by hm61.locaweb.com.br with QMTP; 7 Jan 2005 18:42:10 -0000 Received: (qmail 22784 invoked by uid 1000); 7 Jan 2005 18:42:14 -0000 Received: from unknown (10.1.10.15) by hm145.locaweb.com.br with QMQP; 7 Jan 2005 18:42:14 -0000 Message-ID: <20050107184214.8947.qmail@hm15.locaweb.com.br> From: "Gustavo Hideyuki Okamoto" Date: Fri, 7 Jan 2005 16:42:14 -0200 To: freebsd-scsi@freebsd.org References: In-Reply-To: X-Mailer: LocaMail X-IPAddress: 200.234.206.43 X-Sender: gustavo.hideyuki@hideyuki.eng.br MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Adaptec SCSI RAID 2200S and Firmware 7349 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 18:42:18 -0000 Does anyone have already tested the new Adaptec firmware release 7349 with the FreeBSD 5.3 Release? Regards Gustavo From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 7 22:03:19 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EFD616A4CE; Fri, 7 Jan 2005 22:03:19 +0000 (GMT) Received: from mail.wavebandwireless.com (mail.wavebandwireless.com [65.248.172.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43A9F43D1D; Fri, 7 Jan 2005 22:03:19 +0000 (GMT) (envelope-from jeff@solutionsitconsulting.com) Received: from jeff (office.solutionsitconsulting.com [65.248.173.50]) by mail.wavebandwireless.com (Postfix) with ESMTP id 8B67D48E0AB; Fri, 7 Jan 2005 16:03:18 -0600 (CST) From: "Jeff Tollison" To: , Date: Fri, 7 Jan 2005 16:01:16 -0600 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcT1BGjKhhaurT4lToqthofHmpteXg== Message-Id: <20050107220318.8B67D48E0AB@mail.wavebandwireless.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Sony autoloader X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 22:03:19 -0000 Hello, I have having difficulties setting up a Sony AIT-1 External Autoloader TSL-SA300C to work with FreeBSD 5.3. When I boot the system, I get this: . . . pci1: at device 7.0 (no driver attached) . . . I have a GENERIC kernel, so I have the "device scbus" and "device ch" installed in the kernel. Any ideas? Thanks, Jeff Tollison Network Specialist Solutions IT Consulting Waveband Wireless Internet From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 00:00:45 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5704216A4D0; Sat, 8 Jan 2005 00:00:45 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6BF243D45; Sat, 8 Jan 2005 00:00:44 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j0800ftn010295; Fri, 7 Jan 2005 18:00:41 -0600 (CST) (envelope-from dan) Date: Fri, 7 Jan 2005 18:00:41 -0600 From: Dan Nelson To: Jeff Tollison Message-ID: <20050108000041.GA99385@dan.emsphone.com> References: <20050107220318.8B67D48E0AB@mail.wavebandwireless.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050107220318.8B67D48E0AB@mail.wavebandwireless.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Sony autoloader X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 00:00:45 -0000 In the last episode (Jan 07), Jeff Tollison said: > I have having difficulties setting up a Sony AIT-1 External > Autoloader TSL-SA300C to work with FreeBSD 5.3. When I boot the > system, I get this: > > pci1: at device 7.0 (no driver attached) > > I have a GENERIC kernel, so I have the "device scbus" and "device ch" > installed in the kernel. Looks like you're missing the driver for your server's SCSI card. GENERIC should have all the SCSI drivers built in, though. Maybe it's a supported card using a new PCI ID. What does "pciconf -lv" say for that slot? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 00:29:20 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3C1C16A4CE for ; Sat, 8 Jan 2005 00:29:20 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8916E43D2D for ; Sat, 8 Jan 2005 00:29:20 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j080S0lA007549 for ; Fri, 7 Jan 2005 17:28:00 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Fri, 07 Jan 2005 17:28:00 -0700 (MST) Message-Id: <20050107.172800.74744432.imp@harmony.village.org> To: scsi@freebsd.org From: Warner Losh X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Worrisome or no? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 00:29:21 -0000 I think I have something wrong with my system. I'm not sure what, and am trying to diagnose it. I have a 19190 card with one drive on it. The drive is connected via a cable that's believed good, through an SCA adapter that's likely believed to be good to a 36GB drive that's wide Ultra (40MB/s): da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Every so often (once every few hours) I'm getting the following in dmesg: (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x1a7) SCSIRATE(0x95) (da0:ahc0:0:0:0): READ(10). CDB: 28 0 2 81 97 c7 0 0 80 0 (da0:ahc0:0:0:0): CAM Status: SCSI Status Error (da0:ahc0:0:0:0): SCSI Status: Check Condition (da0:ahc0:0:0:0): ABORTED COMMAND asc:48,0 (da0:ahc0:0:0:0): Initiator detected error message received (da0:ahc0:0:0:0): Retrying Command (per Sense Data) What do these indicate? A bad path to disk? A bad disk? A bad controller? Space alien fucking with me? Warner From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 00:47:37 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2789C16A4CE; Sat, 8 Jan 2005 00:47:37 +0000 (GMT) Received: from mail.wavebandwireless.com (mail.wavebandwireless.com [65.248.172.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC10B43D46; Sat, 8 Jan 2005 00:47:36 +0000 (GMT) (envelope-from jeff@solutionsitconsulting.com) Received: from jeff (office.solutionsitconsulting.com [65.248.173.50]) by mail.wavebandwireless.com (Postfix) with ESMTP id C89F748E0A8; Fri, 7 Jan 2005 18:47:35 -0600 (CST) From: "Jeff Tollison" To: "'Dan Nelson'" Date: Fri, 7 Jan 2005 18:45:33 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050108000041.GA99385@dan.emsphone.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 thread-index: AcT1FTQTXYaSX4LTRaSOHv9OhO16zQABZ9YQ Message-Id: <20050108004735.C89F748E0A8@mail.wavebandwireless.com> cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: RE: Sony autoloader X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 00:47:37 -0000 pciconf -lv for the slot says: none2@pci1:7:0: class=0x010000 card=0x80101191 chip=0x80101191 rev=0x01 hdr=0x00 vendor = 'Acard Technology Corp' device = 'ATP870 Ultra Wide SCSI Contoller (AEC6712UW)' class = mass storage subclass = SCSI Thanks, Jeff Tollison Network Specialist Solutions IT Consulting Waveband Wireless Internet -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Dan Nelson Sent: Friday, January 07, 2005 6:01 PM To: Jeff Tollison Cc: freebsd-scsi@freebsd.org; freebsd-questions@freebsd.org Subject: Re: Sony autoloader In the last episode (Jan 07), Jeff Tollison said: > I have having difficulties setting up a Sony AIT-1 External Autoloader > TSL-SA300C to work with FreeBSD 5.3. When I boot the system, I get > this: > > pci1: at device 7.0 (no driver attached) > > I have a GENERIC kernel, so I have the "device scbus" and "device ch" > installed in the kernel. Looks like you're missing the driver for your server's SCSI card. GENERIC should have all the SCSI drivers built in, though. Maybe it's a supported card using a new PCI ID. What does "pciconf -lv" say for that slot? -- Dan Nelson dnelson@allantgroup.com _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 04:08:36 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F9A116A4CE for ; Sat, 8 Jan 2005 04:08:36 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FBAB43D3F for ; Sat, 8 Jan 2005 04:08:35 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j084Bj1U028967; Fri, 7 Jan 2005 21:11:46 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41DF5C62.8020906@freebsd.org> Date: Fri, 07 Jan 2005 21:06:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: KC Somaratne References: <9967ef0705010519435b6bbd66@mail.gmail.com> <41DE36BE.8050205@freebsd.org> <9967ef0705010703424e9081a0@mail.gmail.com> <9967ef0705010707196cf0434b@mail.gmail.com> In-Reply-To: <9967ef0705010707196cf0434b@mail.gmail.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: Fwd: Recommended RAID controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 04:08:36 -0000 KC Somaratne wrote: > On Fri, 07 Jan 2005 00:14:06 -0700, Scott Long wrote: > >>>Hi, >>> >>>With respect to the support for the IBM ServeRAID cards, has there been a change >>>of status since then. I am looking at getting two IBM servers with ServeRAID-6M >>>cards to run 5.3-R. >>> >>>Also, are there any management apps available in 5.3 for the ServeRAID-6M card? >>> >>>thanks n rgds, >>>-kc. >> >>There really is no way to monitor or manage a serveraid card under >>FreeBSD. IBM/Adaptec seems to have no interest in releasing specs or >>porting their apps, and there is no way to make the linux apps work. >> >>Scott >> > > Hi, > > Do I have any other choices of well supported SCSI RAID cards that I > can use on a IBM eServer xSeries255 that you can recommend to use with > FreeBSD 5.3-R? > > Thnks in advance, > -kc. > PS: A card that has good management apps support. What is the > management app support for the Adaptec SCSI RAID 2230SLP like? The 2230SLP will use the 'aaccli' that can be found in the FreeBSD ports tree, and can run the linux aaccli that can be found on the CD that comes with the card. I haven't done a lot of testing with this card to say whether or not it's reliable, but it's definitely a candidate. I really don't know what I'd recommend. The aac cards seem to be 'good enough' for most people. The amr driver is suffering from instability under heavy load, unfortunately. The ciss hardware and drivers are pretty good, but are somewhat hard to get ahold of. Scott From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 06:28:47 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 144B616A4CE; Sat, 8 Jan 2005 06:28:47 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C01F43D54; Sat, 8 Jan 2005 06:28:46 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j086SjZp025065; Sat, 8 Jan 2005 00:28:45 -0600 (CST) (envelope-from dan) Date: Sat, 8 Jan 2005 00:28:45 -0600 From: Dan Nelson To: Jeff Tollison Message-ID: <20050108062845.GA10306@dan.emsphone.com> References: <20050108000041.GA99385@dan.emsphone.com> <20050108004735.C89F748E0A8@mail.wavebandwireless.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050108004735.C89F748E0A8@mail.wavebandwireless.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Sony autoloader X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 06:28:47 -0000 In the last episode (Jan 07), Jeff Tollison said: > pciconf -lv for the slot says: > > none2@pci1:7:0: class=0x010000 card=0x80101191 chip=0x80101191 rev=0x01 > hdr=0x00 > vendor = 'Acard Technology Corp' > device = 'ATP870 Ultra Wide SCSI Contoller (AEC6712UW)' > class = mass storage > subclass = SCSI Unfortunately, I don't think there are any FreeBSD drivers for Acard controllers. There are about 3 requests a year asking about Acard support, so unless one of them volunteers to write a driver, you may be better off getting a cheap Adaptec or Symbios card. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 07:06:46 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D215A16A4CE for ; Sat, 8 Jan 2005 07:06:46 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B2F343D3F for ; Sat, 8 Jan 2005 07:06:46 +0000 (GMT) (envelope-from kc.somaratne@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so149173rnf for ; Fri, 07 Jan 2005 23:06:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding; b=BLIAZShmaEafasD4E8yWeVwj5Chsj6sjOgoKOUB3nYIfHqqB7la7p8jFtRKY4WbUqLRTkl2b3UIYcMvbTAmUrXNG8mYJK74bbw5dOcyX61zap+Os2ssdQbSlPhaTfaKc9oWGnLRbf8ZZXHMimiobTCdsQKiB91BBYAm/zuip1UQ= Received: by 10.38.150.75 with SMTP id x75mr64888rnd; Fri, 07 Jan 2005 23:06:46 -0800 (PST) Received: by 10.38.79.61 with HTTP; Fri, 7 Jan 2005 23:06:45 -0800 (PST) Message-ID: <9967ef070501072306635014f8@mail.gmail.com> Date: Sat, 8 Jan 2005 15:06:45 +0800 From: KC Somaratne To: gilstrap@nren.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Adaptec SCSI RAID 2230SLP and 5.2.1-RELEASE X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KC Somaratne List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 07:06:46 -0000 Ray Gilstrap wrote: > Hi Scott, > > Okay, the system is up and running with the change that you committed. > The kernel (5.3-STABLE) recognized the controller just fine and I was able > to do fdisk/bsdlabel/newfs/mount on aacd0. > > I haven't done any meaningful performance testing yet... I had started > playing with the (randomly chosen) Bonnie benchmark, but it reported > strange numbers that are apparently an allergic reaction to the large > amount of RAM in the machine. Let me know if there are other tests that > you'd like me to run. In the meantime, just having the array (a 3-disk > RAID 5) up and running is a great start. Thanks again! > > ray Hi Ray, How have you found the above to be behaving under 5.2.1? Are you happy with it's performance and stability? How easy/difficult is it to manage this card using the aaccli management app? I was initially considering this card for two new servers. That's when I posted this original thread to the freebsd-scsi mailing list (which you found on the google groups). Later, I was looking at the HP Smart Array 6402/128, as this seem to be supported by the widely popular ciss driver and the management app support seemed pretty good too. But the vendor is refusing to budge on the price for the whole package. So, now I am forced to back look at the Adaptec Card again. The only other option available is the IBM ServeRAID-6M which seem to be be giving headaches to a lot of people (looking at the last 3-4 months mailing list archives). Would really appreciate your feedback, as you've been using this card for over 2 weeks now. Thanks in advance, -kc. From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 14:48:00 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E440816A4CE; Sat, 8 Jan 2005 14:48:00 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E5E543D1F; Sat, 8 Jan 2005 14:47:59 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j08Ep1wl030949; Sat, 8 Jan 2005 07:51:01 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41DFF232.60007@freebsd.org> Date: Sat, 08 Jan 2005 07:46:10 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <20050108000041.GA99385@dan.emsphone.com> <20050108004735.C89F748E0A8@mail.wavebandwireless.com> <20050108062845.GA10306@dan.emsphone.com> In-Reply-To: <20050108062845.GA10306@dan.emsphone.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Sony autoloader X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 14:48:01 -0000 Dan Nelson wrote: > In the last episode (Jan 07), Jeff Tollison said: > >> pciconf -lv for the slot says: >> >>none2@pci1:7:0: class=0x010000 card=0x80101191 chip=0x80101191 rev=0x01 >>hdr=0x00 >> vendor = 'Acard Technology Corp' >> device = 'ATP870 Ultra Wide SCSI Contoller (AEC6712UW)' >> class = mass storage >> subclass = SCSI > > > Unfortunately, I don't think there are any FreeBSD drivers for Acard > controllers. There are about 3 requests a year asking about Acard > support, so unless one of them volunteers to write a driver, you may be > better off getting a cheap Adaptec or Symbios card. > There looks to be a linux driver, so writing one for FreeBSD shouldn't be impossible. Where does one get one of these cards? Scott From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 18:37:24 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55B0916A4CE; Sat, 8 Jan 2005 18:37:24 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0063843D3F; Sat, 8 Jan 2005 18:37:24 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j08IbMDJ032390; Sat, 8 Jan 2005 12:37:22 -0600 (CST) (envelope-from dan) Date: Sat, 8 Jan 2005 12:37:21 -0600 From: Dan Nelson To: Scott Long Message-ID: <20050108183721.GB10306@dan.emsphone.com> References: <20050108000041.GA99385@dan.emsphone.com> <20050108004735.C89F748E0A8@mail.wavebandwireless.com> <20050108062845.GA10306@dan.emsphone.com> <41DFF232.60007@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41DFF232.60007@freebsd.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Sony autoloader X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 18:37:24 -0000 In the last episode (Jan 08), Scott Long said: > Dan Nelson wrote: > >In the last episode (Jan 07), Jeff Tollison said: > >>pciconf -lv for the slot says: > >> > >>none2@pci1:7:0: class=0x010000 card=0x80101191 chip=0x80101191 rev=0x01 > >>hdr=0x00 > >> vendor = 'Acard Technology Corp' > >> device = 'ATP870 Ultra Wide SCSI Contoller (AEC6712UW)' > >> class = mass storage > >> subclass = SCSI > > > >Unfortunately, I don't think there are any FreeBSD drivers for Acard > >controllers. There are about 3 requests a year asking about Acard > >support, so unless one of them volunteers to write a driver, you may > >be better off getting a cheap Adaptec or Symbios card. > > There looks to be a linux driver, so writing one for FreeBSD shouldn't > be impossible. Where does one get one of these cards? Daniel O'Connor might have one, since back in 2000 he claimed to have specs for a card: http://www.FreeBSD.org/cgi/mid.cgi?XFMail.001214210618.doconnor@gsoft.com.au -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 19:07:54 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DF3216A4CE for ; Sat, 8 Jan 2005 19:07:54 +0000 (GMT) Received: from spider.tela.com (spider.tela.com [206.98.7.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCD243D53 for ; Sat, 8 Jan 2005 19:07:54 +0000 (GMT) (envelope-from mike@tela.com) Received: by spider.tela.com (Postfix, from userid 103) id 996F6111DE3E; Sat, 8 Jan 2005 13:07:53 -0600 (CST) Date: Sat, 8 Jan 2005 13:07:53 -0600 From: Mike Selner To: freebsd-scsi@freebsd.org Message-ID: <20050108190753.GA59202@spider.tela.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Adaptec 2200S hang with 5.3 kernel and APIC enabled X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 19:07:54 -0000 Hi, I have a new supermicro X6DH8-G server with an Adaptec 2200S RAID controller. 2200S firmware build 7349. I booted and installed FreeBSD from the 5.2.1 CD image. System was fine. I did cvsup to 5.3-STABLE & installed new kernel and world. When I restarted it would display: Waiting 15 seconds for SCSI devices to settle aacd0: on aac0 aacd0: 139948MB (286614016 sectors) and than hang for about 45 seconds. Then I would get a continual message: AAC0 command 0xc31c3bb8 TIMEOUT AFTER X Seconds (the command changes through a small group of values) forever. The same thing happens with the 5.3 Kernel from the MINI ISO cdrom. I was able to determine that it is related to the APIC interrupt by trying safe mode and device hints. If I include the /boot/device.hints = hint.apic.0.disabled="1" the kernel I built boots and seems to work fine. I stress tested by doing several of simultaneous compiles. The 5.2 kernel is still installed as /kernel.orig. It shows a dmesg line for the controller as: aac0: mem 0xdc000000-0xdfffffff irq 72 at device 2.0 on pci3 aac0: [MPSAFE] aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.2-0, Build 7349, S/N be8f06 aac0: Supported Options=31d7e aacp0: on aac0 aacp1: on aac0 The 5.3 kernel I built and boot with the above hint returns: aac0: mem 0xdc000000-0xdfffffff irq 5 at device 2.0 on pci3 aac0: can't set up FAST interrupt aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.2-0, Build 7349, S/N be8f06 aac0: Supported Options=31d7e aacp0: on aac0 aacp1: on aac0 My questions: 1. Is there any reason not to run with hint.apic.0.disabled="1"? Any disadvatages to the smaller number of IRQs? I do not have many devices, no usb/onboard scsi. Only need ide cdrom occasionally. 2. Wher should I report this for fixing? 3. Are there any other suggestions / recommendations? thank you -- Mike Selner From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 8 19:59:48 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A24D16A4CF for ; Sat, 8 Jan 2005 19:59:48 +0000 (GMT) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1606843D48 for ; Sat, 8 Jan 2005 19:59:48 +0000 (GMT) (envelope-from marquis@roble.com) Received: from localhost (localhost [127.0.0.1]) by mx5.roble.com (Postfix) with ESMTP id DE5B62BF1C for ; Sat, 8 Jan 2005 11:59:47 -0800 (PST) Date: Sat, 8 Jan 2005 11:59:47 -0800 (PST) From: Roger Marquis To: freebsd-scsi@freebsd.org In-Reply-To: <20050108183721.GB10306@dan.emsphone.com> References: <20050108000041.GA99385@dan.emsphone.com> <20050108004735.C89F748E0A8@mail.wavebandwireless.com> <20050108062845.GA10306@dan.emsphone.com> <41DFF232.60007@freebsd.org> <20050108183721.GB10306@dan.emsphone.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <20050108195947.DE5B62BF1C@mx5.roble.com> Subject: LSI 1030, RAID1 unsupported X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 19:59:48 -0000 On Sun May 23 2004 Scott Long wrote: >The mpt and amr drivers are largely unmaintained right now as LSI >no longer sponsors an engineer to take care of them. I'm not sure >what else to say about that other than we would gladly accept a new >maintainer. Is this likely to change in the foreseeable future? I just put together an IBM e325 and discovered that the LSI 1030's performance in RAID1 mode is abominable (5.3-RELEASE-p4, amd64, with Fujitsu MAP3367NCs). --------[ raid1, bytebench ]------------------------------------------ TEST BASELINE RESULT INDEX File Copy (30 seconds) 179.0 2353.0 13.1 Pipe-based Context Switching Test 1318.5 0.0 0.0 Shell scripts (8 concurrent) 4.0 334.9 83.7 --------[ raid0, bytebench ]------------------------------------------ File Copy (30 seconds) 179.0 62105.0 347.0 Pipe-based Context Switching Test 1318.5 0.0 0.0 Shell scripts (8 concurrent) 4.0 410.5 102.6 --------[ raid1, bonnie ]--------------------------------------------- -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 2351 1.6 1872 0.3 3132 0.5 120906 99.7 1809091 99.4 130039.0 98.3 ^^^^ ^^^^ ^^^^ --------[ raid0, bonnie ]--------------------------------------------- -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 66495 44.5 58027 10.3 72578 11.9 116567 99.7 1149760 99.6 115243.9 98.5 ^^^^^ ^^^^^ ^^^^^ ---------------------------------------------------------------------- At least there's room for an Adaptec 2200s. -- Roger Marquis Roble Systems Consulting http://www.roble.com/