Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Umfriend

  1. Don't panic. If the drives do not show up in BIOS, chances are you made some sort of silly mistake that will be easily correctable. Just take the drives out, connect just one and see if you can get that one recognised. If that works, try it on a different port and with a different power cable. Add on drives as you go. I had a PSU with detachable cables. None of my HDDs worked. Turned out cables were not connected to PSU. A brief scare for a few minutes but only something silly. Probably something like that with you.
  2. I don't have enough info to try to diagnose this but remeasuring seems like a sensible thing to do. Screenprints illustrating what you say is the case help.
  3. Have you tried reading https://stablebit.com/? Anyway, DP combines volumes into a large NTFS volume. It can have redundancy if you want. Either for the entire "Pool" or just certain folders therein. If one drive fails, the most you can lose is the data on that one drive. The data on the other drives will still be available. If all was redundant (we call that x2 duplication) then the Pool will reduplicate the lost files, provided you have enough space. Each drive you add to the Pool is not exclusively for the Pool. It will create a hidden PoolPart.* folder within which the Pooled file
  4. Why not use the 30-day trial period so that you have time working thus out with support?
  5. What you can do is deactivate the license on the old machine, build/install the new one and active the license there. Write down or somehow copy the license key. Deactivating the key will not delete any files in the Pool. I think the Pool remains accessible just read-only perhaps.
  6. What I think I know and would do is : Yes, you can use the C:\ drive as part of the Pool. The OS itself won;t be in the Pool but part of the Pool will be written to the hidden Poolpart.* folder that will be placed on the C drive. Personally, I would consider doing it with a separate partition as it makes it easier to backup/restore/reinstall the OS itself. It is in fact possible to use one SSD with x2 duplication (even though I consider it a bug and would not do it). You would have to split the x2 Pool first into two x1 Pools and then create a Hierarchical Pool consisting of the x1 Pools
  7. This is what you are looking for: https://www.google.com/url?q=https://wiki.covecube.com/StableBit_DrivePool_Q4142489&sa=U&ved=2ahUKEwjwmvXEvNXqAhWQ2aQKHW54CW8QFjAAegQICBAB&usg=AOvVaw2GKZPsTgAT1LC_a4XMvhJB
  8. Yes, drives larger than 2TB are not supported by MBR. So you had to convert to GPT if they were MBR. That did not increase space, it just allowed to access the entire drive. You already have access to your entire 16TB drive.
  9. I think you may want to read up on TB vs TiB...
  10. How did you get it in? Some here use DP together with 3rd party parity software, I believe SnapRaid is most popular. Perhaps that would work for you but I would not be able to advise on how to do that.
  11. That ain't easy. Best thing for you, IMHO, is to have two Pools, one for the old drives and one for the new. Then copy from old Pool to new. Power off machine and disconnect all old drives. I realise this is different from what I suggested before but at that time I was not aware you wanted to have the old drives as sort of a backup. Also, this way the usefullness of the old drives as a backup will fade over time, I would expect, as it does not track changes/new files.
  12. Yep, another 30TB would be needed. No parity.
  13. You can also use placement limiters I think. Never tried it myself. The advantage would be that when you remove a drive, the files won't be placed on other drives that you would remove thereafter. Requires rebalancing I would think.
  14. Use DP. Add as many HDD as you can. Remove one by one. You can do more at one time but it is a serial process anyway.
  15. Well what do you know, sry, I may well have been wrong. Amazing (not me being wrong, Seagate not marketing this explicitly). You could go for the IronWolf series.
  16. With future products I would say the expectation is they will be there at some point. It is not that hard to find non-Helium drives as all helium drives I've seen explicitly advertise this. So if it is not stated then it is not Helium. Also, typically, if you can afford it, it is not a Helium-filled drive.
  17. If you use x2 duplication and want to use the SSD Optimizer plug-in, you'll need two SSDs (or play around with hierarchical Pools, then you can do it with one SSD (or at least that has been written here, I actually consider that a bug and maybe it is "solved" but I could tell you how to do it.)). And yes, I imagine that if you do it will make a difference when you upload that much provided that there is no other bottleneck (1Gb Lan for instance). On Clouddrive as a backup: No idea.
  18. So I think it is a matter of use case and personal taste. IMHO, just use one Pool. If you're going to replace the 5900rpm drives anyway over time anyway. I assume you run things over a network. As most are still running over 1Gbit networks (or slower), even the 5900rpm drives won't slow you down. I've never used an SSD Optimizer plugin but yeah, it is helpful for writing, not reading (except for the off-chance that the file you read is still on the SSD). But even then it would need a datapath that is faster than 1Gbit all the way. What you could do is test a little by writing to the
  19. Umfriend

    deleted disk

    Did you have duplication set (ot better, a real backup)? If not, I guess you need to look for some file recovery software. Don't do anything else with that drive. You might try https://www.easeus.com/datarecoverywizard/recover-formatted-partition.htm for instance. I have no experience with such issues.
  20. I didn't want to react at first but snapdragon is right. No one in their right mind combines crucial functionality and beta testing. It is crucial to separate the two. The demand that they work to circumvent "any future issues" is simply ridiculous.
  21. A bit by accident as I did not really expect that simple thing to make such a difference. Anyway, you are welcome. What you say about the "Other", yeah, that is part of it. Donnow whether it can lead to more serious consequences but stopping the DP Service when you want to do your own file tranfers is best practice. Now to nitpick, SnapRAID is not a backup. Sure, it may save you from HDD failure to some extent but not against accidental deletions, theft, fire, simultaneous multiple HDD failure (and you got a few). If you value your data, you might consider a real solution. You wouldn
  22. BTW, if you move files among pooled-drives, I think it is strongly advised to stop the DrivePool Service (and restart it or reboot when done). Also, I realise it is painfully slow for you (and I have no clue as to what would be the cause of that) but in my experience, DP is really a fire-and-forget program. I wouldn't care if it took a month so to say, it works just fine while it is balancing.
  • Create New...