Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Can we get more info on when these messages pop up?
  3. Yes, if you click Remove on the dying drive then it will automatically move everything (in the pool) that's on that drive to the other drives (in the pool). You may or may not wish to choose the option of "Force damaged drive removal (unreadable files will be left on the disk)." This will help if the drive has damaged files that can't be read. However, since you are using SnapRaid, you should instead be incorporating its instructions to safely transfer the files without messing up your parity (Disclaimer: I'm not great with SnapRaid, please double-check this): (turn off DrivePool balancing/placement if you're using it - which you probably aren't using if you're using SnapRaid) (stop DrivePool service) copy files from good Drive2 to good Drive3 check with diff, if good (identified as copies) proceed with a sync and continue to next step delete files on good Drive2 run a sync copy files from failing Drive1 to good Drive2 check with diff, if good (identified as copies) proceed with a sync and continue to next step delete files on failing Drive1 run a sync might as well take the failing Drive1 out of the machine at this point - run a secure erase on it if you need/want to - but remember to follow the SnapRaid procedure for removing a data disk from the array (start DrivePool service) (remove the "missing" Drive1) (might need to do a Manage Pool -> Re-measure if DrivePool doesn't do it automatically) (turn on DrivePool balancing/placement if you're using it - which you probably aren't using if you're using SnapRaid) You can still use Remove on a drive containing unduplicated files; it will still move them to another drive. DrivePool duplication, if enabled, is like RAID1 in that it ensures that duplicated files exist on two or more drives (so that if one drive dies unexpectedly you haven't lost any of the duplicated files that were on it as they will also be on at least one other drive). 2x duplication does use 2x the space of course, and so on. You can turn it on for the entire pool or customise it for specific folders.
  4. Yesterday
  5. Thanks or your help. So just to clarify, if I click remove on the dying drive, it will automatically move everything from that drive to the others ? I know it gives some options of what to do when clicking remove, anything specific I need to select if I just want to move all data off to another drive in the pool ? You mention duplication, my failing drive shows up as 2.63tb out of 2.76tb unduplicated, what does this actually mean and would this then mean I can't use the remove function and will have to manually copy the files ? As you say, I won't move, but copy. Does duplication mean like a RAID so everything copied is duplicated ? Thanks.
  6. If the drive's failing but stiil currently readable, then you could just tell DrivePool to Remove it and it will evacuate the data file by file to the rest of the drives in your pool (usually the one(s) with the most free space). If you're wanting to manually move the content as you describe (e.g. because you're using SnapRaid or because you want it done ASAP and don't have duplication), then as long as you turn off any Balancing and Placement, and stop the StableBit DrivePool service you can safely move* content between the poolparts so long as the internal structure is kept the same (e.g. don't change "pathX\fileY" in "Drive1:\PoolPart1342343\pathX\fileY" to "Drive2:\PoolPart324343\pathX\fileY"). Once you're done you can then restart the service, Remove the drive you manually emptied, and then turn back on any Balancing and Placement. *Note: for a failing disk with no duplication, instead of doing a "direct" move, I would copy the content to the destination and verify the copies before I deleted any content from the source. This minimises writes to the suspect disk while I'm getting data from it. "Also, the drives are SnapRaided, would it be safer to copy everything off and hope everything is in tact data wise, or restore from the parity drive ?" See the SnapRaid FAQ for the "100% safe way to proceed": https://www.snapraid.it/faq#move
  7. If you are looking for a list of forum admins, then from the community.covecobe.com main page click Browse -> Staff. Alex and Christopher are the StableBit staff/admins, while Shane (myself) and saitoh183 are volunteer moderators. You can message any of them from the above page. I'd suggest Christopher first for general official responses/statements, myself if you just want some help re something on the forum? You can also contact StableBit re product sales/issues/feedback/development or the like via the Contact form.
  8. As the old thread explains, DrivePool uses *.copytemp files in the process of balancing/duplicating files; if DrivePool is interrupted (e.g. power outage) during balancing/duplicating then both the original file and the temporary file.copytemp will remain. You can thus safely delete any *.copytemp files without losing data if DrivePool is not currently balancing or duplicating when you do so, and doing so will free up space occupied by the pool. (technically, a copytemp file from a previous balancing/duplication would be safe to delete during a current one, but as there's no easy way to distinguish between such it is best to wait until the current one completes)
  9. Yes my apologies you are correct Shane. Sorry for the misquoting of the error. I have done as you suggested and overrode the SSD optimizer. It has removed the error and is working as expected. I appreciate your help with this Shane.
  10. Last week
  11. So, one of my 3TB drives from my 53TB pool is failing (showing flashing red X on HDD Sentinel), I have a lot of unused space on the pool, approx 11TB. So I have a few drives in the pool with only a few GB on. Instead of buying a new 3TB drive is there any way for me to move off the data off a little used drive in my pool, and then also move across all the 3TB of data from the failing drive on to that drive ? What actually happens if I manually move data in the hidden pool folder to another pool folder on another drive ? Any suggestions on how best to do this ? Here is an example of what I mean (poolpart numbers are random, not real)......... Drive1 = PoolPart1342343 - Failing 3TB drive, it is 2.62TB used. Drive2 = PoolPart324343 - 4TB drive only has 100gb on. Drive3 = PoolPart4534534 - 4TB drive, plenty of space on So if I were to copy the 100gb from Drive2 to Drive3, leaving Drive2 empty, and then copy all of Drive1 on to Drive2. If so what is the safest method to do this ? Would it automatically keep everything in order ? Also, the drives are SnapRaided, would it be safer to copy everything off and hope everything is in tact data wise, or restore from the parity drive ? Thanks !!
  12. I have been using DrivePool for a while and love it. I currently have three *.copytemp files on my pool, taking up about 2TB of space. I found this, which is helpful. but I was wondering what the files contain and whether any data would be lost upon their deletion. My pool is still currently duplicating, but these files have been around since the beginning of February this year. Will they disappear when the pool is fully duplicated, and presuambly the available space in my pool is going to reduce by 2TB?
  13. The error message is not "there isn't enough space". The error message is "Make sure that you have enough disk space in order to satisfy your file placements rules and that they're not conflicting with other balancing settings" (emphasis mine). So since you have plenty of free space the problem is likely to be a conflict with other balancing settings, and in this case I suspect the SSD Optimizer. If you don't mind your File Placement rule over-riding the SSD Optimizer, try UN-ticking "File placement rules respect real-time file placement limits set by the balancing plug-ins." Edit: P.S. I would also not recommend a file placement rule that says to keep files on the same disk(s) that your SSD Optimizer has marked as "SSD" as the former would conflict with the latter wanting to empty files from there.
  14. I guess I am not understanding why it is allowing the files to be placed on only one specific archive disk and not the others with the error message"there isn't enough space". As you can see there is plenty of room for 24gb of data on any of my archive disks. There is only one specific folder I have in file placement settings to follow a rule.
  15. It might be a conflict between the file placement rules and the SSD Optimizer, as both do real-time placement. You may need to experiment with what you have (un)ticked in the File placement settings. Another option would be to have sub-pools for your cache disks and archive disks, so that you can have the file placement rules only apply to files as they move onto the archive disks.
  16. So if I move it to any other disk than my cache ssd which is disk 12 it gives me the same error that there is not enough room. So I am not sure where the conflict is coming from as there is plenty of room on all disks. Besides the three balancers that I have in the screenshot there is nothing else applied to the pool.
  17. I did open a support ticket. Drashna suggested the drivepool troubleshooter and reset drivepool to defaults. I also marked the nvme boot drive dirty and rebooted. After that, Disk Manager showed all three disks correctly, but DrivePool showed one pool disk as a non-pooled disk. DrivePool eventually finished duplication this morning, and I started re-enabling services after removing and making a new L2 cache. It's working now as a 2-disk pool. I'm going to wait until BackBlaze is finished before doing anything else with DrivePool, but may re-add the excluded disk when it's done. At least I have the pulled WD80EFZZ drives if I need to replicate everything before burning the homeserver down and starting over....
  18. That setting was already enabled. Sorry I didn't include that in the original post. There is no duplication enabled either.
  19. You may need to tick "Balancing plug-ins respect file placement rules" in the Balancing Settings section. If you have duplication enabled, you will need to select the appropriate number of disks for a file placement rule (e.g. 2x duplication -> two disks).
  20. If they're offline due to collision that suggests that somehow they've ended up with the same "unique" disk ID (a serial number assigned to a drive when initialised by Windows). Normally such collisions only happen when cloning a disk. ( @Christopher (Drashna) I can't imagine DrivePool having any need to change a physical disk's ID - any ideas what could cause this? Windows? ) You can use the Windows Disk Management utility and the DISKPART tool from an Administrator command prompt to view the ID. Find the disk numbers in the former, then use SELECT DISK number followed by UNIQUEID DISK in the latter, to select each disk in the pool in turn and view their IDs. They should be in the form of a long dash-separated hexadecimal string. The pool itself uses an eight character hex string. If you find two of your disks in the pool have the same ID, you can change one of them via selecting it (as above) and using UNIQUEID DISK ID=newstring command where newstring is a string chosen by you in the same format (e.g. just use the same string but change one of the characters); restart the computer afterwards. Be very careful here that you change only the ID of the particular disk you want. If you don't find two disks with the same ID then I would recommend opening a support ticket with StableBit. Regardless, your data should still be intact in the hidden poolpart folders on each disk and could be moved to a new pool if the old one can't be restored.
  21. I recently started using the file placement feature. I thought I had it configured correctly but looking into it seems not so much. Wondering if anyone can help me understand what might be going on with my setup. I have attached the screenshots of the file placement section and the error I am receiving along with the enabled balancers.
  22. My DrivePool was: 1x DC520 12TB 2x WD80EFBX 8TB (0BUK and MIEG) 1x WD80EFZZ 8TB (HDRK) One disk (HDRK) was slower than the others and I wanted to repurpose it in another machine, so last night I removed it from the pool. This should have left me a pool consisting of the two WD80EFBX and the DC520. It didn't turn out that way this morning.... This morning I verified there was no disk activity, and DrivePool showed the old disk (HDRK) was available to add, so I shut down and removed the old disk. Boot back up and now DrivePool is complaining that a disk (0BUK) that hasn't been removed is missing. Funny thing is, it shows said disk TWICE, but only one instance of it as missing. Another disk (MIEG) which is part of this same pool, is still installed, but DrivePool doesn't show it at all, and doesn't appear to be complaining that it's missing. It also doesn't show it as available to add to the pool. In Windows the disk is shown as offline due to collision. Minus what's been backed up in the last week, this pool houses all of my data. Right now, Windows and DrivePool only correctly identify ONE of my three pool disks, with the other two apparently identified as the same disk. How do I proceed?
  23. So i know that Drive pool has no official support for WSL2. I also know that we have in place some kind of hack solution that offers partial support but it is not a listed feature because that would be way too complicated. I have it currently working with wsl2 via docker volumes. I've tried both linking directly to the pool by drive letter and now i am trying cifs. The problem I'm running into is that my pc periodically freezes and will not crash or recover, happens about once a day. I cant say for sure it is drive pool, but it does seem to happen right after a drive is accessed. The system has crashed now over both types of docker volumes. Is the non-support of WSL2 circumventable by having the drivepool hosted on a completely different system and having my WSL2 interface only with drivepool via SMB/cifs? I feel like that abstraction layer should offer some protection but i don't know enough about how these things work under the hood to say for sure. I've been dealing with these freezes for months and I could really use some help in figuring out what the source is if it is even drivepool. EDIT: Uploaded a screenshot of event viewer. This is the only thing i really have to go off of and it seems to point to either a storage issue or a network issue(NDIS). I always see these errors minutes before a crash, but also when there is no crash for what it's worth.
  24. Earlier
  25. I really like this feature. Thanks for having it. It was useful for me because ... Spent a couple of days intermittently wondering why a pool wouldn't come back properly. Remeasuring is just taking forever (days!) but hd-sentinel shows drives all healthy. Accessing drives individually was fast-ish. Couldn't tell whether any lag I experienced was because of it being bogged down by remeasure or if it's really slow. I even have new hard drive enclosures in my cart ready for a purchase! Finally, came across this thread and decided to eject a member (had my suspicions) and the pool is blazing (albeit missing the files of this drive of course)! But, in my situation, a semi working pool is better than a non working pool. Now I can work on this bad drive separately. i.e. scandisk, recovering files, whatever. In hindsight, I suppose I could've physically ejected it, but this gives a nice flexible troubleshooting technique for these half broken mysterious sort of , but not really broken drives I guess.
  26. Wow! Thank you so much! You answered all my questions. I will get their software and try them out. Best regards,
  27. Unfortunately, I had tried this, but it did not work. I don't know what criteria it uses to determine that the balance is not 100%. Let's say that it looks at tenths of a percentage. The problem is that my files are so small, that it sees the balance as still being 100%. I feel like a little explanation is in order here. My tool pool is rather large, I believe it is currently on the order of 36TB. I use that size because I do in fact have a lot of very large files. However, I do a lot of work with very small batch files and documents. Some of these can very small, on the order of a few KB, but nonetheless they are the result of a lot of intensive research and testing, so I want these files on the array, and I want them protected. Likewise, I generate a lot of documentation in Word. These documents start life as a group of individual small docs that will eventually be combined into a larger document. But even an 80-page document many only be a couple of MB. However, in the meantime, they are very small. Let's make the assumption that the balancing sees an out of balance condition at 99.9% (this is just a guess on my part). That would mean that 0.1% would still be equivalent to 3.6GB that would have to change. At that point I could manually set the threshold to 1GB instead, but you can fit a whole lot of Word docs and batch files into 1GB. I should note at this point that I have raised this issue with support, and they are kindly looking into the matter with development. But I sincerely appreciate your response.
  1. Load more activity
×
×
  • Create New...