From owner-freebsd-scsi@FreeBSD.ORG Mon May 5 11:02:38 2003 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 0BC5B37B405 for ; Mon, 5 May 2003 11:02:38 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AC2143FA3 for ; Mon, 5 May 2003 11:02:34 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h45I2YUp081385 for ; Mon, 5 May 2003 11:02:34 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h45I2Xll081380 for scsi@freebsd.org; Mon, 5 May 2003 11:02:33 -0700 (PDT) Date: Mon, 5 May 2003 11:02:33 -0700 (PDT) Message-Id: <200305051802.h45I2Xll081380@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: 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, 05 May 2003 18:02:38 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. From owner-freebsd-scsi@FreeBSD.ORG Tue May 6 18:51:13 2003 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 3F7CA37B401 for ; Tue, 6 May 2003 18:51:13 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D43543FA3 for ; Tue, 6 May 2003 18:51:12 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Tue, 6 May 2003 21:51:11 -0400 Message-ID: From: Don Bowman To: "'nate@root.org'" , "'freebsd-scsi@freebsd.org'" Date: Tue, 6 May 2003 21:51:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: re: aic7902: Ultra320 and ses with SEAGATE ST318452LW 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, 07 May 2003 01:51:13 -0000 On Sat, 3 May 2003, Nate Lawson wrote: >On Sat, 3 May 2003, Don Bowman wrote: >> I'm finding that I don't get any ses device with this > adapter. >> >> The system is a supermicro x5dpr motherboard, 2x 2.8GHz >> XEON with 533MHz FSB. The adaptec 7902 is onboard in this >> system. >> >Are you sure your drive is in an enclosure that offers SES? ses(4) only >attaches to devices that claim they are of type T_ENCLOSURE (see >ses_type() in sys/cam/scsi/scsi_ses.c). I don't see any devices >like that in your dmesg. > >-Nate Hmmm, you could be correct. This isn't an enclosure per se, just a drive in the case. I was confused since earlier similar systems i used supported ses on the drive or on the adapter on the motherboard, but this one doesn't seem to. Instead, this drive supports SMART. "The operating mode of S.M.A.R.T. is controlled by the DEXCPT bit and the PERF bit of the "Informational Exceptions Control Mode Page" (1Ch). The DEXCPT bit is used to enable or disable the S.M.A.R.T. process. Setting the DEXCPT bit will disable all S.M.A.R.T. functions. When enabled, S.M.A.R.T. will collect on-line data as the drive performs normal read/write operations. When the PERF bit is set, the drive is considered to be in "On-line Mode Only" and will not perform off-line functions." So I guess I will investigate that instead. From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 08:55:03 2003 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 07D6237B401 for ; Wed, 7 May 2003 08:55:03 -0700 (PDT) Received: from jess.glam.ac.uk (jess.glam.ac.uk [193.63.147.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD8FB43FA3 for ; Wed, 7 May 2003 08:55:01 -0700 (PDT) (envelope-from jdhall@glam.ac.uk) Received: from ems3.glam.ac.uk ([193.63.150.66]) by jess.glam.ac.uk with esmtp (Exim 3.35 #1) id 19DRDy-0002b5-00 for freebsd-scsi@freebsd.org; Wed, 07 May 2003 16:52:54 +0100 Received: by ems3.glam.ac.uk with Internet Mail Service (5.5.2656.59) id <28BQ08LC>; Wed, 7 May 2003 16:52:41 +0100 Message-ID: From: "Hall J D (ISeLS)" To: "'freebsd-scsi@freebsd.org'" Date: Wed, 7 May 2003 16:52:37 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: AIC-7902 problems 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, 07 May 2003 15:55:03 -0000 Hello, I've just got a SuperMicro X5DE8 motherboard based server with dual Xeon 2.4GHz processors and 2GB ram. This has got an on board AIC-7902 based dual channel Ultra 320 SCSI controller onboard. Plugged into channel A of the controller are two Fujitsu LVD Ultra320 SCA drives a 36GB and a 73GB. When trying to install FreeBSD 4.8 (or 4.7) the install starts OK but not long after the extractions of the distributions starts I start getting lot's of (da0:ahd0:0:0:0): .CDB:2a (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 errors appearing on the debug console. The install then fails. I also tried FreeBSD 5.0 and while I can get this to install and run for a short period I then start getting these SCSI errors again. Are there any know issues with the AIC-7902 driver or any parameters I can configure to fix this problem? Thanks, Jonathan From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 09:13:50 2003 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 2A81637B401 for ; Wed, 7 May 2003 09:13:50 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E45943FCB for ; Wed, 7 May 2003 09:13:49 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h47GDmPM048474; Wed, 7 May 2003 10:13:48 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h47GDm1a048473; Wed, 7 May 2003 10:13:48 -0600 (MDT) (envelope-from ken) Date: Wed, 7 May 2003 10:13:48 -0600 From: "Kenneth D. Merry" To: "Hall J D (ISeLS)" Message-ID: <20030507101348.A48403@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jdhall@glam.ac.uk on Wed, May 07, 2003 at 04:52:37PM +0100 cc: "'freebsd-scsi@freebsd.org'" Subject: Re: AIC-7902 problems 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, 07 May 2003 16:13:50 -0000 On Wed, May 07, 2003 at 16:52:37 +0100, Hall J D (ISeLS) wrote: > Hello, > > I've just got a SuperMicro X5DE8 motherboard based server with dual Xeon > 2.4GHz processors and 2GB ram. This has got an on board AIC-7902 based dual > channel Ultra 320 SCSI controller onboard. Plugged into channel A of the > controller are two Fujitsu LVD Ultra320 SCA drives a 36GB and a 73GB. > > When trying to install FreeBSD 4.8 (or 4.7) the install starts OK but not > long after the extractions of the distributions starts I start getting lot's > of > > (da0:ahd0:0:0:0): .CDB:2a > (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 > > errors appearing on the debug console. The install then fails. Is that *exactly* what it prints out? There's usually more information. In any case, asc,ascq 0x25,0x00 means "Logical unit not supported". It sounds like the drive has pretty much lost its brain, and doesn't think it has a LUN 0 anymore. > I also tried FreeBSD 5.0 and while I can get this to install and run for a > short period I then start getting these SCSI errors again. > > Are there any know issues with the AIC-7902 driver or any parameters I can > configure to fix this problem? You might try looking for updated firmware for the Fujitsu disks, or maybe Justin or Scott will have some insight into what's going on here. You could also try a newer release. There have been a number of changes to the aic79xx driver recently. The latest snapshot ISO image is here: ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/ISO-IMAGES/5.1-BETA-20030507-JPSNAP.iso You could also just try grabbing the boot floppy images from that release and see how they work: ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/5.1-BETA-20030507-JPSNAP Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 11:21:34 2003 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 B37C937B401 for ; Wed, 7 May 2003 11:21:34 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ECFE43FB1 for ; Wed, 7 May 2003 11:21:33 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Wed, 7 May 2003 14:21:31 -0400 Message-ID: From: Don Bowman To: "'Kenneth D. Merry'" , "Hall J D (ISeLS)" Date: Wed, 7 May 2003 14:21:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-scsi@freebsd.org'" Subject: RE: AIC-7902 problems 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, 07 May 2003 18:21:35 -0000 From: Kenneth D. Merry [mailto:ken@kdm.org] > > On Wed, May 07, 2003 at 16:52:37 +0100, Hall J D (ISeLS) wrote: > > Hello, > > > > I've just got a SuperMicro X5DE8 motherboard based server > with dual Xeon > > 2.4GHz processors and 2GB ram. This has got an on board > AIC-7902 based dual > > channel Ultra 320 SCSI controller onboard. Plugged into > channel A of the > > controller are two Fujitsu LVD Ultra320 SCA drives a 36GB > and a 73GB. > > > > When trying to install FreeBSD 4.8 (or 4.7) the install > starts OK but not > > long after the extractions of the distributions starts I > start getting lot's > > of > > > > (da0:ahd0:0:0:0): .CDB:2a > > (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 > > > > errors appearing on the debug console. The install then fails. > > Is that *exactly* what it prints out? There's usually more > information. > > In any case, asc,ascq 0x25,0x00 means "Logical unit not > supported". It > sounds like the drive has pretty much lost its brain, and > doesn't think it > has a LUN 0 anymore. > > > I also tried FreeBSD 5.0 and while I can get this to > install and run for a > > short period I then start getting these SCSI errors again. > > > > Are there any know issues with the AIC-7902 driver or any > parameters I can > > configure to fix this problem? > > You might try looking for updated firmware for the Fujitsu > disks, or maybe > Justin or Scott will have some insight into what's going on here. > > You could also try a newer release. There have been a number > of changes to > the aic79xx driver recently. > FWIW, we have just run into the same issue with new supermicro X5 motherboards as well. Downgrading the system bios to c182 from 1.3c (no idea what these mean:) made the problem go away. We are working with supermicro support on it right now. The issue is exacerbated by having any other PCI devices on the same bus as the AIC7902. Since we are using the 1U system, this means using the slim pci slot or the USB in the ICH3. We get, sometime after booting (@ random intervals) Current Parameters: (pass0:ahd0:0:0:0): sync parameter: 8 (pass0:ahd0:0:0:0): frequency: 160.000MHz (pass0:ahd0:0:0:0): offset: 63 (pass0:ahd0:0:0:0): bus width: 16 bits (pass0:ahd0:0:0:0): disconnection is enabled (pass0:ahd0:0:0:0): tagged queueing is enabled # Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 b 60 ff 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported We are using a seagate cheetah drive with Ultra 320 scsi. The current theory is that either: a) the new supermicro system bios has upgraded some firwmare for the adaptect 7902 b) the new supermicro system bios has changed the pci arbiter on the ICH3 Upgrading the seagate drive bios had no affect. Changing the packetising to 'off' in the adaptec bios (or via camcontrol) may reduce the problem. I am using the latest RELENG-4 aic7xxx driver. If anyone has any suggestions for me, i'd love to hear them, i've got a large number of these we need to ship asap, and the problem has just cropped up with the new system bios. downgrading the system bios brings back some problems i'd prefer not to see (disables ECC for example). we've also found that seagate's 'seatools' utility under win2k won't run on this system (it doesn't detect the drive). It will if packetisation is disabled for some reason. I'm going to try seagate's 'seatools' os-less version next. camcontrol changing clock down or other parameters doesn't fix issue. drive otherwise seems to work ok, but this error causes consternation. --don From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 11:37:03 2003 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 ED34037B401 for ; Wed, 7 May 2003 11:37:03 -0700 (PDT) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AE6A43F75 for ; Wed, 7 May 2003 11:37:03 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (mail [198.78.66.163])h47Ib3eq065205 for ; Wed, 7 May 2003 11:37:03 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Date: Wed, 7 May 2003 11:37:02 -0700 (PDT) From: Josh Brooks To: freebsd-scsi@freebsd.org Message-ID: <20030507113048.Y5537-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: aaccli core dumps ... looking for solution... 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, 07 May 2003 18:37:04 -0000 Hello, I had some mirrors that had members marked offline, and before I buy new disks and replace them i wanted to try (at least once) to verify them and rejoin them and see how long they last. So, I started aaccli and ran: disk verify /repair=TRUE (2,1,0) and then ran: disk verify /repair=TRUE (3,2,0) so i was running two verifys concurrently - I checked it by running `task list` a few times, and they were both proceeding just fine. So I went to bed. I wake up this morning, and the machine is fine, but I can no longer use aaccli. When I run it, it starts, I get the prompt, and I can run things like `controller list`, but when I try to `open aac0` i get: CLI > open aac0 Executing: open "aac0" AAC0> Floating exception (core dumped)r: , State:DNE 100.0% So ... it looks like the ANSI screen drawing screws up a little, as it prints the core dump message on top of the status: done message ... ------- So, I am wondering what to do ... I cannot check the state of my disks without being able to open the controller ... but I also cannot reboot this machine right now (since, presumably that would just make this problem go away). Any suggestions ? I was thinking of running one of these commands: controller rescan - Rescans the SCSI buses, and updates all underlying structures. controller reset_scsi_bus - Resets the specified SCSI bus. controller resume_io - Does rescan operation and then resumes IO after pause_io. But I am afraid to run them on this live, running system - can anyone tell me if any of these commands, in general, are safe to run as an attempt to "slap the controller and make it behave" ? Any comments appreciated... From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 11:55:21 2003 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 662F337B401 for ; Wed, 7 May 2003 11:55:21 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA4A843F75 for ; Wed, 7 May 2003 11:55:20 -0700 (PDT) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h47IptZ20058; Wed, 7 May 2003 11:51:55 -0700 Received: from btc.adaptec.com (FWTESTSYS2.adaptec.com [10.10.3.60] (may be forged)) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id LAA08242; Wed, 7 May 2003 11:55:12 -0700 (PDT) Message-ID: <3EB95680.8060009@btc.adaptec.com> Date: Wed, 07 May 2003 12:54:56 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Brooks References: <20030507113048.Y5537-100000@mail.econolodgetulsa.com> In-Reply-To: <20030507113048.Y5537-100000@mail.econolodgetulsa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: aaccli core dumps ... looking for solution... 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, 07 May 2003 18:55:21 -0000 If the aaccli died while it had the controller open, then the refcount in the driver will remain non-zero and you won't be able to open it again until you reboot (it's a long-standing bug that I'll hopefully fix someday). However, rebuild, scrub, clear, and verify tasks are designed to survive reboots. The adapter will merely pick up where it left off a few seconds after the reboot. This will not affect your data integrity any more than it is now. The pause/resume functions are rather dangerous in general and I would not recommend using them without good reason. aaccli is very much a 'no seatbelts' application. Scott Josh Brooks wrote: > Hello, > > I had some mirrors that had members marked offline, and before I buy new > disks and replace them i wanted to try (at least once) to verify them and > rejoin them and see how long they last. > > So, I started aaccli and ran: > > disk verify /repair=TRUE (2,1,0) > > and then ran: > > disk verify /repair=TRUE (3,2,0) > > so i was running two verifys concurrently - I checked it by running `task > list` a few times, and they were both proceeding just fine. So I went to > bed. > > I wake up this morning, and the machine is fine, but I can no longer use > aaccli. When I run it, it starts, I get the prompt, and I can run things > like `controller list`, but when I try to `open aac0` i get: > > CLI > open aac0 > Executing: open "aac0" > > AAC0> > Floating exception (core dumped)r: , State:DNE 100.0% > > > So ... it looks like the ANSI screen drawing screws up a little, as it > prints the core dump message on top of the status: done message ... > > ------- > > So, I am wondering what to do ... I cannot check the state of my disks > without being able to open the controller ... but I also cannot reboot > this machine right now (since, presumably that would just make this > problem go away). > > Any suggestions ? I was thinking of running one of these commands: > > controller rescan - Rescans the SCSI buses, and updates all underlying > structures. > controller reset_scsi_bus - Resets the specified SCSI bus. > controller resume_io - Does rescan operation and then resumes IO after > pause_io. > > But I am afraid to run them on this live, running system - can anyone tell > me if any of these commands, in general, are safe to run as an attempt to > "slap the controller and make it behave" ? > > Any comments appreciated... > > _______________________________________________ > 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 May 7 15:45:19 2003 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 11BC437B401 for ; Wed, 7 May 2003 15:45:19 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 330A743F75 for ; Wed, 7 May 2003 15:45:18 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Wed, 7 May 2003 18:45:17 -0400 Message-ID: From: Don Bowman To: "'Kenneth D. Merry'" , "Hall J D (ISeLS)" Date: Wed, 7 May 2003 18:45:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-scsi@freebsd.org'" Subject: RE: AIC-7902 problems 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, 07 May 2003 22:45:19 -0000 From: Kenneth D. Merry [mailto:ken@kdm.org] > On Wed, May 07, 2003 at 16:52:37 +0100, Hall J D (ISeLS) wrote: > > Hello, > > > > I've just got a SuperMicro X5DE8 motherboard based server > with dual Xeon > > 2.4GHz processors and 2GB ram. This has got an on board > AIC-7902 based dual > > channel Ultra 320 SCSI controller onboard. Plugged into > channel A of the > > controller are two Fujitsu LVD Ultra320 SCA drives a 36GB > and a 73GB. ... I've merged the driver from MAIN (actually just dropped it in intact) to releng-4. The problem is still present for me. I'm not sure what a READ(6)/WRITE(6) not supported is. Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 (da0:ahd0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. (da0:ahd0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. (da0:ahd0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. (da0:ahd0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x25 0x0 0x0 0x0 0x0 0x0 (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 5 b1 5f 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 5 b0 7f 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 b 61 7f 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 b 61 3f 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 11 19 bf 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 b 62 bf 0 0 20 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 0 0 5 c7 1f 0 0 8 0 (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 (da0:ahd0:0:0:0): Logical unit not supported (da0:ahd0:0:0:0): Invalidating pack (da0:ahd0:0:0:0): SCB 0x13 - timed out >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x29 Mode 0x11 Card was paused SAVED_MODE[0x11] DFFSTAT[0x31] SCSISIGI[0x0] SCSIPHASE[0x0] SCSIBUS[0x0] LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x10] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] CCSCBCTL[0x0] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x1] SCB Count = 32 LASTSCB 0x14 CURRSCB 0x14 NEXTSCB 0xff40 qinstart = 2701 qinfifonext = 2701 QINFIFO: WAITING_TID_QUEUES: Pending list: 19 SCB_CONTROL[0x60] SCB_SCSIID[0x7] SCB_TAG[0x13] Kernel Free SCB list: 20 18 2 21 15 1 3 5 6 7 8 9 10 11 12 13 14 0 31 30 29 22 28 25 23 26 24 27 4 17 16 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x4, LJSCB 0xff00 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x825a, SCB 0x14, LJSCB 0x14 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x55 0x0 0x0 0x14 0x0 0x3f 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1e 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 SIMODE0[0xc] ahd0: REG0 == 0x60, SINDEX = 0x111, DINDEX = 0x102 ahd0: SCBPTR == 0x14, SCB_NEXT == 0xff40, SCB_NEXT2 == 0xff36 CDB 2a 0 0 6 69 9b STACK: 0x10 0xfe 0x2a 0x10 0x25a 0x25a 0x219 0x27 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> (da0:ahd0:0:0:0): Now packetized. Copied 18 bytes of sense data offset 12: 0xf0 0x0 0x6 0x0 0x0 0xb5 0xa8 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0xcc 0x0 0x0 0x0 May 7 22:42:33 TPC-D6-28 /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Once this has happened, the system seems pretty hosed: # camcontrol inquiry da0 spec_getpages:(#da/0x20000) I/O read failure: (error=6) bp 0xcf8911d4 vp 0xdec14ec0 size: 49152, resid: 49152, a_count: 49152, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 12 bash: /sbin/camcontrol: Input/output error From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 16:35:08 2003 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 C7C6537B401 for ; Wed, 7 May 2003 16:35:08 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 127FA43F85 for ; Wed, 7 May 2003 16:35:08 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Wed, 7 May 2003 19:35:07 -0400 Message-ID: From: Don Bowman To: Don Bowman , "'Kenneth D. Merry'" , "Hall J D (ISeLS)" Date: Wed, 7 May 2003 19:35:06 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-scsi@freebsd.org'" Subject: RE: AIC-7902 problems 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, 07 May 2003 23:35:09 -0000 From: Don Bowman [mailto:don@sandvine.com] > From: Kenneth D. Merry [mailto:ken@kdm.org] > > On Wed, May 07, 2003 at 16:52:37 +0100, Hall J D (ISeLS) wrote: > > > Hello, > > > > > > I've just got a SuperMicro X5DE8 motherboard based server > > with dual Xeon > > > 2.4GHz processors and 2GB ram. This has got an on board > > AIC-7902 based dual > > > channel Ultra 320 SCSI controller onboard. Plugged into > > channel A of the > > > controller are two Fujitsu LVD Ultra320 SCA drives a 36GB > > and a 73GB. > > ... > > I've merged the driver from MAIN (actually just dropped it > in intact) to releng-4. The problem is still present for > me. I'm not sure what a READ(6)/WRITE(6) not supported is. Further, it appears that disabling tagging causes the problem to go away (for me): camcontrol negotiate da0 negotiate -T disabled this can probably be done within your bios (^A on boot) to allow you to install. with the old system bios and the new system bios, this seems to have the same value (the entire output of camcontrol negotiate is the same) so i'm not sure what is different. --don From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 03:04:01 2003 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 B794437B401 for ; Thu, 8 May 2003 03:04:01 -0700 (PDT) Received: from jess.glam.ac.uk (jess.glam.ac.uk [193.63.147.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9BD643FAF for ; Thu, 8 May 2003 03:04:00 -0700 (PDT) (envelope-from jdhall@glam.ac.uk) Received: from ems3.glam.ac.uk ([193.63.150.66]) by jess.glam.ac.uk with esmtp (Exim 3.35 #1) id 19DiDq-0001hq-00 for freebsd-scsi@freebsd.org; Thu, 08 May 2003 11:01:54 +0100 Received: by ems3.glam.ac.uk with Internet Mail Service (5.5.2656.59) id <28BRAFTS>; Thu, 8 May 2003 11:01:40 +0100 Message-ID: From: "Hall J D (ISeLS)" To: "'freebsd-scsi@freebsd.org'" Date: Thu, 8 May 2003 11:01:35 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: AIC-7902 problems 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, 08 May 2003 10:04:02 -0000 Sorry Ken, Yes there are more details to the error message than that. I also get "copied 32 bytes of sense data" followed by the data dump. There are also some extra byes after the CDB: 2a. The trouble is I couldn't think of any easy way to get this info off the machine without writing it all down by hand. I've checked with Fujitsu and there doesn't seem to be a firmware upgrade for these drives available to download. I'm in the process of downloading the latest 5.1-BETA snapshot. I'll give that a try to see if it helps. Although as this server is for a production service it won't be a solution for me. Thanks, Jonathan -----Original Message----- From: Kenneth D. Merry [mailto:ken@kdm.org] Sent: 07 May 2003 17:14 To: Hall J D (ISeLS) Cc: 'freebsd-scsi@freebsd.org' Subject: Re: AIC-7902 problems On Wed, May 07, 2003 at 16:52:37 +0100, Hall J D (ISeLS) wrote: > Hello, > > I've just got a SuperMicro X5DE8 motherboard based server with dual Xeon > 2.4GHz processors and 2GB ram. This has got an on board AIC-7902 based dual > channel Ultra 320 SCSI controller onboard. Plugged into channel A of the > controller are two Fujitsu LVD Ultra320 SCA drives a 36GB and a 73GB. > > When trying to install FreeBSD 4.8 (or 4.7) the install starts OK but not > long after the extractions of the distributions starts I start getting lot's > of > > (da0:ahd0:0:0:0): .CDB:2a > (da0:ahd0:0:0:0): ILLEGAL REQUEST asc:25,0 > > errors appearing on the debug console. The install then fails. Is that *exactly* what it prints out? There's usually more information. In any case, asc,ascq 0x25,0x00 means "Logical unit not supported". It sounds like the drive has pretty much lost its brain, and doesn't think it has a LUN 0 anymore. > I also tried FreeBSD 5.0 and while I can get this to install and run for a > short period I then start getting these SCSI errors again. > > Are there any know issues with the AIC-7902 driver or any parameters I can > configure to fix this problem? You might try looking for updated firmware for the Fujitsu disks, or maybe Justin or Scott will have some insight into what's going on here. You could also try a newer release. There have been a number of changes to the aic79xx driver recently. The latest snapshot ISO image is here: ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/ISO-IMAGES/5.1-BET A-20030507-JPSNAP.iso You could also just try grabbing the boot floppy images from that release and see how they work: ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/5.1-BETA-20030507- JPSNAP Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 03:21:07 2003 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 04B6F37B401 for ; Thu, 8 May 2003 03:21:07 -0700 (PDT) Received: from jess.glam.ac.uk (jess.glam.ac.uk [193.63.147.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5371D43F93 for ; Thu, 8 May 2003 03:21:06 -0700 (PDT) (envelope-from jdhall@glam.ac.uk) Received: from ems3.glam.ac.uk ([193.63.150.66]) by jess.glam.ac.uk with esmtp (Exim 3.35 #1) id 19DiUN-0001sy-00 for freebsd-scsi@freebsd.org; Thu, 08 May 2003 11:18:59 +0100 Received: by ems3.glam.ac.uk with Internet Mail Service (5.5.2656.59) id <28BRAF8J>; Thu, 8 May 2003 11:18:42 +0100 Message-ID: From: "Hall J D (ISeLS)" To: "'freebsd-scsi@freebsd.org'" Date: Thu, 8 May 2003 11:18:35 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: AIC-7902 problems 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, 08 May 2003 10:21:07 -0000 From: Don Bowman [mailto:don@sandvine.com] > On Wed, May 07, 2003 at 16:52:37 +0100, Hall J D (ISeLS) wrote: > > Hello, > > > > I've just got a SuperMicro X5DE8 motherboard based server > with dual Xeon > > 2.4GHz processors and 2GB ram. This has got an on board > AIC-7902 based dual > > channel Ultra 320 SCSI controller onboard. Plugged into > channel A of the > > controller are two Fujitsu LVD Ultra320 SCA drives a 36GB > and a 73GB. > > ... > > I've merged the driver from MAIN (actually just dropped it > in intact) to releng-4. The problem is still present for > me. I'm not sure what a READ(6)/WRITE(6) not supported is. > > Further, it appears that disabling tagging causes the problem > to go away (for me): > > camcontrol negotiate da0 negotiate -T disabled > >this can probably be done within your bios (^A on boot) to allow you >to install. > >with the old system bios and the new system bios, this seems >to have the same value (the entire output of camcontrol negotiate >is the same) so i'm not sure what is different. There's no option in the SCSI BIOS that I can find to disable tagging and the cut-down version of camcontrol that's available during the 4.8 install doesn't have the negotiate option available. Incidentally my X5DE8 is running bios 1.1c and there's a 1.2b available for download. Might give that a try. By the sound of your bios version numbers you've got one of the Intel chipset boards, mine is ServerWorks GC-SL based. Jonathan From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 04:17:10 2003 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 92F0E37B401 for ; Thu, 8 May 2003 04:17:10 -0700 (PDT) Received: from zrha220a.siemens-sbs.ch (zrha220a.siemens-sbs.ch [194.204.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id C938F43FB1 for ; Thu, 8 May 2003 04:17:08 -0700 (PDT) (envelope-from pascal.fabbri@ren.es1.siemens.ch) Received: from fw3ext.siemens.ch (fw3ext.siemens-sbs.ch [194.204.64.99]) NAA08011 for ; Thu, 08 May 2003 13:17:10 +0200 Received: from zrha221a.siemens.ch by fw3ext.siemens.ch with ESMTP; Thu, 8 May 2003 13:17:05 +0200 Received: from ray.ren.es1.siemens.ch (ray.ren.es1.siemens.ch [139.16.185.140])NAA30597 for ; Thu, 08 May 2003 13:17:24 +0200 Received: from ren.es1.siemens.ch (bee.ren.es1.siemens.ch) by ray.ren.es1.siemens.ch (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with ESMTP id <0HEK00I02FAVUX@ray.ren.es1.siemens.ch> for freebsd-scsi@freebsd.org; Thu, 8 May 2003 13:16:07 +0200 (MET DST) Date: Thu, 08 May 2003 13:17:02 +0200 From: Fabbri Pascal Sender: fabbri@ray.ren.es1.siemens.ch To: freebsd-scsi@freebsd.org Message-id: <3EBA3CAE.60F6CD8D@ren.es1.siemens.ch> MIME-version: 1.0 X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.8 sun4u) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Subject: Load firmware on EXABYTE 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, 08 May 2003 11:17:10 -0000 Hello, Do you know how it is possible to load new firmware on EXABYTE SCSI Tape. Partial dmesg command: sa1 at ahc0 bus 0 target 4 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 5.000MB/s transfers (5.000MHz, offset 15) Thanks in advance, fabbri... ________________________________________ Fabbri Pascal mailto: pascal.fabbri@ren.es1.siemens.ch ________________________________________ From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 09:50:44 2003 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 B704D37B401 for ; Thu, 8 May 2003 09:50:44 -0700 (PDT) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2877C43FBD for ; Thu, 8 May 2003 09:50:44 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (mail [198.78.66.163])h48Godeq020576; Thu, 8 May 2003 09:50:43 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Date: Thu, 8 May 2003 09:50:39 -0700 (PDT) From: Josh Brooks To: Scott Long In-Reply-To: <3EB95680.8060009@btc.adaptec.com> Message-ID: <20030508094945.I5537-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: aaccli core dumps ... looking for solution... 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, 08 May 2003 16:50:45 -0000 > If the aaccli died while it had the controller open, then the refcount > in the driver will remain non-zero and you won't be able to open it > again until you reboot (it's a long-standing bug that I'll hopefully Is it bad to verify two disks simultaneously on the same controller like I did ? I am just looking for an explanation as to why aaccli died out... thanks! > Josh Brooks wrote: > > Hello, > > > > I had some mirrors that had members marked offline, and before I buy new > > disks and replace them i wanted to try (at least once) to verify them and > > rejoin them and see how long they last. > > > > So, I started aaccli and ran: > > > > disk verify /repair=TRUE (2,1,0) > > > > and then ran: > > > > disk verify /repair=TRUE (3,2,0) > > > > so i was running two verifys concurrently - I checked it by running `task > > list` a few times, and they were both proceeding just fine. So I went to > > bed. > > > > I wake up this morning, and the machine is fine, but I can no longer use > > aaccli. When I run it, it starts, I get the prompt, and I can run things > > like `controller list`, but when I try to `open aac0` i get: > > > > CLI > open aac0 > > Executing: open "aac0" > > > > AAC0> > > Floating exception (core dumped)r: , State:DNE 100.0% > > > > > > So ... it looks like the ANSI screen drawing screws up a little, as it > > prints the core dump message on top of the status: done message ... > > > > ------- > > > > So, I am wondering what to do ... I cannot check the state of my disks > > without being able to open the controller ... but I also cannot reboot > > this machine right now (since, presumably that would just make this > > problem go away). > > > > Any suggestions ? I was thinking of running one of these commands: > > > > controller rescan - Rescans the SCSI buses, and updates all underlying > > structures. > > controller reset_scsi_bus - Resets the specified SCSI bus. > > controller resume_io - Does rescan operation and then resumes IO after > > pause_io. > > > > But I am afraid to run them on this live, running system - can anyone tell > > me if any of these commands, in general, are safe to run as an attempt to > > "slap the controller and make it behave" ? > > > > Any comments appreciated... > > > > _______________________________________________ > > 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 Thu May 8 21:09:56 2003 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 EF5F637B401 for ; Thu, 8 May 2003 21:09:56 -0700 (PDT) Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1318F43F3F for ; Thu, 8 May 2003 21:09:56 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by aslan.scsiguy.com (8.12.8/8.12.8) with ESMTP id h4949lIh062470; Thu, 8 May 2003 22:09:47 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Thu, 08 May 2003 22:09:47 -0600 From: "Justin T. Gibbs" To: Don Bowman , "'Kenneth D. Merry'" , "Hall J D (ISeLS)" Message-ID: <2919880000.1052453387@aslan.scsiguy.com> In-Reply-To: References: X-Mailer: Mulberry/3.0.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: "'freebsd-scsi@freebsd.org'" Subject: RE: AIC-7902 problems 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, 09 May 2003 04:09:57 -0000 > FWIW, we have just run into the same issue with new supermicro > X5 motherboards as well. Downgrading the system bios to c182 from > 1.3c (no idea what these mean:) made the problem go away. > We are working with supermicro support on it right now. As I mentioned to Don in private email, I believe that this problem is caused by an errata in the P64H2 PCI-X hub. Information about this errata can be found here: http://developer.intel.com/design/chipsets/e7500/specupdt/290735.htm My suspicion is that the SCBs for some transactions are getting partially corrupted so the command that we think we are sending to the drive is not really getting sent. A good way to verify this is to force the PCI-X bus into PCI mode. The problem is supposed to only occur if there is another device on the PCI-X bus sharing the 7902, but it would not surprise me if the 7902 could also be hit with an unexpected GNT. I will be working with Supermicro to see if I can get both a PCI-X and SCSI bus trace to help isolate the problem. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 23:36:54 2003 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 5F0FB37B401 for ; Thu, 8 May 2003 23:36:54 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6F0443FA3 for ; Thu, 8 May 2003 23:36:53 -0700 (PDT) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h496XNZ13357; Thu, 8 May 2003 23:33:23 -0700 Received: from btc.adaptec.com ([10.100.0.149]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id XAA27486; Thu, 8 May 2003 23:36:46 -0700 (PDT) Message-ID: <3EBB4BD7.5070806@btc.adaptec.com> Date: Fri, 09 May 2003 00:33:59 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Brooks References: <20030508094945.I5537-100000@mail.econolodgetulsa.com> In-Reply-To: <20030508094945.I5537-100000@mail.econolodgetulsa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: aaccli core dumps ... looking for solution... 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, 09 May 2003 06:36:54 -0000 Josh Brooks wrote: > >>If the aaccli died while it had the controller open, then the refcount >>in the driver will remain non-zero and you won't be able to open it >>again until you reboot (it's a long-standing bug that I'll hopefully > > > Is it bad to verify two disks simultaneously on the same controller like I > did ? I am just looking for an explanation as to why aaccli died out... > > thanks! > The controller can handle the operation just fine, but there is likely a bug in aaccli. Scott > > > >>Josh Brooks wrote: >> >>>Hello, >>> >>>I had some mirrors that had members marked offline, and before I buy new >>>disks and replace them i wanted to try (at least once) to verify them and >>>rejoin them and see how long they last. >>> >>>So, I started aaccli and ran: >>> >>>disk verify /repair=TRUE (2,1,0) >>> >>>and then ran: >>> >>>disk verify /repair=TRUE (3,2,0) >>> >>>so i was running two verifys concurrently - I checked it by running `task >>>list` a few times, and they were both proceeding just fine. So I went to >>>bed. >>> >>>I wake up this morning, and the machine is fine, but I can no longer use >>>aaccli. When I run it, it starts, I get the prompt, and I can run things >>>like `controller list`, but when I try to `open aac0` i get: >>> >>>CLI > open aac0 >>>Executing: open "aac0" >>> >>>AAC0> >>>Floating exception (core dumped)r: , State:DNE 100.0% >>> >>> >>>So ... it looks like the ANSI screen drawing screws up a little, as it >>>prints the core dump message on top of the status: done message ... >>> >>>------- >>> >>>So, I am wondering what to do ... I cannot check the state of my disks >>>without being able to open the controller ... but I also cannot reboot >>>this machine right now (since, presumably that would just make this >>>problem go away). >>> >>>Any suggestions ? I was thinking of running one of these commands: >>> >>> controller rescan - Rescans the SCSI buses, and updates all underlying >>>structures. >>> controller reset_scsi_bus - Resets the specified SCSI bus. >>> controller resume_io - Does rescan operation and then resumes IO after >>>pause_io. >>> >>>But I am afraid to run them on this live, running system - can anyone tell >>>me if any of these commands, in general, are safe to run as an attempt to >>>"slap the controller and make it behave" ? >>> >>>Any comments appreciated... >>> >>>_______________________________________________ >>>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 May 9 01:28:05 2003 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 BDEE437B401 for ; Fri, 9 May 2003 01:28:05 -0700 (PDT) Received: from jess.glam.ac.uk (jess.glam.ac.uk [193.63.147.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0F9F43F85 for ; Fri, 9 May 2003 01:28:04 -0700 (PDT) (envelope-from jdhall@glam.ac.uk) Received: from ems3.glam.ac.uk ([193.63.150.66]) by jess.glam.ac.uk with esmtp (Exim 3.35 #1) id 19E3CX-0002Dr-00; Fri, 09 May 2003 09:25:57 +0100 Received: by ems3.glam.ac.uk with Internet Mail Service (5.5.2656.59) id <28BRAS09>; Fri, 9 May 2003 09:25:38 +0100 Message-ID: From: "Hall J D (ISeLS)" To: "'Justin T. Gibbs'" , Don Bowman , "'Kenneth D. Merry'" , "Hall J D (ISeLS)" Date: Fri, 9 May 2003 09:25:28 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-scsi@freebsd.org'" Subject: RE: AIC-7902 problems 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, 09 May 2003 08:28:06 -0000 Thanks for the further information Justin. My problem is I've got a X5DE8 motherboard which is ServerWorks Grand Champion SL based so I don't think it's got a P64H2. At least there's no mention of one in the motherboard manual and I can't find one on the board. Don's suggestion of turning off packetisation has helped with the problem and I've now managed to install 4.8-RELEASE. Uptime is 17 hours so far with no SCSI errors reported. Although everything is now running at Ultra160 instead of Ultra320. I don't know if this gives you any clues as to where the problem might lie. Jonathan -----Original Message----- From: Justin T. Gibbs [mailto:gibbs@scsiguy.com] Sent: 09 May 2003 05:10 To: Don Bowman; 'Kenneth D. Merry'; Hall J D (ISeLS) Cc: 'freebsd-scsi@freebsd.org' Subject: RE: AIC-7902 problems > FWIW, we have just run into the same issue with new supermicro > X5 motherboards as well. Downgrading the system bios to c182 from > 1.3c (no idea what these mean:) made the problem go away. > We are working with supermicro support on it right now. As I mentioned to Don in private email, I believe that this problem is caused by an errata in the P64H2 PCI-X hub. Information about this errata can be found here: http://developer.intel.com/design/chipsets/e7500/specupdt/290735.htm My suspicion is that the SCBs for some transactions are getting partially corrupted so the command that we think we are sending to the drive is not really getting sent. A good way to verify this is to force the PCI-X bus into PCI mode. The problem is supposed to only occur if there is another device on the PCI-X bus sharing the 7902, but it would not surprise me if the 7902 could also be hit with an unexpected GNT. I will be working with Supermicro to see if I can get both a PCI-X and SCSI bus trace to help isolate the problem. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 07:29:34 2003 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 9071F37B40D for ; Fri, 9 May 2003 07:29:34 -0700 (PDT) Received: from eowyn.nextra.cz (eowyn.nextra.cz [213.210.153.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65A6843FBF for ; Fri, 9 May 2003 07:29:33 -0700 (PDT) (envelope-from benkovsk@eowyn.nextra.cz) Received: from eowyn.nextra.cz (localhost [127.0.0.1]) by eowyn.nextra.cz (8.12.6/8.12.6) with ESMTP id h49ESuxf074041 for ; Fri, 9 May 2003 16:28:56 +0200 (CEST) (envelope-from benkovsk@eowyn.nextra.cz) Received: (from benkovsk@localhost) by eowyn.nextra.cz (8.12.6/8.12.6/Submit) id h49ESuI3074040 for freebsd-scsi@freebsd.org; Fri, 9 May 2003 16:28:56 +0200 (CEST) Date: Fri, 9 May 2003 16:28:56 +0200 From: benkovsky@nextra.cz To: freebsd-scsi@freebsd.org Message-ID: <20030509142856.GE70376@nextra.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-NCC-RegID: cz.terminal User-Agent: Mutt/1.5.4i Subject: RAID status on PowerEdge 2600 with Perc 4/DI 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, 09 May 2003 14:29:34 -0000 Hi, folks, I apologize if I ask a faq, but I did not find anything about the subject. I have a Dell PE 2600 with LSILogic PERC 4/Di RAID controller. FreeBSD 4.8 detects the status of the RAID during the boot fine: amr0: mem 0xfebf0000-0xfebfffff irq 11 at device 8.0 on pci8 amr0: Firmware 2.20, BIOS 1.03, 128MB RAM .... amrd0: on amr0 amrd0: 349390MB (715550720 sectors) RAID 5 (degraded) .... pass0 at amr0 bus 0 target 6 lun 0 pass0: Fixed Processor SCSI-2 device I would like to get the information about degraded status / disk removal in /var/log/messages without a need to reboot the machine, but I could not find how - ses does not work or I am doing something stupid. Is there currently a way to do so? Thank you for any help, Jarda Benkovsky From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 09:08:02 2003 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 9B52E37B404 for ; Fri, 9 May 2003 09:08:02 -0700 (PDT) Received: from mail0.lsil.com (mail0.lsil.com [147.145.40.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCDDC43FAF for ; Fri, 9 May 2003 09:08:01 -0700 (PDT) (envelope-from emoore@lsil.com) Received: from mhbs.lsil.com (mhbs.lsil.com [147.145.31.100]) by mail0.lsil.com (8.12.8/8.12.8) with ESMTP id h49FdDuu010810 for ; Fri, 9 May 2003 09:07:17 -0700 (PDT) Received: from atl1.se.lsil.com by mhbs.lsil.com with ESMTP; Fri, 9 May 2003 09:07:37 -0700 Received: by EXA-ATLANTA.se.lsil.com with Internet Mail Service (5.5.2653.19) id ; Fri, 9 May 2003 12:07:37 -0400 Message-Id: <0E3FA95632D6D047BA649F95DAB60E57023AE16D@EXA-ATLANTA.se.lsil.com> From: "Moore, Eric Dean" To: benkovsky@nextra.cz, freebsd-scsi@freebsd.org Date: Fri, 9 May 2003 12:07:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: RAID status on PowerEdge 2600 with Perc 4/DI 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, 09 May 2003 16:08:03 -0000 MegaRAID - http://people.freebsd.org/~emoore/MegaRAID_SCSI/UserInterfaceGUI/ MegaMON - http://people.freebsd.org/~emoore/MegaRAID_SCSI/Daemon/ Eric Moore > -----Original Message----- > From: benkovsky@nextra.cz [mailto:benkovsky@nextra.cz] > Sent: Friday, May 09, 2003 10:29 AM > To: freebsd-scsi@freebsd.org > Subject: RAID status on PowerEdge 2600 with Perc 4/DI > > > Hi, folks, > > I apologize if I ask a faq, but I did not find anything about > the subject. > > I have a Dell PE 2600 with LSILogic PERC 4/Di RAID controller. > FreeBSD 4.8 detects the status of the RAID during the boot fine: > > amr0: mem 0xfebf0000-0xfebfffff irq 11 at > device 8.0 on pci8 > amr0: Firmware 2.20, BIOS 1.03, 128MB RAM > .... > amrd0: on amr0 > amrd0: 349390MB (715550720 sectors) RAID 5 (degraded) > .... > pass0 at amr0 bus 0 target 6 lun 0 > pass0: Fixed Processor SCSI-2 device > > I would like to get the information about degraded status / > disk removal > in /var/log/messages without a need to reboot the machine, > but I could not find > how - ses does not work or I am doing something stupid. > > Is there currently a way to do so? > > Thank you for any help, > Jarda Benkovsky > > _______________________________________________ > 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 May 9 10:02:29 2003 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 E4AF037B401 for ; Fri, 9 May 2003 10:02:29 -0700 (PDT) Received: from tangelo.mediumgreen.com (tangelo.mediumgreen.com [207.188.202.243]) by mx1.FreeBSD.org (Postfix) with SMTP id 074AB43F85 for ; Fri, 9 May 2003 10:02:29 -0700 (PDT) (envelope-from lists@mediumgreen.com) Received: (qmail 65005 invoked from network); 9 May 2003 17:02:28 -0000 Received: from localhost.mediumgreen.com (HELO tangelo) (127.0.0.1) by localhost.mediumgreen.com with SMTP; 9 May 2003 17:02:28 -0000 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-scsi@freebsd.org From: lists@mediumgreen.com In-Reply-To: Message from "Moore, Eric Dean" <0E3FA95632D6D047BA649F95DAB60E57023AE16D@EXA-ATLANTA.se.lsil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 May 2003 13:02:27 -0400 Message-Id: <20030509170229.074AB43F85@mx1.FreeBSD.org> Subject: Re: RAID status on PowerEdge 2600 with Perc 4/DI 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, 09 May 2003 17:02:30 -0000 I think I heard "Moore, Eric Dean" say: >MegaRAID - http://people.freebsd.org/~emoore/MegaRAID_SCSI/UserInterfaceGUI/ >MegaMON - http://people.freebsd.org/~emoore/MegaRAID_SCSI/Daemon/ Very cool... But... kumquat# dmesg | grep -i raid amr0: mem 0xc8000000-0xcfffffff irq 14 at device 0.0 on pci3 amrd0: on amr0 amrd0: 69356MB (142041088 sectors) RAID 5 (optimal) kumquat# MegaCtrl -start 32 Bit Compiled Code MegaCtrl Version : Free BSD Version : 1.01 23-Jan-03 Set CheckConsistencyProgressInterval to 0 MegaCtrl:Service started normally MegaServ:Service started normally Megaserv started. No MegaRAID found... That last message doesn't seem quite right.. -matthew From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 10:13:21 2003 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 4C39237B401 for ; Fri, 9 May 2003 10:13:21 -0700 (PDT) Received: from mail0.lsil.com (mail0.lsil.com [147.145.40.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id B929743FB1 for ; Fri, 9 May 2003 10:13:20 -0700 (PDT) (envelope-from emoore@lsil.com) Received: from mhbs.lsil.com (mhbs.lsil.com [147.145.31.100]) by mail0.lsil.com (8.12.8/8.12.8) with ESMTP id h49EtUf0007295 for ; Fri, 9 May 2003 10:12:37 -0700 (PDT) Received: from atl1.se.lsil.com by mhbs.lsil.com with ESMTP; Fri, 9 May 2003 10:13:13 -0700 Received: by EXA-ATLANTA.se.lsil.com with Internet Mail Service (5.5.2653.19) id ; Fri, 9 May 2003 13:13:13 -0400 Message-Id: <0E3FA95632D6D047BA649F95DAB60E57023AE184@EXA-ATLANTA.se.lsil.com> From: "Moore, Eric Dean" To: lists@mediumgreen.com, freebsd-scsi@freebsd.org Date: Fri, 9 May 2003 13:13:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: RAID status on PowerEdge 2600 with Perc 4/DI 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, 09 May 2003 17:13:21 -0000 Can you check and let me know if /dev/amr0 device node was created? If not, use MAKEDEV. On Friday, May 09, 2003 1:02 PM, lists@mediumgreen.com wrote: > I think I heard "Moore, Eric Dean" say: > >MegaRAID - > http://people.freebsd.org/~emoore/MegaRAID_SCSI/UserInterfaceGUI/ > >MegaMON - http://people.freebsd.org/~emoore/MegaRAID_SCSI/Daemon/ > > Very cool... But... > > kumquat# dmesg | grep -i raid > amr0: mem 0xc8000000-0xcfffffff irq 14 at > device 0.0 on pci3 > amrd0: on amr0 > amrd0: 69356MB (142041088 sectors) RAID 5 (optimal) > > kumquat# MegaCtrl -start > > 32 Bit Compiled Code > > > MegaCtrl Version : Free BSD Version : 1.01 23-Jan-03 > > > > Set CheckConsistencyProgressInterval to 0 > > MegaCtrl:Service started normally > MegaServ:Service started normally > Megaserv started. > > No MegaRAID found... > > > > That last message doesn't seem quite right.. > > -matthew > > _______________________________________________ > 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 May 9 11:18:37 2003 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 5A2E237B404 for ; Fri, 9 May 2003 11:18:37 -0700 (PDT) Received: from tangelo.mediumgreen.com (tangelo.mediumgreen.com [207.188.202.243]) by mx1.FreeBSD.org (Postfix) with SMTP id E09B143FBF for ; Fri, 9 May 2003 11:18:35 -0700 (PDT) (envelope-from lists@mediumgreen.com) Received: (qmail 988 invoked from network); 9 May 2003 18:18:33 -0000 Received: from localhost.mediumgreen.com (HELO tangelo) (127.0.0.1) by localhost.mediumgreen.com with SMTP; 9 May 2003 18:18:33 -0000 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Moore, Eric Dean" From: lists@mediumgreen.com In-Reply-To: Message from "Moore, Eric Dean" <0E3FA95632D6D047BA649F95DAB60E57023AE184@EXA-ATLANTA.se.lsil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 May 2003 14:18:33 -0400 Message-Id: <20030509181835.E09B143FBF@mx1.FreeBSD.org> cc: freebsd-scsi@freebsd.org Subject: Re: RAID status on PowerEdge 2600 with Perc 4/DI 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, 09 May 2003 18:18:37 -0000 I think I heard "Moore, Eric Dean" say: >Can you check and let me know if /dev/amr0 device node was created? >If not, use MAKEDEV. Yup - that was it.. I thought that since I had the amrd devices that I didn't need anything else... So, I created the amr0 device, started it up: RAID Monitor Service Free BSD Version 1.02 Feb 18, 2003 started tail Initial CheckConsistency Schedule :- EnableFlag: 1 Date: 05/09/2003 DayOfWeek: 0 HourOfDay: 0 Week(s): 1 ReportChkonProgInterval: 0 seconds(0 means report in-frequently) And my machine hung - I had to call someone to go and press it's reset button. -matthew From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 12:44:26 2003 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 9712A37B401 for ; Fri, 9 May 2003 12:44:26 -0700 (PDT) Received: from web14811.mail.yahoo.com (web14811.mail.yahoo.com [66.163.172.95]) by mx1.FreeBSD.org (Postfix) with SMTP id E1F8243FAF for ; Fri, 9 May 2003 12:44:25 -0700 (PDT) (envelope-from mccrobie2000@yahoo.com) Message-ID: <20030509194425.35530.qmail@web14811.mail.yahoo.com> Received: from [68.165.211.163] by web14811.mail.yahoo.com via HTTP; Fri, 09 May 2003 12:44:25 PDT Date: Fri, 9 May 2003 12:44:25 -0700 (PDT) From: Chuck McCrobie To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Error handling of SERIAL NUMBER probe during device probing 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, 09 May 2003 19:44:26 -0000 I have a Powerfile Firewire device. It contains two DVD-RAM drives, a TOSHIBA and a PANASONIC. One of the drives does not support the probe for SERIAL NUMBER, specifically the following command: sbp0:0:1 XPT_SCSI_IO: cmd: 12 21 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense sbp0:0:1 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 3 . . . This inquiry command appears to be generated only during the SERIAL NUMBER probe (the 0x80 in the INQUIRY was found only in the SERIAL NUMBER probe.) This command and its response are repeated over and over in the log file. I left this sequence run for a few minutes with no end. I suppose I need a quirk entry in cam_xpt.c for CAM_QUIRK_NOSERIAL, but shouldn't the serial number probe simply give up on ILLEGAL_COMMAND (key=5, code=24 => INVALID FIELD IN CDB). So, should I just add the quirk or should the probe give up on inquiries that return ILLEGAL COMMAND? Thanks, Chuck McCrobie __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 13:41:42 2003 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 1C23E37B401 for ; Fri, 9 May 2003 13:41:42 -0700 (PDT) Received: from eowyn.nextra.cz (eowyn.nextra.cz [213.210.153.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E21CA43FA3 for ; Fri, 9 May 2003 13:41:39 -0700 (PDT) (envelope-from benkovsk@eowyn.nextra.cz) Received: from eowyn.nextra.cz (localhost [127.0.0.1]) by eowyn.nextra.cz (8.12.6/8.12.6) with ESMTP id h49Kf2xf078356 for ; Fri, 9 May 2003 22:41:02 +0200 (CEST) (envelope-from benkovsk@eowyn.nextra.cz) Received: (from benkovsk@localhost) by eowyn.nextra.cz (8.12.6/8.12.6/Submit) id h49Kf2gZ078355 for freebsd-scsi@freebsd.org; Fri, 9 May 2003 22:41:02 +0200 (CEST) Date: Fri, 9 May 2003 22:41:02 +0200 From: benkovsky@nextra.cz To: freebsd-scsi@freebsd.org Message-ID: <20030509204102.GF70376@nextra.cz> References: <0E3FA95632D6D047BA649F95DAB60E57023AE184@EXA-ATLANTA.se.lsil.com> <20030509181835.E09B143FBF@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030509181835.E09B143FBF@mx1.FreeBSD.org> X-NCC-RegID: cz.terminal User-Agent: Mutt/1.5.4i Subject: Re: RAID status on PowerEdge 2600 with Perc 4/DI 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, 09 May 2003 20:41:42 -0000 On Fri, May 09, 2003 at 02:18:33PM -0400, lists@mediumgreen.com wrote: > > So, I created the amr0 device, started it up: > > RAID Monitor Service Free BSD Version 1.02 Feb 18, 2003 started > tail > Initial CheckConsistency Schedule :- > EnableFlag: 1 > Date: 05/09/2003 > DayOfWeek: 0 > HourOfDay: 0 > Week(s): 1 > ReportChkonProgInterval: 0 seconds(0 means report in-frequently) > > > And my machine hung - I had to call someone to go and press it's reset > button. Similar for me. First time it caused /bin/sh to coredump immediately when run, second time it rebooted the machine -- Jaroslav Benkovsky From owner-freebsd-scsi@FreeBSD.ORG Sat May 10 23:58:45 2003 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 7C76937B40E for ; Sat, 10 May 2003 23:58:45 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA3B043FE0 for ; Sat, 10 May 2003 23:58:44 -0700 (PDT) (envelope-from scottl@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h4B6t6Z18471 for ; Sat, 10 May 2003 23:55:06 -0700 Received: from hollin.btc.adaptec.com ([10.100.0.149]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id XAA17678 for ; Sat, 10 May 2003 23:58:37 -0700 (PDT) Received: from hollin.btc.adaptec.com (localhost [127.0.0.1]) by hollin.btc.adaptec.com (8.12.9/8.12.9) with ESMTP id h4B6tkdS002754 for ; Sun, 11 May 2003 00:55:46 -0600 (MDT) (envelope-from scottl@hollin.btc.adaptec.com) Received: (from scottl@localhost) by hollin.btc.adaptec.com (8.12.9/8.12.9/Submit) id h4B6tkWI002753 for freebsd-scsi@freebsd.org; Sun, 11 May 2003 00:55:46 -0600 (MDT) (envelope-from scottl) Date: Sun, 11 May 2003 00:55:46 -0600 From: Scott Long To: freebsd-scsi@freebsd.org Message-ID: <20030511065545.GC1832@hollin.btc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: ServeRAID driver now in the tree 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: Sun, 11 May 2003 06:58:45 -0000 A lot of people have asked about this in the past few months, so I'll just a make a general announcement: At long last, there is support for the IBM ServeRAID line of SCSI RAID controllers. The 'ips' driver can be loaded as a module or compiled into the kernel as noted in /sys/i386/conf/NOTES. I've only tested this driver with a 4L model and only on ia32 (SMP), so more testing is welcomed and encouraged. I'd like to that David Jeffreys and Adaptec for providing this driver. My work on it involved porting it forward to 5.x and fixing a couple of bugs. I hope to get the 4.x version working with the bugfixes in the next week. Hopefully my time for this won't disappear like it has for the past 8 months. Also, while this driver contains a management device, there are no management apps for FreeBSD that I know of at this time. It is also unlikely that any Linux apps will work with this driver, though it's low on my priority list at the moment and I'd be happy to be proven wrong. Scott