Development stopped?

[Support]

Thank you for your answer. Leesamn describes a problem which strongly resembles yours. I posted a simple troubleshooting procedure there, which may come in handy for you too. There are now two cases of trouble with RAID + Updates, which may indicate a real problem with PrimoCache.

Thanks! Yes, we have noticed these reports and are investigating it.

[supercilious]

Good to hear that this is being looked into. Let me know if you need more details like a step-by-step on how to re-create the problem I experienced.

[Yozzer]

I do not wish to confuse the issue here at all, but I have had 3 instances where large Windows updates have resulted in corruption, (see my post April 15th), and resulted in my restoring my system from a backup.
I am not sure exactly what is to blame, but now I always pause, or sometimes even stop the cache before applying any updates that are on the large size, certainly updates over 60mb/70mb, and have had no problems since doing that.
I am using Windows 8.1 64 bit, and a L1 cache of 4gb, much smaller than the problem highlighted here. I was using a write defer of 20 seconds, but have reduced that to only 10 seconds.
My problem may not be related, just thought I would mention it. The practice I have adopted takes me no time, and I have run trouble free for many months now, though mine is just a home setup, and I backup daily.

[supercilious]

This seems to be the case. I experimented by installing PrimoCache on my old laptop at home just for experimenting and it caused corruption in the WinSxS component store during a windows update run. The next boot reverted the update and required me to "dism /online /cleanup-image /restorehealth" to continue with Windows update.

There is clearly some buggy interaction with Windows Update and PrimoCache.

[robertcollier4]

[quote="supercilious"]That's not going to help. For example, the shutdown scripts run before the Windows Update mechanism patches files. The only way to do it with shutdown scripts is to delete the cache in the script, and re-create it in the start-up script.

viewtopic.php?f=29&t=2246#p5940

I have done this quite effectively with WinRAR - plus the speed is faster as well.

Startup Bat File

Code: Select all

"C:\Program Files\WinRAR\WinRAR.exe" x -mt4 -ri15 -cfg- "E:\TempDriveFiles\TempDriveFilesAuto.rar" "T:\"

Shutdown Bat File:

Code: Select all

"C:\Program Files\WinRAR\WinRAR.exe" a -x@"E:\TempDriveFiles\TempDriveFilesExcludeList.txt" -mt4 -ri15 -cfg- -ma4 -s -m1 -md512k "E:\TempDriveFiles\TempDriveFilesAutoNew.rar" "T:\"

[Davey126]

I have yet to experience a problem with Windows/Microsoft updates including the recent Win 8.1 upgrade and other sizable patches. But my primary rig is a somewhat older G31/775 based system (heavily overclocked) that only supports SATA II. While the system drive is a reasonably fast HyperX 3K throttling by other components may have something to do with the lack of issues. I also have an i5 based laptop with a speedy Samsung SSD. I use similar PrimoCache parameters which involve a relatively small L1 read/write cache, no L2, 16KB blocks and 60s deferral. No issues with recent MS updates but that system isn't used on a regular basis so not a lot of data points.

Just adding my experiences to the pot.

(10/30 edit: fix a few typos - d'oh!)