Arman

Hey, so I just installed the new update that you linked to and zipped up the new logs. I used the Dropbox link in the wiki to submit the logs because they were 10MB and couldn't be attached to the post. Let me know if you got them. Cheers!

Sorry for the delay in this. Was away for the weekend on a business trip and didn't have access to my home computer. I have sent the logs to the Dropbox folder specified in the link you mentioned. I am also attaching them here in case you can't find it. Service.zip

Hmm, I don't see any errors in Scanner nor do I see any SMART problems on any of the drives in the pool. Also, burst testing using Scanner seems to saturate my ports to its max of around 500MB/s on average. There shouldn't be any problems with the SATA controller or cables as I had this issue with my previous motherboard as well (cables were different). Any indication as to what these VDS errors are so maybe I can isolate the cause?

Great. So I assume that this would require me to wait for a new build to be released with the fixes implemented right? In that case, is there anything I can do in the now or nope?

Hey Drashna, Just sent over the logs from the Troubleshooter. Do let me know if there is anything else you need. Thanks!

Hello Drashna, First some backstory and context. I have 4 physical hard drives connected to my onboard SATA ports 1 through 4 (excluding my SSD which is my OS drive on SATA port 0) called: Data 1 Data 2 Data 3 Data 4 These 4 drives are then pooled as such: Data Original (which is comprised of Data 1 and Data 2 drives) Data Duplicated (which is comprised of Data 3 and Data 4 drives) These 2 pools are then further pooled and mounted as my D: drive (this pool is called "Data"). The reason for this structure is because I wanted to control which drives are used for original files and which drives are used in the duplication process so that my backup software doesn't backup the duplicated files because I can specify which volumes to be backed up (I use Veeam Endpoint Backup - now called Veeam Agent for Windows). Moving on, I also have another 3 drives connected via USB which are pooled and mounted as my E: drive (this pool is called "Backup"). In total I have 3 volumes mounted and showing up in Windows - OS (C:), Data (D:), and Backup (E:). Now during the normal Windows startup, my OS and Backup volumes mount instantly, however my Data volume takes around 45 seconds to mount. This causes some issues with programs that rely on that drive to have been mounted during startup. I have notices that the Drivepool service takes the same amount of time as my Data volume being mounted to startup. My question is, what can I do to mount Data as instantly as Backup (which is also a pool) so that programs don't get unhappy when they cannot find paths located on Data? Is there a way to instantly start the service on Windows boot but before Windows login? I have attached my Boot time log if that helps. Some more info about my system: My system is running Windows 10 Pro Creators Update with the latest updates installed. I recently reinstalled Windows and all of my programs due to significant hardware changes. Stablebit Drivepool is on version 2.2.0.877 Beta. I also have Stablebit Scanner version 2.5.2.3129 Beta installed. I do not have CloudDrive installed. My SATA ports are using the Intel chipset. Hopefully that's enough info to help out. Thanks in advance! DrivePool.CoveFs.etl DrivePool.CoveFsDisk.etl

Hey Chris, So I figured out what the issue was a few hours before your reply. It turns out, a SATA port on my controller was busted causing a connectivity issue. Switched ports and things are working well now. I hope you don't mind but I have a question regarding Drivepool now: So I am on the latest beta (746) and am trying out the hierarchical pool support. I have a scenario I am trying and wanted to see if this is correct. So I have 4 drives, each 1TB. I have put Drive 1 & 2 in a pool called Data Original, and Drive 3 & 4 in a pool called Data Duplicated. I then created another pool called Data Combined which is a combination of the two other pools. What I want to do is have Data Original hold all unduplicated files and Data Duplicated holds all duplicated files. Do you think this works if I set the Drive Usage Limiter balancer settings inside the Data Combined pool for Data Original to only unduplicated and for Data Duplicated set it to only duplicated? Also, how does system handle this situation if a hard drive has to be evacuated due to Scanner finding issues?

Here is a video of the scan to explain the problem more clearly: https://gfycat.com/LightheartedComposedJabiru

Hey guys, loving the software so far. Just got some issues that I was hoping to get an answer on. So last night, one of my pools randomly ejected a disk and I thought that maybe something was going wrong with a drive in my pool. So I decided to have scanner re-scan all drives in the pool and it is taking a REALLY LONG TIME to finish the scans. The scan has been running for close to 12 hours on a 1TB drive and it is still at 50% as of writing this post. The issue I am seeing is the scanner seems to be scanning in bursts - reading a few sectors and then stopping for like 5 minutes or so to start the next sector scan. At this rate, my scan will finish by my calculations in 4 months (over exaggeration warning) which is just a little bit too slow for my liking. My USB drives in another pool seem to scan continuously unlike my internal drives (which are the ones being scanned currently). Hope someone can help me resolve why this is happening before my drives die. Thanks! EDIT: So I started scanning another drive in the same pool and it seems like only one drive (the first drive in the pool / the second drive on the controller / drive 1 not drive 0) has this long scanning time issue. Could it be that the drive is failing?