From owner-freebsd-scsi Sun Sep 2 23: 5:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from pmp.uni-hannover.de (kirk.pmp.uni-hannover.de [130.75.117.28]) by hub.freebsd.org (Postfix) with ESMTP id B826837B401 for ; Sun, 2 Sep 2001 23:05:31 -0700 (PDT) Received: from mako.pmp.uni-hannover.de (mako [130.75.117.34]) by pmp.uni-hannover.de (8.9.3+Sun/8.9.3) with SMTP id IAA10368; Mon, 3 Sep 2001 08:07:19 +0200 (MEST) From: Gerrit Kuehn To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: problems with camcontrol rescan Date: Mon, 3 Sep 2001 08:00:30 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <0108241008070E.15703@mako.pmp.uni-hannover.de> <20010830235852.A52801@panzer.kdm.org> <200109012053.f81KrFF02761@uriah.heep.sax.de> In-Reply-To: <200109012053.f81KrFF02761@uriah.heep.sax.de> Cc: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <01090308052802.31737@mako.pmp.uni-hannover.de> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Am Sat, 01 Sep 2001 schrieb Joerg Wunsch > >> BTW: If I don't get this thing working, I'll have to buy another > >> controller anyway. So the first point (hardware) could be helped... > > Yep, we'll just have to find someone with the time, ability and > > motivation for you to send it to. :) > I might volunteer for that point. ;-) Great. :-) > Would give me an opportunity to > understand more of the CAM subsystem... Well, maybe i'll rather > assist Gerrit in learning C, this would help two persons. :-)) :-))) I fear that it may take quite a long time until we get a working driver then. > I also think it's unfortunate their driver didn't make it into our > sources. The quality of the driver might not be en par with ahc(4) or > sym(4), but OTOH, their amd(4) driver made it into the tree years ago. > We can always mention in the BUGS section of the manpage that it > doesn't survive a camcontrol rescan. ;-) Here is a update with my latest experiences with v1.09 of the driver: Booting is still fine, all devices are probed and working corretly. Rescanning works for all devices present at boot-time given a rescan a:b:c for this single device only. A Rescan of the whole bus hangs. A Rescan a:b:c of a device that has just been tuned on or off also hangs. So after all Rescan is working exactly in those cases when it's useless. :-) I guess I'll try to contact the author now... cu Gerrit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 4 12:17:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from femail35.sdc1.sfba.home.com (femail35.sdc1.sfba.home.com [24.254.60.25]) by hub.freebsd.org (Postfix) with ESMTP id 6E64637B40C; Tue, 4 Sep 2001 12:17:24 -0700 (PDT) Received: from cx543097a ([65.13.57.165]) by femail35.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010904191723.NWJV19181.femail35.sdc1.sfba.home.com@cx543097a>; Tue, 4 Sep 2001 12:17:23 -0700 From: "Ian Cartwright" To: "FreeBSD Questions" , , Subject: Strange SCSI Problems with Enlightenment? Date: Tue, 4 Sep 2001 12:13:40 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Greetings, I have an interesting quandary that perhaps someone can shed some light on for me: I have a Dell PowerApp 200 running FreeBSD 4.3-STABLE (Aug 27) and have been struggling with a SCSI problem for about a month now (ever since I installed FreeBSD on it). I compiled XFree86 4.1.0 and Enlightenment 16 out of the Ports Collection (along with various other programs, all compiled out of Ports). Installation went smoothly and I was up and running within hours. However I am getting strange ahc0 and fxp0 messages that cause the machine to respond very slowly. This starts seemingly at random (though it is more likely to occur under heavy disk usage, for instance when the daily cron jobs run) and only a reboot will fix it. At first I thought it was an issue with the ahc driver, but I have tried several versions from the CVS repository with no success. I have noticed that if I do not open any Eterm windows it seems to last longer (which I find rather strange). On a hunch, I compiled and installed KDE 2.2 and started running that. It has been running for a week with no problems. I am now testing whether running Eterm, GKRellm, or xscreensaver (the three programs I was running with Enlightenment) have any effect. Has anyone else had issues like this? Some system info: dmesg info: ahc0: port 0xcc00-0xccff mem 0xf4fff000-0xf4ffffff irq 10 at device 4.0 on pci3 aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xc800-0xc8ff mem 0xf4ffe000-0xf4ffefff irq 5 at device 4.1 on pci3 aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: port 0xece0-0xecff mem 0xfcf00000-0xfcffffff,0xfafff000-0xfaffffff irq 10 at device 4.0 on pci1 fxp0: Ethernet address 00:03:47:3b:91:06 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0xecc0-0xecdf mem 0xfce00000-0xfcefffff,0xfaffe000-0xfaffefff irq 5 at device 5.0 on pci1 fxp1: Ethernet address 00:03:47:3b:91:07 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Logs: Aug 18 04:27:27 hostname /kernel: fxp2: device timeout Aug 18 04:29:01 hostname /kernel: fxp2: device timeout Aug 18 04:31:01 hostname /kernel: ahc0: Timedout SCB already complete. Interrupts may not be functioning. Aug 18 04:33:01 hostname /kernel: fxp2: device timeout Aug 18 04:35:02 hostname /kernel: fxp2: device timeout Aug 18 04:37:02 hostname /kernel: fxp2: device timeout Aug 18 04:37:02 hostname /kernel: ahc0: Timedout SCB already complete. Interrupts may not be functioning. If anyone has any info or similar experiences I would love to hear about it. Also, I am not subscribed to these lists, so if you reply please CC me... Thanks! Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 4 13:37:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from henoch.cc.fh-lippe.de (henoch.cc.fh-lippe.de [193.16.112.72]) by hub.freebsd.org (Postfix) with ESMTP id 1E17037B403; Tue, 4 Sep 2001 13:37:03 -0700 (PDT) Received: from sulu.cc.fh-lippe.de([193.16.118.119]) (6987 bytes) by henoch.cc.fh-lippe.de via sendmail with P:esmtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 4 Sep 2001 22:37:01 +0200 (MET DST) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Mar-17) Received: from door.lippe.de(displicata.cc.fh-lippe.de[193.16.112.171]) (6615 bytes) by sulu.cc.fh-lippe.de via sendmail with P:smtp/R:smart_host/T:smtp (sender: ) id for ; Tue, 4 Sep 2001 22:36:55 +0200 (MET DST) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Mar-17) Received: from odie.lippe.de (root@odie.lippe.de [192.168.4.2]) by door.lippe.de (8.9.3/8.9.3) with ESMTP id WAA12434; Tue, 4 Sep 2001 22:26:19 +0200 (CEST) (envelope-from lkoeller@lippe.de) Received: from odie.lippe.de (lkoeller@localhost [127.0.0.1]) by odie.lippe.de (8.11.6/8.11.1) with ESMTP id f84KQIb01056; Tue, 4 Sep 2001 22:26:18 +0200 (CEST) (envelope-from lkoeller@odie.lippe.de) Message-Id: <200109042026.f84KQIb01056@odie.lippe.de> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Lars =?iso-8859-1?Q?K=F6ller?= To: "Justin T. Gibbs" , "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG, lkoeller@FreeBSD.org Subject: Wire of SCSI devices gives warning messages X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -------- Dear Justin, Kenneth! I use wired scsi devices since years, and it wored lik a charm up to = now. It seems still working, but during boot up I get the following = messages: I ask you cause I didn't see any mistake in my configuration but want = to avoid making a foolish PR. =2E... Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 d= evice = sa0: 7.812MB/s transfers (7.812MHz, offset 15) (pass0:ahc0:0:4:0): Duplicate Wired Device entry! (pass0:ahc0:0:4:0): Second device (pass device at scbus0 target 5 lun 0) = will no t be wired (pass0:ahc0:0:4:0): Duplicate Wired Device entry! (pass0:ahc0:0:4:0): Second device (pass device at scbus0 target 8 lun 0) = will no t be wired da1 at ahc1 bus 0 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device = da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing E= nabled da1: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) da3 at ahc1 bus 0 target 9 lun 0 da3: Fixed Direct Access SCSI-2 device = da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing E= nabled da3: 2061MB (4222640 512 byte sectors: 255H 63S/T 262C) da4 at ahc1 bus 0 target 10 lun 0 da4: Fixed Direct Access SCSI-2 device = da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing E= nabled da4: 2061MB (4222640 512 byte sectors: 255H 63S/T 262C) cd2 at ahc1 bus 0 target 5 lun 0 cd2: Removable CD-ROM SCSI-2 device = cd2: 10.000MB/s transfers (10.000MHz, offset 15) cd2: cd present [331802 x 2048 byte records] da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device = da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled= da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) cd3 at ahc1 bus 0 target 6 lun 0 cd3: Removable CD-ROM SCSI-2 device = cd3: 10.000MB/s transfers (10.000MHz, offset 15) cd3: cd present [345419 x 2048 byte records] da2 at ahc0 bus 0 target 8 lun 0 da2: Fixed Direct Access SCSI-2 device = da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing E= nabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Mounting root from ufs:/dev/da1s1a ccd0-3: Concatenated disk drivers lpt0: switched to polled extended mode /dev/vmmon: Module vmmon: registered with major=3D200 minor=3D0 tag=3D$Na= me: build-570 $ /dev/vmmon: Module vmmon: initialized fxp0: promiscuous mode enabled vmnet1: promiscuous mode enabled cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device = cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present -= tray c losed There are two identical Ultra wide Adaptex controllers used: ahc0: port 0xd400-0xd4ff mem 0xdefee000= -0xdefe efff irq 11 at device 9.0 on pci0 ahc1: port 0xdc00-0xdcff mem 0xdefef000= -0xdefe ffff irq 9 at device 12.0 on pci0 The kernel config file has the following entries: =2E... device ahc0 # AHA2940 and onboard AIC7xxx devices device ahc1 # device scbus0 at ahc0 # bus (required) device scbus1 at ahc1 # bus (required) device da # Access (disks) device sa # Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI) # device da0 at scbus1 target 0 # Seagate ST15150N device da1 at scbus1 target 8 # Seagate ST39102LW (DEC) device da2 at scbus0 target 8 # Seagate ST19101W device da3 at scbus1 target 9 # Seagate ST32171W device da4 at scbus1 target 10 # Seagate ST32171W # device pass15 at scbus0 target 3 # UMAX Astra 2200 # device sa0 at scbus0 target 4 # Seagate Python 28388 # device cd0 at scbus0 target 5 # Plextor PX-40TS device cd1 at scbus0 target 6 # Ricoh 7060S device cd2 at scbus1 target 5 # Pioneer DR-U10x device cd3 at scbus1 target 6 # Pioneer DR-U12x camcontrol devlist: at scbus0 target 4 lun 0 (pass0,sa0) at scbus0 target 5 lun 0 (pass1,cd0) at scbus0 target 8 lun 0 (pass2,da2) at scbus1 target 0 lun 0 (pass3,da0) at scbus1 target 5 lun 0 (pass4,cd2) at scbus1 target 6 lun 0 (pass5,cd3) at scbus1 target 8 lun 0 (pass6,da1) at scbus1 target 9 lun 0 (pass7,da3) at scbus1 target 10 lun 0 (pass8,da4) Do you have any idea where the kernel messages above results from? What have I missed? Thank you very mutch and best regards Lars -- = Lars K=F6ller E-Mail: lkoeller@cc.fh-lippe.de (LKoeller@FreeBSD.ORG) PGP-key: http://www.pgp.net/pgpnet/www-key.html -------- FreeBSD, was sonst? ---- http://www.de.freebsd.org -------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 4 14: 9:42 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id E6AFB37B40C; Tue, 4 Sep 2001 14:09:39 -0700 (PDT) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.5/8.11.5) with ESMTP id f84L9YY55883; Tue, 4 Sep 2001 15:09:34 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200109042109.f84L9YY55883@aslan.scsiguy.com> To: Lars =?iso-8859-1?Q?K=F6ller?= Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG, lkoeller@FreeBSD.ORG Subject: Re: Wire of SCSI devices gives warning messages In-Reply-To: Your message of "Tue, 04 Sep 2001 22:26:18 +0200." <200109042026.f84KQIb01056@odie.lippe.de> Date: Tue, 04 Sep 2001 15:09:34 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Dear Justin, Kenneth! > >I use wired scsi devices since years, and it wored lik a charm up to >now. It seems still working, but during boot up I get the following >messages: Is this current or stable? There are some differences in the two branches that affect wired devices. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 4 14:21:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 197CF37B40C; Tue, 4 Sep 2001 14:21:23 -0700 (PDT) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.5/8.11.5) with ESMTP id f84LLIY56024; Tue, 4 Sep 2001 15:21:18 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200109042121.f84LLIY56024@aslan.scsiguy.com> To: Lars =?iso-8859-1?Q?K=F6ller?= Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG, lkoeller@FreeBSD.ORG Subject: Re: Wire of SCSI devices gives warning messages In-Reply-To: Your message of "Tue, 04 Sep 2001 22:26:18 +0200." <200109042026.f84KQIb01056@odie.lippe.de> Date: Tue, 04 Sep 2001 15:21:18 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hmm. There seems to be a bug in the -stable code. Does this patch make a difference for you? -- Justin Index: cam_periph.c =================================================================== RCS file: /usr/cvs/src/sys/cam/cam_periph.c,v retrieving revision 1.24.2.1 diff -c -r1.24.2.1 cam_periph.c *** cam_periph.c 2000/09/11 05:37:00 1.24.2.1 --- cam_periph.c 2001/09/04 21:19:10 *************** *** 330,341 **** char pathbuf[32], *strval, *periph_name; unit = 0; - hit = 0; periph_name = p_drv->driver_name; snprintf(pathbuf, sizeof(pathbuf), "scbus%d", pathid); i = -1; while ((i = resource_locate(i, periph_name)) != -1) { dname = resource_query_name(i); dunit = resource_query_unit(i); if (resource_string_value(dname, dunit, "at", &strval) == 0) { --- 330,341 ---- char pathbuf[32], *strval, *periph_name; unit = 0; periph_name = p_drv->driver_name; snprintf(pathbuf, sizeof(pathbuf), "scbus%d", pathid); i = -1; while ((i = resource_locate(i, periph_name)) != -1) { + hit = 0; dname = resource_query_name(i); dunit = resource_query_unit(i); if (resource_string_value(dname, dunit, "at", &strval) == 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 5 13:34:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1C04A37B406; Wed, 5 Sep 2001 13:34:41 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA98712; Wed, 5 Sep 2001 14:34:34 -0600 (MDT) (envelope-from ken) Date: Wed, 5 Sep 2001 14:34:34 -0600 From: "Kenneth D. Merry" To: Ian Cartwright Cc: FreeBSD Questions , freebsd-scsi@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Strange SCSI Problems with Enlightenment? Message-ID: <20010905143433.A98671@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from ian351c@home.com on Tue, Sep 04, 2001 at 12:13:40PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Sep 04, 2001 at 12:13:40 -0700, Ian Cartwright wrote: > Greetings, > > I have an interesting quandary that perhaps someone can shed some light on > for me: > > I have a Dell PowerApp 200 running FreeBSD 4.3-STABLE (Aug 27) and have been > struggling with a SCSI problem for about a month now (ever since I installed > FreeBSD on it). I compiled XFree86 4.1.0 and Enlightenment 16 out of the > Ports Collection (along with various other programs, all compiled out of > Ports). Installation went smoothly and I was up and running within hours. > However I am getting strange ahc0 and fxp0 messages that cause the machine > to respond very slowly. This starts seemingly at random (though it is more > likely to occur under heavy disk usage, for instance when the daily cron > jobs run) and only a reboot will fix it. At first I thought it was an issue > with the ahc driver, but I have tried several versions from the CVS > repository with no success. I have noticed that if I do not open any Eterm > windows it seems to last longer (which I find rather strange). On a hunch, I > compiled and installed KDE 2.2 and started running that. It has been running > for a week with no problems. I am now testing whether running Eterm, > GKRellm, or xscreensaver (the three programs I was running with > Enlightenment) have any effect. > > Has anyone else had issues like this? > > Some system info: > > dmesg info: > ahc0: port 0xcc00-0xccff mem > 0xf4fff000-0xf4ffffff irq 10 at device 4.0 on pci3 > aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1: port 0xc800-0xc8ff mem > 0xf4ffe000-0xf4ffefff irq 5 at device 4.1 on pci3 > aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs > fxp0: port 0xece0-0xecff mem > 0xfcf00000-0xfcffffff,0xfafff000-0xfaffffff irq 10 at device 4.0 on pci1 > fxp0: Ethernet address 00:03:47:3b:91:06 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp1: port 0xecc0-0xecdf mem > 0xfce00000-0xfcefffff,0xfaffe000-0xfaffefff irq 5 at device 5.0 on pci1 > fxp1: Ethernet address 00:03:47:3b:91:07 > inphy1: on miibus1 > inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > Logs: > > Aug 18 04:27:27 hostname /kernel: fxp2: device timeout > Aug 18 04:29:01 hostname /kernel: fxp2: device timeout > Aug 18 04:31:01 hostname /kernel: ahc0: Timedout SCB already complete. > Interrupts may > not be functioning. > Aug 18 04:33:01 hostname /kernel: fxp2: device timeout > Aug 18 04:35:02 hostname /kernel: fxp2: device timeout > Aug 18 04:37:02 hostname /kernel: fxp2: device timeout > Aug 18 04:37:02 hostname /kernel: ahc0: Timedout SCB already complete. > Interrupts may > not be functioning. > > If anyone has any info or similar experiences I would love to hear about it. > Also, I am not subscribed to these lists, so if you reply please CC me... I'm not sure this is the problem, but Jonathan Lemon checked in a fix for the fxp driver on August 30th. I'm not sure if it would affect your system, but you may want to try updating to the latest -stable and see if your problem goes away. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 6 2:15:22 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id C638937B403 for ; Thu, 6 Sep 2001 02:15:16 -0700 (PDT) Received: from pythia1.hrz.uni-bielefeld.de (pythia1.hrz.uni-bielefeld.de [129.70.180.8]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.10.12.16.25.p8) with ESMTP id <0GJ8002ADHPIQS@mail.uni-bielefeld.de> for freebsd-scsi@FreeBSD.ORG; Thu, 6 Sep 2001 11:15:18 +0200 (MET DST) Received: from pythia1.hrz.uni-bielefeld.de (lkoeller@localhost) by pythia1.hrz.uni-bielefeld.de (8.10.2+Sun/8.10.2) with ESMTP id f869FA701740; Thu, 06 Sep 2001 11:15:11 +0200 (MET DST) Date: Thu, 06 Sep 2001 11:15:10 +0200 From: Lars =?iso-8859-1?Q?K=F6ller?= X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ To: "Kenneth D. Merry" , "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG, Lars =?iso-8859-1?Q?K=F6ller?= , lkoeller@cc.fh-lippe.de Message-id: <200109060915.f869FA701740@pythia1.hrz.uni-bielefeld.de> MIME-version: 1.0 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -------- Hi! >> I use wired scsi devices since years, and it wored lik a charm up to = >> now. It seems still working, but during boot up I get the following = >> messages: > > Is this current or stable? There are some differences in the two > branches that affect wired devices. Sorry, it's an top actual -stable (from last weekend, 4.4-RC) What can I do to help debugging? Regards Lars -- = E-Mail: Lars.Koeller@Uni-Bielefeld.DE \ Lars K=F6ller lkoeller@FreeBSD.org \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany = Key-ID: A430D499 \ Tel: +49 521 106 4964 ----------- FreeBSD, what else? ---- http://www.freebsd.org -------------= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 6 11:21:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from henoch.cc.fh-lippe.de (henoch.cc.fh-lippe.de [193.16.112.72]) by hub.freebsd.org (Postfix) with ESMTP id ADA6837B407 for ; Thu, 6 Sep 2001 11:21:16 -0700 (PDT) Received: from sulu.cc.fh-lippe.de([193.16.118.119]) (9946 bytes) by henoch.cc.fh-lippe.de via sendmail with P:esmtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 6 Sep 2001 20:21:15 +0200 (MET DST) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Mar-17) Received: from door.lippe.de(aurantia.cc.fh-lippe.de[193.16.112.164]) (9588 bytes) by sulu.cc.fh-lippe.de via sendmail with P:smtp/R:smart_host/T:smtp (sender: ) id for ; Thu, 6 Sep 2001 20:21:12 +0200 (MET DST) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Mar-17) Received: from odie.lippe.de (root@odie.lippe.de [192.168.4.2]) by door.lippe.de (8.9.3/8.9.3) with ESMTP id UAA56347; Thu, 6 Sep 2001 20:19:01 +0200 (CEST) (envelope-from lkoeller@lippe.de) Received: from odie.lippe.de (lkoeller@localhost [127.0.0.1]) by odie.lippe.de (8.11.6/8.11.1) with ESMTP id f86IJ1f01094; Thu, 6 Sep 2001 20:19:01 +0200 (CEST) (envelope-from lkoeller@odie.lippe.de) Message-Id: <200109061819.f86IJ1f01094@odie.lippe.de> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: "Lars =?iso-8859-1?Q?K=F6ller?=" To: "Justin T. Gibbs" Cc: Lars =?iso-8859-1?Q?K=F6ller?= , "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Subject: Re: Wire of SCSI devices gives warning messages In-Reply-To: Message from "Justin T. Gibbs" of "Tue, 04 Sep 2001 15:21:18 MDT." <200109042121.f84LLIY56024@aslan.scsiguy.com> X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! No. it doesn't help, with this patch more devices and every = lunproduce a warning message: Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:1): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:1): Second device (probe d= evice at scbus1 target 6 lun 1) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:1): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:1): Second device (probe d= evice at scbus1 target 8 lun 1) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:2): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:2): Second device (probe d= evice at scbus1 target 6 lun 2) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:2): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:2): Second device (probe d= evice at scbus1 target 0 lun 1) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:2): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:2): Second device (probe d= evice at scbus1 target 9 lun 1) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:3): Second device (probe d= evice at scbus1 target 8 lun 2) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:3): Second device (probe d= evice at scbus1 target 6 lun 3) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:3): Second device (probe d= evice at scbus1 target 10 lun 1) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:4): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:4): Second device (probe d= evice at scbus1 target 6 lun 4) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:4): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:4): Second device (probe d= evice at scbus1 target 8 lun 3) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:5): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:5): Second device (probe d= evice at scbus1 target 9 lun 2) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:5): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:5): Second device (probe d= evice at scbus1 target 6 lun 5) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:5): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:5): Second device (probe d= evice at scbus1 target 0 lun 2) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:6): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:6): Second device (probe d= evice at scbus1 target 10 lun 2) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:6): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:6): Second device (probe d= evice at scbus1 target 8 lun 4) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:6): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:6): Second device (probe d= evice at scbus1 target 6 lun 6) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:7): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:7): Second device (probe d= evice at scbus1 target 6 lun 7) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:7): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:5:7): Second device (probe d= evice at scbus1 target 8 lun 5) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Second device (probe d= evice at scbus1 target 0 lun 3) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Second device (probe d= evice at scbus1 target 10 lun 3) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Second device (probe d= evice at scbus1 target 8 lun 6) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Duplicate Wired Device= entry! Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:3): Second device (probe d= evice at scbus1 target 8 lun 7) will not be wired Sep 6 19:43:18 odie /kernel: (probe0:ahc1:0:9:4): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:4): Second device (probe d= evice at scbus1 target 10 lun 4) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:4): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:4): Second device (probe d= evice at scbus1 target 0 lun 4) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:5): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:5): Second device (probe d= evice at scbus1 target 10 lun 5) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:5): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:5): Second device (probe d= evice at scbus1 target 0 lun 5) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:6): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:6): Second device (probe d= evice at scbus1 target 10 lun 6) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:7): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:7): Second device (probe d= evice at scbus1 target 0 lun 6) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:7): Duplicate Wired Device= entry! Sep 6 19:43:19 odie /kernel: (probe0:ahc1:0:9:7): Second device (probe d= evice at scbus1 target 10 lun 7) will not be wired Sep 6 19:43:19 odie /kernel: (probe0:ahc0:0:4:3): Duplicate Wired Device= entry! =2E... and the compiler stated a = possible use of uninitialized variable hit in the line unit =3D camperiphnextunit(p_drv, unit, /*wired*/hit, pathid, target, lun); In reply to "Justin T. Gibbs" who wrote: >Justin > >Index: cam_periph.c >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >RCS file: /usr/cvs/src/sys/cam/cam_periph.c,v >retrieving revision 1.24.2.1 >diff -c -r1.24.2.1 cam_periph.c >*** cam_periph.c 2000/09/11 05:37:00 1.24.2.1 >--- cam_periph.c 2001/09/04 21:19:10 >*************** >*** 330,341 **** > char pathbuf[32], *strval, *periph_name; > = > unit =3D 0; >- hit =3D 0; > = > periph_name =3D p_drv->driver_name; > snprintf(pathbuf, sizeof(pathbuf), "scbus%d", pathid); > i =3D -1; > while ((i =3D resource_locate(i, periph_name)) !=3D -1) { > dname =3D resource_query_name(i); > dunit =3D resource_query_unit(i); > if (resource_string_value(dname, dunit, "at", &strval) =3D=3D 0) { >--- 330,341 ---- > char pathbuf[32], *strval, *periph_name; > = > unit =3D 0; > = > periph_name =3D p_drv->driver_name; > snprintf(pathbuf, sizeof(pathbuf), "scbus%d", pathid); > i =3D -1; > while ((i =3D resource_locate(i, periph_name)) !=3D -1) { >+ hit =3D 0; > dname =3D resource_query_name(i); > dunit =3D resource_query_unit(i); > if (resource_string_value(dname, dunit, "at", &strval) =3D=3D 0) { > Regards Lars -- = Lars K=F6ller E-Mail: lkoeller@cc.fh-lippe.de (LKoeller@FreeBSD.ORG) PGP-key: http://www.pgp.net/pgpnet/www-key.html -------- FreeBSD, was sonst? ---- http://www.de.freebsd.org -------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 6 12: 6:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id D62E737B403 for ; Thu, 6 Sep 2001 12:06:10 -0700 (PDT) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.5/8.11.5) with ESMTP id f86J64Y78966; Thu, 6 Sep 2001 13:06:04 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200109061906.f86J64Y78966@aslan.scsiguy.com> To: "Lars =?iso-8859-1?Q?K=F6ller?=" Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Subject: Re: Wire of SCSI devices gives warning messages In-Reply-To: Your message of "Thu, 06 Sep 2001 20:19:01 +0200." <200109061819.f86IJ1f01094@odie.lippe.de> Date: Thu, 06 Sep 2001 13:06:04 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > >Hi! > >No. it doesn't help, with this patch more devices and every Hit needs to be initialized to 0 both inside and outside the loop or if you wanted to only do it once (but in a somewhat obfuscated way): while (hit = 0 && (i = resource_locate(i, periph_name)) != -1) { ... } Sorry for not looking at the code more closely when writing the patch. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 6 12:25: 3 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from henoch.cc.fh-lippe.de (henoch.cc.fh-lippe.de [193.16.112.72]) by hub.freebsd.org (Postfix) with ESMTP id C423037B408 for ; Thu, 6 Sep 2001 12:24:56 -0700 (PDT) Received: from sulu.cc.fh-lippe.de([193.16.118.119]) (3799 bytes) by henoch.cc.fh-lippe.de via sendmail with P:esmtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 6 Sep 2001 21:24:55 +0200 (MET DST) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Mar-17) Received: from door.lippe.de(hentzii.cc.fh-lippe.de[193.16.112.177]) (3442 bytes) by sulu.cc.fh-lippe.de via sendmail with P:smtp/R:smart_host/T:smtp (sender: ) id for ; Thu, 6 Sep 2001 21:24:54 +0200 (MET DST) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Mar-17) Received: from odie.lippe.de (root@odie.lippe.de [192.168.4.2]) by door.lippe.de (8.9.3/8.9.3) with ESMTP id VAA57577; Thu, 6 Sep 2001 21:20:49 +0200 (CEST) (envelope-from lkoeller@lippe.de) Received: from odie.lippe.de (lkoeller@localhost [127.0.0.1]) by odie.lippe.de (8.11.6/8.11.1) with ESMTP id f86JKgf03193; Thu, 6 Sep 2001 21:20:42 +0200 (CEST) (envelope-from lkoeller@odie.lippe.de) Message-Id: <200109061920.f86JKgf03193@odie.lippe.de> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Lars =?iso-8859-1?Q?K=F6ller?= To: "Justin T. Gibbs" Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG, lkoeller@cc.fh-lippe.de Subject: Re: Wire of SCSI devices gives warning messages In-Reply-To: Your message of "Thu, 06 Sep 2001 13:06:04 MDT." <200109061906.f86J64Y78966@aslan.scsiguy.com> X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ---------- In reply to "Justin T. Gibbs" who wrote: >> >>Hi! >> >>No. it doesn't help, with this patch more devices and every > >Hit needs to be initialized to 0 both inside and outside the loop >or if you wanted to only do it once (but in a somewhat obfuscated way): > > while (hit = 0 && (i = resource_locate(i, periph_name)) != -1) { > > ... > > } > >Sorry for not looking at the code more closely when writing the patch. That doesn't matter, nobody is perfect ;-) No problem, I place the original initialization of hit = 0 back, but this changes nothing! static u_int camperiphunit(struct periph_driver *p_drv, path_id_t pathid, target_id_t target, lun_id_t lun) { u_int unit; int hit, i, val, dunit; const char *dname; char pathbuf[32], *strval, *periph_name; unit = 0; hit = 0; periph_name = p_drv->driver_name; snprintf(pathbuf, sizeof(pathbuf), "scbus%d", pathid); i = -1; while ((i = resource_locate(i, periph_name)) != -1) { hit = 0; dname = resource_query_name(i); dunit = resource_query_unit(i); .... But nothing has changed! .... SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) (pass0:ahc0:0:4:0): Duplicate Wired Device entry! (pass0:ahc0:0:4:0): Second device (pass device at scbus0 target 5 lun 0) will not be wired (pass0:ahc0:0:4:0): Duplicate Wired Device entry! (pass0:ahc0:0:4:0): Second device (pass device at scbus0 target 8 lun 0) will not be wired Mounting root from ufs:/dev/da1s1a cd2 at ahc1 bus 0 target 5 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 10.000MB/s transfers (10.000MHz, offset 15) cd2: cd present [331802 x 2048 byte records] .... Best regards Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 8 16:24: 7 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from athena.fasturl.net (athena.fasturl.net [209.32.216.150]) by hub.freebsd.org (Postfix) with ESMTP id 3471237B405 for ; Sat, 8 Sep 2001 16:24:01 -0700 (PDT) Received: by athena.fasturl.net (Postfix, from userid 1001) id 4B45866B07; Sat, 8 Sep 2001 23:24:02 +0000 (GMT) Date: Sat, 8 Sep 2001 23:24:02 +0000 From: Michael Burns To: freebsd-scsi@freebsd.org Subject: RAID 5 controller replacement (DPT/Adaptec SmartRAID IV) Message-ID: <20010908232402.A33391@fasturl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Has anybody attempted to replace a SmartRAID IV controller that was managing a RAID 5 array without destroying the array in the process? From what I understand, this card uses NVRAM to store its configuration, so in the event of a controller failure, the only way to recover the array would be to either recover the original configuration from NVRAM or to configure the replacement controller with the same configuration. Unfortunately, I don't recall seeing a utility to save the original configuration to a disk, and I'm not sure the DPT Storage Manager utility allows one to set configuration parameters without initializing (i.e. destroying) the array, or if two identically configured controllers with RAID 5 are interchangeable. Any reports of successes or failures are welcome. -- Michael Burns Systems Administrator Vener Net Inc. michael@fasturl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 8 16:48: 1 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id B6B9337B401 for ; Sat, 8 Sep 2001 16:47:58 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 15frQs-0003lr-00; Sat, 8 Sep 2001 16:22:38 -0700 Date: Sat, 8 Sep 2001 16:22:36 -0700 (PDT) From: Tom Samplonius To: Michael Burns Cc: freebsd-scsi@freebsd.org Subject: Re: RAID 5 controller replacement (DPT/Adaptec SmartRAID IV) In-Reply-To: <20010908232402.A33391@fasturl.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've had a DPT SmartRAID IV die before. I popped in a new controllor, hooked up the drive array and turned it on. Everything just worked. The DPT controllers store the config in NVRAM and on disk. If there is no config in NVRAM, and it pull it off the disks. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 8 17:37:30 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from athena.fasturl.net (athena.fasturl.net [209.32.216.150]) by hub.freebsd.org (Postfix) with ESMTP id 8121937B405 for ; Sat, 8 Sep 2001 17:37:28 -0700 (PDT) Received: by athena.fasturl.net (Postfix, from userid 1001) id 6536266B07; Sun, 9 Sep 2001 00:37:33 +0000 (GMT) Date: Sun, 9 Sep 2001 00:37:33 +0000 From: Michael Burns To: Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: Re: RAID 5 controller replacement (DPT/Adaptec SmartRAID IV) Message-ID: <20010909003733.A60723@fasturl.net> References: <20010908232402.A33391@fasturl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from tom@sdf.com on Sat, Sep 08, 2001 at 04:22:36PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ON Sat, Sep 08, 2001 at 04:22:36PM -0700, Tom Samplonius wrote: > > I've had a DPT SmartRAID IV die before. I popped in a new controllor, > hooked up the drive array and turned it on. Everything just worked. The > DPT controllers store the config in NVRAM and on disk. If there is no > config in NVRAM, and it pull it off the disks. Do you know whether the array was RAID 5? -- Michael Burns Systems Administrator Vener Net Inc. michael@fasturl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 8 19:16: 9 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id D64A337B406 for ; Sat, 8 Sep 2001 19:16:05 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 15ftkD-0003vx-00; Sat, 8 Sep 2001 18:50:45 -0700 Date: Sat, 8 Sep 2001 18:50:44 -0700 (PDT) From: Tom Samplonius To: Michael Burns Cc: freebsd-scsi@freebsd.org Subject: Re: RAID 5 controller replacement (DPT/Adaptec SmartRAID IV) In-Reply-To: <20010909003733.A60723@fasturl.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 9 Sep 2001, Michael Burns wrote: > ON Sat, Sep 08, 2001 at 04:22:36PM -0700, Tom Samplonius wrote: > > > > I've had a DPT SmartRAID IV die before. I popped in a new controllor, > > hooked up the drive array and turned it on. Everything just worked. The > > DPT controllers store the config in NVRAM and on disk. If there is no > > config in NVRAM, and it pull it off the disks. > > Do you know whether the array was RAID 5? Yes, it was RAID 5. I don't really see that the DPT treats logical disks any differently no matter what the RAID level. The config goes on disk regardless. > > -- > Michael Burns > Systems Administrator > Vener Net Inc. > michael@fasturl.net > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 8 19:39:39 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from athena.fasturl.net (athena.fasturl.net [209.32.216.150]) by hub.freebsd.org (Postfix) with ESMTP id 97B2D37B401 for ; Sat, 8 Sep 2001 19:39:36 -0700 (PDT) Received: by athena.fasturl.net (Postfix, from userid 1001) id 97B2266B07; Sun, 9 Sep 2001 02:39:41 +0000 (GMT) Date: Sun, 9 Sep 2001 02:39:41 +0000 From: Michael Burns To: Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: Re: RAID 5 controller replacement (DPT/Adaptec SmartRAID IV) Message-ID: <20010909023941.A89545@fasturl.net> References: <20010909003733.A60723@fasturl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from tom@sdf.com on Sat, Sep 08, 2001 at 06:50:44PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ON Sat, Sep 08, 2001 at 06:50:44PM -0700, Tom Samplonius wrote: > > On Sun, 9 Sep 2001, Michael Burns wrote: > > > Do you know whether the array was RAID 5? > > Yes, it was RAID 5. I don't really see that the DPT treats logical > disks any differently no matter what the RAID level. The config goes on > disk regardless. That's what I had hoped. Thanks for the response and the clarification. -- Michael Burns Systems Administrator Vener Net Inc. michael@fasturl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message