Page 1 of 1

L2 storage error 0x00000057

Posted: Thu Feb 03, 2022 6:49 pm
by micronyaol
Hi!

I just installed Windows 11 and trial of PrimoCache 4.2.0.
I'm getting error 0x00000057 when trying to format drive for L2 storage.
L2 drive is is Apple iMac 2015 128Gb SSD, i used adapter to connect it to PCIE x4 slot.
Drive is working perfectly fine when formatted to NTFS.
I tried creating NTFS and RAW partition, GPT and MBR Mode.

I attach screenshot and my PC info (AIDA64 report).

Can you please help with this problem?

Re: L2 storage error 0x00000057

Posted: Mon Feb 07, 2022 3:15 pm
by Support
I'm sorry for the late reply because we were on Lunar New Year Holiday.
We checked the error code and it seems that some commands are not supported well on this kind of drives. If you are available, we will compile a debug version to trace the root cause. Thanks.

Re: L2 storage error 0x00000057

Posted: Mon Feb 07, 2022 8:06 pm
by micronyaol
Hi! Yes I can test debug build, my email is in my forum profile.
I also tried my boot drive (Sabrent 1Tb 4Kn) and got similar results.

Re: L2 storage error 0x00000057

Posted: Thu Feb 10, 2022 11:43 am
by Support
Thank you. We will send you the debug version when it is ready.

Re: L2 storage error 0x00000057

Posted: Wed Mar 02, 2022 3:54 am
by Support
I'm sorry for the late response. We have emailed you the debug version. Thank you.

Re: L2 storage error 0x00000057

Posted: Tue Apr 12, 2022 3:33 am
by myeto
Hi support,

I am also currently using the trial version of PrimoCache to evaluate use on some iMac Retina 4k 2017's I am using.
On these I have a "apple fusion drive" which seems to be a regular HDD (Model: APPLE HDD HTS541010A9E632)
and a nvme SSD (Model: APPLE SSD SM0032L) with 32GB capacity, this SSD I would like to use as cache with your software but it keeps returning error 0x00000057.

Would you be able to help with this? Please use my email if you want to contact me.
Thank you very much!

Re: L2 storage error 0x00000057

Posted: Tue Apr 18, 2023 3:42 pm
by Support
This issue has been fixed in version 4.3.0. Thanks.