A2000 hd install problem

[utri007]

My setup is ::

A2000 kickstart 2.0
Supra Worsync scsi with latest rom AMAB6

When I boot with supraboot, it says "no partitions". I wants me to do low level format wich I did. I can create partitions, but I can't format them and when I reboot with supraboot I says that "no partitions", but I can see them in workbench. How ever, I can recreate them and they appear in workbench, but I can't format them and still if I boot again supraboot says no partitions.

I have tried to format with workbench and with supraboot. In workbench it says that format failed, with supraboot says OK, but but format doesn't do anything.

I have also tried with HDinstTools, it founds a HD, allows me to create partitions, but actually it doesn't do anything. No partitions, no format. But everything is "successfull", or at least it says so.

Sorry this and would be very surprises if anyone could help me, I have tried everything wich I know.

[danbeaver]

Experience with KS2.04 and its use is going to be limited I'm afraid (I haven't used it in ~20 years), so you may have to wait a while for someone experienced with it to help.  Have you thought of either setting up a dual boot system (1.3/2.04 and 3.1) or just moving to KS3.1?  The reason they came up with 3.1 was to fix problems in 2.04.

In KS3.1, if you see the unformatted partitions on the Workbench, they should format unless the file system is not stored on the HDD, the format command is not in the SYS:System directory, or the RDB has an error in it.  A bit more information on the type of hard drive, and screen shots during setup would help.  Plus, any controller that supports RDB should allow use of the Hard Disk Toolbox, and not require the Supra install disk.  I know this is of no immediate help, but I hate seeing a posted problem go unanswered as if no one cares.

[Matt_H]

I'm guessing the Supra software was designed for 1.3; try prepping the hard drive with HDToolBox if you can. I recommend using the HDToolBox version from the 3.1 Install disk, since it has a few improvements. It works under Kickstart 2.x. Use the Tooltypes to change it to scan for Supra's device driver (which is probably something other than scsi.device).

It sounds like the Supra software messed something up with the RDB, so you'll probably want to recreate it from scratch. Once you're in HDToolBox, change the drive type, define new, and read the drive parameters.

Also, you shouldn't need to low-level format drives anymore - that's a vestige of 80s hard drive manufacturing techniques.

[utri007]

Thanks

I will try 3.1 install disk. 2.0 hd install disk doesn't help I tried it also, it doesn't found hd at all. Can I use OS3.1 with kickstart 2.0? 37.175 if I remember correctly?  

HDinstTools I need to specify suprascsi.device also, so that is not a problem. I have good experiences for HDinstTools so I just thought it would be best choise. Just wondering, should I disable auto boot or not when I install hd? Supra's guide says that I should.

[danbeaver]

The OS3.1 install won't work with KS2.04, but it has a better feature list over WB 2.  The upgrade is reasonable and replacing the ROM takes 30 minutes -- due to removing the PSU. The new owners of this site will sell you a ROM with a papal blessing via Hyperion.

[Matt_H]

The OS3.1 install won't work with KS2.04

True. I was only talking about HDToolBox, which does work with 2.x.

@ utri007

So, to clarify in case there's any confusion, boot from a 2.x Workbench disk, then insert a copy of the 3.1 Install disk and run HDToolBox.

Keep autoboot enabled. Otherwise the driver won't be loaded (and you won't be able to work with the drive), unless you have a software version in SYS:Expansion. If you've had autoboot disabled this whole time, it's possible that whatever software version of the driver is in your Expansion drawer is older/buggier than the ROM version, which could also explain some of your problems.

[danbeaver]

And I was only responding to the question, "Will OS3.1 run on KS2.0?"  

I used OS2.04 last year on an A3000 I was restoring and it was so frustrating that I set it aside until the 3.1 ROMs came in from overseas.  Then I was actually able to finish that project, blood loss and all.

[utri007]

Thanks for help guys

Install disk indeed works with kickstart 2.0

Problem found but not solved. None of these HD install tools gives righ values to disk. 3.1 hd install tells that disk size is -37mb, negative value. All of them gives wrong numbers head/blocks per track etc. and so far haven't been able to found correct values.

Next I'm going to try these https://groups.google.com/forum/#!topic/comp.sys.amiga.misc/8StlIhvwGpE

HD is Quantum LPS270S

[Matt_H]

And I was only responding to the question, "Will OS3.1 run on KS2.0?"  

I used OS2.04 last year on an A3000 I was restoring and it was so frustrating that I set it aside until the 3.1 ROMs came in from overseas.  Then I was actually able to finish that project, blood loss and all.

Ah, thanks. I'd missed that part of the original post.

I never actually used 2.04 back in the day. I went straight from 1.3 to 2.1, then to 3.1. Apart from Datatypes/Multiview, there wasn't a whole lot different between 2.1 and 3.1 on the surface. More recently I did actually boot up 2.04 and I was quite surprised at how much I took for granted in 2.1 wasn't there. I understand your frustration

[danbeaver]

The file system is giving you the negative number as the early Amigas were designed before 1 GB or 1 TB drives; a straight 3.1 FFS limits you to some ridiculous low size, God Only Knows what 2.04 limits you to.  There are patches for FFS or you could grab Version 45.16 from OS3.9 that should help.  Using SFS v1.277 (1.279 seems to have disappeared) might work on a KS 2.04 system.

[utri007]

I have one A500 with GVP HD8+ and Workbench 2.04 it has a 4gb hard drive, works well. Also there was a 800mb hard drive originally connected to this supra wordsync, it is broken.

I'm starting to belive that this hard drive is broken.

[Matt_H]

@ utri007

Good find on that old Usenet thread. It looks like several Quantum drives of that era don't autodetect the drive parameters correctly. Did you see this post/try these settings?

I too had a problem setting up my new Quantum LPS270 hard drive.  HDToolbox
doesn't read the information from the drive.  I originally came up with the
following settings:
                        Cylinders - 4130
                        Heads     - 1
                        Blocks per Track - 135
                        Blocks per Cylinder - 135
 
which gave me 272 megs of disk space and it would format correctly.  I called
Quantum's tech line and the amiga tech guy told me to use the following
settings:
   
                        Cylinders - 944
                        Heads - 14
                        Blocks Per Track - 40
                        Blocks per Cylinder - 560
   
which gives you 257 megs.  When I asked if there were really 14 heads he said
"no" but it is only a mathmatical abstraction.  I can't remember exactly but
it is the number of cylinders times the number of heads times 512 (or
something of that nature) and whatever gets you closest to 272 meg will work.

I'd start with the second set of settings from Quantum's ancient tech support.

[utri007]

I tried that. There is a problem, if scsi ID is 0 everything seems to be OK, but HD is all luns 0-9. If I change scsi ID to any other, lets say it is ID2 then lun is 0, but I can't save changes to to drive, I get error 44.

Occurs when an internal microprocessor detects incorrect status or receives an illegal request from the device electronics.  This is a hardware failure.

I starting to be end, I can't figure out what to test next.

[danbeaver]

Test another drive?

[utri007]

You are right Problem is this is my only scsi hard drive, excluding one wich is in use.