Using a big hard disk with the Amiga

[AndyLandy]

So, this has come up many times before, but I'm still not sure what's the best route to go down.

In my search for a disk for Phantom, I've discovered quite a few 18GB and 36GB SCSI disks lying around the place, and it'd be lovely to use one of these on my Amiga(s) -- So, the question is 'how?'

I'm currently using a GVP Impact SCSI card, with v4.15 ROMs on a Kickstart 3.1 Amiga 2000. What do I need to partition/format the disk? (HDInstTools gets upset at disks this big) and then what filesystem should I be using?

To be honest, I doubt I'll need that much space, but the disks are available, so I thought it might be worth trying at least.

 

[Zetr0]

@Andy

The big trick is getting the geometry right. without the GuruROM you are limmited as to what the controller can actually see via its software.

1. Install a 3.1 Kick ROM
2. Plumb up the drive in and configure its SCSI ID.
3. Boot from a (modified)* Workbench 3.1 Floppy
4. Run HDToolsBox, it should discover the drive.
5. Define NEW, Read Data From Drive
6. Ignore the negative numbers and SAVE
7. Run the Partitioning, you should see the full SIZE available.

*(modified) - include gvpscsi.device in the DEVS/ directory

This works for most of the things I have tried it on (with exception to a GVP A500HD+ ROM 3.15), I also found that when writing beyond the 3.8GB the A500HD starts to error on the drive and sends into validation frenzie, BUT i am only using FFS file system.

I know I am doing somthing wrong, as our good brazilian buddy has an 18GB SCSI drive running on such a unit.

The next part after you have setup say larger than 4GB partitons, you will need to install and configure SFS (smart file system) I will dig up some HOW-TO links later for you.

 

[rkauer]

If the SCSI card have the ROM fitted there is no use the gvpscsi.device in EXPANSION drawer.

Boot from the 3.1 install floppy, open a CLI window, change the drawer to "tools" and type "hdtoolbox gvpscsi.device" (notice the device name is case sensitive!).

If nothing shows up in the HDToolBox program you misspelled the device name. Quit the box and type "version gvpscsi.device" and try different names until you receive a 3.15 answer.

 

[Kin Hell]

Just to add over Zetr0's suggestions above, HDToolbox under a fully patched install of OS3.9 will give you better functionality over OS3.1 HDToolbox. I have an IBM 10K ddys 68pin affair that HDToolbox 3.1 just refuses to read correctly. More so if you are forcing SE on the SCSI bus from one of your devices which you are terminating from/with. :nuts:

Kin

 

[AndyLandy]

Just to add over Zetr0's suggestions above, HDToolbox under a fully patched install of OS3.9 will give you better functionality over OS3.1 HDToolbox. I have an IBM 10K ddys 68pin affair that HDToolbox 3.1 just refuses to read correctly. More so if you are forcing SE on the SCSI bus from one of your devices which you are terminating from/with. :nuts:

Kin

So, which bit makes the difference? I'm not using HDToolBox that came with any AmigaOS install, I downloaded a version of HDInstTools from Aminet, which is dated October '99 and have been using that, but sometimes it struggles with larger disks. Do I need any magic libraries or devices, or a newer version of setpatch?

 

[Kin Hell]

Just to add over Zetr0's suggestions above, HDToolbox under a fully patched install of OS3.9 will give you better functionality over OS3.1 HDToolbox. I have an IBM 10K ddys 68pin affair that HDToolbox 3.1 just refuses to read correctly. More so if you are forcing SE on the SCSI bus from one of your devices which you are terminating from/with. :nuts:

Kin

So, which bit makes the difference? I'm not using HDToolBox that came with any AmigaOS install, I downloaded a version of HDInstTools from Aminet, which is dated October '99 and have been using that, but sometimes it struggles with larger disks. Do I need any magic libraries or devices, or a newer version of setpatch?

HDToolbox has never been an Issue for me under OS3.9. That's with both BoingBag 1 & 2 updates & for kicking the new ROM from BB2 into RAM (if that makes a difference :shrug: )

Kin

 

[r0jaws]

Harrisons post HERE covers using a 40Gb HDD. I nice clear walk through TBH.