Date: Thu, 22 Oct 1998 14:56:40 -0700 From: eric <eric@tarsier.domain.net> To: Karl Pielorz <kpielorz@tdx.co.uk> Cc: "Kenneth D. Merry" <ken@plutotech.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: possible CAM problem, ahc/st34371w Message-ID: <19981022145640.55552@tarsier.domain.net> In-Reply-To: <362F92CB.F0C5E15A@tdx.co.uk>; from Karl Pielorz on Thu, Oct 22, 1998 at 09:17:15PM %2B0100 References: <199810221958.NAA17781@panzer.plutotech.com> <362F92CB.F0C5E15A@tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 22, 1998 at 09:17:15PM +0100, Karl Pielorz wrote: > I have three of those drives, mine ID a little differently though... > > da4 at ahc2 bus 0 target 8 lun 0 > da4: <SEAGATE ST34371W 0202> Fixed Direct Access SCSI2 device > da4: 20.0MB/s transfers (10.0MHz, offset 8, 16bit) > da4: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) > > Your firmware seems to be a little older than mine - but the drive also > seems to be saying it will do 40.0MB/s transfers? - The one I have is Wide, > but not Ultra wide... Does yours say in the spec it's UltraWide? (I guess > they may have updated the drive and kept the same ID, i.e. ST34371W)... The drive will do ultra-wide according to the seagate documentation (http://www.seagate.com/support/disc/st34371w.shtml) but you need a 2940uw to be willing to negotiate 40MB/s transfers, and even then you have to specifically turn on ultra negotiation on the adapter, because the default behavior is to _not_ try to negotiate it. I suppose it's possible that that's because it's not reliable at 40MB/s, but I can't imagine nobody else is using such a common scsi adapter with ultra disks. This drive is a lot slower with 40MB/s disabled - iozone writes clock at ~4800KB/sec without and ~8900KB/sec with. It's possible my cabling/termination is faulty, although there's nothing else on the bus except the host adapter and the st34371w drive. It may be that the drive's internal termination is broken, or that the cable is flaky, though. I will at least try replacing the cable and using an external terminator, to see if that helps. I'll let you know if I start seeing problems with tagged command queueing once i fix that. Incidentally, does option "FAILSAFE" still disable t.c.q. ? > > I also get problems if I leave Tagged Command Queuing enabled, there again I > also seen to be getting problems with it completely disabled, but not as > many (and nothing sadly relating to Parity)... > > Regards, > > Karl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- ------------------------------------------------------------------------------ e|a|e|d|c| Eric Volpe p|t|r|o|o| v| |o|t|m| Springfield VA | |l| | | USA | |s| | | http://tarsier.colo.erols.net/Images/ ------------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981022145640.55552>