Jump to content
Covecube Inc.

blueman2

Members
  • Content Count

    41
  • Joined

  • Last visited

  • Days Won

    7

blueman2 last won the day on June 17 2015

blueman2 had the most liked content!

About blueman2

  • Rank
    Advanced Member
  1. Thanks! unchecking all the balancing options, and removing all file placement rules, solved the problem. The issue was, as you said, two conflicting balancers. The scanner balancer was set to move unduplicated files from any 'damaged' drive. All drives show fine, but one does have 8 sectors reallocated. I guess that is enough to mark it 'damaged'? Stablebit scanner says it is fine and no failure predicted, so I am confused. There was another conflicting file placement rule and I guess the 2 balancers fought each other back and forth. I also changed the check boxes on the settings as follows: File Placement Settings: uncheck: File placement fules respect limits...... Checked: Balancing plug-ins respect..... Uncheck: Unless the drive is being emptied. Thanks for the tip!
  2. Well, I have continue to battle some very odd issues with DrivePool after years of a stable experience. It all started when I removed a drive and added a larger replacement. I have a total of 4 drives: 1) SSD OS drive (no change) 2) 2TB drive (no change) 3) 2TB drive (no change) 4) 8TB drive (replaced an older 1.5TB) After replacing the 1.5TB with 8TB, the balancer just went crazy. I has gone through the process of completely emptying the 2TB drives to zero contents, then filling them back up to about 50%, then emptying them again about a dozen times in the past 3 weeks. The balancer never stops. It is ALWAYS processing files in some sort of infinite loop. Here is a screen shot of the main screen. As you can see, it is in the process of emptying the 2TB drives to zero. When it is done, it will then fill them back up once again. Here are my other settings: Any clue as to what the heck is going on??
  3. I have been using DP for many years. Decided to replace a drive recently, and the entire pool just went crazy in terms of where it is putting files!! 1) I set file placement to put certain files (such as VMs) only on my fast drives. It promptly put them all on the very slowest drive that I had explicitly excluded! 2) I set it to never put unduplicated files on the large, slow drive. It promptly started to put all the unduplicated files over on that drive! Here are some screen shots. Starting with VM location, here is what is set: Yet after doing this, all VMs were moved to the 8TB drive that I specifically de-selected. And here is the selection showing to not put unduplicated files on the 8TB drive. Yet, the file is now full of them. I did not change anything. Yet now the balancer is doing the opposite of what it was set for before. I must be doing something really dumb here!
  4. Sorry for letting my frustration come out! Yes, you are right. I did run a file monitor program to see what Drivepool was doing, and it was going one by one checking every file, accessing copies on the disk I was removing and another disk a copy was on. I just did not think about the reason for this until you mention it. I guess it just ensures, one last time, that there really are copies before allowing removal. Good safety check. Happy after the switch though. Everything back to running very smoothly. I love how well thought out DrivePool is in terms of handling removal and addition of drives. Nothing else comes close. Thanks for the great product!!
  5. UPDATE: Well, I just pulled the drive, replaced it with the new drive, rebooted. I had to do a remove of the 'missing' drive afterwards, but it worked just great. So anyone who has a drive that they have allowed only duplicated data on (or have removed non-duplicated data manually) can save themselves an entire day of wasted time by just ignoring the 'remove' command and pull the drive anyway, as if it were a failed drive. Drivepool seems quite smart about how to handle this situation. Just not very smart about knowing what it needs to do if you remove that drive using the remove command! Lesson learned.
  6. 9 hours now. Enough of this crap. I am just puling the drive out. Someday I would love to learn what the heck drivepool thought it was doing for over 9 hours when it needed to do absolutely nothing. .
  7. OK, this is just silly. 7 hours and counting, and there is NOTHING that Drivepool needs to do but just remove the drive. No duplicated files are on it. What the heck does it think it needs over 7 hours to do!!!
  8. I have a 1.5TB drive that I have been using only for duplicated files. Drivepools shows only duplicated files are on it. I plan to replace with a 6TB drive. I selected remove, and duplicate later, but after 6 hours, it is still "in process"! Shouldn't removal be almost instantaneous in this case? It contains no unduplicated files, so what is taking so long? Should I abort and just do a 'dirty' remove?? I am on the latest Beta 2.2.0.651.
  9. I use offsite backup, Crashplan. This is purely for disaster recovery, and I did it mostly for my photos and home videos. Relatively inexpensive and definitely allows me to sleep better.
  10. RFOneWatt, I just have to know. What are you using all that space for?? Video?
  11. blueman2

    Which HDD

    I avoid giving advice based on a small sample size, but of 3 external drives I removed and put in my server, all 3 have failed within 2 years. Not a single failure from my other regular internal drives. Maybe not a statistically valid sample size, but I agree with Drashna on this one.
  12. Just to chime in on my own opinion of which version to use with WHS 2011. I started with V1 and moved to V2. From my perspective, V2 is the right choice. 1) I like the V2 remote view/control scheme much better. The WHS Dashboard is soooo sloooow to load whereas the V2 remote app for DP is super fast. 2) I like being able to place certain files on a specific drive (I put my VM images on a very fast drive, for example) 3) I have yet to see any benefit of the tighter integration from V1 vs V2. So no downside with V2 over V1, and several areas of upside. Frankly, I am surprised to see Covecube still supporting a separate product for WHS. IMHO, V1 is really not needed.
  13. You don't have a button directly below the "Activation ID" box that says "Start 30-day Trial"????
  14. Well, Avast is up to its nastiness again. It killed my ability to run DP on my remote system once again. So I decided to add back the exclusion for the c:\program files\stablebit\drivepool\ directory, turned off Avast while doing a re-install, and turned Avast back on. All is working fine again now. Last time the file was drivepool.comm.dll, but this time it was DrivePool.Service.exe. Oh well, I will just leave the directory excluded for now on. I am running Beta 2.2.0.572_x64 on my client. The server as always is running fine (no Avast there!). No action needed, I just wanted to report in case others get this problem.
×
×
  • Create New...