Hi chell,
It looks like you have quite a large amount of L1 RAM cache and it takes quite a large amount of time to write all this cache to the storage in order to avoid data loss and proper StarWind stop.
Actually, it can be the reason.
Hi Kevin,
I suggested you run flushcacheall.ps1 before you restart the service to speed up the process and for a proper restart.
The next build should be in the middle of the next month.
Hi Chell, Could you please follow these steps to avoid the issue with RAW disks: 1) Stop StarWindService. And do not forget to run the FlushCacheAll.ps1 script from StarWindX PowerShell examples folder before stopping the service; 2) rename .splumap and .spvmap extension in folders where failed devi...
Hi Kevin, We investigated the issue with defragmentation of HA device. It was identified and a proper fix was introduced. This fix will be available in the next StarWind build. As for now, you can restart the StarWind service on your servers, wait for the full mounting of the devices and then do the...
Hi t0m, We investigated the issue with defragmentation of HA device. It was identified and a proper fix was introduced. This fix will be available in the next StarWind build. As for now, you can restart the StarWind service on your servers, wait for the full mounting of the devices and then do the s...
Hi Kevin,
Can you please collect the logs from your systems and PM me for better understanding the problem you faced? Also, please specify more details about your system configuration.
You can collect log using this tool.
Thank you!
Thank you, Petas3, for your comment :) Regarding data integrity was a very similar question, here is the answer: "No, there is no scrubbing in StarWind, this is resolving on a RAID level. In case of disk error on read another node will serve the request to HA. The HA device on the node with err...