Romex Software Forum

I posted this in the main forum forgetting there was a dedicated thread for the beta. I have an 120GB SSD drive that is dedicated to both READ/WRITE Cache of a Large SATA drive. I cannot restart or boot my Windows 10 machine with the cache drive plugged in. I get a spinning wheel of death that never stops or I get sent to the repairing screen. It appears to be the same issue with the non-standard volume messing with windows boot up. I have to detach the drive, boot into windows and then plug the drive in afterwards. Fortunately my raid controller allows hot swaping drives so its not an issue to plug the drive in once windows boots. Annoying to have to open the case everytime I restart my machine though.

I have 1607 WIN10 Build (all updates, no creators edition though) with a M2 SSD as the boot drive, RAID0 5TB sata disks as a secondary volume and the 120SSD for Primocache.

Love the product otherwise, awesome performance of my Virtual Machines now that I have the volume cached with PrimoCache.

@Davey126, regarding "'Free Cache on Written", it means that deferred write blocks will be immediately marked as standby blocks after their data are sync to underlying disks. But they are still there for caching purpose until they are requested to cache new data.

@hang10z, thank you for the bug report!
I'd like to know if you ever used v2.x before. If yes, does this problem happen in v2.x?
And could you help us test the case that disable L2 write caching (in Advanced L2 Settings -> Check "Individual ..." -> Move the slider to "100% read")?
Thanks a lot!

Hello!

I did not have this problem in version 2, although I did not use the product for very long, literally a day or two before I found this thread and saw that L2 Cache could be used for writes. I do remember being able to restart my machine without having to unplug the drive.

I will change to all L2 READ and report back.

Also I wanted to add that I upgraded from V2.7 to 3. It was not a fresh install.

@hang10z, you may reset L2 cache content (right click on the cache task and then choose "Reset Cache Content" in the pop-up menu) and make L2 re-populate data. This will avoid the effect from the old version.

Ok should I set L2 to all read and then reset it? Or just reset the L2 R/W cache with the above instructions? Just want to know how you'd like me to test so I can provide the best information.

@hang10z,
I'd appreciate it if you could do the following two tests.
1) Set L2 to 100% read, then reset cache content.
2) Set L2 to shared read/write, then reset cache content.
You may run each test for several days if you don't see an error. We suspect the problem is related to changing the settings of r/w space ratio .

I will try both and report back. Thank you for your assistance!

Are you looking for translations? I could translate it to spanish

@l0rdraiden, thank you very much for your offer!
We haven't started the localization work. If you're willing, I'll email you when we begin to do the translation.