Jump to content
Covecube Inc.

Arman

Members
  • Content Count

    9
  • Joined

  • Last visited

  1. 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!
  2. 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
  3. 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?
  4. 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?
  5. Hey Drashna, Just sent over the logs from the Troubleshooter. Do let me know if there is anything else you need. Thanks!
  6. 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 driv
  7. 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 a
  8. Here is a video of the scan to explain the problem more clearly: https://gfycat.com/LightheartedComposedJabiru
  9. 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 s
×
×
  • Create New...