Re: jumpering a seagate st15150n (aka rz29b)
From: John Forkosh (john_at_SeeSigForAddress.com)
Date: 11/17/03
- Previous message: Chris Scheers: "Re: jumpering a seagate st15150n (aka rz29b)"
- In reply to: Chris Scheers: "Re: jumpering a seagate st15150n (aka rz29b)"
- Next in thread: John Laird: "Re: jumpering a seagate st15150n (aka rz29b)"
- Reply: John Laird: "Re: jumpering a seagate st15150n (aka rz29b)"
- Reply: Chris Scheers: "Re: jumpering a seagate st15150n (aka rz29b)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 17 Nov 2003 08:26:48 +0000 (UTC)
Chris Scheers <chris@applied-synergy.com> wrote:
: John Forkosh wrote:
: >
: > I have a couple of these in a vs4000/90, one as on "online backup"
: > that I'd rather not spin up until I actually mount it, since they
: > run kind of hot. I have the seagate docs for the drive, and have
: > tried jumpering the "delay motor start" and "enable motor start"
: > jumpers, but the drive always spins up at power on. How can I get
: > it to stop doing that? Thanks,
: FWIW:
:
: The VS4000/90 does not automatically issue a start command to drives.
: It WILL issue one if you use the console command SHOW DEVICE. In
: particular, SHOW CONFIG does not start the drive.
:
: If you are using VMS, it does not start the drive until you access it,
: either with MOUNT or INIT.
:
: The correct way to jumper the drive is to disable both "delay" and
: "start". "delay" starts the drive after some number of seconds times the
: SCSI ID, so if the drive is jumpered to ID 0, it starts immediately.
:
: Good luck!
Thanks, Chris; ditto Ben and John. You and John Laird seem to have
differing takes on whether or not VS4000/90 automatically issues
start command...
John Laird <nospam@laird-towers.org.uk> wrote:
: On Sun, 16 Nov 2003 04:31:20 GMT (Ben Myers) wrote:
: ><<snip>> is it possible the SCSI adapter and
: >driver software are sending out a motor start command?
: > <<snip>> Ben Myers
:
: You are quite right. SCSI "start" commands are sent when booting,
: obviously, or if console commands are issued to show the status of all
: devices. VMS, for one, will issue start commands to the non-system devices
: early on in the startup phase. It is necessary to set the various jumpers
: for operating systems that fail to do this.
What's happening to me is that both drives spin up very "early on in the
startup phase", like John said, way _before_ I ever get to the console prompt.
So it's not a question of issuing console commands like sh dev.
If by "disable both jumpers" you mean I should leave the jumpers open,
then that's what I'm doing. I did fool around with them a little
to see what effect it might have, but both drives always spin up "early on"
regardless of jumpering. I've now removed all jumpers except for scsi id --
boot drive is jumpered 1 (dka100) and second drive is jumpered 2.
And, as always, both drives spin up almost immediately.
By the way, there's also a cd rom on the external chain jumpered/set
as 5; and the machine is Model VS49K-AB, SN AB23904UM8, in case any
of that makes any difference. Otherwise, I guess I'll have to live
with the extra heat (and noise). Thanks, everyone, for all the
information,
-- John Forkosh ( mailto: j@f.com where j=john and f=forkosh )
- Previous message: Chris Scheers: "Re: jumpering a seagate st15150n (aka rz29b)"
- In reply to: Chris Scheers: "Re: jumpering a seagate st15150n (aka rz29b)"
- Next in thread: John Laird: "Re: jumpering a seagate st15150n (aka rz29b)"
- Reply: John Laird: "Re: jumpering a seagate st15150n (aka rz29b)"
- Reply: Chris Scheers: "Re: jumpering a seagate st15150n (aka rz29b)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|