Jump to content
Covecube Inc.

Umfriend

Members
  • Content Count

    930
  • Joined

  • Last visited

  • Days Won

    48

Everything posted by Umfriend

  1. In RAID might work. Just adding a few drives as SSD Cache may run into the same problem I fear. Also, one SSD, even if it is SATA, will outperform 4 HDDs I think. I am assuming you don't have actual SAS-drives. Depending on the actual chipset, two RAIDed SSDs might do the job fully.
  2. Assuming there is no duplication, wouldn't a single 2TB SSD suffice as a cache? Way simpler for a somewhat specific use case IMHO.
  3. Actually, if you have duplication then this procedure is, IMHO, incomplete. When you move files out of the poolpart.* folder, DP may remeasure and suddenly find duplicates are missing and re-duplicate. If you have duplication, you can just power off the machine, physically remove the drive, reboot and then remove the missing/faulty drive from the Pool through the GUI. Remeasure/re-duplicate and it is done. If you do not have duplication, then I would attach the new drive, stop the drivepool service (so DP will not interfere), copy the data from the faulty HDD poolpart.* folder to th
  4. I read this is as asking how to identify the actual physical drives in the case. I physically label my drives and stack them in the server according to their labels. Without something like that, I have no clue how you would be able to identify the physical drives...
  5. Moving data to the Pool while retaining the data on the same drive is called seeding and it is advised to stop the service first (https://wiki.covecube.com/StableBit_DrivePool_Q4142489). I think this is because otherwise DP might start balancing while you are in the process of moving drive-by-drive. I am not sure but I would think you would first set settings, then do the seeding. (I am pretty sure that) DP does not "index" the files. Whenever you query a folder DP will on the spot read the drives and indeed show the "sum". Duplicate filenames will be an issue I think. I think that D
  6. Yes, DP does not need nor use drive letters for the underlying drives.
  7. Do you have this option checked in Scanner: Settings -> Advanced Settings and Troubleshooting -> Advanced Settings -> DirectoIO -> Unsafe check.
  8. I had DP running on a Celeron 430 or somesuch, 8GB without any issues. DP is rather lean and simply does not need much.
  9. If you are comparing single SSD vs a Pool of spinners, then yeah, the SSD will load way faster. However, if you compare a single HDD vs a Pool of spinners then the difference should be negligible (or perhaps sometimes a bit better but I have hardly ever seen that happening).
  10. And here I was thinking HBA==IT.... Turns out I was wrong.
  11. So I don;t really know. I have a SAS HBA, an IBM1015 butcalled Dell H310 or somesuch. I never understood the LSI chip/card numbering. In any case, I did have to get the latest bios for my card, P20* or something. Also, with Scanner, I had to Settings -> Advanced Settings and Troubleshooting -> Advanced Settings -> DirectoIO -> Unsafe check. Never had an issue with that and SMART is read. I would try the Scanner setting first, reboot and see how it goes.
  12. Not a dev either. Another problem might be that once one starts writing a file, it may not be yet known how large that file will be. Sure, a simple copy should not have that issue but what if you save a stream of as yet unknown length? Writing to the disk with most space free seems to be the safest option (and personally, I like safe). Also, I find it hard to think of a scenario where a subsequent reshuffle of files would measurably impact performance.
  13. That's why I'm asking for the exact model.
  14. Yes, you can simply uninstall. no files will be lost. Unless you do something weird.
  15. So many have no such issues at all. Could it be there is something somewhat specific to your situation is going on? Some here will be trying to help but it helps if you provide a bit of sensible information. So, again, have you checked Event Viewer (for IDE/ATAPI/DISK errors specifically but any other errors might be relevant) and what model HDD s this exactly? Also, can you try to copy some represntative files to that drive F:\ instead of to the Pool?
  16. Have you checked Event Viewer and what model is thus exactly? And if the data you want in the Pool is already on the disks you want to add to the Pool, then there is a much faster way of getting them in the Pool.
  17. Adding a drive does not mean that you can not store data outside of the Pool on that drive. The Pool data is located in a hidden folder (PoolPart.*). I think you want to move the data outside of the Pool on that drive into the Pool. This is called seeding and how to do it is described here: https://wiki.covecube.com/StableBit_DrivePool_Q4142489
  18. I know there is an SSD Optimzier plugin but AFAIK it only serves as a write cache, you can't dictate which files should be on the SSDs for fast reads. There are also File Placement Rules where you can map certain folders to specific SSD/HDDs but there I don't think you can use a single SSD for both functions (not sure, maybe you can).
  19. Remeasuring just checks whether the duplication that is actually there agrees with your settings. So if you have no duplication as setting but some files are duplicated, DP will correct that too.
  20. 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.
  21. 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.
  22. 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
  23. Why not use the 30-day trial period so that you have time working thus out with support?
  24. 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.
×
×
  • Create New...