fattipants2016

Thanks for the help. Everything seems happy right now, so I'll stop tinkering with it.

I'm curious about the precedence / interaction between the JSON settings in ProgramData, the config file in Program Files and the configuration in the GUI. Do JSON settings take precedence over a config file that might still reside in my application directory? And adjusting settings (turning NTFS filter bypass, for instance) doesn't turn on the corresponding setting in the GUI. If I've turned on filter bypass in the JSON and the GUI still says it's off, which is correct!? I don't mind changing the option in multiple places, it's just a lot of bases to cover when troubleshooting / tweaking.

I wouldn't sweat it, it's definitely a Windows Issue and not one specific to DrivePool. It's just not a particularly common scenario (drives with no letters) with the exception of this community, so I figured I'd ask.

Yes, assigning the devices drive letters alleviates the problem. In fact, until I hear about a permanent solution, I've found you can assign each volume a drive letter and simply hide them with group policy settings. I'm happy enough to call that a fix and stop worrying about it. Thank you.

So I suspect this may be a Windows problem and not a DrivePool problem, but hopefully someone here has experienced something similar... I have 4 physical drives in an external USB enclosure. 3 are members of my pool, the 4th is SnapRAID parity data. Aside from the 3 pool members, the 4 discs are mounted to NTFS subfolders inside of /SnapRAID/ but have no drive letters assigned. DrivePool and SnapRAID are both happy. Windows is not. I have multiple warnings, and my event log is SPAMMED with device driver errors. Assigning drive letters to one or more of these physical discs (while keeping folder mount points) alleviates the problem. Once the drive letters are removed, and I reboot the computer, the errors are back. If anyone knows what I can try to make this madness stop, I'd be mighty grateful. Screen grab of what the errors look like: HERE Error log snippet: 02/07/2018 23:43:31,Error,Disk,The driver detected a controller error on \Device\Harddisk5\DR5. 02/07/2018 23:43:31,Error,Disk,The driver detected a controller error on \Device\Harddisk6\DR6.