lava890

I’ve had this happen twice in the past couple years so I’d like to see what I can do differently: I have a pool on Windows 10 with about 10 drives. I have folder duplication enabled for several folders. I had a power failure, and it seems one of my 10tb drives got corrupted. When I started the server again, the drive was missing from the pool and was listed as an unpooled drive. There were no folders or files showing up in file explorer, however in drivepool it said that the 8tb that was previously being used by drivepool was “other” and not usable. In file explorer, the space was unavailable as well. I ran chckdsk /r for 15 hours and it found no problems. Scanner found no problems either. I think that file system corruption has occurred but there were no "found.###" folders. All of the files that were on that drive (duplicated or not) are missing from my pool. How can I prevent this from happening in the future? It seems like drivepool treats the duplicated files as though they were purposely deleted instead of making the pool “read only” until the missing drive is replaced or the duplicated files can be duplicated again. As a side note, i have a cloud backup of the files and do not have to recover them.

It was sporadic, so it would have to be logging for several days to probably catch the problem, and it was pretty disruptive so I'd rather not turn the read striping back on since it's been working well now since July 30.

Hope it works

That’s possible, but I didn’t try read-striping with Defender turned off, so I can’t say it’s that combo and not some other aspect of my configuration. Either way, it caused me 2 years of frustration, but finally it’s solved!

I have had zero issues since I turned off read striping in July. Everything works fine with just the windows antivirus running. It seems related just related to the read striping for me.

When I turned off read striping, it solved the problem. I just use the windows antivirus which you can’t really shut off permanently.

Ok, thanks for responding. I’ll experiment a bit more before I give up on drivepool. I think it worked flawlessly until I added the SSDs a couple years ago.

Did you ever figure this out? I’m having the same problem. Was it the SSD optimizer, read striping, the cables, bypass system filters, real time duplication, or something else? I’ve set pretty much everything to default, and I’m trying one by one to see what’s doing it, but it is sporadic so it’s tough.

Thanks!

I'm using a Mini PC/NUC (Beebox-S 7200U) as my Plex server with two external USB 3.0 hard drives in my Drivepool, and it has worked perfectly for the past year. I need more space, so now I'm looking at purchasing a 4 or 8 bay hard drive enclosure. I've read in this forum in posts from a few years ago that there are inherent issues with USB connections to these enclosures, and it's better to use eSATA. Does anyone know if the same USB issues are present with USB 3.1 Gen2 (Type C)? It's my only other connection type on this NUC. If so, and I have to re-purpose an old PC instead of using my NUC, is there a better connection type now instead of eSATA? I've read more recently that eSATA cards are having issues in newer Windows OS's. Thanks.

I was having the same problem with a new 8TB WD My Book, found this post, and this seems to have fixed it.