braith

Hi Drashna, thanks for checking in. This is oddly enough an almost brand-new build, maybe 2 months, so it doesn't have a lot of "cruft"; no outside defrag or AV, few utility tools at all. (It's basically a file server/database engine, running a desktop OS for curiosity's sake). The only low-ish-level utility on it is Macrium Reflect, which doesn't do anything vastly stupid with filter drivers (like -spit- Acronis). C:\WINDOWS\system32> fltmc filters Filter Name Num Instances Altitude Frame ------------------------------ ------------- ------------ ----- WdFilter 18 328010 0 luafv 1 135000 0 npsvctrig 1 46000 0 FileInfo 18 45000 0 Wof 0 40700 0 which seems okay, I think, although that new (to me) npsvctrig I dunno much about. I did a thorough memtest86 when I put the box together in July, but another never hurt; right now it's chugging through chkdsk, but that's going to take several days. (4x3T, about 85% full). I've turned on trace in DrivePool.Service.exe.config (I still can't access the UI) and it's generating logs. Will zip up in a bit. Thanks again!

Crashes is the wrong word. Loses connection to the service? I have 2 Windows 8.1 machines, each with a pool of 4x3T drives (and unpooled application/work drive and SSD OS drive. The pools are rsynced on demand, basically production and staging). Things have been going more or less swimmingly well since I set it up, around a month. However a couple days ago weird stuff started happening on one of the machines: - When I would try to delete a folder, I'd get a permissions failure, even as administrator/owner - after said error, I could go into the folder but not modify it - "eventually" (I don't know how long, an hour?) the folder would disappear and all would seem well I chalked it up to some syncing issue between Drivepool and the Windows kernel and made a note to look later (busy, and this isn't really a production system, it's at home). But- this morning when I opened the Drivepool app and looked at it for a second I realized it was connected remotely to the OTHER machine; the machine I was on wasn't even listed. I restarted the Drivepool service and the app could connect. As soon as I did it would begin "Measuring...", for around 30 seconds, then quietly switch BACK to the remote machine; local no longer listed again. Rebooted, same. Uninstalled/reinstalled, same. Waited a few hours (I also own Scanner, which is chugging away, without error), same. Nothing in Event logs. Note that the pool seems FINE, at first. However the pool drive will briefly disappear and then reappear, with no notice (sporadically). CPU usage is slightly high but meh, disk access is heavy but as I said, Scanner is chugging. Explorer is quite slow. The only way to get the app to connect is to restart the service, but it only lasts a minute. No software/etc has been installed or modified. No third party AV. sfc /scannow comes back clean. Thoughts? Something I can test or a way to get a logfile? I'm really a Linux guy but I can follow instructions. Shocker, I know! Drivepool service running, but app unable to connect, pool slow/missing/fine/repeat Unable to delete folders, reports as some kind of permissions/ACL issue, but may be that folder doesn't exist anymore Windows 8.1 pro, i5 3570k, 24G RAM 4x3T pool, no duplication Drivepool 2.1.1.561 Thanks for any suggestions... -S.