Jump to content
Covecube Inc.


Popular Content

Showing content with the highest reputation since 11/03/20 in all areas

  1. 2 points

    Plugin Source

    I actually wrote a balancing plugin yesterday which is working pretty well now. It took a bit to figure out how to make it do what I want. There's almost no documentation for it, and it doesn't seem very intuitive in many places. So far, I've been "combining" several of the official plugins together to make them actually work together properly. I found the official plugins like to fight each other sometimes. This means I can have SSD drop drives working with equalization and disk usage limitations with no thrashing. Currently this is working, although I ended up re-writing most of the original plugins from scratch anyway simply because they wouldn't combine very well as originally coded. Plus, the disk space equalizer plugin had some bugs in a way which made it easier to rewrite than fix. I wasn't able to combine the scanner plugin - it seems to be obfuscated and baked into the main source, which made it difficult to see what it was doing. Unfortunately, the main thing I wanted to do doesn't seem possible as far as I can tell. I had wanted to have it able to move files based on their creation/modified dates, so that I could keep new/frequently edited files on faster drives and move files that aren't edited often to slower drives. I'm hoping maybe they can make this possible in the future. Another idea I had hoped to do was to create drive "groups" and have it avoid putting duplicate content on the same group. The idea behind that was that drives purchased at the same time are more likely to fail around the same time, so if I avoid putting both duplicated files on those drives, there's less likelihood of losing files in the case of multiple drive failure from the same group of drives. This also doesn't seem possible right now.
  2. 2 points
    After posting, I found an issue I had missed: the disk was marked as Read Only in disk management. After running DISKPART from cmd I managed to remove the read-only tag using the command attributes disk clear readonly and it appears to be OK now.
  3. 1 point

    Upgrading mirrored drives in drivepool

    i would go with option 1 - as you only have two drives with duplication so they are the "same" - does not matter which one you choose - vss will not be copied etc 3 - would work but will be slower than 1 2 - avoid cloning liable to give you problems and yes - shut down any service thats writing to the pool before you start - more for maintaining the best speed internal copy will be approx 1TB per 3 hrs - give or take - remember speed will vary by files size (lots of small files very slow) (large files quick) and where the data is on the disk - i suspect that the new 8TB will be quicker than the 4TB so the speed will depend on the 4TB disk....
  4. 1 point

    Plugin Source

    I'm interested in extending the behavior of the current balancing plugins, but don't want to re-write them from scratch. Is there any chance the current balancing plugins could be made open source to allow the community to contribute and extend them?
  5. 1 point

    Plugin Source

    Currently I think my balancer works better than the official plugins. It offers all the features of all of them, but without any fighting. I also solved all the bugs I'm aware of in the disk space equalizer plugin (there were some corner cases where it balanced incorrectly). I'm working on some issues with the ordered placement portion and then I'll release it.
  6. 1 point

    Windows 10 questions

    Two years ago I tried running DrivePool on Windows 10. Everything seemed ok during the install but I had problems where Windows 7 mediacenter computers had problems opening the movie files. I wasn't sure if the problem was caused by the pair of MediaSonic ProBoxes connected with the Asmedia 106x SATA controller or ethernet driver issues. I just put the Windows 7 OS SSD I put aside back in and continued until now with Win7. I've now upgraded all the mediacenter computers to Windows 10 with Chameleon Media Center. Does anyone have a Drive Pool machine with a pair of ProBoxes/Asmedia 106 running fine in Windows 10? Thanks,
  7. 1 point
    Hi, I bought DrivePool a couple days ago and it was running great for the first day. Since I have been plagued by it working correctly for 1-2 boots, then every boot afterwards takes approximately 10 minutes to load DrivePool upon logging in to Windows 10, I can open it but it said loading with the time taken so far. During this time the drive pools are inaccessible. I have had brief luck in waiting for it to load, then resetting the settings in DrivePool and then... reconfiguring the balancing (SSD Optimisation only). However, this is not an ideal situation. Does anyone have any ideas than may permanently resolve the issue? Thanks in advance.
  8. 1 point

    Considering changing drive letters

    Well, there may be some scenario where drive letters are required. But with 16 HDDs in my pool, I am more than happy to assign names to the HDDs and not have to bother with drive letters. In theory, DrivePool is able to pool many more than 26 HDDs, so you would reach a point where you would run out of drive letters anyway. If you need to assign a drive letter to a DrivePool HDD that has a name only, you can easily do that in Disk Management and it will not affect DrivePool at all. Again, DrivePool does not read the drive letter at all. It only uses the hidden PoolPart directory for identification. As mentioned, you may have to restart your computer if you decide to reassign drive letters to your DrivePool HDDs, not for DrivePool itself, but sometimes other Windows program will not recognize the newly named drive without a restart. IIRC, Disk Management will warn you about that when you change/add/remove a drive letter.
  9. 1 point

    Considering changing drive letters

    I just removed the letters on all 8 pool drives and nothing exploded! Same for SB scanner, business as usual (except for now blank drive letters You now have me interested in leaving them unlettered, but there must be a scenario/usage case where lettered pool drives are desirable. EDIT: Should a need arise, I could always revert to letters, but I'll leave them out for now and see how it goes. Thanks @gtaus
  10. 1 point

    Considering changing drive letters

    Yeah, old habits... When I removed the drive letters and just used drive names, life with DrivePool became easier with my 16 HDDs. It works better for me.
  11. 1 point

    Considering changing drive letters

    This sounds like good news to me I think when I started using drivepool, individual drives were "letter-less" (file explorer would only show pool drives, and non-pooled OS drive also, obviously).. For a specific reason I fail to remember (lets call it old habits), I switched to lettering and never looked back once. Thanks !
  12. 1 point

    Considering changing drive letters

    FWIW, I just removed all drive letters from my DrivePool HDDs. DrivePool does not need a drive letter to recognize a HDD in the pool. It uses the hidden PoolPart directory. Removing drive letters on the HDDs makes a less cluttered display in Windows 10 File Explorer as it will only show HDDs with drive letters. That works great for me as I currently have 16 HDDs in my DrivePool. Those HDDs are dedicated to DrivePool and nothing else. So I don't need any drive letters assigned to them. Of course, when you remove the drive letters, Windows 10 File Explorer can longer "see" the drive normally. You would have to go back into Disk Management and reassign a drive letter. I track all my pool HDDs by name, such as DP01, DP02, DP03, etc.... which also corresponds to the physical location on my rack. I also put the drive name sticker on the physical drive/case for easy identification. The HDDs in my pool do not have drive letters assigned to them, as I stated. The DrivePool UI lists the names all in alphabetic order, which is very nice. However, if for some reason I want to reassign a drive letter to a particular drive, I just use Disk Management and look up the HDD by name. That is much easier then trying to track all the S/N of the HDDs. I am not using Scanner, so I am not sure if that program requires drive letters to work. Is there some reason you need/want to keep any drive letters assigned to your pool HDDs? I found DrivePool was easier to work with when I removed all those drive letters from my pool HDDs. Just my thoughts to your initial question on how to not drive yourself crazy with numerous drives in DrivePool.
  13. 1 point
    Hi gtaus, I can see that your account is following this thread, so hopefully you'll get notified about this response. Maybe check that https://community.covecube.com/index.php?/notifications/options/ is set to your liking?
  14. 1 point
    The drive may have failed. Do you have another computer you could test the drive in? Or if not, could you boot from a Live CD or Live USB to see if it shows up in a different OS?
  15. 1 point
    Hi! I have the same issue, but worse. After this error code I rebooted my PC, and it took about 5 minutes to boot up again, and when it booted I noticed that the drive - that produced the error code when I tried to make new folder - was missing. It isn't shown in file manager and in the disk manager neither. Now I don't know what to do...
  16. 1 point
    Checking, it seems the ST6000DM003 is a SMR drive. I don't recommend putting it in any pool where you want decent rewrite performance, but if you're only wanting good read performance it's fine.
  17. 1 point
    ... Would that 6TB USB HDD happen to be a Seagate Backup Plus Hub by any chance? Because I bought one a ways back (P/N 1XAAP2-501) and it behaves exactly the same way you've described. The drive inside might actually be okay, just with a lemon enclosure. Since yours is out of warranty and you're planning to ditch it, consider instead shucking it and using the HDD as an internal drive (run the Seagate long test on it again of course). BTW just FYI, Seagate has used SMR drives in its Backup Plus Hubs and I don't recommend using SMR drives in a pool, so also check the part number of the drive itself to see if it is one, with (if you don't want to open it up to check) a utility like Crystal Disk Info or similar.
  18. 1 point
    Well, my excellent idea has proven successful, but maybe in an unexpected way. I created a 2nd DrivePool for my non-critical \movie\ data using my suspect 6TB USB HDD. Everything seemed to be working fine as I used Teracopy to move 6TB of \movie\ files to the new DrivePool using the verify command to ensure all files were 100% correct upon transfer. Everything worked fine for a day or two. Thinking I was good to go, I was about to add some more older HDDs to that 2nd DrivePool when, for whatever reason, that 2nd DrivePool went offline and I could not access it (only the suspect 6TB USB HDD on the pool at that time). Fortunately for me, I only had that one suspect 6TB HDD on the 2nd DrivePool at that time, so troubleshooting was fast and easy. Turns out, that suspect 6TB HDD has a tendency to shut itself down, go offline, and then throw the DrivePool into an error state. I was able to unplug the 6TB, plug it back in, and then both the drive and the 2nd DrivePool came back to life. This happened a couple more times yesterday, with that 6TB USB HDD going offline seemingly random, requiring me to unplug it and then plug it back in, so I decided it was just not worth the trouble trying to salvage use out of that 6TB HDD anymore. I am currently in the process of using Teracopy with verify to move all the \movies\ file off that 2nd DrivePool with only the 6TB USB HDD back to my original DrivePool. Turns out that creating a 2nd DrivePool using only that suspect 6TB USB HDD was a good idea because I quickly was able to determine there is indeed something wrong with it (despite all the diagnostic programs that scan it and report it is working fine). The only program that correctly determined the HDD was failing was Seagate Seatools using the long generic test (it passed the short tests). Unfortunately, the HDD is out of warranty so I will have to just eat the loss and move on. But, I would like to shout out to Stablebit Drivepool because, even though that 6TB HDD is failing, my data seems to be recoverable. I am currently about 50% complete on the file transfer off that suspect HDD and all files are intact. I can guarantee you that if that same suspect HDD had gone bad in my MS Windows 10 Storage Spaces setup, using data packets spread all over the pool, it would have most assuredly crashed the entire Storage Space and all my data would have been lost. How do I know that? Because I used Storage Spaces for years and after my 3rd catastrophic loss of data due to a HDD failure, I moved over to Storage Spaces. Despite having 2 and even 3 HDD failure protection on Storage Spaces, I lost entire pools of data when only 1 drive out 20 drives went bad. I guess I can attest to the fact that when a HDD goes bad in DrivePool, I have been able to recover my data off that failing HDD. For my few folder/files that require duplication, I have 2x or 3x duplication set and with DrivePool I don't worry that any 1 drive will crash my entire pool. Thanks to everyone for their responses and helping me work through this issue.
  19. 1 point
    I think a 2nd Pool for non-critical data using old hardware is an excellent idea.
  20. 1 point
    For whatever it's worth, in the past I have encountered problems with "copier" software silently missing files. Admittedly I was dealing with very large file sets, very long paths, and unicode names, all back when a lot of software would have trouble with just one of those let alone all three, and the less-than-reliable hardware I was (ahem) relying on at the time probably didn't help, but the important takeaway is that if you're working with "irreplaceable" data you might want to stress-test your copier and verify that it is actually doing what it says it's doing.
  21. 1 point
    In the File Placement Rules section: your FIRST (uppermost) rule should be that all files matching "\movies\*" are to be placed on all drives INCLUDING that one (check all drives) your LAST (lowermost) rule should be that all files matching "*" are to be placed on all drives EXCLUDING that one (check all the others, leave it unticked, and in your particular case you also want to select "Never allow files to be placed on any other disks" for this rule). Any other rules you might have should be placed ABOVE the LAST rule, and should not have that drive checked (and again, you may wish to select "Never allow..."). This is because FPR checks the rules from uppermost to lowermost until it finds a matching rule for the file being balanced and then uses only that rule. NOTE that File Placement is only performed when balancing is triggered instead of in real time; you might wish to use the SSD Optimizer balancer plugin to mark at least one of the other disks as "SSD" so that new files are never even temporarily placed on the 6TB HDD, which is otherwise possible even if you have "Balance immediately" selected in the Settings tab.
  22. 1 point
    another way would be if you dont need duplication 1 dont add the disk to the pool 2 use backup software - set a job to copy the changed/added files to it - nightly job or similar simpler and you dont have to mess with FPR's that may get complex also you can detach it and move it to another pc without having to remove it from DP as it would throw an error
  23. 1 point
    I have never tried to use File Placement Rules but as I understand it, if you tell DP to place \movies on that 6TB HDD then it will and also spill over to other drives when the 6TB HDD is full. DP will not, I think, through a no space error. Not sure how to ensure that non other data arrives on that drive, that might need a lot of FPRs, but may be easy. Having said that, I would not add a drive I am suspicious about if, unlike me, you do not use duplication. Do you have Scanner? Maybe run the Seagate tool again.
  24. 1 point
    Thank you for posting the solution! Same problem, same fix. I could see this having taken me a LONG time to figure out.
  25. 1 point
    Yuuuuup. This happens from time to time (I've seen it 4-5 times in the last 10 years, including both my systems and other peoples, so exceptionally rare). I'm glad you were able to figure this out, and posted the solution! Hopefully, no more weird stuff for you!


  • Create New...