CompuServe Thread

#2nd SCSI HD Problems

13 messages in this thread
#7989From: Randy MonkFeb 27, 1991 9:18 PM
I've connected a 2nd internal SCSI hard drive to a GVP Impact Series II controller. The trouble is, a cold boot doesnt recognise the 2nd drive. (inaccessible from WorkBench and the CLI) A warm boot recognises it just fine. What gives? Randy Monk
#7995From: Mike SchillerFeb 28, 1991 12:51 AM
Randy: It sounds like your drive might take a while to spin up to speed. If it's not ready when Kickstart goes to read the RDB (sort of a boot block for HD's) then the drive won't be recognised. When you warm boot, the drive is already spinning, so the system has no problem seeing it. -Mike Schiller In sunny Fort Lauderdale
#8008From: Randy MonkFeb 28, 1991 9:06 PM
Thanks for the quick reply. So how do I solve it? Randy
#8031From: Mike SchillerMar 1, 1991 8:15 PM
Randy: About the only way I know of is to hold down the Ctrl-Amiga-Amiga keys when you first powerup the machine for a few seconds to give the drive time to powerup. -Mike Schiller In sunny Fort Lauderdale
#8041From: Randy MonkMar 2, 1991 8:30 AM
Mike, your help has been extremely valuable. Many thanks. If you come up with any other ideas, let me know. Thanks again. Randy
#8068From: Neil RobinsonMar 3, 1991 10:43 AM
Randy, I just called the author of the drivers for GVP and he said that you can do a couple of things. 1. Get the latest revision of the driver. It has a number of improvements to speed up booting and solve your specific problem as well as a utility for mounting devices that take longer to spin up. 2. Set the SCSI ID of the slower device to 0 and make the faster device a higher number. Hope this helps, Neil
#8075From: Randy MonkMar 3, 1991 6:58 PM
Many, many thanks. I'll try both of your suggestions. Randy Monk
#8001From: Don Curtis/SYSOPFeb 28, 1991 3:58 PM
Randy, Is it a SeaGate drive? If so, SeaGates are notorious for taking a long time to come 'online' and thus aren't recognized on cold start. Don
#8009From: Randy MonkFeb 28, 1991 9:08 PM
You guessed it, a Seagate. So how do I solve the problem? Thanks for your help Randy
#8016From: Don Curtis/SYSOPFeb 28, 1991 11:32 PM
Randy, I don't have a GVP, so don't know for sure…but memory tells me that they have a jumper on the board that allows a longer timeout period during bootup. I could also be wrong on that…perhaps someone with a GVP that knows for sure could jump in and let you know for sure. Another thing that could be done is to have the Seagate on a separate power supply and turn that on about 5 to 10 seconds before you turn the computer on. But short of those two things…there is nothing you can do to fix it. Don
#8027From: Randy MonkMar 1, 1991 5:30 PM
Would it make a difference to boot from the slower (Seagate) drive? Thanks again. Randy
#8038From: Don Curtis/SYSOPMar 2, 1991 1:16 AM
Randy, No…that won't help because it can't see the drive (since the drive isn't ready) thus can't boot off the drive. There is no way the host adapter can know about a drive until the drive itself reports that it's ready. If the drive takes longer to report ready than the timeout value of the bus…the drive will not "exist" for all intent and purposes. The SeaGates only take this long time period on cold start. On warm start, they're already spun up, and the power-on diagnostics have already been run so they come on-line much faster. Don
#8040From: Randy MonkMar 2, 1991 8:29 AM
Don, your help has been extremely valuable. Many thanks. If you come up with any other ideas, let me know. Thanks again. Randy