Newly installed HD not showing in Workbench

[prowler]

Hi All,

I found an old 6gig SCSI HD gathering dust which I forgot I had and decided to install it into my Amiga.

I am running AmigaOS 3.9 and when I use HDToolBox it shows up fine. I tell it to install the drive and setup the partition sizes and select reboot when offered the option after saving the changes. The system comes back up and nothing is there.

I have also tried a 500meg HD, a 2gig HD all with the same results.

btw - the HD's are hooked up to the internal SCSI controller in my 3000 on a chain with 2x4.3Gig HDs and a CD-ROM.

I had exactly the same problem with my HD. Bought a brand new 20 gig HD, installed and partitioned it (was shown quite nicely in HDToolBox) and rebooted...no HD seen anywhere. Tried just about anything to get it working without success. Then I decided to try it on the secondary bus as master (previously I had tried it as slave in the primary bus) and - it appeared on WB as if by magic. It could be that this HD of yours is like the one I have - It doesn't like being a slave (I'm quite sure I had jumpered it properly). If possible you could try setting it to be master on secondary bus, other than that I have no idea.

Oops, I just noticed it was a SCSI, not IDE. Still, it could be a problem with jumpering or your SCSI set-up.

J.

[Thomas]

Do you run the AmigaOS ROM Update ? Did you check NSDPatch.cfg ? Have you installed Boingbag 1 and 2 ? Have you installed the new FastFileSystem on the HDD ? How large are the partitions ? Do they appear if you reboot manually (Ctrl-Amiga-Amiga) ?

Bye,
Thomas

[DeQuevedo]

Hi!

I think your problem is the rom update.

Install the BB1 and BB2, your trouble will be solved.

BB2 will tell you the new rom are a bit conflicting with some hard but don´t take care and do the installation.

I hope this helps.

Regards

[vortexau]

Another potential problem (according to a text file with my Blizzard 2060's Partitioning Util) can exist with much older SCSI drives previously in use with older Amiga SCSI Controllers!

The concept is that MASK and MaxTransfer values used earlier won't match those that a more-modern SCSI Controller uses!!

BTW - the HDInstTools partitioning utility allows those values to be changed ..... and that SAVing the NEWer values (MASK and MaxTransfer) won't usually destroy your data.

 ° In fact, I linked up an older drive recently that had been partitioned with my earlier GVP G-Force 030 Accellerator, and tried to copy its contents over to another Hard Drive partitioned with my present Blizzard 2060 WITHOUT having reset the older drive's MASK and MaxTransfer values!

The result? About 2-5% of the larger graphic files were "rounded down" to 120 000 bytes, and lost their end-of-file markers!

The only way I could salvage some part (the TOP part) of those files was by loading each into The Art Department and Re-SAVing from there.

The values reccommended by HDInstTools were:
 MASK - 0xFFFFFFFF
 MaxTransfer - 0x00FFFFFF

The values that scsiconfig3 is ready to set are:
 MASK - 0xffffffff
 MaxTransfer - 0xffffff
(scsiconfig3 is supplied with the Blizzard 2060)  

[QuikSanz]

@ vortexau

I use a Tekmagic 060. should I use factory recomended settings or the newer ones?

Chris

[vortexau]

@ QuikSanz

Is your question relating to the use of a Hard Drive previously used on a different Amiga SCSI controller? That's the type of case where this option is the most relevant.

What happens with a drive NOT previously used on an Amiga when partitioning it with a utility such as HDInstTools is that utility gives the values for MASK and MaxTransfer that work best with your SCSI Controller. ie. these values are read FROM your controller.

So, these are the values matched to the controller itself.

When a drive HAS been used on an Amiga before - it already has RDB formatting with the information written to the MIDDLE of each partition - the Amiga Partitioning Tool in use READs the values that were used before (unless I'm wrong here ....? )

Don't go by the values that I quoted - those are the ones pertaining to the Blizzard 2060 Controller that I use!

[lurkist]

I just had this same problem.  Formatted and partitioned for hours with no success, then almost as a last resort I ran QBtools (Quarterback Tools) and did a Find And Fix Errors on it - turns out the root contents were corrupted, QBTools fixed this and all was well.  It took literally seconds.  Shame one has to resort to third party utils to install an OS from scratch...

[prowler]

I got bored so I downloaded BB1 and installed that (I have heard a few conflicting comments about BB2 not being offical or something ?)

When I next brought the system up to use, the partitions I had specified on the new drive where there. A format later they were usable

[Indoro]

If your drive does not show in Workbench to format, open a cli window and try formatting it there.

I believe the command should be Format [device] [diskname] [options]. Device shopuld be the device name of your new mhard disk as shown in HDToolbox. Diskname should be what you ae naming it. Options include such things as International mode, etc that you can normally select from the workbench.

Using the format command from a cli you should be able to format your disks and they will appear in the workbench.

//RC//

[QuikSanz]

@ vortexau
Didn't realize those values were read from the controller. Thanks much, good info

Chris