Hi,
Does PrimoCache still lose it's cache if C: drive is cached and the user runs chkdsk /f on it to check the file system?
I am wondering if this issue was ever resolved:
viewtopic.php?t=4578
chkdsk C: Current Behaviour
Re: chkdsk C: Current Behaviour
Have you also encountered the problem of losing all the cache on the C: drive after running chkdsk?
The case you cited is that running chkdsk on C: drive (not cached) caused the cache of the D: drive to be lost. There are some differences with your situation. When a drive is cached, if you run chkdsk on the drive, the cache contents might be updated if the cache space is full. But normally, not all cached contents will be lost.
The case you cited is that running chkdsk on C: drive (not cached) caused the cache of the D: drive to be lost. There are some differences with your situation. When a drive is cached, if you run chkdsk on the drive, the cache contents might be updated if the cache space is full. But normally, not all cached contents will be lost.
-
- Level 1
- Posts: 2
- Joined: Mon Oct 07, 2024 9:28 am
Re: chkdsk C: Current Behaviour
Correct, I lose all the cache content if I run chkdsk /f on C: drive as C: drive is cached for me (L2-Storage cache using a small SSD).
I am not sure what Windows Fast Startup does but I have tried it with both ON and OFF, same behaviour.
Upon next restart after chkdsk /f, the L2-cache is lost. So this is a problem. I wonder if this will be fixed in version 5.0.
If I run chkdsk in read-only mode, then the cache persists.
I am not sure what Windows Fast Startup does but I have tried it with both ON and OFF, same behaviour.
Upon next restart after chkdsk /f, the L2-cache is lost. So this is a problem. I wonder if this will be fixed in version 5.0.
If I run chkdsk in read-only mode, then the cache persists.
Re: chkdsk C: Current Behaviour
Thank you for your information! I'm not sure if this problem will be addressed in v5.0, but I have reported this problem again to our R&D team.