A600 with KS37.300 not being kind with new HDD

[Jope]

Also be sure to check by rebooting with both mouse buttons down that the partitions are visible in the early startup menu..

If not, then it can't be an automount bug either.

I remember having the same kind of problems with a 3.0 A4000 at some point in time, but I think those were solved by

- installing the correct filesystem in the RDB
- checking that the dostype of the partitions correspond to a findable filesystem

I was running PFS3 on the drive and it so happened that I had it in the RDB of my first drive, but not the second drive.. -> remove first drive, second one mysteriously broke

So also look to see that the dostype isn't plain vanilla FFS.

[Jope]

cartmanau wrote:

- installing the correct filesystem in the RDB

Is this done in HDToolBox?

Yes..

And I said it a bit unclearly before:

Set your dostypes to normal FFS (DOS/1 or 0x444f5301) .. my sentence was a bit backwards.

[Jope]

It might have been a better idea to carefully open either end of the 44pin flat cable and peel out the red cable.

But end result is the same in both cases - the reset signal doesn't get to the drive and it is immediately ready for action even after keyboard resets.

IDE drives very seldom hang in a way that they stop responding to commands, so you will probably never miss that reset signal.

[Jope]

The _RESET signal is pulsed only for a brief moment, but the kickstart versions differ in the amount of time they sit around waiting for the drive.

KS3.1 waits up to 30 sec before it deems that there is no physical drive answering to the unit it's trying to query.