fattipants2016 Posted February 9, 2018 Share Posted February 9, 2018 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. Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted February 9, 2018 Share Posted February 9, 2018 By chance, does assigning them a drive letter fix the issue? Also, you should be able to safely disable this Quote Link to comment Share on other sites More sharing options...
0 fattipants2016 Posted February 9, 2018 Author Share Posted February 9, 2018 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. Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted February 11, 2018 Share Posted February 11, 2018 I'm going to have to go digging then. I know similar has happened in the past, ... Quote Link to comment Share on other sites More sharing options...
0 fattipants2016 Posted February 11, 2018 Author Share Posted February 11, 2018 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. Quote Link to comment Share on other sites More sharing options...
0 Merwinsson Posted March 8, 2018 Share Posted March 8, 2018 On 2/11/2018 at 1:51 PM, Christopher (Drashna) said: I'm going to have to go digging then. I know similar has happened in the past, ... That would be me. My disks are mounted to folders on the system drive, not to drive letters, and I get device manager errors on all of their removable device entries. I have lots of disks (10) and also lots of already used drive letters. I still have enough drive letters left over to assign to the disks but would prefer to see this fixed in some way. I always have an action center icon with a warning about the errors, so even though the errors seem to be harmless I a constantly wondering whether the action center icon is warning me about this phantom error or whether its something else I need to worry about. Quote Link to comment Share on other sites More sharing options...
Question
fattipants2016
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.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.