Date: Thu, 22 Apr 1999 11:37:07 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Darren Pilgrim <dpilgrim@uswest.net> Cc: Mark Ovens <marko@uk.radan.com>, "Francis Percival C. Favoreal" <dune@cats.edu.ph>, freebsd-questions@freebsd.org, freebsd-isp@freebsd.org Subject: Re: SCSI problem Message-ID: <Pine.BSF.4.03.9904221136420.7869-100000@resnet.uoregon.edu> In-Reply-To: <371E6704.B6E8A560@uswest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 21 Apr 1999, Darren Pilgrim wrote: > Mark Ovens wrote: > <brevity snip> > > Just a thought but this couldn't be caused by (SCSI) BIOS settings > > could it? I only ask because I've just added a second SCSI HD to my > > system and it exhibits similar behaviour, although it never fails to > > start. > > > > The original disk is an IBM Ultrastar 2ES U/W and that spins up as > > soon as the power is switched on but the new disk, IBM Ultrastar 9ES > > U/W, doesn't spin up until the SCSI controller probes it (I thought > > I'd forgotten to connect the power lead the first time I powered up > > after installing it). > > > > The SCSI card is a Diamond Fireport (NCR/Symbios 53c875 chip). It > > seems strange that one disk spins up immediately and the other waits > > until it's probed, but since it always spins up and works without > > problems I've never bothered investigating further. > > Some of the SCSI HBAs I have stage the spin-ups to avoid overloading > the power supply. Perhaps this might be the cause? Some drives can be keyed this way too by pulling off the auto-spinup jumper. We have an IBM drive that acts this way -- it's annoying! :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9904221136420.7869-100000>