From owner-freebsd-scsi Sun Sep 12 13:12:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp2.xs4all.nl (smtp2.xs4all.nl [194.109.6.52]) by hub.freebsd.org (Postfix) with ESMTP id C297614CBE for ; Sun, 12 Sep 1999 13:12:19 -0700 (PDT) (envelope-from skyllaonline@hotmail.com) Received: (from root@localhost) by smtp2.xs4all.nl (8.9.3/8.9.3) id WAA07170; Sun, 12 Sep 1999 22:12:17 +0200 (CEST) From: "Grover" To: freebsd-scsi@freebsd.org X-Via: imploder /usr/local/lib/mail/news2mail/news2mail at smtp2.xs4all.nl Subject: 53C875 SCSI-adapter and DOS Date: Sun, 12 Sep 1999 22:11:13 +0200 Organization: XS4ALL Internet BV Message-ID: <7rh1eu$in8$1@news1.xs4all.nl> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there, I have bought a Symbios 53C875 SCSI-adapter and a Quantum Viking II harddrive. Now I want to use this SCSI-drive as my boot-drive with windows. I can select in my system-bios (Award) the drive to start from (C/A/SCSI), so that must not be the problem. I managed to make my SCSI drive bootable with FDISK. DOS doesn't see my adapter (and drives). I have put some files on the win98 startup disk. I downloaded these files from the LSIlogic homepage (DOS-drivers). These files are : symc8xx.sys and aspidisk.sys. I put some lines in config.sys (Device=symc8xx.sys and Device=aspidisk.sys). Now DOS must see my adapter... but DOS doesn't see it, while FDISK in DOS does. I find this strange. If I only knew how to let DOS see my SCSI drive, I could put Windows on it. My Windows 98 system says that I can't put an older windows (95 rel. 25) on my system, so I must do this in DOS. I hope someone can help me with this. Regards, Rick Vermeer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 12 14:36:38 1999 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 AF17414DD6 for ; Sun, 12 Sep 1999 14:36:36 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA02200; Sun, 12 Sep 1999 15:36:33 -0600 (MDT) (envelope-from ken) Message-Id: <199909122136.PAA02200@panzer.kdm.org> Subject: Re: 53C875 SCSI-adapter and DOS In-Reply-To: <7rh1eu$in8$1@news1.xs4all.nl> from Grover at "Sep 12, 1999 10:11:13 pm" To: skyllaonline@hotmail.com (Grover) Date: Sun, 12 Sep 1999 15:36:33 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Grover wrote... > Hello there, > > I have bought a Symbios 53C875 SCSI-adapter and a Quantum Viking II > harddrive. Now I want to use this SCSI-drive as my boot-drive with windows. > > I can select in my system-bios (Award) the drive to start from (C/A/SCSI), > so that must not be the problem. I managed to make my SCSI drive bootable > with FDISK. > > DOS doesn't see my adapter (and drives). I have put some files on the win98 > startup disk. I downloaded these files from the LSIlogic homepage > (DOS-drivers). These files are : > > symc8xx.sys and aspidisk.sys. I put some lines in config.sys > (Device=symc8xx.sys and Device=aspidisk.sys). Now DOS must see my adapter... > but DOS doesn't see it, while FDISK in DOS does. I find this strange. > > If I only knew how to let DOS see my SCSI drive, I could put Windows on it. > > My Windows 98 system says that I can't put an older windows (95 rel. 25) on > my system, so I must do this in DOS. > > I hope someone can help me with this. This is a FreeBSD mailing list, not a DOS or Windows mailing list. Unless you can explain how your problem relates to FreeBSD, I'd suggest you look elsewhere for help. (LSI or Microsoft support would probably be a good place to start.) 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 Mon Sep 13 8:46:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2CC8314D58 for ; Mon, 13 Sep 1999 08:46:33 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA24294; Mon, 13 Sep 1999 11:46:28 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA13772; Mon, 13 Sep 1999 11:45:58 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Sep 1999 11:45:57 -0400 (EDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org, anderson@cs.duke.edu, Don Lewis Subject: Re: data corruption when using aic7890 In-Reply-To: <199909110138.TAA03862@caspian.plutotech.com> References: <199909110138.TAA03862@caspian.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14301.2437.648605.15748@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > >I would continue to tweak the variable. I assume you tried setting > >the read threshold to MIN and the write threshold to MAX? In other > >words, don't start a read from host memory until the FIFO is almost > >empty, and don't start a write to host memory until the FIFO is almost > >full. The assumption here is that PCI is faster than the SCSI bus > >speed so we'll get the longest bursts this way. > > I misread the data book. If you set them both to MAX, then you would > get this behavior. The read fifo threshold is based on the amount > of empty space in the fifo, not the amount of data in it. I've tried all the extremes, with the following results: RD_DFTHRSH_MAX | WR_DFTHRSH_MIN: corruption on read soon after first pass RD_DFTHRSH_MIN | WR_DFTHRSH_MIN: corruption on read soon after first pass RD_DFTHRSH_MAX | WR_DFTHRSH_MAX: immediate corruption (maybe write was corrupted?) RD_DFTHRSH_MIN | WR_DFTHRSH_MAX: immediate corruption (maybe write was corrupted?) Before I go marching through all the combinations, is it possible that there is a flag set someplace when a fifo overrun/underrun occurs that you're not checking? Are the docs for this board available? BTW, in case I wasn't clear originally, I'm not just running the test on 2 disks connected to the 7890 controller. I'm also running our sequential read/write test on 2 identical disks connected to an ncr875 controller & to an IDE drive connected to the built-in PIIX4. Eg, I'm beating the snot out of the PCI bus by pushing about 50-70MB/sec of data across it from 3 separate PCI devices, so its not unreasonable to expect that a fifo might fill up under these conditions. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 13 8:55: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 6DE6014D21 for ; Mon, 13 Sep 1999 08:55:06 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id JAA14180; Mon, 13 Sep 1999 09:55:13 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909131555.JAA14180@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: "Justin T. Gibbs" , scsi@freebsd.org, anderson@cs.duke.edu, Don Lewis Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Mon, 13 Sep 1999 11:45:57 EDT." <14301.2437.648605.15748@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Sep 1999 09:55:13 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've tried all the extremes, with the following results: > >RD_DFTHRSH_MAX | WR_DFTHRSH_MIN: corruption on read soon after first pas >s >RD_DFTHRSH_MIN | WR_DFTHRSH_MIN: corruption on read soon after first pas >s >RD_DFTHRSH_MAX | WR_DFTHRSH_MAX: immediate corruption (maybe write was c >orrupted?) >RD_DFTHRSH_MIN | WR_DFTHRSH_MAX: immediate corruption (maybe write was c >orrupted?) > >Before I go marching through all the combinations, is it possible that >there is a flag set someplace when a fifo overrun/underrun occurs that >you're not checking? Are the docs for this board available? The docs are not immediately available. You need to sign a PUA (Publications Use Agreement) with adaptec (essentially a giant disclaimer) and then you can get the docs. The DMA engine on these chips shouldn't require any external intervention from the software side to deal with the FIFOs. You fire it up, and wait for it to complete. Perhaps if you can better characterize how the data is corrupted I can think of more things to check. I'll take a peek at the S/G and DMA handling code in the firmware later today regardless. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 13 8:58:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 95CB3155F1 for ; Mon, 13 Sep 1999 08:58:51 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA24590; Mon, 13 Sep 1999 11:58:46 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA13789; Mon, 13 Sep 1999 11:58:16 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Sep 1999 11:58:16 -0400 (EDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org, anderson@cs.duke.edu, Don Lewis Subject: Re: data corruption when using aic7890 In-Reply-To: <199909131555.JAA14180@caspian.plutotech.com> References: <14301.2437.648605.15748@grasshopper.cs.duke.edu> <199909131555.JAA14180@caspian.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14301.7890.525919.607760@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > >I've tried all the extremes, with the following results: > > > >RD_DFTHRSH_MAX | WR_DFTHRSH_MIN: corruption on read soon after first pas > >s > >RD_DFTHRSH_MIN | WR_DFTHRSH_MIN: corruption on read soon after first pas > >s > >RD_DFTHRSH_MAX | WR_DFTHRSH_MAX: immediate corruption (maybe write was c > >orrupted?) > >RD_DFTHRSH_MIN | WR_DFTHRSH_MAX: immediate corruption (maybe write was c > >orrupted?) > > > >Before I go marching through all the combinations, is it possible that > >there is a flag set someplace when a fifo overrun/underrun occurs that > >you're not checking? Are the docs for this board available? > > The docs are not immediately available. You need to sign a PUA (Publications > Use Agreement) with adaptec (essentially a giant disclaimer) and then > you can get the docs. > > The DMA engine on these chips shouldn't require any external intervention > from the software side to deal with the FIFOs. You fire it up, and wait for > it to complete. > > Perhaps if you can better characterize how the data is corrupted I can > think of more things to check. I'll take a peek at the S/G and DMA > handling code in the firmware later today regardless. I'll try to alter my test so as to obtain more information... Thanks! ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 13 10: 2:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pathlink.net (linda.pathlink.com [165.113.238.197]) by hub.freebsd.org (Postfix) with ESMTP id 6DFC4155E4 for ; Mon, 13 Sep 1999 10:02:28 -0700 (PDT) (envelope-from kachun@pathlink.com) Received: from dvl-1 (dvl-1.pathlink.com [207.211.168.211]) by pathlink.net (8.9.3/8.8.7) with SMTP id KAA75325; Mon, 13 Sep 1999 10:02:31 -0700 (PDT) Message-Id: <199909131702.KAA75325@pathlink.net> To: freebsd-scsi@freebsd.org Subject: Re: data corruption when using aic7890 Cc: gibbs@caspian.plutotech.com From: kachun@pathlink.com (Kachun Lee) Date: Mon, 13 Sep 1999 10:02:09 -0700 X-Mailer: WinVN 0.99.8 (x86 32bit) In-Reply-To: <199909111438.IAA08309@caspian.plutotech.com> References: Your message of "Sat, 11 Sep 1999 00:20:28 PDT." <199909110720.AAA06762@salsa.gv.tsc.tdk.com> <199909111438.IAA08309@caspian.plutotech.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199909111438.IAA08309@caspian.plutotech.com>, you say... > >>Please tell me that this hardware doesn't silently corrupt data on a >>FIFO underflow or overflow without at least setting a flag somewhere ... > >I can't tell you what it does as I haven't reproduced the problem >myself and haven't seen enough information to hazard a guess at just >what is happening. > >-- >Justin I am not sure if this may help or even related. Our server that exhibits problem has 3 adaptec controllers... a 7870 with 3 Ultra-W drives and 2x7890 with 13 Ultra2 drives. It is only pumping out around 30mbps = ~8Mbyte/s of network data... not very high for 3 SCSI buses. Normally, the server panic'ed about every 5-7 day. However, if I increased the PCI latency to 128, it would panic in less than a day (for 3 days in row before I put it back at 32). I kept it up with 3.2 stable (3.3 rc) within a week. Regards ------------ ahc0: rev 0x00 int a irq 12 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x02 int a irq 12 on pci0.9.0 fxp0: Ethernet address 00:a0:c9:78:c6:ef ahc1: rev 0x00 int a irq 10 on pci0.11.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: rev 0x03 int a irq 11 on pci0.12.0 ahc2: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 13 13:58:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id B6BCB15611 for ; Mon, 13 Sep 1999 13:58:38 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA07270; Mon, 13 Sep 1999 16:58:36 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA14361; Mon, 13 Sep 1999 16:58:04 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Sep 1999 16:58:02 -0400 (EDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org, anderson@cs.duke.edu, Don Lewis Subject: Re: data corruption when using aic7890 In-Reply-To: <199909131555.JAA14180@caspian.plutotech.com> References: <14301.2437.648605.15748@grasshopper.cs.duke.edu> <199909131555.JAA14180@caspian.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14301.23120.948268.723629@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > > The DMA engine on these chips shouldn't require any external intervention > from the software side to deal with the FIFOs. You fire it up, and wait for > it to complete. > > Perhaps if you can better characterize how the data is corrupted I can > think of more things to check. I'll take a peek at the S/G and DMA > handling code in the firmware later today regardless. Does this help? Using the default driver settings & a more verbose test (prints every bad word) I see occasional behaviour like below -- ##error 0 page 41315 expected [0x000000000b1631b4] saw [0x00000000171b71b4] continuing ##error 1 page 41315 expected [0x000000000b1631b8] saw [0x00000000171b71b8] continuing ##error 2 page 41315 expected [0x000000000b1631bc] saw [0x00000000171b71bc] continuing ##error 3 page 41315 expected [0x000000000b1631c0] saw [0x00000000171b71c0] continuing ##error 4 page 41315 expected [0x000000000b1631c4] saw [0x00000000171b71c4] continuing ##error 5 page 41315 expected [0x000000000b1631c8] saw [0x00000000171b71c8] continuing ##error 6 page 41315 expected [0x000000000b1631cc] saw [0x00000000171b71cc] continuing ##error 7 page 41315 expected [0x000000000b1631d0] saw [0x00000000171b71d0] continuing ##error 8 page 41315 expected [0x000000000b1631d4] saw [0x00000000171b71d4] continuing ##error 9 page 41315 expected [0x000000000b1631d8] saw [0x00000000171b71d8] continuing ##error 10 page 41315 expected [0x000000000b1631dc] saw [0x00000000171b71dc] continuing ##error 11 page 41315 expected [0x000000000b1631e0] saw [0x00000000171b71e0] continuing ##error 12 page 41315 expected [0x000000000b1631e4] saw [0x00000000171b71e4] continuing ##error 13 page 41315 expected [0x000000000b1631e8] saw [0x00000000171b71e8] continuing ##error 14 page 41315 expected [0x000000000b1631ec] saw [0x00000000171b71ec] continuing ##error 15 page 41315 expected [0x000000000b1631f0] saw [0x00000000171b71f0] continuing ##error 16 page 41315 expected [0x000000000b1631f4] saw [0x00000000171b71f4] continuing ##error 17 page 41315 expected [0x000000000b1631f8] saw [0x00000000171b71f8] continuing ##error 18 page 41315 expected [0x000000000b1631fc] saw [0x00000000171b71fc] continuing This means that offsets 0x1b4 through 0x1fc are all bad, but the rest of the page is OK. The reuses buffers & doesn't prezero them, so what it found in the buffer is not really very meaningful. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Sep 13 20:13:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id B82CF14D5D for ; Mon, 13 Sep 1999 20:13:31 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA18016; Tue, 14 Sep 1999 12:43:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA26341; Tue, 14 Sep 1999 12:43:27 +0930 (CST) Date: Tue, 14 Sep 1999 12:43:27 +0930 From: Greg Lehey To: "Kenneth D. Merry" Cc: Kris Kirby , scsi@FreeBSD.ORG Subject: Re: Reformatting a 520-byte-per-sector drive Message-ID: <19990914124327.E10106@freebie.lemis.com> References: <37D5DF0B.FFF98713@airnet.net> <199909080534.XAA48516@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199909080534.XAA48516@panzer.kdm.org>; from Kenneth D. Merry on Tue, Sep 07, 1999 at 11:34:08PM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 7 September 1999 at 23:34:08 -0600, Kenneth D. Merry wrote: > Kris Kirby wrote... >> da3 at ahc0 bus 0 target 0 lun 0 >> da3: Fixed Direct Access SCSI-2 device >> da3: 5.000MB/s transfers (5.000MHz, offset 12), Tagged Queueing Enabled >> da3: 957MB (1931265 520 byte sectors: 64H 32S/T 943C) >> >> I want this to be 512 bytes/sector. >> >> I've tried to edit the modepage, but it comes up blank in vi. I'm going >> to guess that that means I can't change any of those parameters. :-) >> IBM's webpage >> on the >> drive says that I can change the number of blocks and the block size >> ("Block descriptor"). However, I don't seem to find anything in >> camcontrol's manpage to indicate how to go about changing it. Make no >> mistake about it, I can read the bytes/sector from modepage 0x03, but I >> can't change them. > > Hmm. Well, there's no option from the camcontrol modepage command to edit > things in the block descriptor. If you want to do that, you'll probably > have to do it with a manual command. (i.e. camcontrol cmd) > > Here's how you can display the mode page header and block descriptor: > > # camcontrol cmd da1 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" > 35 0 16 8 1 1052654 0 512 > > The last 3-byte integer is the block size. So, in theory, I suppose you > could change the blocksize by doing something like this: > > # camcontrol cmd da1 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 0:i3 0 v:i3" 512 > [ of course you'd substitute "da3" for "da1" above ] > > Hmm, that's remarkably similar to something Greg Lehey told me he had to do > to get a Seagate drive of his to format to a different sector size. Here's > a quote from Greg: > > ======================================================================== > Yup, there's some other way to change it. Set the current values, > then immediately issue a format command: > > # camcontrol cmd da1 -v -c "15 10 0 0 v:i1 0" 12 -o 12 "0 0 0 8 0 0:i3 0 v:i3" 512 > # camcontrol cmd -n da -u 1 -v -t 7200 -c "4 0 0 0 0 0" > # camcontrol modepage da1 -m 3 > Tracks per Zone: 19 > Alternate Sectors per Zone: 12 > Alternate Tracks per Zone: 0 > Alternate Tracks per Logical Unit: 38 > Sectors per Track: 84 > Data Bytes per Physical Sector: 512 > Interleave: 1 > Track Skew Factor: 13 > Cylinder Skew Factor: 22 > SSEC: 0 > HSEC: 1 > RMB: 0 > SURF: 0 > > > ======================================================================== > > Hmm, well, if this works (either Greg's command or my command, followed > *immediately* by a format), an example of this might be a good thing to > stick in the camcontrol man page. Kris, did this work for you? >> I know that Seagate has a few drives that can change bytes/sector. I'm >> currently perusing a manual from Seagate about SCSI-II/III but if >> someone else comes up with an answer sooner... > > Well, I think with most IBM disks you can change the blocksize from mode > page 3, but apparantly with this one you have to do it from the block > descriptor. It sounds similar to the Seagate disk that Greg used the above > command on. > > Since you've got to format your disk anyway, you might want to try out my > format patches to camcontrol. They've been sitting around for months in my > tree, and as far as I know, no one (except me) has tried them. Here they > are: > > http://www.freebsd.org/~ken/camcontrol.format.061799 I tried them. They seemed to work OK, but I had some library dependency problems. > I think the patches should apply okay to -current or -stable, but if they > don't it shouldn't be too hard to get them to apply. > > One warning, though -- in your situation, you'll probably want to use the > -q option to camcontrol format. The reason is, without "quiet" turned on, > camcontrol will do an inquiry on your disk, which may nullify any block > setting you just made, if your disk behaves anything like Greg's Seagate. Are you planning to commit these patches? I'd think it's worth it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 8:43:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 6B38A15081 for ; Tue, 14 Sep 1999 08:43:38 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id LAA16690; Tue, 14 Sep 1999 11:43:37 -0400 (EDT) Received: (from ath@localhost) by stiegl.niksun.com (8.9.2/8.8.7) id LAA06343; Tue, 14 Sep 1999 11:43:36 -0400 (EDT) (envelope-from ath) To: kachun@pathlink.com (Kachun Lee) Cc: freebsd-scsi@freebsd.org Subject: Re: data corruption when using aic7890 References: <199909082031.QAA74557@stiegl.niksun.com> <14295.54853.441698.273640@grasshopper.cs.duke.edu> <199909092117.OAA39115@pathlink.net> From: Andrew Heybey Date: 14 Sep 1999 11:43:36 -0400 In-Reply-To: kachun@pathlink.com's message of "Thu, 09 Sep 1999 14:17:03 -0700" Message-ID: <85btb5fqhj.fsf@stiegl.niksun.com> Lines: 50 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >In article <14295.54853.441698.273640@grasshopper.cs.duke.edu>, you say... >> >> >>Andrew Heybey writes: >> > gallatin> What!?? You mean if I just move the cable to the 20Mhz >> > gallatin> connector, all my problems will just go away??? Even >> > gallatin> though its just a different port on the same PCI >> > gallatin> controller? (at least on my P2B-LS) >> > >> > Well, I don't know if *your* problems will go away (I'm not 100% sure >> >>There is still no joy in mudville -- I'm getting the errors even after >>moving the connector. >> >>I've upgraded my P2B-LS bios from 1006 to 1011. After the bios >>upgrade, the 7890 bios went from v2.01 to v2.11. While I had a >>monitor on it, I also took the PCI latency setting from 32->128. >>I'm re-running my tests now to see if the bios upgrade had any >>effect. >> >>Sigh, >> >>Drew > >I believe I am seeing similar problem as you did. I have this NFS server - >P2B-DS (only 1 CPU) + extra 7890 + 13 ST118273LW (18G LVD) - panics once every >several days with 'ufs_dirbad: bad dir' or 'fault on nofault entry'. I spend >past 4 months swapping out every pieces of hardware with our other systems that >would run for months. The only variable is that this is our 1st server using >LVD (Ultra2) drives. You may have confirmed my suspicion that there was a >problem with 7890 running Ultra2 drives. I tried upgrade the adaptec BIOS to >v2.11 and increaed the PCI lateny setting to 128, but that did not solve the >problem. > >I am at the point of giving up on the adaptec controller. I saw you mentioned >that you had no problem with the NCR 35C875 chip. I was wondering which board >manufacturer did you use . Do you know if they make a dual channel LVD >(Ultra2-wide - we need the LVD bus because of the cable length) board using the >NCR 35C875(6)? Or anyone has success with one? > >Regards I have tried a Tekram card using the NCR chip with LVD. It worked fine (didn't see the corruption problems), but for our purposes was slower than just plugging the disks into the Ultra (20MHz, 40MB/s) connector of the aic7890. However, if you need LVD for the longer cable lengths, maybe you should try the Tekram. It was model DC-390U2W. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 8:47:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 2395514BFD for ; Tue, 14 Sep 1999 08:47:52 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id LAA16715; Tue, 14 Sep 1999 11:47:50 -0400 (EDT) Received: (from ath@localhost) by stiegl.niksun.com (8.9.2/8.8.7) id LAA06404; Tue, 14 Sep 1999 11:47:46 -0400 (EDT) (envelope-from ath) To: Andrew Gallatin Cc: freebsd-scsi@freebsd.org, gibbs@caspian.plutotech.com, anderson@cs.duke.edu, don.lewis@tsc.tdk.com Subject: Re: data corruption when using aic7890 References: <199909110138.TAA03862@caspian.plutotech.com> <14301.2437.648605.15748@grasshopper.cs.duke.edu> From: Andrew Heybey Date: 14 Sep 1999 11:47:46 -0400 In-Reply-To: Andrew Gallatin's message of "Mon, 13 Sep 1999 11:45:57 -0400 (EDT)" Message-ID: <85aeqpfqal.fsf@stiegl.niksun.com> Lines: 42 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin writes: > Justin T. Gibbs writes: > > >I would continue to tweak the variable. I assume you tried setting > > >the read threshold to MIN and the write threshold to MAX? In other > > >words, don't start a read from host memory until the FIFO is almost > > >empty, and don't start a write to host memory until the FIFO is almost > > >full. The assumption here is that PCI is faster than the SCSI bus > > >speed so we'll get the longest bursts this way. > > > > I misread the data book. If you set them both to MAX, then you would > > get this behavior. The read fifo threshold is based on the amount > > of empty space in the fifo, not the amount of data in it. > > > I've tried all the extremes, with the following results: > > RD_DFTHRSH_MAX | WR_DFTHRSH_MIN: corruption on read soon after first pass > RD_DFTHRSH_MIN | WR_DFTHRSH_MIN: corruption on read soon after first pass > RD_DFTHRSH_MAX | WR_DFTHRSH_MAX: immediate corruption (maybe write was corrupted?) > RD_DFTHRSH_MIN | WR_DFTHRSH_MAX: immediate corruption (maybe write was corrupted?) > > Before I go marching through all the combinations, is it possible that > there is a flag set someplace when a fifo overrun/underrun occurs that > you're not checking? Are the docs for this board available? > > BTW, in case I wasn't clear originally, I'm not just running the test > on 2 disks connected to the 7890 controller. I'm also running our > sequential read/write test on 2 identical disks connected to an ncr875 > controller & to an IDE drive connected to the built-in PIIX4. Eg, I'm > beating the snot out of the PCI bus by pushing about 50-70MB/sec of > data across it from 3 separate PCI devices, so its not unreasonable to > expect that a fifo might fill up under these conditions. Contention on the PCI bus seems to be the key to causing the problem. In my case it was 10MByte/s of network traffic (with 44K interrupts/sec) plus reading the disks as fast as possible. I never saw the problem with *just* reading disks, only when I added the network traffic. In your case you have multiple disk controllers fighting for the bus. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 11:12:23 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.delanet.com (hermes.delanet.com [208.9.136.62]) by hub.freebsd.org (Postfix) with SMTP id 99B3115764 for ; Tue, 14 Sep 1999 11:11:37 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 25501 invoked from network); 14 Sep 1999 18:12:53 -0000 Received: from unknown (HELO delanet.com) (208.9.136.123) by mail.delanet.com with SMTP; 14 Sep 1999 18:12:53 -0000 Message-ID: <37DE8F21.F0FD1FC9@delanet.com> Date: Tue, 14 Sep 1999 14:08:34 -0400 From: "Stephen C. Comoletti" Organization: DelaNET, Inc. X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Clustering nt and bsd on shared raid box Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've recently setup an external raid box from metastor. It's got a FreeBSD 3.2 box serving nfs for my web/ftp/shell servers. We were wanting to also support our few NT based machines and have run into a few problems. I was wondering if anyone has successfully run bsd and NT both on the same scsi bus? The Metastor unit has a Symbios differential raid5 controller, and I have a adaptec 2944uw in both the BSD and NT boxes. I've been told NT has problems with file locking/etc..however would this apply if it was only accessing a partition for itself formatted as ntfs? Leaving the BSD box to access the other partitions for the unix servers? Only emails I've seen similar to this were talking about multiple BSD boxes, or one guy who did it with an Amiga and a BSD box.. I do have NT Enterprise Server, which is supposedly capable but OSSI (company who sold me the metastor unit) will not support a BSD/NT combination..and I have no desire to trash the data on the unit in testing. -- Stephen Comoletti Systems Administrator Delanet, Inc. http://www.delanet.com ph: (302) 326-5800 fax: (302) 326-5802 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 11:37:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 8FAB5151B7 for ; Tue, 14 Sep 1999 11:37:44 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 1302 invoked by uid 1825); 14 Sep 1999 18:37:38 -0000 Date: Tue, 14 Sep 1999 14:37:37 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: reboot errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm getting the following errors during any soft or hard reboot after being up for days, and it won't come up: >> FreeBSD/i386 BOOT Default: 0:da(0,a)FreeBSD/i3 boot: login: 24;48f [24;64f [25;1fboot: [25;29f [25;8f[25;10fo;[25;13f[1;O[5;18f;/i8;[25;29 No [25;8f[25;10fo;[25;13f[1;O[5;18f;/i8;[25;29 If I then give it another power-cycle, it almost always comes up fine. Hardware is Intel L440GX+ (built-in Adaptec AIC-7896) 3 x 9.1GB 7200rpm IBM ultra2 SCSI. 256MB ECC memory. OS is FreeBSD 3.2-RELEASE Any and all clues gratefully accepted...please cc any replies directly to me, as I'm not sub'd to the questions list. Thank you, James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 11:46:17 1999 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 B03BA15627 for ; Tue, 14 Sep 1999 11:45:41 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA36540; Tue, 14 Sep 1999 12:45:32 -0600 (MDT) (envelope-from ken) Message-Id: <199909141845.MAA36540@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <19990914124327.E10106@freebie.lemis.com> from Greg Lehey at "Sep 14, 1999 12:43:27 pm" To: grog@lemis.com (Greg Lehey) Date: Tue, 14 Sep 1999 12:45:32 -0600 (MDT) Cc: kris@airnet.net (Kris Kirby), scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey wrote... > On Tuesday, 7 September 1999 at 23:34:08 -0600, Kenneth D. Merry wrote: > > Kris Kirby wrote... > >> I know that Seagate has a few drives that can change bytes/sector. I'm > >> currently perusing a manual from Seagate about SCSI-II/III but if > >> someone else comes up with an answer sooner... > > > > Well, I think with most IBM disks you can change the blocksize from mode > > page 3, but apparantly with this one you have to do it from the block > > descriptor. It sounds similar to the Seagate disk that Greg used the above > > command on. > > > > Since you've got to format your disk anyway, you might want to try out my > > format patches to camcontrol. They've been sitting around for months in my > > tree, and as far as I know, no one (except me) has tried them. Here they > > are: > > > > http://www.freebsd.org/~ken/camcontrol.format.061799 > > I tried them. They seemed to work OK, but I had some library > dependency problems. Yeah, you have to rebuild libcam and then rebuild camcontrol. I forgot to tell Kris about that. > > I think the patches should apply okay to -current or -stable, but if they > > don't it shouldn't be too hard to get them to apply. > > > > One warning, though -- in your situation, you'll probably want to use the > > -q option to camcontrol format. The reason is, without "quiet" turned on, > > camcontrol will do an inquiry on your disk, which may nullify any block > > setting you just made, if your disk behaves anything like Greg's Seagate. > > Are you planning to commit these patches? I'd think it's worth it. Well, I'll probably have to to get any more feedback. I want to go through the patches one more time and clean things up before I do that, though. Maybe if I let them sit in -current for a couple of months, I'll get some feedback. 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 Tue Sep 14 14:31:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 63DD614C8E for ; Tue, 14 Sep 1999 14:31:42 -0700 (PDT) (envelope-from kyle@stdio.com) Received: from localhost (kyle@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id RAA06154; Tue, 14 Sep 1999 17:30:47 -0400 (EDT) (envelope-from kyle@heathers.stdio.com) Date: Tue, 14 Sep 1999 17:30:47 -0400 (EDT) From: Kyle McPeek To: "Stephen C. Comoletti" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Clustering nt and bsd on shared raid box In-Reply-To: <37DE8F21.F0FD1FC9@delanet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have done this type of setup with 3 nt boxes and 1 bsd box on an HP autoraid unit. Just make sure you get the termination correct. kyle. On Tue, 14 Sep 1999, Stephen C. Comoletti wrote: > I've recently setup an external raid box from metastor. It's got a FreeBSD > 3.2 box serving nfs for my web/ftp/shell servers. We were wanting to also > support our few NT based machines and have run into a few problems. I was > wondering if anyone has successfully run bsd and NT both on the same scsi > bus? The Metastor unit has a Symbios differential raid5 controller, and I > have a adaptec 2944uw in both the BSD and NT boxes. I've been told NT has > problems with file locking/etc..however would this apply if it was only > accessing a partition for itself formatted as ntfs? Leaving the BSD box to > access the other partitions for the unix servers? Only emails I've seen > similar to this were talking about multiple BSD boxes, or one guy who did it > with an Amiga and a BSD box.. I do have NT Enterprise Server, which is > supposedly capable but OSSI (company who sold me the metastor unit) will not > support a BSD/NT combination..and I have no desire to trash the data on the > unit in testing. > > > -- > Stephen Comoletti > Systems Administrator > Delanet, Inc. http://www.delanet.com > ph: (302) 326-5800 fax: (302) 326-5802 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 16: 2:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id C539714F15 for ; Tue, 14 Sep 1999 16:02:14 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA34009; Wed, 15 Sep 1999 08:32:02 +0930 (CST) Date: Wed, 15 Sep 1999 08:32:02 +0930 From: Greg Lehey To: "Kenneth D. Merry" Cc: Kris Kirby , scsi@FreeBSD.ORG Subject: Re: Reformatting a 520-byte-per-sector drive Message-ID: <19990915083202.B30655@freebie.lemis.com> References: <19990914124327.E10106@freebie.lemis.com> <199909141845.MAA36540@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199909141845.MAA36540@panzer.kdm.org>; from Kenneth D. Merry on Tue, Sep 14, 1999 at 12:45:32PM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 14 September 1999 at 12:45:32 -0600, Kenneth D. Merry wrote: > Greg Lehey wrote... >> On Tuesday, 7 September 1999 at 23:34:08 -0600, Kenneth D. Merry wrote: >>> I think the patches should apply okay to -current or -stable, but if they >>> don't it shouldn't be too hard to get them to apply. >>> >>> One warning, though -- in your situation, you'll probably want to use the >>> -q option to camcontrol format. The reason is, without "quiet" turned on, >>> camcontrol will do an inquiry on your disk, which may nullify any block >>> setting you just made, if your disk behaves anything like Greg's Seagate. >> >> Are you planning to commit these patches? I'd think it's worth it. > > Well, I'll probably have to to get any more feedback. I want to go through > the patches one more time and clean things up before I do that, though. > > Maybe if I let them sit in -current for a couple of months, I'll get some > feedback. That's what it's for :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 18:37:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id D475D15106 for ; Tue, 14 Sep 1999 18:37:46 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-106.dialup.HiWAAY.net [216.180.35.106] (may be forged)) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA06887; Tue, 14 Sep 1999 20:36:27 -0500 (CDT) Message-ID: <37DEF81A.520E2D1B@airnet.net> Date: Tue, 14 Sep 1999 20:36:26 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: Re: Reformatting a 520-byte-per-sector drive References: <199909140220.UAA32921@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > > # camcontrol cmd da1 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" > > > 35 0 16 8 1 1052654 0 512 This spits out the appropriate answer. #root:orgy: {17} camcontrol cmd da0 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" 35 0 16 8 0 1931265 0 520 > > > The last 3-byte integer is the block size. So, in theory, I suppose you > > > could change the blocksize by doing something like this: > > > # camcontrol cmd da1 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 0:i3 0 v:i3" 512 > > > [ of course you'd substitute "da3" for "da1" above ] This sets it properly, but when chased with a format, doesn't do anything. (Except format the drive. :-) > > What would be the proper command to change the number of blocks? Docs > > say it needs both. > > Well, in that case, you'd do this I think: > > # camcontrol cmd da3 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 v:i3 0 v:i3" xxxx 512 > > Where the 'xxxx' is the number of 512 byte blocks. #root:orgy: {15} camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 v:i3 0 v:i3" 1962030 512 camcontrol: error sending command (pass0:aha0:0:0:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass0:aha0:0:0:0): ILLEGAL REQUEST asc:26,0 (pass0:aha0:0:0:0): Invalid field in parameter list sks:80,0 > To figure out the number of blocks, you'll probably want to look at the > current dmesg, and find the number of blocks. Then: I've got the IBM pages, which tell exactly how many blocks. -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 19:29:44 1999 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 A731E1568D for ; Tue, 14 Sep 1999 19:29:16 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA39212; Tue, 14 Sep 1999 20:29:11 -0600 (MDT) (envelope-from ken) Message-Id: <199909150229.UAA39212@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37DEF81A.520E2D1B@airnet.net> from Kris Kirby at "Sep 14, 1999 08:36:26 pm" To: kris@airnet.net (Kris Kirby) Date: Tue, 14 Sep 1999 20:29:11 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby wrote... > Kenneth D. Merry wrote: > > > > > # camcontrol cmd da1 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" > > > > 35 0 16 8 1 1052654 0 512 > > This spits out the appropriate answer. > #root:orgy: {17} camcontrol cmd da0 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 > i1 i1 i1 i3 i1 i3" > 35 0 16 8 0 1931265 0 520 Good. > > > > The last 3-byte integer is the block size. So, in theory, I suppose you > > > > could change the blocksize by doing something like this: > > > > > # camcontrol cmd da1 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 0:i3 0 v:i3" 512 > > > > [ of course you'd substitute "da3" for "da1" above ] > > This sets it properly, but when chased with a format, doesn't do > anything. (Except format the drive. :-) Hmm...so the setting doesn't stick? > > > What would be the proper command to change the number of blocks? Docs > > > say it needs both. > > > > Well, in that case, you'd do this I think: > > > > # camcontrol cmd da3 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 v:i3 0 v:i3" xxxx 512 > > > > Where the 'xxxx' is the number of 512 byte blocks. > > #root:orgy: {15} camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 > 8 0 v:i3 0 v:i3" 1962030 512 > camcontrol: error sending command > (pass0:aha0:0:0:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass0:aha0:0:0:0): ILLEGAL REQUEST asc:26,0 > (pass0:aha0:0:0:0): Invalid field in parameter list sks:80,0 Well, I neglected the fact that the length parameter in the mode page header is reserved for mode select. The above error is pointing to the first byte in the parameter list. So, try this instead: camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "0 0 0 8 0 v:i3 0 v:i3" 1962030 512 > > To figure out the number of blocks, you'll probably want to look at the > > current dmesg, and find the number of blocks. Then: > > I've got the IBM pages, which tell exactly how many blocks. > Good deal. Let me know whether this works. 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 Tue Sep 14 22:28:23 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3D9E914BDE for ; Tue, 14 Sep 1999 22:28:20 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-175.dialup.HiWAAY.net [216.180.35.175]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id AAA03762; Wed, 15 Sep 1999 00:28:08 -0500 (CDT) Message-ID: <37DF2E67.B9F54D28@airnet.net> Date: Wed, 15 Sep 1999 00:28:07 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: Re: Reformatting a 520-byte-per-sector drive References: <199909150229.UAA39212@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > Kris Kirby wrote... > > Kenneth D. Merry wrote: > > > > > > > # camcontrol cmd da1 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" > > > > > 35 0 16 8 1 1052654 0 512 > > > > This spits out the appropriate answer. > > #root:orgy: {17} camcontrol cmd da0 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 > > i1 i1 i1 i3 i1 i3" > > 35 0 16 8 0 1931265 0 520 > > Good. > > > > > > The last 3-byte integer is the block size. So, in theory, I suppose you > > > > > could change the blocksize by doing something like this: > > > > > > > # camcontrol cmd da1 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 0:i3 0 v:i3" 512 > > > > > [ of course you'd substitute "da3" for "da1" above ] > > > > This sets it properly, but when chased with a format, doesn't do > > anything. (Except format the drive. :-) > > Hmm...so the setting doesn't stick? > > > > > What would be the proper command to change the number of blocks? Docs > > > > say it needs both. > > > > > > Well, in that case, you'd do this I think: > > > > > > # camcontrol cmd da3 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 v:i3 0 v:i3" xxxx 512 > > > > > > Where the 'xxxx' is the number of 512 byte blocks. > > > > #root:orgy: {15} camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 > > 8 0 v:i3 0 v:i3" 1962030 512 > > camcontrol: error sending command > > (pass0:aha0:0:0:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > (pass0:aha0:0:0:0): ILLEGAL REQUEST asc:26,0 > > (pass0:aha0:0:0:0): Invalid field in parameter list sks:80,0 > > Well, I neglected the fact that the length parameter in the mode page > header is reserved for mode select. The above error is pointing to the > first byte in the parameter list. So, try this instead: > > camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "0 0 0 8 0 v:i3 0 v:i3" 1962030 512 > Good deal. Let me know whether this works. As of now, it is running this command. Until the machine hangs... (I have a bad widdle 1542CF. But three good 1542Bs. Well, the CF is the only one with a BIOS more intelligent than mud. :-) -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 22:35:33 1999 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 75A161548A for ; Tue, 14 Sep 1999 22:35:31 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA40299; Tue, 14 Sep 1999 23:35:29 -0600 (MDT) (envelope-from ken) Message-Id: <199909150535.XAA40299@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37DF2E67.B9F54D28@airnet.net> from Kris Kirby at "Sep 15, 1999 00:28:07 am" To: kris@airnet.net (Kris Kirby) Date: Tue, 14 Sep 1999 23:35:28 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby wrote... > Kenneth D. Merry wrote: > > Kris Kirby wrote... > > > #root:orgy: {15} camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 > > > 8 0 v:i3 0 v:i3" 1962030 512 > > > camcontrol: error sending command > > > (pass0:aha0:0:0:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > > (pass0:aha0:0:0:0): ILLEGAL REQUEST asc:26,0 > > > (pass0:aha0:0:0:0): Invalid field in parameter list sks:80,0 > > > > Well, I neglected the fact that the length parameter in the mode page > > header is reserved for mode select. The above error is pointing to the > > first byte in the parameter list. So, try this instead: > > > > camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "0 0 0 8 0 v:i3 0 v:i3" 1962030 512 > > > > Good deal. Let me know whether this works. > > As of now, it is running this command. Until the machine hangs... (I > have a bad widdle 1542CF. But three good 1542Bs. Well, the CF is the > only one with a BIOS more intelligent than mud. :-) I'm not sure I understand. Is the drive doing anything? Does the machine/card normally hang? I would expect the blocksize change to go pretty quickly, unless the drive automatically does a format or something similar when you change the blocksize. (With other drives, you change the blocksize and then format.) Can you tell if the drive is doing anything? The other problem you may have with this is that if the drive does format itself when you change the blocksize, the timeout for the mode select is likely too short. In fact, the default timeout for generic SCSI commands like the one you issued is 5 seconds, which is way too short for a format. 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 Tue Sep 14 23:44: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 1E7CC14A2B for ; Tue, 14 Sep 1999 23:44:00 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-175.dialup.HiWAAY.net [216.180.35.175]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id BAA04574; Wed, 15 Sep 1999 01:43:57 -0500 (CDT) Message-ID: <37DF402B.BEA5086E@airnet.net> Date: Wed, 15 Sep 1999 01:43:55 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: Re: Reformatting a 520-byte-per-sector drive References: <199909150535.XAA40299@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > As of now, it is running this command. Until the machine hangs... (I > > have a bad widdle 1542CF. But three good 1542Bs. Well, the CF is the > > only one with a BIOS more intelligent than mud. :-) > > I'm not sure I understand. Is the drive doing anything? Does the > machine/card normally hang? This card will crash any machine. It's known to be broken, but it gets the job done sometimes. I usually just use a 1542B instead. It's less painful. Mind, I'm not saying _all_ 1542CF's are broken, just the one I have in my possession. > I would expect the blocksize change to go pretty quickly, unless the drive > automatically does a format or something similar when you change the > blocksize. (With other drives, you change the blocksize and then format.) > > Can you tell if the drive is doing anything? It doesn't have a led output, so no. I can hear what I think is accessing, but it may just be the bearings. > The other problem you may have with this is that if the drive does format > itself when you change the blocksize, the timeout for the mode select is > likely too short. In fact, the default timeout for generic SCSI commands > like the one you issued is 5 seconds, which is way too short for a format. I'm chasing them on the command line ; one right after the other. (That's not _just_ a grammatical example!) So, like the energizer bunny, it keeps right on going, formatting. -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 14 23:47:19 1999 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 1EB3914CE4 for ; Tue, 14 Sep 1999 23:47:16 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA40575; Wed, 15 Sep 1999 00:47:14 -0600 (MDT) (envelope-from ken) Message-Id: <199909150647.AAA40575@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37DF402B.BEA5086E@airnet.net> from Kris Kirby at "Sep 15, 1999 01:43:55 am" To: kris@airnet.net (Kris Kirby) Date: Wed, 15 Sep 1999 00:47:14 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby wrote... > Kenneth D. Merry wrote: > > > As of now, it is running this command. Until the machine hangs... (I > > > have a bad widdle 1542CF. But three good 1542Bs. Well, the CF is the > > > only one with a BIOS more intelligent than mud. :-) > > > > I'm not sure I understand. Is the drive doing anything? Does the > > machine/card normally hang? > > This card will crash any machine. It's known to be broken, but it gets > the job done sometimes. I usually just use a 1542B instead. It's less > painful. Mind, I'm not saying _all_ 1542CF's are broken, just the one I > have in my possession. Hmm, that's strange indeed. > > I would expect the blocksize change to go pretty quickly, unless the drive > > automatically does a format or something similar when you change the > > blocksize. (With other drives, you change the blocksize and then format.) > > > > Can you tell if the drive is doing anything? > > It doesn't have a led output, so no. I can hear what I think is > accessing, but it may just be the bearings. That's a good sign. > > The other problem you may have with this is that if the drive does format > > itself when you change the blocksize, the timeout for the mode select is > > likely too short. In fact, the default timeout for generic SCSI commands > > like the one you issued is 5 seconds, which is way too short for a format. > > I'm chasing them on the command line ; one right after the other. > (That's not _just_ a grammatical > example!) So, like the energizer bunny, it keeps right on going, > formatting. Ahh, okay. I thought that the mode select was hanging somehow. But, of course, the format should take a while. I'm curious to see whether the sector size change will stick after the format. 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 Tue Sep 14 23:48:30 1999 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 8E0D314C84 for ; Tue, 14 Sep 1999 23:48:28 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA40597; Wed, 15 Sep 1999 00:48:26 -0600 (MDT) (envelope-from ken) Message-Id: <199909150648.AAA40597@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37DF402B.BEA5086E@airnet.net> from Kris Kirby at "Sep 15, 1999 01:43:55 am" To: kris@airnet.net (Kris Kirby) Date: Wed, 15 Sep 1999 00:48:26 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby wrote... > Kenneth D. Merry wrote: > > The other problem you may have with this is that if the drive does format > > itself when you change the blocksize, the timeout for the mode select is > > likely too short. In fact, the default timeout for generic SCSI commands > > like the one you issued is 5 seconds, which is way too short for a format. > > I'm chasing them on the command line ; one right after the other. > (That's not _just_ a grammatical > example!) So, like the energizer bunny, it keeps right on going, > formatting. One other thing -- with my new format patches (the URL I sent out earlier), you'll know whether it's formatting or not, since you'll see the percentage done. 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 Wed Sep 15 0:23:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 29D3314BCA for ; Wed, 15 Sep 1999 00:23:41 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-175.dialup.HiWAAY.net [216.180.35.175]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id CAA23644; Wed, 15 Sep 1999 02:23:37 -0500 (CDT) Message-ID: <37DF4978.653EF779@airnet.net> Date: Wed, 15 Sep 1999 02:23:36 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: Re: Reformatting a 520-byte-per-sector drive References: <199909150648.AAA40597@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > One other thing -- with my new format patches (the URL I sent out earlier), > you'll know whether it's formatting or not, since you'll see the percentage > done. While I do have a copy of the src cvsup'd to -current, my machine is not even -stable. If I could apply the patches against 3.2-RELEASE or the upcoming 3.3-RELEASE, I'd be happy to see. But I've got to change the card in that machine first.... :-) > > Ahh, okay. I thought that the mode select was hanging somehow. But, of > course, the format should take a while. I'm curious to see whether the > sector size change will stick after the format. > No, I checked that first; I got a prompt right after I sent the command. -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 1:17:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 2063514E80 for ; Wed, 15 Sep 1999 01:17:37 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id BAA08811; Wed, 15 Sep 1999 01:17:28 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA19831; Wed, 15 Sep 1999 01:17:27 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA17039; Wed, 15 Sep 1999 01:17:26 -0700 (PDT) From: Don Lewis Message-Id: <199909150817.BAA17039@salsa.gv.tsc.tdk.com> Date: Wed, 15 Sep 1999 01:17:26 -0700 In-Reply-To: Andrew Gallatin "Re: data corruption when using aic7890" (Sep 13, 11:45am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Andrew Gallatin , "Justin T. Gibbs" Subject: Re: data corruption when using aic7890 Cc: scsi@FreeBSD.ORG, anderson@cs.duke.edu, Don Lewis Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sep 13, 11:45am, Andrew Gallatin wrote: } Subject: Re: data corruption when using aic7890 } } I've tried all the extremes, with the following results: } } RD_DFTHRSH_MAX | WR_DFTHRSH_MIN: corruption on read soon after first pass } RD_DFTHRSH_MIN | WR_DFTHRSH_MIN: corruption on read soon after first pass } RD_DFTHRSH_MAX | WR_DFTHRSH_MAX: immediate corruption (maybe write was corrupted?) } RD_DFTHRSH_MIN | WR_DFTHRSH_MAX: immediate corruption (maybe write was corrupted?) It looks like this problem is not affected by the setting of RD_DFTHRSH and is affected by the setting of WR_DFTHRSH. Too bad neither extreme setting is error free. According to Justin's comment, this knob controls the behavior of writes by the adapter to memory (disk reads). I wonder if it might be botching PCI MWI transactions. Is there a way to get this beast to just use plain PCI Memory Write transactions (with the obvious performance penalty)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 1:21:42 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D4AA414A1C for ; Wed, 15 Sep 1999 01:21:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id BAA17180; Wed, 15 Sep 1999 01:19:51 -0700 Date: Wed, 15 Sep 1999 01:21:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Don Lewis Cc: Andrew Gallatin , "Justin T. Gibbs" , scsi@FreeBSD.ORG, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-Reply-To: <199909150817.BAA17039@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I wonder if it might be botching PCI MWI transactions. Is there a way > to get this beast to just use plain PCI Memory Write transactions (with > the obvious performance penalty)? Umm- can't you clear the INVAL bit in the PCI command register? See ahc_pci_attach where it enables BUS mastering.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 1:36:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 370ED151A1 for ; Wed, 15 Sep 1999 01:36:38 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id BAA08984; Wed, 15 Sep 1999 01:36:33 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id BAA19973; Wed, 15 Sep 1999 01:36:32 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA17105; Wed, 15 Sep 1999 01:36:31 -0700 (PDT) From: Don Lewis Message-Id: <199909150836.BAA17105@salsa.gv.tsc.tdk.com> Date: Wed, 15 Sep 1999 01:36:31 -0700 In-Reply-To: Matthew Jacob "Re: data corruption when using aic7890" (Sep 15, 1:21am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: mjacob@feral.com, Don Lewis Subject: Re: data corruption when using aic7890 Cc: Andrew Gallatin , "Justin T. Gibbs" , scsi@FreeBSD.ORG, anderson@cs.duke.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sep 15, 1:21am, Matthew Jacob wrote: } Subject: Re: data corruption when using aic7890 } } > I wonder if it might be botching PCI MWI transactions. Is there a way } > to get this beast to just use plain PCI Memory Write transactions (with } > the obvious performance penalty)? } } Umm- can't you clear the INVAL bit in the PCI command register? See } ahc_pci_attach where it enables BUS mastering.. Yeah, I forgot that this was a standard bit in the PCI command register. According to the PCI spec it should already default to being off after reset (unless the BIOS is enabling it). It looks like the driver currently doesn't touch it. It would be an interesting experiment to see what this bit is set to and to turn it off it is on. Maybe this can even be done from the BIOS setup ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 1:39:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5C79E14BD7 for ; Wed, 15 Sep 1999 01:39:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id BAA17274; Wed, 15 Sep 1999 01:38:13 -0700 Date: Wed, 15 Sep 1999 01:39:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Don Lewis Cc: Andrew Gallatin , "Justin T. Gibbs" , scsi@FreeBSD.ORG, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-Reply-To: <199909150836.BAA17105@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sep 15, 1:21am, Matthew Jacob wrote: > } Subject: Re: data corruption when using aic7890 > } > } > I wonder if it might be botching PCI MWI transactions. Is there a way > } > to get this beast to just use plain PCI Memory Write transactions (with > } > the obvious performance penalty)? > } > } Umm- can't you clear the INVAL bit in the PCI command register? See > } ahc_pci_attach where it enables BUS mastering.. > > Yeah, I forgot that this was a standard bit in the PCI command register. > According to the PCI spec it should already default to being off after > reset (unless the BIOS is enabling it). It looks like the driver > currently doesn't touch it. > > It would be an interesting experiment to see what this bit is set to > and to turn it off it is on. Maybe this can even be done from the BIOS > setup ... Or do it in the driver. Now that I think about it, I could easily imagine massive breakage for unaligned transfers if Adaptec pooched it by assuming MWI would be always enabled by drivers . -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 3:20: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id AFEBA1508A for ; Wed, 15 Sep 1999 03:19:52 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id TAA40452; Wed, 15 Sep 1999 19:49:42 +0930 (CST) Date: Wed, 15 Sep 1999 19:49:41 +0930 From: Greg Lehey To: "Kenneth D. Merry" Cc: Kris Kirby , scsi@FreeBSD.ORG Subject: Re: Reformatting a 520-byte-per-sector drive Message-ID: <19990915194941.G30655@freebie.lemis.com> References: <37DF2E67.B9F54D28@airnet.net> <199909150535.XAA40299@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199909150535.XAA40299@panzer.kdm.org>; from Kenneth D. Merry on Tue, Sep 14, 1999 at 11:35:28PM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 14 September 1999 at 23:35:28 -0600, Kenneth D. Merry wrote: > Kris Kirby wrote... >> Kenneth D. Merry wrote: >>> Kris Kirby wrote... >>>> #root:orgy: {15} camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 >>>> 8 0 v:i3 0 v:i3" 1962030 512 >>>> camcontrol: error sending command >>>> (pass0:aha0:0:0:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 >>>> (pass0:aha0:0:0:0): ILLEGAL REQUEST asc:26,0 >>>> (pass0:aha0:0:0:0): Invalid field in parameter list sks:80,0 >>> >>> Well, I neglected the fact that the length parameter in the mode page >>> header is reserved for mode select. The above error is pointing to the >>> first byte in the parameter list. So, try this instead: >>> >>> camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "0 0 0 8 0 v:i3 0 v:i3" 1962030 512 >> >> >>> Good deal. Let me know whether this works. >> >> As of now, it is running this command. Until the machine hangs... (I >> have a bad widdle 1542CF. But three good 1542Bs. Well, the CF is the >> only one with a BIOS more intelligent than mud. :-) > > I'm not sure I understand. Is the drive doing anything? Does the > machine/card normally hang? > > I would expect the blocksize change to go pretty quickly, unless the drive > automatically does a format or something similar when you change the > blocksize. (With other drives, you change the blocksize and then format.) The block size change requires a format. It changes the number of sectors, for example. > Can you tell if the drive is doing anything? The 1542B doesn't illuminate the LED when formatting. The CF could be the same. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 3:21: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4F50614C30 for ; Wed, 15 Sep 1999 03:21:01 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id TAA40481; Wed, 15 Sep 1999 19:50:51 +0930 (CST) Date: Wed, 15 Sep 1999 19:50:51 +0930 From: Greg Lehey To: "Kenneth D. Merry" Cc: Kris Kirby , scsi@FreeBSD.ORG Subject: Re: Reformatting a 520-byte-per-sector drive Message-ID: <19990915195051.H30655@freebie.lemis.com> References: <37DF402B.BEA5086E@airnet.net> <199909150648.AAA40597@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199909150648.AAA40597@panzer.kdm.org>; from Kenneth D. Merry on Wed, Sep 15, 1999 at 12:48:26AM -0600 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 15 September 1999 at 0:48:26 -0600, Kenneth D. Merry wrote: > Kris Kirby wrote... >> Kenneth D. Merry wrote: >>> The other problem you may have with this is that if the drive does format >>> itself when you change the blocksize, the timeout for the mode select is >>> likely too short. In fact, the default timeout for generic SCSI commands >>> like the one you issued is 5 seconds, which is way too short for a format. >> >> I'm chasing them on the command line ; one right after the other. >> (That's not _just_ a grammatical >> example!) So, like the energizer bunny, it keeps right on going, >> formatting. > > One other thing -- with my new format patches (the URL I sent out earlier), > you'll know whether it's formatting or not, since you'll see the percentage > done. How do you get this info? I thought the drive went catatonic until it was finished. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 15 9:48: 7 1999 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 3EC0D152FD for ; Wed, 15 Sep 1999 09:39:20 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA42939; Wed, 15 Sep 1999 10:39:10 -0600 (MDT) (envelope-from ken) Message-Id: <199909151639.KAA42939@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <19990915195051.H30655@freebie.lemis.com> from Greg Lehey at "Sep 15, 1999 07:50:51 pm" To: grog@lemis.com (Greg Lehey) Date: Wed, 15 Sep 1999 10:39:10 -0600 (MDT) Cc: kris@airnet.net (Kris Kirby), scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey wrote... > On Wednesday, 15 September 1999 at 0:48:26 -0600, Kenneth D. Merry wrote: > > Kris Kirby wrote... > >> Kenneth D. Merry wrote: > >>> The other problem you may have with this is that if the drive does format > >>> itself when you change the blocksize, the timeout for the mode select is > >>> likely too short. In fact, the default timeout for generic SCSI commands > >>> like the one you issued is 5 seconds, which is way too short for a format. > >> > >> I'm chasing them on the command line ; one right after the other. > >> (That's not _just_ a grammatical > >> example!) So, like the energizer bunny, it keeps right on going, > >> formatting. > > > > One other thing -- with my new format patches (the URL I sent out earlier), > > you'll know whether it's formatting or not, since you'll see the percentage > > done. > > How do you get this info? I thought the drive went catatonic until it > was finished. If you set the immediate bit on the format command, it returns immediately. Then you just get sense information from the drive. It returns a 16-bit value representing the percentage done. I think you can get the progress indication if you do a non-immediate format as well, but it's obviously easier to do with the immediate bit in camcontrol. (Otherwise I'd have to spawn a separate process to track the progress of the format.) 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 Wed Sep 15 11:51: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 66AA715344 for ; Wed, 15 Sep 1999 11:50:33 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA27467; Wed, 15 Sep 1999 20:50:11 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id UAA06239; Wed, 15 Sep 1999 20:22:38 +0200 (MET DST) (envelope-from j) Message-ID: <19990915202237.13604@uriah.heep.sax.de> Date: Wed, 15 Sep 1999 20:22:38 +0200 From: J Wunsch To: scsi@FreeBSD.ORG Cc: Kris Kirby Subject: Re: Reformatting a 520-byte-per-sector drive Reply-To: Joerg Wunsch References: <37DF2E67.B9F54D28@airnet.net> <199909150535.XAA40299@panzer.kdm.org> <19990915194941.G30655@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19990915194941.G30655@freebie.lemis.com>; from Greg Lehey on Wed, Sep 15, 1999 at 07:49:41PM +0930 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Greg Lehey wrote: > The block size change requires a format. It changes the number of > sectors, for example. IIRC, it does require an _immediate_ format command right after the blocksize change, with nothing like an intervening bus reset etc. (or at least with only a very limited number of actions allowed between, like status inquiries). This defeats the idea to use the controller's BIOS in order to format the drive after the mode page change. Instead, use "camcontrol cmd daX -t 7200 -c '4 0 0 0 0 0'" right after changing the blocksize. I'm pretty sure i've done this before successfully (pre-CAM, using the old scsi(8) command). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 5:33:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f21.hotmail.com [207.82.251.201]) by hub.freebsd.org (Postfix) with SMTP id 1D2BC15395 for ; Thu, 16 Sep 1999 05:33:32 -0700 (PDT) (envelope-from webgio@hotmail.com) Received: (qmail 33881 invoked by uid 0); 16 Sep 1999 12:33:31 -0000 Message-ID: <19990916123331.33880.qmail@hotmail.com> Received: from 212.216.41.212 by www.hotmail.com with HTTP; Thu, 16 Sep 1999 05:33:30 PDT X-Originating-IP: [212.216.41.212] From: "Giorgio Bozio" To: freebsd-scsi@freebsd.org Subject: tandberg ns8 with on-board adaptec AIC-7890 Date: Thu, 16 Sep 1999 12:33:30 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to install a tandberg tape ns8 (fast-Scsi) on a pc with a asus P2B-S motherboard that has a on-board adaptec AIC-7890. The motherboard has a quantum vicking II on (Ultra2 scsi) and has always worked fine. HD is on ID 0 and tape on ID 4. The problem I encountered is that approx. 1 out of 3 boots (and reboots) the system hangs at the point when it says "waiting 15 seconds for scsi devices to settle". I wonder if changing the scsi_delay setting in the kernel config and raising it would do any help. Please help! thank you, Giorgio Bozio ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 6: 0:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 1036A14FD1 for ; Thu, 16 Sep 1999 06:00:44 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 12500 invoked by uid 1825); 16 Sep 1999 13:00:43 -0000 Date: Thu, 16 Sep 1999 09:00:43 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: Giorgio Bozio Cc: freebsd-scsi@freebsd.org Subject: Re: tandberg ns8 with on-board adaptec AIC-7890 In-Reply-To: <19990916123331.33880.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Having gone though this myself recently...have a look at your termination. On Thu, 16 Sep 1999, Giorgio Bozio wrote: > I'm trying to install a tandberg tape ns8 (fast-Scsi) on a pc with a asus > P2B-S motherboard that has a on-board adaptec AIC-7890. The motherboard has > a quantum vicking II on (Ultra2 scsi) and has always worked fine. HD is on > ID 0 and tape on ID 4. The problem I encountered is that approx. 1 out of 3 > boots (and reboots) the system hangs at the point when it says "waiting 15 > seconds for scsi devices to settle". I wonder if changing the scsi_delay > setting in the kernel config and raising it would do any help. > Please help! > thank you, > Giorgio Bozio > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 6: 9:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f204.hotmail.com [207.82.251.95]) by hub.freebsd.org (Postfix) with SMTP id 93E1A150EB for ; Thu, 16 Sep 1999 06:09:37 -0700 (PDT) (envelope-from webgio@hotmail.com) Received: (qmail 39257 invoked by uid 0); 16 Sep 1999 13:09:36 -0000 Message-ID: <19990916130936.39256.qmail@hotmail.com> Received: from 212.216.41.222 by www.hotmail.com with HTTP; Thu, 16 Sep 1999 06:09:36 PDT X-Originating-IP: [212.216.41.222] From: "Giorgio Bozio" To: up@3.am, webgio@hotmail.com Cc: freebsd-scsi@freebsd.org Subject: Re: tandberg ns8 with on-board adaptec AIC-7890 Date: Thu, 16 Sep 1999 13:09:36 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tape and disk are both terminated, is this correct? > > >Having gone though this myself recently...have a look at your termination. > >On Thu, 16 Sep 1999, Giorgio Bozio wrote: > > > I'm trying to install a tandberg tape ns8 (fast-Scsi) on a pc with a >asus > > P2B-S motherboard that has a on-board adaptec AIC-7890. The motherboard >has > > a quantum vicking II on (Ultra2 scsi) and has always worked fine. HD is >on > > ID 0 and tape on ID 4. The problem I encountered is that approx. 1 out >of 3 > > boots (and reboots) the system hangs at the point when it says "waiting >15 > > seconds for scsi devices to settle". I wonder if changing the scsi_delay > > setting in the kernel config and raising it would do any help. > > Please help! > > thank you, > > Giorgio Bozio > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 9: 5:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mocha.baileylink.net (mocha.baileylink.net [63.71.213.4]) by hub.freebsd.org (Postfix) with ESMTP id 45D3B15007 for ; Thu, 16 Sep 1999 09:05:25 -0700 (PDT) (envelope-from brad@baileylink.net) Received: from togo (dhcp51.javabit.com [63.71.213.51]) by mocha.baileylink.net (Netscape Mail Server v2.02) with SMTP id AAA20818 for ; Thu, 16 Sep 1999 11:04:02 -0500 From: brad@baileylink.net To: Subject: RE: tandberg ns8 with on-board adaptec AIC-7890 Date: Thu, 16 Sep 1999 10:58:06 -0500 Message-ID: <000201bf005c$43cf17e0$33d5473f@togo.javabit.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <19990916130936.39256.qmail@hotmail.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Probably not. If I read correctly you use one SCSI bus. Every SCSI bus should have 2 terminators, one on each end. I believe that the motherboard controller will terminate one end automatically. It is advisable to either terminate the last device and place it at the end of the cable or to use and external (preferably active) terminator. On a side note, I have heard that one would only need one terminator for busses with cable length of less than 18 inches, personally I always use two. BMG p.s. Please go easy on me if this is not exactly correct, SCSI busses have changed a lot over the years. -----Original Message----- From: owner-freebsd-scsi@FreeBSD.ORG [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of Giorgio Bozio Sent: Thursday, September 16, 1999 8:10 AM To: up@3.am; webgio@hotmail.com Cc: freebsd-scsi@freebsd.org Subject: Re: tandberg ns8 with on-board adaptec AIC-7890 tape and disk are both terminated, is this correct? > > >Having gone though this myself recently...have a look at your termination. > >On Thu, 16 Sep 1999, Giorgio Bozio wrote: > > > I'm trying to install a tandberg tape ns8 (fast-Scsi) on a pc with a >asus > > P2B-S motherboard that has a on-board adaptec AIC-7890. The motherboard >has > > a quantum vicking II on (Ultra2 scsi) and has always worked fine. HD is >on > > ID 0 and tape on ID 4. The problem I encountered is that approx. 1 out >of 3 > > boots (and reboots) the system hangs at the point when it says "waiting >15 > > seconds for scsi devices to settle". I wonder if changing the scsi_delay > > setting in the kernel config and raising it would do any help. > > Please help! > > thank you, > > Giorgio Bozio > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 10: 7:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7DA331561E for ; Thu, 16 Sep 1999 10:06:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA22050; Thu, 16 Sep 1999 10:05:07 -0700 Date: Thu, 16 Sep 1999 10:06:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: brad@baileylink.net Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: tandberg ns8 with on-board adaptec AIC-7890 In-Reply-To: <000201bf005c$43cf17e0$33d5473f@togo.javabit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 16 Sep 1999 brad@baileylink.net wrote: > Probably not. If I read correctly you use one SCSI bus. Every SCSI bus > should have 2 terminators, one on each end. I believe that the motherboard > controller will terminate one end automatically. It is advisable to either Usually it's an option to set in the BIOS. > terminate the last device and place it at the end of the cable or to use and > external (preferably active) terminator. > > On a side note, I have heard that one would only need one terminator for > busses with cable length of less than 18 inches, personally I always use > two. (stubs) Nope. About 2 inches, but not at ultra speeds. > > BMG > > p.s. Please go easy on me if this is not exactly correct, SCSI busses have > changed a lot over the years. Not really. They're pretty much the same as they've been all along. Some extra lines and some higher speeds, but the basics have been the same. What *has* changed is the ability of cable manufactures to get clean enough cables to make things like SYNC mode (at 5Mhz through 40Mhz) work pretty reliably. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 10:23: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f205.hotmail.com [207.82.251.96]) by hub.freebsd.org (Postfix) with SMTP id 225FA14DA3 for ; Thu, 16 Sep 1999 10:23:00 -0700 (PDT) (envelope-from webgio@hotmail.com) Received: (qmail 18002 invoked by uid 0); 16 Sep 1999 17:22:59 -0000 Message-ID: <19990916172259.18001.qmail@hotmail.com> Received: from 212.216.41.232 by www.hotmail.com with HTTP; Thu, 16 Sep 1999 10:22:59 PDT X-Originating-IP: [212.216.41.232] From: "Giorgio Bozio" To: brad@baileylink.net, freebsd-scsi@freebsd.org Subject: RE: tandberg ns8 with on-board adaptec AIC-7890 Date: Thu, 16 Sep 1999 17:22:59 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know if they are on one scsi bus, actually they plug on different connectors on the motherboard and so have different cables. the motherboard manual states: ------ this motherboard has onboard 50-pin fast scsi connector for 8-bit scsi devices, 68-pin wide scsi cinnector for 16-bit scsi devices, and 68-pin ultra2 scsi connector for 32-bit scsi devices. IMPORTANT: the 68-pin wide scsi connector is always terminated and will only work as an end device. ... the onboard adaptec aic-7890ab chipset incorporates an advanced multimode i/o cell that supports both single-ended (SE) and ultra2 devices, the scsi bus platform performs at full ultra2 speed (up to 40 MB/sec in 8 bit mode and up to 80 in 16 bit mode) and extended cabling 12m. When the SE device is attached, the bus defaults to an SE speed and cable length. In mixed enviroment of Ultra2 and SE devices, the onboard host adapter can be coupled with adaptec aic-3860 transceiver chipset to bridge the compatibility gap. By dividing the scsi bus into indipendent SE and low voltage differential (LVD) segments, the transceiver chipset support legacy devices without limiting performance and cable lenght on the LVD segment. ------ I should check if the HD is on SE mode or auto switch with LVD. I think it's on SE, anyway, but not sure. The pc is colocated, I'm not able able to check right now. ciao Giorgio >Probably not. If I read correctly you use one SCSI bus. Every SCSI bus >should have 2 terminators, one on each end. I believe that the motherboard >controller will terminate one end automatically. It is advisable to either >terminate the last device and place it at the end of the cable or to use >and >external (preferably active) terminator. > >On a side note, I have heard that one would only need one terminator for >busses with cable length of less than 18 inches, personally I always use >two. > >BMG > >p.s. Please go easy on me if this is not exactly correct, SCSI busses have >changed a lot over the years. > > >tape and disk are both terminated, is this correct? > > > > > > > >Having gone though this myself recently...have a look at your >termination. > > > >On Thu, 16 Sep 1999, Giorgio Bozio wrote: > > > > > I'm trying to install a tandberg tape ns8 (fast-Scsi) on a pc with a > >asus > > > P2B-S motherboard that has a on-board adaptec AIC-7890. The >motherboard > >has > > > a quantum vicking II on (Ultra2 scsi) and has always worked fine. HD >is > >on > > > ID 0 and tape on ID 4. The problem I encountered is that approx. 1 out > >of 3 > > > boots (and reboots) the system hangs at the point when it says >"waiting > >15 > > > seconds for scsi devices to settle". I wonder if changing the >scsi_delay > > > setting in the kernel config and raising it would do any help. > > > Please help! > > > thank you, > > > Giorgio Bozio > > > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 13:36: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front4.grolier.fr (front4.grolier.fr [194.158.96.54]) by hub.freebsd.org (Postfix) with ESMTP id 1C35114EB0 for ; Thu, 16 Sep 1999 13:35:57 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-240-152.villette.club-internet.fr [195.36.240.152]) by front4.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id WAA16055 for ; Thu, 16 Sep 1999 22:35:54 +0200 (MET DST) Date: Thu, 16 Sep 1999 22:56:05 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.ORG Subject: New experimental SIM for SYM53C8XX chips. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, If you use a SYM53C896 PCI-SCSI controller under FreeBSD-current or=20 under some recent FreeBSD version, you may be interested in the following= =20 stuff: ftp://ftp.tux.org/pub/roudier/drivers/freebsd/experimental/SYM-0.0.0-990915= =2Etar.gz This code is EXPERIMENTAL, and some work is probably still needed to make it really reliable, but it performs well for me and I decided to make it available. The history of this driver (named sym_hipd) is the following: ncr -> 1995 Linux ncr53c8xx -> 1998 Linux sym53c8xx -> 1999 sym_hipd=20 This driver uses LOAD/STORE SCSI scripts instructions and so it does not support old 810, 815, (820?) and 825 chips. All other 8XX chips, including the 810A and 825A, are supported.=20 The purpose of this driver is to take advantage of features of recent chips. For this reason, it may drop support for some early chip at any time, if maintaining such a support may add too much complexity to the code. So, a generic driver (the ncr) is needed for the entire 53C8XX family to be supported under FreeBSD. FYI, under Linux: - ncr53c8xx driver supports everything from 810 rev. 1 up to latest 896. - sym53c8xx driver supports only chips that implement LOAD/STORE. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 16 20: 9: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B2C2314E69 for ; Thu, 16 Sep 1999 20:09:03 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-61.dialup.HiWAAY.net [216.180.35.61] (may be forged)) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id WAA13078; Thu, 16 Sep 1999 22:07:59 -0500 (CDT) Message-ID: <37E1B079.27022011@airnet.net> Date: Thu, 16 Sep 1999 22:07:37 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: Re: Reformatting a 520-byte-per-sector drive References: <199909150229.UAA39212@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > Kris Kirby wrote... > > Kenneth D. Merry wrote: > > > > > > > # camcontrol cmd da1 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" > > > > > 35 0 16 8 1 1052654 0 512 > > > > This spits out the appropriate answer. > > #root:orgy: {17} camcontrol cmd da0 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 > > i1 i1 i1 i3 i1 i3" > > 35 0 16 8 0 1931265 0 520 > > Good. > > > > > > The last 3-byte integer is the block size. So, in theory, I suppose you > > > > > could change the blocksize by doing something like this: > > > > > > > # camcontrol cmd da1 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 0:i3 0 v:i3" 512 > > > > > [ of course you'd substitute "da3" for "da1" above ] > > > > This sets it properly, but when chased with a format, doesn't do > > anything. (Except format the drive. :-) > > Hmm...so the setting doesn't stick? > > > > > What would be the proper command to change the number of blocks? Docs > > > > say it needs both. > > > > > > Well, in that case, you'd do this I think: > > > > > > # camcontrol cmd da3 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 v:i3 0 v:i3" xxxx 512 > > > > > > Where the 'xxxx' is the number of 512 byte blocks. > > > > #root:orgy: {15} camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 > > 8 0 v:i3 0 v:i3" 1962030 512 > > camcontrol: error sending command > > (pass0:aha0:0:0:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > > (pass0:aha0:0:0:0): ILLEGAL REQUEST asc:26,0 > > (pass0:aha0:0:0:0): Invalid field in parameter list sks:80,0 > > Well, I neglected the fact that the length parameter in the mode page > header is reserved for mode select. The above error is pointing to the > first byte in the parameter list. So, try this instead: > > camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "0 0 0 8 0 v:i3 0 v:i3" 1962030 512 This latest incantation produces: #root:orgy: {7} fmt.sh Sep 16 22:03:05 orgy /kernel: (pass0:aha0:0:6:0): CCB 0xc04992e0 - timed out Sep 16 22:03:05 orgy /kernel: aha0: ahadone - Attempt to free non-active ACCB 0xbf89d000 camcontrol: error sending command CAM status is 0x14b #root:orgy: {8} Sep 16 22:03:05 orgy /kernel: aha0: ahadone - Attempt to free non-active ACCB 0xbf89d000 Sep 16 22:03:08 orgy /kernel: (pass0:aha0:0:6:0): CCB 0xc04992e0 - timed out Sep 16 22:03:05 orgy /kernel: aha0: ahadone - Attempt to free non-active ACCB 0xbf89d000 Sep 16 22:03:08 orgy /kernel: (pass0:aha0:0:6:0): CCB 0xc04992e0 - timed out Sep 16 22:03:08 orgy /kernel: aha0: No longer in timeout Usually the machine panics here (I think only when the id is 0). I've been disconnecting the drive to allow it to finish, without the machine. I'm using a AHA-1542B: aha0: AHA-1540/1542 64 head BIOS FW Rev. 1.1 (ID=41) SCSI Host Adapter, SCSI ID 7, 16 CCBs I've changed the drive's id to 6. And it _still_ thinks it has 520 byte sectors. :-/. Well, I've tried all that I can think of. I'm about to return the drives to the owner and let him deal with it. -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 17 6:49:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.delanet.com (hermes.delanet.com [208.9.136.62]) by hub.freebsd.org (Postfix) with SMTP id 4448014BCC for ; Fri, 17 Sep 1999 06:49:15 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 45343 invoked from network); 17 Sep 1999 13:51:54 -0000 Received: from unknown (HELO delanet.com) (208.9.136.123) by mail.delanet.com with SMTP; 17 Sep 1999 13:51:54 -0000 Message-ID: <37E247E4.E98ABB88@delanet.com> Date: Fri, 17 Sep 1999 09:53:40 -0400 From: "Stephen C. Comoletti" Organization: DelaNET, Inc. X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: scsi errors on Qlogic 1040b controller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've noticed a number of errors recently which have me somewhat worried. Wondering if someone can explain them for me or direct me to where I can find a description. The server is a DEC 300i+ p2/300 with 256mb ram, a Qlogic 1040b scsi controller on MB with a 2gig DEC scsi2 as boot drive and Tecmar travan ns-20 tr5 tape drive, Adaptec 2944uw with a Metastor external raid array (symbios series 3 controller in the external case). The error occurs when my nightly backup runs from a script I made. It tars various directories on the 2gig into a tarball on the external raid. It has occured 5 times before I noticed it, and the 2gig drive crashed with the /usr partition badly damaged. No logs were written when this occured so I do not know the error messages when the server crashed. Error is as follows: Sep 16 23:59:51 metis /kernel: (da0:isp0:0:0:0): READ(06). CDB: 8 15 d3 4f 80 0 Sep 16 23:59:51 metis /kernel: (da0:isp0:0:0:0): RECOVERED ERROR info:15d359 asc:18,1 Sep 16 23:59:51 metis /kernel: (da0:isp0:0:0:0): Recovered data with error corr. & retries applied field replaceable unit: ea sks:80,7 If you could cc me in any replies as I'm not on this list it would be appreciated. -- Stephen Comoletti Systems Administrator Delanet, Inc. http://www.delanet.com ph: (302) 326-5800 fax: (302) 326-5802 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 17 9:35:23 1999 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 F0DD014E07 for ; Fri, 17 Sep 1999 09:35:13 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA57340; Fri, 17 Sep 1999 10:35:07 -0600 (MDT) (envelope-from ken) Message-Id: <199909171635.KAA57340@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37E1B079.27022011@airnet.net> from Kris Kirby at "Sep 16, 1999 10:07:37 pm" To: kris@airnet.net (Kris Kirby) Date: Fri, 17 Sep 1999 10:35:07 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby wrote... > Kenneth D. Merry wrote: > > Well, I neglected the fact that the length parameter in the mode page > > header is reserved for mode select. The above error is pointing to the > > first byte in the parameter list. So, try this instead: > > > > camcontrol cmd da0 -v -c "15 10 0 0 c 0" -o 0xc "0 0 0 8 0 v:i3 0 v:i3" 1962030 512 > > This latest incantation produces: > #root:orgy: {7} fmt.sh > Sep 16 22:03:05 orgy /kernel: (pass0:aha0:0:6:0): CCB 0xc04992e0 - timed > out > Sep 16 22:03:05 orgy /kernel: aha0: ahadone - Attempt to free non-active > ACCB 0xbf89d000 > camcontrol: error sending command > CAM status is 0x14b > #root:orgy: {8} Sep 16 22:03:05 orgy /kernel: aha0: ahadone - Attempt to > free non-active ACCB 0xbf89d000 > Sep 16 22:03:08 orgy /kernel: (pass0:aha0:0:6:0): CCB 0xc04992e0 - timed > out > Sep 16 22:03:05 orgy /kernel: aha0: ahadone - Attempt to free non-active > ACCB 0xbf89d000 > Sep 16 22:03:08 orgy /kernel: (pass0:aha0:0:6:0): CCB 0xc04992e0 - timed > out > Sep 16 22:03:08 orgy /kernel: aha0: No longer in timeout Which command causes the errors? The mode select or the format? If it's the mode select, there's definitely something weird going on. If it's the format, you probably haven't set the timeout long enough. > Usually the machine panics here (I think only when the id is 0). I've > been disconnecting the drive to allow it to finish, without the machine. > I'm using a AHA-1542B: > aha0: AHA-1540/1542 64 head BIOS FW Rev. 1.1 (ID=41) SCSI Host Adapter, > SCSI ID > 7, 16 CCBs It would be helpful if you could send a stack trace from the panic. > I've changed the drive's id to 6. And it _still_ thinks it has 520 byte > sectors. :-/. Well, I've tried all that I can think of. I'm about to > return the drives to the owner and let him deal with it. Hmm. Well, if the format has been able to go all the way through after you changed the sector size, and it still thinks it has 520 byte sectors, yeah, you may be out of luck. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message