Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Umfriend

  1. Not sure ppl who emigrated from DP still frequent this forum...
  2. No. DP does not make copies, it manages "duplicates". Delete a file, DP deletes all duplicates. Windows File History should work on a Pool however so if you just use File History on a Pool like you would use it on a drive, then you should have what File History is offering you anyways.
  3. Yeah, so the D drive has files that are on F as well, right? Move everything over from D and you have two copies of the same file on one drive (won't work actually, it'll then overwrite or not move). So this idea leave you with a partial x1 duplication that then DP has to solve for you. How much slower is E:? I would seriously consider just using DP. It is solid SW. Maybe spend a bit of time but avoid headaches?
  4. AFAIK, copying, even cloning does not work. The easiest way is: 1. Install/connect new HDD 2. Add HDD to the Pool 3. And now you can either click on Remove for the 6TB HDD or use Manage Pool -> Balancing -> Balancers -> Drive Usage Limiter -> uncheck Duplicated and Unduplicated -> Save -> Remeasure and Rebalance. 4. Wait. Until. It. Is. Done. (though you can reboot normally if you want/need to and it'll continue after boot. Not entirely sure if you go the Remove route.
  5. AFAIK, but others may confirm, using a 250GB cache drive does indeed not work when writing a 300GB file. I think it is something that Windows/NTFS/DrivePool doesn't know in advance what the file size will be. I would recommend using 2 cache SSDs. However, there is a workaround to use one physical SSD as 2 SSDs for caching purposes. It would involve setting up 2 unduplicated Pools, each using 1/2 of the SSD (which you would have to partition into two volumes, one for each Pool) and then combining the two x1 Pools into one x2 Pool. It has its advantages (e.g., backing up using VSS becomes possible) but you lose a little bit of flexibility/efficiency and run the risk of the SSD actually failing. I have read here though that there is at least one other who does exactly this.
  6. Whether there is a benefit I am not sure about but if you want to disable it, select the disk -> disk settings -> never scan automatically. IIRC.
  7. I wouldn't know but I highly doubt Drivepool pins MFT data and so, even a simply directory listing would require access to the USB drives. I would not want that to change either. In my experience, DP is very fast at dealing with changes to the Pool even when made directly to the underlying disk.
  8. When you are moving files from/to the Pool directly through Explorer (as opposed to the Pool), do you stop the DrivePool service first?
  9. Why not simply power down -> disconnect from sata ports -> connect to SAS? I am assuming it is an HBA in IT-mode. Otherwise, if you must, it is easier to use the Drive Usage Limiter. Uncheck both Duplicated and Unduplicated for the drives you want to empty, then hit rebalance. The big advantage is that no files will be placed on the other HDDs that you want to empty. When using Remove, some of the 1st HDD may be written to the other 3 HDD you want to empty and that is a waste of time.
  10. Yes, that is a tad annoying. I would consider connecting them to another PC (via USB even), then try to salvage what I can over the network. Also, because I'd prefer to run HDD recovery software on a client. How do you know they have been broken for a while and why hasn't Scanner tried to evacuate?
  11. Yes, duplication does not matter, unless, you want to use a backup solution that uses VSS (like Windows Server) or some sort of images and want to avoid backing up both duplicates. But if not, then it does not matter.
  12. I am assuming no duplication, no backups and stable connections to the hard drives. In that case, I would think a single large Pool makes most sense. The reason being that should scanner find an issue and trigger DP to evacuate a drive, you have the best chances the other drives will be able to take on the load. With smaller pools, that is a question for each pool separately. Performance wise? No issue or noticeable difference.
  13. Well, if it is any of those three, I hope he just lost interest...
  14. What have you tried? I note that you now only have other on 2 drives. You could look at the PoolPart.* folder on G:\ with properties through explorer and see if the used space agrres with the none-other data.
  15. I would consider using windirtree to have a look at one such drive and see if the results tally with the DP GUI.
  16. With me, it is typically the trashcan and/or data in those annoying hidden SystemVolumeInformation folders.
  17. I don't really know. I speculate that MB-SATA may not be designed to be optimal. For instance, I do not know whether they can actually deliver 600MBps on all ports simultaneously. I guess it can be found through Yahoo but not sure. PCIe SATA cards, I have read that they can deliver lackluster performance, as in shared bandwidth dependent on the actual number of PCIe lanes it uses, but never that they'd interfere with MB-Sata. Again, I don't actually know and I am sure that there may be different qualities out there. But really, I think your PCIe SATA card will be fine and give no issues. It should work for your transition. I'd leave the card in the PC once done so that, AIW you need it, you have two ports readily available. The SAS HBA route is one I would recommend if you expect storage to grow as measured by number of drives. For me, it works like a charm and as these are, AFAIK, all made with enterprise servers in mind, I am pretty comfortable about performance, compatability and endurance.
  18. I am sure it is possible to do it that way but it is, IMHO, messy and prone to issues. If you physically remove a drive, the Pool would become read only and I am not sure you could add another drive and then transfer, even if you did it outside of DrivePool. I would certainly recommend going the PCI SATA card (or better yet, install a SAS HBA like an IBM M1015/Dell Perc H310 and enjoy an abundance of SATA ports) route. Personally, I always ensure I have at least one SATA port available for upgrading/troubleshooting. Having said this, for this upgrade, you could also use a USB3 drive adapter (although I do not recommend USB for long time use).
  19. https://wiki.covecube.com/StableBit_DrivePool_Q4142489 Mind you, USB connections may drop once in a while. You won't lose any data normally but the Pool will become read-only until the connection is restored or the drive is removed from the Pool.
  20. Umfriend

    Drive missing

    Let me guess, Chia? AFAIK, USB may drop connection occasionally and DP will put a Pool in read-only mode while a disk is missing until it gets connected or you remove it from the Pool. Search this forum, there are posts about disk connected through USB.
  21. OK. That you have multiple PoolPart.* folders on H and K is a clear issue. That you don;t have them on P and M is weird. And then there are the PoolPart/* files which shouldn't be there. Not sure what to do here. Tranferring files, removing drives from Pool through GUI, reformat and add is a possibility but takes a long time. Perhaps better to contact support (https://stablebit.com/Support) or wait for a better volunteer here. Another scenario, but I am not sure if that would work well, is: 1. Remove the suspect drives from the Pool throuh the GUI 2. From each PoolPart.* folder on those drives, check whether they have any contents. If they don't, delete them. If they do, rename the folders. 3. Add the drives to the Pool 4. You will now see a new PoolPart.* folder. For each of the for drives, move the contents from the renamed PoolPart.* folder(s) to the new PoolPart.* folder according to this: StableBit DrivePool Q4142489 (Follow this well, you will need to stop the DrivePoolService and start it when done) 5. Do a re-measure I *think* this will work but....
  22. If you haven't yet, a reboot never hurts. And then, try and determine if you have two hidden PoolPart.* folders on a single drive (like P:/ for instance) and whether you can open a file directly from within such PoolPart.* folder. Once we know that we can go from there.
  23. First, DON'T PANIC! 99% sure it'll be just fine. I don't know what the problem is. I wonder whether you may have run into some issue with security rights to the files. That is why I want you to open a file on a suspect disk directly and not through the Pool. DrivePool stores all files in a hidden folder, that you can tell explorer to show regardless, and in plain NTFS format. It may be that you have two PoolPart.* folders on in the root on a disk as well. So don't panic, just gather facts & symptoms first. BTW, I am not support, if we (there are others who regularly help here as well) don't succeed, you can raise a ticket for real support. Oh, one other thing, in DP, can you do Manage Pool -> Re-measure?
  24. Don't start every sentence on a new line, it makes it harder to read & navigate :D. Can you access the data directly? I mean, go to P:\, then explore the hidden Poolpart.* folder and below, open a file from it that way?
  25. Yeah, although I primarily use DP for redundancy/uptime of my SOHO server. I just had some disks doing nothing that I put in, never bought anything for Chia.
  • Create New...