Problem with SCSI drive not working on A500 hd8+

[countzero]

I'm trying to use an IBM 4.3 gb scsi drive (model DCAS-34330) with no succes. I'm trying to set this up on an A500+ with 2.04 roms, wb 2.1, using HDinstTools from aminet placed on wb 2.1 install disk. GVP A500hd8+ has 4.15 Roms I recently bought from TJlaser. Drive starts spinning during boot, but HDInstTools will not find the drive. I guess I'm doing something wrong with the jumper settings. I'ld be glad if someone can give me advice what jumpers to set on.

Available jumpers are :
1 Spare (50 pin) id bit 3 (for wide)
2 id bit 2
3 id bit 1
4 id bit 0
5 Disable auto spin
6 SCSI term on
7 disable unit attn
8 TI sync nego
9 auto start delay
10 delay start 6/12
11 disable parity
12 led out

The factory default scsi id of the hd is 6. I've tried with id bit 1, scsi term and disable parity (on and off). I have no idea what the 7 and 8 pins do. btw, I have two identical drives, and I tried with both.

[countzero]

Another question about the a500 hd8+, what does the jumper2 do on the hd8+ (it's under the rf shield, under the hd) ? and what is the factory setting ?

[countzero]

*bump*

I noticed something about the ICD trifecta drive at amiga-hardware.

"Please note, it does not support Western Digital or IBM hard drives"

does anybody know if the same thing goes for the gvp a500hd+ as well ?

Also, is there a way to check if the gvpscsi.device is properly loaded ? (with some kind of command or utility ?)

[orange]

try setting the jumper for: DISABLE SYNC NEGOTIATIONS
auto spinup shoud not be disabled, IIRC

[Amigaz]

I have a GVP A530 which uses the same SCSI controller and I can only prep it with the GVP install disk...have you tried that one?
Not even OS3.9 hdtoolbox seem to fix the job  :-(

install disk

[doctorq]

I'm using a IBM 2 GB drive in my GVP HD8+ without any problems. It can be accessed without any problems from HDInstTools, HDToolbox and the GVP FaaastPrep program.

IIRC I had to softkick to Kickstart 2.0 in order to load up the HDInstTools program to setup the drive (FaaastPrep and HDToolbox reportet errors under Kickstart 1.3).

What version of the GVP rom do you have? I was once told that the older versions of the GVP rom had issues with larger harddrive. You should be fine if the rom is ver. 4.15 or higher, but not really sure on this one.

As for the JP2 jumper, I'll try to see if I have the manual somewhere.

-EDIT-

Read the first post again, and saw that it answer to my question. Try to remove the jumpers from the ID pins, it should make the drive unit 0. Then a jumper on the SCSI term pins, and you should be set to go.

You specify the right driver when launching HDInstTools right? The program should be started from CLI/Shell with gvpsci.device as a parameter.

[Argus]

It's probably a combination of IBM technology and your GVP Fastrom version.  I've had a heck of a time trying to get certain IBM drives to work with both amiga standards scsi ports and on GVP boards.  I had a big half-height 2.1G that I eventually got to work with GVP Expertprep but it took a while before everything was working.  Even then, I wasn't able to change partition sizes from the default settings, so I am stuck with three 600+MB partitions.  I think IBM used proprietary stuff on some of their drives for extra speed/compatability with their controllers, so it may be hit or miss if your drive came out of an old Big Blue server.  I had a similar problem with a 500MB 2.5" DCAA IBM drive in my A1200 that came out of a Thinkpad; it would work with the default HDSetup (only 5MB System partition) but would fail to recognize different custom partition sizes, even with HDInstalltools. So, try to just use the default sizes under GVPExpertprep or HDInstalltools/HDSetup.

[Amigaz]

Argus wrote:
It's probably a combination of IBM technology and your GVP Fastrom version.  I've had a heck of a time trying to get certain IBM drives to work with both amiga standards scsi ports and on GVP boards.  I had a big half-height 2.1G that I eventually got to work with GVP Expertprep but it took a while before everything was working.  Even then, I wasn't able to change partition sizes from the default settings, so I am stuck with three 600+MB partitions.  I think IBM used proprietary stuff on some of their drives for extra speed/compatability with their controllers, so it may be hit or miss if your drive came out of an old Big Blue server.  I had a similar problem with a 500MB 2.5" DCAA IBM drive in my A1200 that came out of a Thinkpad; it would work with the default HDSetup (only 5MB System partition) but would fail to recognize different custom partition sizes, even with HDInstalltools. So, try to just use the default sizes under GVPExpertprep or HDInstalltools/HDSetup.

Exactly the prob have, mine is also an IBM
I thought it was just me  :crazy:   :lol:

[countzero]

doctorq wrote:

You specify the right driver when launching HDInstTools right? The program should be started from CLI/Shell with gvpsci.device as a parameter.

Oh no, never knew about that  :angry: I'll try this and the gvp install disk (if hdinsttools doesn't work) this monday and I guess I'll manage to solve this problem. Thanks everyone for the great information.

[Tomas]

I didnt get hdinstalltools to work either.. But downing the adf image of the gvp install floppy disk solved all my issues.

[Amiga4k]

doctorq,
It is refreshing to read your concise reply. Most drives install with the "original" install disk (ie this case GVP install disk).
The loss of drive showing up is usually a tooltype issue, as you said. There is a program called SCSI Inquire that reflects this issue quite candidly. Here's a list of some device handlers that go in the devs.


Commodore A2091/590/3000                scsi.device
2nd Commodore A2091                     "2nd.scsi.device"
Commodore 1200/4000                     scsi.device
Commodore 4091/DKB                      "2nd.scsi.device"
GURU ROM                                omniscsi.device
GVP 4008/Impact SeriesII A500/2000      gvpscsi.device
GVP 3001 680x0 Combo SCSI               gvpscsi.device
GVP 3001 68030 Combo IDE                gvpat.device
IVS Trumpcard Classic                   IVS_SCSI.device
IVS Trumpcard Professional              IVS_SCSIpro.device
Expansion Systems DataFlyer             ExpSys.device
Expansion Systems SCSI+ or XDS Chassis  ExpXDS.device
AS&S FastLane Z3                        z3scsi.device
Warp Engine                             warpdrive.device
NewTek Flyer                            flyerscsi.device
ICD Advantage 2000                      icddisk.device
ICD AdSCSI                              icdscsi.device
ICD AdIDE                               adide.device
ICD AdIDE2                              icdide.device
DKB RapidFire                           dkbscsi.device
AlfaData/bcs Oktagon SCSI               oktagon.device
Comspec SCSI                            CompspecSCSI.device
Supra Series II/III                     suprascsi.device
MicroBotics Hardframe                   HardFrame.device

Note: Capitals and quotes are important, as device handlers are case sensitive.

[doctorq]

@Amiga4k

Seing your list, there is actually a couple of the device drivers that are read of ROM, and therefore doesn't necesarely need to be in devs:

For instance
Commodore 1200/4000 scsi.device
Impact SeriesII A500/2000 gvpscsi.device