Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 02/19/24 in all areas

  1. Folks, thank all for the ideas. I am not neglecting them but I have some health issues that make it very hard for me to do much of anything for a while. I will try the more promising ones as my health permits but it will take some time. From operation and the lack of errors during writing/reading it seems that I am in no danger except duplication won't work. I can live with that for a while. Keep the ideas coming and, maybe, I can get this mess fixed and report back which tools worked for me. I am making one pass through my pool where I remove a drive from the pool, run full diagnosis and file system diagnosis on that drive then I re-add it back to the pool. When completed that will assure that there are no underlying drive problems and I can proceed from there. Thanks to all who tried to help this old man.
    1 point
  2. Google Drive support is being discontinued in StableBit CloudDrive. Please make sure to back up all of your data on any existing Google Drive cloud drives to a different location as soon as possible. Google Drive cloud drives will not be accessible after May 15, 2024. FAQ Q: What does this mean? Do I have to do anything with the data on my existing cloud drives that are using the Google Drive storage provider? A: Yes, you do need to take action in order to continue to have access to your data stored on Google Drive. You need to make a copy of all of the data on your Google Drive cloud drives to another location by May 15, 2024. Q: What happens after Google Drive support is discontinued in StableBit CloudDrive? What happens to any data that is still remaining on my drives? A: Your Google Drive based cloud drives will become inaccessible after May 15, 2024. Therefore, any data on those drives will also be inaccessible. It will technically not be deleted, as it will still continue to be stored on Google Drive. But because StableBit CloudDrive will not have access to it, you will not be able to mount your drives using the app. Q: Is there any way to continue using Google Drive with StableBit CloudDrive after the discontinue date? A: You can, in theory, specify your own API keys in our ProviderSettings.json file and continue to use the provider beyond the discontinue date, but this is not recommended for a few reasons: Google Drive is being discontinued because of reliability issues with the service. Continuing to use it puts your data at risk, and is therefore not recommended. We will not be actively updating the Google Drive storage provider in order to keep it compatible with any changes Google makes to their APIs in the future. Therefore, you may lose access to the drive because of some future breaking change that Google makes. Q: What happens if I don't backup my data in time? Is there any way to access it after the discontinue date? A: Yes. It's possible to download your entire CloudPart folder from Google Drive. The CloudPart folder represents all of your cloud drive data. You can then run our conversion tool to convert this data to a format that you can mount locally using the Local Disk storage provider. The conversion tool is located here: C:\Program Files\StableBit\CloudDrive\Tools\Convert\CloudDrive.Convert.exe The steps to do this would be: Log in to your Google Drive web interface ( https://drive.google.com/ ). Find the CloudPart... folder that you would like to recover under the root "StableBit CloudDrive" folder. Each CloudPart folder represents a cloud drive, identified by a unique number (UID). Download the entire CloudPart folder (from the Google Drive web interface, click the three dots to the right of the folder name and click Download). This download may consist of multiple files, so make sure to get them all. Decompress the downloaded file(s) to the same location (e.g. G:\CloudPart-1ddb5a50-cae2-456a-a017-b48c254088b3) Run our conversion tool from the command line like so: CloudDrive.Convert.exe GoogleDriveToLocalDisk G:\CloudPart-1ddb5a50-cae2-456a-a017-b48c254088b3 After the conversion, the folder will be renamed to: G:\StableBit CloudDrive Data (1e6884be-b748-43db-a78c-a4a2c720ceef) After the conversion completes, open StableBit CloudDrive and connect the Local Disk provider to the parent folder where the converted CloudPart folder is stored. For example, If your cloud part is stored in G:\StableBit CloudDrive Data (1e6884be-b748-43db-a78c-a4a2c720ceef), connect your Local Disk provider to G:\ (you can also use the three dots (...) to connect to any sub-folder, if necessary). You will now see your Google Drive listed as a local cloud drive, and you can attach it just like any other cloud drive. If you need further assistance with this, feel free to get in touch with technical support, and we will do our best to help out: https://stablebit.com/Contact Q: Why is Google Drive being discontinued? A: Over the years we've seen a lot of data consistency issues with Google Drive (spontaneously duplicating chunks, disappearing chunks, chunks reverting to a previous historic state, and service outages), some of which were publicized: https://www.zdnet.com/article/google-heres-what-caused-sundays-big-outage For that last one, we actually had to put in an in-app warning cautioning people against the use of Google Drive because of these issues. Recently, due to a change in policy, Google is forcing all third-party apps (that are using a permissive scope) to undergo another reverification process. For the reasons mentioned above, we have chosen not to pursue this reverification process and are thus discontinuing Google Drive support in StableBit CloudDrive. We do apologize for the great inconvenience that this is causing everyone, and we will aim not to repeat this in the future with other providers. Had we originally known how problematic this provider would be, we would have never added it in the first place. To this end, in the coming months, we will be refocusing StableBit CloudDrive to work with robust object-based storage providers such as Amazon S3 and the like, which more closely align with the original design goals for the app. If you have any further questions not covered in this FAQ, please feel free to reach out to us and we will do our best to help out: https://stablebit.com/Contact Thank you for your continued support, we do appreciate it.
    1 point
  3. You and your fibre broadband bubble Fair enough, thank you for your response. We'll wait for a message from Alex.
    1 point
  4. No. There is some very hidden data that doesn't copy over, really. But if the new drive is added to the pool, you could copy the contents of the PoolPart folder on the old drive to the PoolPart folder on the new drive. Just make sure you remeasure after it's done.
    1 point
  5. Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that. That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads), the writing has been on the wall for a while.
    1 point
  6. You're 100% right, this is a massive change and for me puts the whole CloudDrive & DrivePool setup in question This is how it looks like in 1.2.6.1710 beta, not really explaining anything:
    1 point
  7. @Christopher (Drashna) Can you please elaborate on this - I'm guessing it's not a choice StableBit would prefer to make? I'd also suggest that it seems like the kind of change that should be officially announced in the forums sooner rather than later (also inb4 inevitable confusion of some users over "Google Drive" vs "Google Cloud Storage") and that some kind of warning message should be implemented in the CloudDrive product itself for those who have (or are adding) Google Drive as a provider. Edit: there is a warning message as of the 1.2.6.1706 beta. I need to read the notes more carefully. Thanks to msq for pointing this out and providing screenshots below.
    1 point
  8. HD Sentinel has something similar, but it's not free. It has multiple surface tests you can perform on a drive, in addition to the standard SMART tests. The equivalent you are asking about would be the write + read test, or reinitialize disk surface (more in-depth). You can configure the data pattern (zero byte, sector count, random data, etc). It has overlap with Stablebit scanner in terms of smart monitoring, etc, but scanner has a much better layout to organize/sort and custom name drives. I've always used sentinel's surface tests to prepare new disks before putting data on them. I basically reinitialize them. https://www.hdsentinel.com/help/en/61_surfacetest.html You can configure a couple of other things on the tests.
    1 point
  9. Changelog from beta version https://covecube.download/CloudDriveWindows/beta/download/changes.txt
    1 point
  10. 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.
    1 point
  11. 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
    1 point
  12. eholyst

    File Placement Question

    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.
    1 point
  13. [Update 2] After adding a 16TB new HDD, the Balancing rules have wonderfull worked, and the replacement rules have been respected. I had to really further set exclusions file placement rule for other non /MUSIC /PICTURE root structure directories also. It's really wonderfull how this is working. A real state of the art software. In summary, it was the over 90% usage of other pooled hard drives that forced an Overflow of data, to the SSD.
    1 point
  14. I have two drive pools in Win 7 - each is set for pool file duplication, thus roughly halving the free capacity of the pool as a whole. Windows file explorer reports the free space as the true free space of the pool (as if there were no duplication anticipated). This presents a problem when doing a monthly FULL backup using a popular 3rd party backup (MR) - as the backup program looks for free space, sees twice what is actually available and then runs for hours before running out of space, instead of being able to see that it should first remove the oldest backup to make more room. I realize that reporting the true free space is the technically correct solution, but wonder whether it would be possible to add a optional tick box instructing DP to report free space/duplication factor for those of us in this "niche problem" situation (as getting the vendors of every other program to write a Drive Pool aware check is simply not realisitic. Thanks for listening or any suggestions you might have to help with this! Steve
    1 point
×
×
  • Create New...