This message probably came from the boot sector that was written to a disk by a German DOS format utility. You can verify that with a disk sector editor like Norton Disk Editor - see the raw contents of the first sector of your disk and partition.

So it looks like really something is on this drive then why BIOS says "Drive C error..."?
Other drive ST-255 can be low level formatted in SStor without any problem. After rebooting my computer system is starting from disk A: but it is hanging on black screen with blinking cursor what can I do in this case?

That drive is RLL, not MFM.
Are you trying to use it with an RLL controller, on an MFM one?

I should write this information on the beginning: I am using controller WD1006V-SR1 which was connected to this disk when I bought it inside Amstrad 2386 so RLL controler with RLL drive. For other HDD I am using other controllers. I have several controllers for eg. WD1003-WA2

Tomek TRV wrote on 2024-12-05, 22:52:

So it looks like really something is on this drive then why BIOS says "Drive C error..."?

Some MFM/RLL controllers have a ROM, with format utility usually, but also ROM-less ones might be doing some quick media test on power-on. If they don't like what they see there will be an error. As an example my RLL controller does this if the connected HDD is not yet low-level formatted. The error sort of implies a problem with the HDD but there is none, just the format is not recognized. This "error" is not a show-stopper or otherwise you wouldn't be able to continue the boot (from other HDD or a floppy) to access the formatting routine.

Possibly your drive is only partly formatted? So the controller can read the track 0 and show the bootsector message but otherwise the quick test fails. Or perhaps the error comes from the ROM on the RLL card and it's in German. Some photos of the card in question might help.

Tomek TRV wrote on 2024-12-05, 22:52:

Other drive ST-255 can be low level formatted in SStor without any problem. After rebooting my computer system is starting from disk A: but it is hanging on black screen with blinking cursor what can I do in this case?

Could be a bug in the boot code - which include the BIOS itself. Some early HDD software expects to see exactly 17 sectors per track on HDD, and will fail on RLL formatted drives for that reason. My controller has some workarounds for that in the ROM (you set 17 sectors in BIOS, but that value will be modified by the controller card once HDD is read for booting). Does the hang also happen with MFM format? What if you use RLL format but limit the sectors to 17, does it work then?

What's the goal?
Data recovery, or just getting the drive running?

If the latter, I would start with the simplest case:
- connect the RLL drive to the MFM controller, without any BIOS extension
- enter the HDD parameters into CMOS setup, but with 17 sectors/track, the default for MFM drives
- LLF, from BIOS utility, or HDINIT from Checkit 3.0
- FDISK, FORMAT, etc.

If it works well as MFM, next step would be to connect it to the RLL controller, and reformat...

Building on Deunan's post...
The message is possibly being spat out by the MBR code.
The MBR code is probably immune from any geometry issues (you will always be able to read track zero, head zero, sectors 1-17, in spite of any geometry issues), but if the boot sector of the active partition which gets loaded by the MBR cannot be read, the boot will fail.