Turned out, that this is not a KS or FastATA problem, this is MMULib problem.
Tried two different kickstarts and CF based soltion and result was same.
Problem started to solve, when I noticed that I can get to FastATA prefs, even from cold bot, so it does boot from hard drive, just not to OS.
Here is my startup-sequence's first lines.
C:CheckLMB
IF WARN
SYS:Prefs/FastATAPrefs
ENDIF
C:FastATA.driver QUIET
; $VER: Startup-Sequence_HardDrive 45.4 (28.5.2018)
; Startup-Sequence for hard drive systems
;C:MuMove4k
C:SetPatch QUIET
;C:MuFastZero ON FASTEXEC
C:MuFastRom ON Protect >NIL:
C:CPU CHECKINSTALL
Solution was disable MuMove4k and MuFastZero.
How this was NOT a problem with old hard drive???