#2nd SCSI HD Problems
21 messages in this thread
I've connected a 2nd SCSI hard drive to a GVP Impact Series II controller
(which already has a hard drive on it). The trouble is, the new (2nd) hard
drive is only recognized (and displayed on WorkBench) after a warm reboot.
Cold boots don't acknowledge its existence. Suggestions?
Randy Monk
Randy;
What kind of drive. Some drives do not begin initialization quickly enough
to be recognized by the controller following a power up sequence.
,bill
Bill: I'm booting from a 3.5" Quantum P40S, with a 5.25" Seagate ST296N (80
meg). You are probably right; it explains the odd behavior. So what do I
do? Thanks for helping me.
Randy
Randy;
I am not sure. Maybe Don or one of the other guys on the forum may know a
solution. I am afraid I opted for the cop-out, just put the drive on a
different controller and everything worked fine.
It might be possible to fool with one of the SCSI control lines to get
everything to work. Since I did not try that, I am not sure just exactly
what it is that you would have to do. You might be able to put a "one
shot" on the reset line or something like that. If you don't get an answer
from someone here on the forum then I would suggest either talking to CBM
or one of the controller or drive manufactures.
,bill
Would it make a difference to boot from the slower (Seagate) drive? Thanks
again for your help. Randy
Randy;
I suspect not. If your controller were like the GVP that I use on this
machine, it would wait until the slowest drive is ready before booting. The
controller tries to do that so that it is able to read the RDB on each disk
to find out which has the highest boot priority. On this particular
machine, my boot operation is usually quite slow since I have two SyQuest
drives and the carts are not normally loaded….. thus the controller times
out on both of them. The controller eventually gives up on a drive and
boots from the highest priority drive that responded. The Micropolis that
I tried would stay in a reset condition until after the first boot-up was
complete (similar to what you described).
,bill
*Two* Syquests? Sounds like you really like them, or you've got a special
application…
John;
I had a special need. Now I really don't need two but I suppose that one
can serve as an emergency spare. I don't know anyone within a few hundred
miles that has a SyQuest.
,bill
Or maybe you'd like to let one go, to someone you know, for a good price?
🙂
John;
<chuckle> If you were my next door neighbor, I might consider it, but for
now, I would be "up a creek" if the only one that I had failed.
,bill
Randy:
I have a setup that is almost identical to yours. I have a Supra
Wordsync controller with a Quantum P40S onboard, and a Seagate 296 in my 5
1/4 bay. It works fine, but I think I know what your problem is. In your
Startup-sequence, there should be some kind of mount command that mounts
your hard drive. On my Wordsync, it is SupraMount. I suspect that your
mount command is to close to the beginning of the sequence. Try moving
that command further down in the sequence, giving the Seagate time to
"spool up"
I like having the extra 84 megs, but Seagate is slower and much,
much louder than the Quantum. Oh well, the price was right.
Branden Beachy
72557,107
Ditto. Slower, louder, good price. I do have a mount command in the
startup-sequence, but I'll try putting it later. Thanks for the help.
Perhaps we can compare notes sometime on our similar setups. Thanks again.
Randy Monk
Much later. I have a Q 105 and the spinup time is around 7 seconds.
I think don has suggest some other workarounds in the past but I can't
remember which one I used. Have since moved that drive to another system
where both drives are Quantums so everyone comes up at same time.
lGlamb
Randy,
We're using the same drive and had the same problem. The CBM controller
has a jumper that increases the time the controller will look for a drive.
Dunno about the GVP. Just doing that wasn't enough, we also set the device
jumper on the drive to 5, it came as 0 which didn't give it enough time. If
the GVP has such a jumper it might work. Using the mountlist or wait
commands in the startup-sequence won't work.
Good luck!
Bill Carey – via Whap!
Many, many thanks. I'll keep trying.
Randy Monk
Tell If you have the 2nd hardrive internal or external. If it is external
then just turn the Harddrive on before you turn on your Computer. that is
the way I get around that Problem. Also I'm sure that GVP Tech-support will
help you figure out the Trouble, they have helped me in the past.
James Scott
Great Day to be Alive
It's all internal. GVP tech support is excellent, but so far unable to
solve the problem.
To bad, I pretty sure your trouble is one drive is setting up faster than
the other. Hmmmm….Wish I could help more.
James Scott
Great Day to be Alive
If James is right about the setup speed, booting from the slower drive
might solve the problem!
>> Gary <<
Thanks for your help. I'm going to try switching the SCSI i.d. numbers, and
raising the boot priority. I'll let you know what happens. Thanks again.
Randy
Dear everyone: With the help of GVP, after all other suggestions were
exhausted, I switched the SCSI i.d. numbers of the two drives, and changed
the boot priority of the faster drive to -5 (from -10). Now it works like a
charm (without having to boot from the slower drive). 1,000 thankyous to
all (and there were many) who offered advice. The baud rates are loaded
with nice people. Thanks, thanks, thanks.
Randy Monk