A4000 IDE HDD issue

[Reynolds]

I have a continous issue with a HDD in an A4000. It is configured, partitioned and was in use since years. It has boot partitions besides with the non-bootable ones, in the IDE bus. The machine recognizes it well, I can see all partitions with no issues in the Early Startup. When I boot up the WB (OS3.9) and wanna start the HDToolBox, the util starts with searching for the drives attached to the machine, and my system freezes. I can't get into the partitioning part or anything else, although I'd like to modify things on that drive. Anyone experienced immediate crash of HDToolbox?

[fgh]

Originally Posted by Reynolds

I have a continous issue with a HDD in an A4000. It is configured, partitioned and was in use since years. It has boot partitions besides with the non-bootable ones, in the IDE bus. The machine recognizes it well, I can see all partitions with no issues in the Early Startup. When I boot up the WB (OS3.9) and wanna start the HDToolBox, the util starts with searching for the drives attached to the machine, and my system freezes. I can't get into the partitioning part or anything else, although I'd like to modify things on that drive. Anyone experienced immediate crash of HDToolbox?

Perhaps some device driver is causing it?
Try (temporarily) removing stuff from devs:

You can restrict the device scanning by tool types.
Askdevice=NO will make it just scan the driver given in scsi_device_name
I don’t think Scsi_max_address has any effect on IDE, but you could always try

[thomas]

Originally Posted by fgh

I don’t think Scsi_max_address has any effect on IDE

Of course it has. HDToolbox does not know whether it is SCSI or IDE. It just opens the various units on the .device driver consecutively and stops at a bad return code or if MAX_ADDRESS has been reached. Same for MAX_LUN, makes sense to set this to 0 for IDE because IDE does not support LUNs.

[fgh]

Nice, thanks Thomas