Subject: Re: SCSI disks don't spin up automatically after scsictl sdx stop
To: Michael Lorenz <firstname.lastname@example.org>
From: Manuel Bouyer <email@example.com>
Date: 12/16/2005 23:21:55
On Fri, Dec 16, 2005 at 05:18:04PM -0500, Michael Lorenz wrote:
> > > Exactly. Is your disk a Seagate, IBM or something else?
> > It's a: <IBM, DNES-309170W, SAH0>
> > However it fails with a <SEAGATE, ST32272N, 0784> in the same way
> > reported by Pavel. Unfortunably I won't be able to debug this in
> > the next few days.
> Hmm, with these two, connected to an esiop in an Ultra 10 it works:
> sd0 at scsibus0 target 1 lun 0: <IBM, DCAS-34330W, S61A> disk fixed
> sd0: 4134 MB, 8205 cyl, 6 head, 171 sec, 512 bytes/sect x 8467200
> sd0: sync (50.00ns offset 15), 16-bit (40.000MB/s) transfers, tagged
> sd1 at scsibus0 target 2 lun 0: <SEAGATE, ST150176LW, 0002> disk fixed
> sd1: 47702 MB, 12024 cyl, 22 head, 369 sec, 512 bytes/sect x 97693755
> sd1: sync (50.00ns offset 15), 16-bit (40.000MB/s) transfers, tagged
> ... while these two, connected to a mesh in a UMAX S900 do not:
> sd0 at scsibus1 target 0 lun 0: <SEAGATE, SX19171W, 9D23> disk fixed
> sd0: 8683 MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sect x 17783112
> sd1 at scsibus1 target 2 lun 0: <SEAGATE, ST34520N, 1281> disk fixed
> sd1: drive offline
> For some reason I don't get any SCSI-related error messages at all on
> the S900, all the SCSI options are the same, both kernels are built from
> the same source tree, updated a few hours ago.
You mean, you don't get the "Logical Unit Not Ready, Initialization Command
Required" or similar messages ? If so, it's probably an issue with the
mesh driver itself.
Manuel Bouyer <firstname.lastname@example.org>
NetBSD: 26 ans d'experience feront toujours la difference