Romex Software Forum

Hello,

I have installed PrimoCache on a Laptop (Dell Inspiron 15-3551) which has a
Pentium Quad Core 2.6GHz (Max), 4GB DDR-3 RAM, 500GB HDD running Windows 10 Pro x64

PrimoCache 2.3.0 settings are - Read+Write strategy, L1 = 512MB, L2 = 8GB, Block size = 64KB.
Defer write & Prefetch cache are disabled.

When L2 cache is set to use a 8GB Kingston DataTraveler USB Flash drive, it works correctly.
When system is rebooted, the L2 cache is persistent and is used to speed up the boot process.
However this USB pendrive sticks out too much from the side of laptop and is not convenient.

So I tried using the internal SD card reader that my laptop has. The SD card reader is a Realtek
USB card reader installed inside the laptop. So there is nothing sticking out when it is used.
I used a Samsung 8GB SD card for L2 cache storage.

The problem I am facing is that on every reboot, the L2 cache is flushed and rebuilt from scratch.
L2 is not persistent when internal USB SD card reader is used.

I next tried an external USB memory reader with the Samsung 8GB card and L2 cache is still
NON-Persistent i.e. - L2 cache is rebuilt from scratch after every reboot.

1) Is there any solution to this problem. What are the criteria used by Primocache to determine that
L2 cache is "dirty" and needs to be rebuilt.

2) Can L2 cache be forced to be persistent and its status verified when system load is low.


3) There is a "Ignore Sync Check and Preserve Cache Anyway" option in L2 cache config screen but
it is greyed out. It is supposed be enabled by using command line interface but there are no details.
Please help me in trying out this option. I will test in a separate windows installation.

Thanks

3) There is a "Ignore Sync Check and Preserve Cache Anyway" option in L2 cache config screen but
it is greyed out. It is supposed be enabled by using command line interface but there are no details.
Please help me in trying out this option. I will test in a separate windows installation.

I would also like to know. Why using command line and not in the GUI?

Our support team discussed this problem with vks1000 by emails. I'm sorry that I forgot to update this thread. The problem might be caused by failure of writing sync flags to SD card on shutdown. This problem might also be relevant to hardware devices as vks1000 later reported that another model USB card reader has no this problem. So far we're still checking this problem to see if we can find a solution.

Regarding "Ignore Sync Check and Preserve Cache Anyway" option, because this option may corrupt target volumes, we don't suggest to enable it.

This problem shall be fixed in version 2.4.0. Thanks all!