Curious why you decided to low lever format a scsi HD ?
I do not think that ST 73Gb scsi hd is supposed to be low leveled formatted by a controller that is decades older than the HD.
Also the 1540 series has a max HD size of 8GB iirc, just because it identified the HD (is a command sent and response back thing) does not guarantee support... so attempting to format using the cards bios was a bad idea....
The drive might still be good if it was good before the failed format but would require a newer u160/u320 adapter and tool to reformat it properly.....just my opinion based on what I know.

I‘m afraid all you write might be correct 🫠

I was at first not able to access the drive although being it was detected correctly everywhere. That’s why I tried that. Root cause was the 2hdd limit on my system so I had to disable my 2nd hdd first. But then llf format already was conducted (at the least the try)

🙁

It's not the SCSI host but the device that will decide what to do exactly with the format command. Early drive (<1GB) would actually reformat, all the later ones will only check the surface condition.

What that command does (depending on parameters) is rebuild the GLIST - which is the list of bad sectors stored in GROWN. I've dealt with some damaged SCSI drives and in my experience the hardware error and code would indicate one of the heads has crashed, or otherwise stopped working properly (hit the spindle column due to rubber bumpers going bad, the wires got corroded by the glue that holds it in place, etc). So there is now a portion of the HDD that's completly unusable and the FORMAT can't deal with that. Nothing can really and it's not really worth the effort of trying to do anything about it - the HDD is unstable at best, unusable at worst.

EDIT: If I were inclined to try and salvage it I would install it in Linux machine with a "modern" PCI SCSI controller like AHA-2940UW(2) and try the SCSI tools package to reformat it again. Do note Linux kernel might be very unhappy about the broken drive during boot, that can cause it to boot way longer than usual. And this might persist until (if at all) the format passes. So a lot of patience is required one way or the other. I would not be surprised to discover that a full format in such conditions can take days due to frequent kernel trips on various errors, which cause it to stall and/or trash the console with a lines of error reports.

Thanks a lot. Yes it’s indeed the same as with modern ide drives and lff.

So thanks for confirming my „fear“ reg the device

Guys short update: I found out that my XTIDE bios was interfering with scsi. When I disabled it the drive was correctly identified by afdisk and also accessible via dos.
Strange since xtide uses d000 and the ah1542 d400. Maybe because they in general interfere or because the xtide uses d000 TILL d800 ?!

PS: tested with another hdd that originally showed the same symptoms as not showing up in dos, unable to afdisk etc. The original drive seemed to be broken anyway