Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11565
  • Joined

  • Last visited

  • Days Won

    365

Christopher (Drashna) last won the day on February 29

Christopher (Drashna) had the most liked content!

2 Followers

About Christopher (Drashna)

  • Birthday 06/25/1983

Contact Methods

  • MSN
    drashna@live.com
  • Website URL
    https://drashna.net/blog/
  • Jabber
    christopher@covecube.com
  • Skype
    drashnajaelre

Profile Information

  • Gender
    Male
  • Location
    San Diego, CA, USA

Recent Profile Visitors

12369 profile views

Christopher (Drashna)'s Achievements

  1. That's a hard question to answer. SSDs tend to be fast, including in how they fail. But given this, I suspect that you might have some time. However, back up the drive, for sure! Even if you can't restore/clone the drive, you'd be able to recover settings and such from it. But ideally, you could restore from it. And cloning the drive should be fine. Most everything is SSD aware anymore, so shouldn't be an issue. But also, sometimes a clean install is nice.
  2. Would you mind opening a ticket about this? https://stablebit.com/contact/ This is definitely diving into the more technical aspects of the software, and I'm not as comfortable with how well I understand it, and would prefer to point Alex, the developer, to this discussion directly. However, I think that some of the "twice" is part of the upload verification process, which can be changed/disabled. Also, the file system has duplicate blocks enabled for the storage, for extra redundancy in case of provider issues (*cough* google drive *cough*). But it also sounds like this may not be related to that.
  3. Make sure that you're on the latest release version. There are some changes to better handle when the provider is read only (should be at least version 1.2.5.1670). As for the empty chunks, there isn't really a way to discern that, unfortunately. If you have the space, the best bet is to download the entire directory from Google Drive, and convert the data/drive, and then move the data out.
  4. In general, this shouldn't happen, but certain scenarios seem to trigger this more. Namely the large semi-annual updates for Windows 10/11. But if you do seee this happening, open a ticket, and then run the StableBit Troubleshooter, and let us know when it's complete.
  5. Given the read errors and the NVMe Health warning, I would definitely recommend replacing the drive.
  6. Mostly, it's just accessing the disks via the poolparts. Otherwise, it is theoretically possible. You could use dism tools to install the drivers for the pool into the winPE image, but you'd also need to mount the image, and manually add the drivepool service. This is complicated, and I'm not entirely sure that this will work.
  7. Awesome, thanks. And my guess is that it's probably using an API in a way that is either wrong, or handled wrong by the pool. Though, it could be something else, too.
  8. Unfortunately, no. It would take some code changes to facilitate that.
  9. Glad to hear it! If it happens again, let us know and open a ticket!
  10. Adding a drive to the pool isn't really backing it up. There are programs that can do that, but this isn't the way. If you just want redundancy, then that's absolutely possible. The simplest way, add the existing pool to a new pool, and add the large disk to that "top level" pool. Enable duplication on that pool, and "seed" the pool from the other pool. Eg, do this: https://wiki.covecube.com/StableBit_DrivePool_Q4142489
  11. That's very odd. I'm guessing it's something to do with the API that they're using, as I have a number of games installed to the pool, and don't experience any sort of issue like this. That said, if you could get logging of this, it would go a long way. https://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection Eg, enable logging, reproduce the issue, then exit and stop the logging as soon as it occurs. And note the exact time, if possible. Then open a ticket at https://stablebit.com/Contact and report/repost it there.
  12. Could you open a ticket at https://stablebit.com/Contact After doing so, run the StableBit Troubleshooter: https://wiki.covecube.com/StableBit_Troubleshooter And then try resetting the settings: https://wiki.covecube.com/StableBit_DrivePool_Q2299585B
  13. Worst case: https://wiki.covecube.com/StableBit_DrivePool_Q3017479 And then reinstall the software.
  14. The safest option would be to detach the drive, change API keys, and re-attach. However, you *should* be able to just re-authorize the drive after changing the API keys.
  15. Try rebooting. If that doesn't help, try resetting the settings in StableBit DrivePool. https://wiki.covecube.com/StableBit_DrivePool_Q2299585B If that doesn't help with the missing disk, remove the disk in the UI, and then do this: https://wiki.covecube.com/StableBit_DrivePool_F1655 And the recycle bin should be the one on the desktop. It's a combined list of all of the drive's recycle bin.
×
×
  • Create New...