Jump to content
Covecube Inc.

All Activity

This stream auto-updates     

  1. Yesterday
  2. I disconnected the drive from my old windows install and am currently mounting it on my new install. Its been 30 minutes so far. It is stored on an unlimited google drive education account and has 32TB of data (roughly).
  3. Last week
  4. thank you for your replies Yeah, that should absolutely work. Some features, such as USN Journaling support are not present on the pool, though. any hint on the matter of making it show results from pool drive ?
  5. Thanks for your response @Christopher (Drashna) Some drives are very close to full, but nothing appears to be completely full. its also only happening to one of the two pools I have setup. See image. If there is anything else I can provide, please let me know. I'm super keen to have this issue resolved.
  6. Chris The disk checks out perfectly in Scanner. The only issue presented was this massively excessive "head parking" which looks like was being caused BY Scanner. All other SMART data is fine and I cannot see any evidence of anything else wrong with it. Regarding the "evacuation" by Drivepool/Scanner - I did have a number of the built in balancers activated for a long time but have since cut it back to just two: Disk Space EQ And StableBit Scanner - with a specific focus on ensuring my "unduplicated" files are being targeted - if there's a problem with a drive. And here are my "balancing" settings: What is most concerning to me is that Scanner is NOT honoring the logic of moving "unduplicated" files away for "possible" problematic drives. In this case - here is the drive that exhibited the excessive head parking (But nothing more) and now Scanner/Drivepool have filled this drive to max with unduped files - leaving me in a nasty state if something does happen here: Ideally - I need to see this drive looking more like the rest of the drives with a balance leaning more to "duplicated" files rather than not duplicated. Any ideas with the balancers or balance settings that might make this even out a bit better. Also - this drive is less than a year old - and while I am certainly not saying that problems are not possible - Scanner is not indicating any issues that are obvious. I have also checked the drive extensively with Seagate tools and nothing negative is coming back from that toolset either. As of right now - this drive appears to be as normal as the other three - except for the ridiculous head parking count - which as of now looks to be driven by Scanner itself. I have another server - running a pair of smaller 2TB Seagate drives (from the same series as the server above)- which have been up and running for a year and 4 months - and each drive has a load cycle count of 109 and 110 respectively. The 4x4TB drives in the server above have been running for just over a year and each drive has load cycle counts in 490000 range. The one drive that Scanner started reporting SMART issues with had a load cycle count of over 600000 before I shut it off. Even Seagate themselves were shocked to see that load cycle number so high - indicating that all of these NAS drives should really never exceed 1000-2000 for the life of the drive. So I am not sure exactly what SCANNER is doing to one set of my drives and not the other - but it's a problem just the same. As I mentioned - my File Server (4x4TB) does not see a lot of action daily and anything it does see should be handled with ease by the OS. It is unfortunate that there is some sort of issue with the Advanced Power Management settings on Scanner for the File Server but even with APM enabled on the other server - there appears to be no issues with the Load Cycle or any other issue. Appreciate any additional tips. Cheers Sonic.
  7. What worked for me was resetting the settings and then never connect it to the cloud.
  8. Thank Drashna & Umfriend. All seems to work well.
  9. Sorry for the delay in getting to you! Could you open a ticket at https://stablebit.com/Contact if you haven't already?
  10. To clarify, you only need a license on the systems that you want full functionality on. If you ONLY want remote access to another system, you don't need a license and you don't even need to activate the trial.
  11. If you have data on Google Drive that you want on the drives, then you'll need to download that data to the drives. And if you're pooling the drives, if you decide you only want one drive, you'd want to remove that disk from the pool. This will move all of the data off of the disk you remove. This will take a while to complete depending on how fast your connection is, how fast data can be downloaded, how large the cache drive is, and how much data is being moved.
  12. Correct. StableBit DrivePool tracks the drive by Volume ID, not by the drive letter. And as long as the NTFS volumes on the disk show up, then StableBit DrivePool will continue to be able to use it. The drive will show up "missing" in this case, and you'll have to remove the missing disk to get the pool to be writable again. Additionally, if you reconnect the disk later, it will re-add the disk to the pool. And shamelessly, if you have StableBit Scanner installed too, if it detects issues, it will cause StableBit DrivePool to evacuate the contents of the disk. The best way is to remove the disk from the pool, using the UI. This will make sure that everything is handled correctly. https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Removing a Drive from the Pool It should, but that's tricky. Both in doing and answering. It *should* be fine, but if not: https://wiki.covecube.com/StableBit_DrivePool_F1655 This works for merging pools, or re-pooling a drive. Duplication settings are stored on the pool itself, so that will go with the pool, no matter what. But the balancing settings are stored on the system locally and cannot be copied over. But, yes, DrivePool will detect the poolpart folders and rebuild the pool with the available disks. Absolutely! We recommend using Disk Management, since it's built in. And the same goes for the pooled drives, too. Yeah, that should absolutely work. Some features, such as USN Journaling support are not present on the pool, though. Not really. Multithreaded copies may benefit, but it's HIGHLY situation. It does have a popup on the first pool creation. But yeah. However implementing it in a safe and non-destructive way isn't easy. But it is something that we may add in the future.
  13. It is. However, you should be able to set the "override" value for "CloudFsDisk_IsDriveRemovable" to "false", and it may fixe the issue. But the drive will no longer be treated as a removable drive. https://wiki.covecube.com/StableBit_CloudDrive_Advanced_Settings
  14. Tweaking the I/O Performance options may help too. https://stablebit.com/Support/CloudDrive/Manual?Section=I/O Performance
  15. So, isn't the HDD supposed to take those clusters out of use if they're bad? Is there a way to tell if it has done that? Another thing that would be cool is if Scanner and Drivepool worked together on these sorts of things, where if Scanner detects a damaged file that has a duplicate, Drivepool will then remove the bad version and replace it with a new duplicate that is based on the duplicate that wasn't corrupted.
  16. Yes, it should. It creates a virtual drive, that the data is stored on, and should work like a normal disk.
  17. Specifically: https://wiki.covecube.com/StableBit_DrivePool_F1655
  18. I'll bring this up. But probably won't happen until after StableBit Cloud has a beta release.
  19. It sounds like Windows Search isn't indexing the drive. You may need to change the configuration for it to properly search the pool. https://www.howtogeek.com/272158/how-to-choose-which-files-windows-search-indexes-on-your-pc/
  20. This is an incorrect assumption, and probably the cause of most misunderstandings. StableBit CloudDrive does not show you what is on the provider. Instead, it creates a virtual drive, breaks that up into blocks/chunks, and then stores those chunks on the provider in question.
  21. Nope, definitely not dead! But if it's urgent, or basically, it's the best way, direct any support queries to https://stablebit.com/Contact
  22. The main reasons that folder would be read only is if the pool has a missing disk, or that there is an issue with the licensing. If neither are the case, let me know.
  23. It sounds like these two issues are unrelated. However, if the disk in question also seems to be causing weird behavior in general, it may be simplest to replace it. As for the evacuation, I'm not sure. It is possible that StableBit Scanner detected unreadable sectors, as that would trigger this behavior. As for the "building bucket lists", this is a pre-execution task for balancing. It can take a while, as it's basically determining where to move all of the files. Also, do you have any balancer plugins installed on the system?
  24. Since I don't see it in any of the images, do you have any disks in the pool that are completely full? If so, this can cause StableBit DrivePool to report that it has no free space, since it actually pulls that information from the underlying disks.
  1. Load more activity


  • Create New...