Date: Thu, 17 Dec 1998 21:19:08 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: "Kenneth D. Merry" <ken@plutotech.com> Cc: clash@tasam.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 Message-ID: <Pine.LNX.4.04.9812172118370.18149-100000@feral-gw> In-Reply-To: <199812180516.WAA78573@panzer.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, if that's the case, it's time for me to get off my ass and start merging in the SES driver and start thinking about lots more SCSI-3 things.... On Thu, 17 Dec 1998, Kenneth D. Merry wrote: > Matthew Jacob wrote... > > On Thu, 17 Dec 1998, Joe Gleason wrote: > > > (probe20:ahc1:0:5:0): Sending SDTR!! > > > da0 at ahc1 bus 0 target 5 lun 0 > > > da0: <IBM DGHS09U 0350> Fixed Direct Access SCSI3 device > > > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > > da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > > > > > > I just have the one scsi device. > > > > F/W crash of sorts? Does it really report itself as a SCSI-3 device? How > > interesting...I don't really have a good answer, but yes, I'd worry about > > it. Usually you only see these kinds of crocks on tape drives (SDT 5000s > > had them a lot). > > It really does report itself as a SCSI-3 device. I've got an Ultrastar 9ZX > that reports itself as SCSI-3: > > da1 at ahc1 bus 0 target 1 lun 0 > da1: <IBM DGVS09U 03B0> Fixed Direct Access SCSI3 device > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 8705MB (17829870 512 byte sectors: 255H 63S/T 1109C) > > And the 18G version of the drive he has reports itself as SCSI-3 as well. > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.04.9812172118370.18149-100000>