Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

  1. I feel like an idiot, all these years I thought chkdsk /r read/overwrote/read each block to see not just that it could be read from but that it could be written to and subsequently held the value expected. I'm totally stumped on this one. I let the computer run overnight doing the built in Windows memory test (choosing all the various write tests) and it came up fine. So, presumably it's not memory. Sadly I over-wrote the local file and the SD card files soon after the event so I can't go back and check that. I was hoping JPEGs had some sort of CRC or something but they don't, so I can
  2. I shot some photos, put the SD card into my PC, copied the images to my main drive (SSD), then because they were important family photos and I was feeling paranoid I binary diffed the source and the copy. One file was different (of the ~320 files, ~1.7 GB). I then viewed the files in a hex diff viewer, and I attach that image. I've seen corruption occur before but never like this. There are maybe 40 bytes total that have changed, but they aren't adjacent, though they are in the same region of the file (each change has gaps of 15-40 bytes). I recopied the file from the SD and the new copy m
  3. Nope, none of those things happened. And thanks, I'll let you know if it happens again.
  4. The latest beta didn't resolve the issue. The drive still wasn't attached after logging in or with GUI up. I did the force attach and it gave me all the dire warnings about this having been attached to another computer and possible data loss. I don't have any significant files in there to test for corruption or anything. Not sure why it would have thought I had connected from another computer.
  5. Maybe I'm just not understanding the interface, but I created an encrypted drive with StableBit CloudDrive. It was working. But it was no longer mounted after rebooting and I can't figure out if that's expected behavior, and I can't figure out how to re-mount it. The only options I see to try and mount would be "Attach" but that shows me a dire warning saying "Cloud drive already attached to [The computer name I'm already on]. Please detach from that computer before trying to attach it to this one." I didn't attach from any other computer, just this one, and I didn't crash or do anythi
  6. Weird. I just tried with the latest Drive Pool beta linked on the site since you said the beta worked for you and it still doesn't detect my pool until I restart the Drive Pool service.
  7. Hmm, weird. Yes, I'm using volume encryption. And I just double checked and I do have the entry: In DrivePool.Service.exe.config I have: <setting name="BitLocker_PoolPartUnlockDetect" serializeAs="String"> <value>True</value> </setting> i am not using the beta, though, I'm using I wasn't sure what risk the beta posed (data safety/etc.). Were you testing with the beta?
  8. Hmm... It's not working. I made the setting change. But on reboots (unless I restart the service) the pool does not re-appear. The encryption software I use is Jetico and it's like TrueCrypt or any of the others (when the system drive isn't encrypted), once you log in to Windows Jetico asks for your password to open the volume, you type it in and it mounts. One thing that might be different about Jetico from TrueCrypt, for example, is that it re-uses the same drive letter. So, at boot and at login before you give the container password the O: volume appears raw/unformatted. You then giv
  9. Thanks, that seemed to do it (or restarting the service did). I'm not using bitlocker but another encryption software, does this just happen to have the name bitlocker in it but isn't really bitlocker specific?
  10. I set up a drive pool consisting of two drives (P; and Q:), neither of which can be mounted at boot because they are encrypted and the password request doesn't occur until I'm logged in. I added some content to the pool I created. All was well. I look today (after one or more reboots) and the pool is gone, and in the UI of Drive Pool there's no listing of the drives on which the pool was located. But the drivers (not the pool) are mounted and perfectly usable in Explorer as always. So, I'm assuming Drive Pool on reboot saw both drives missing (I didn't see any alerts/notices) a
  11. Same result, same error, but now with a pop up dialog!
  12. Thanks for the explanation. I think part of my confusion is that when I came across Drive Pool, not knowing its legacy and what was normal for these types of products, I imagined that you could run Drive Pool on multiple computers within a house/company to create one or more pools spanning computers. For example, I have four or five always-on computers in the house and had imagined that I could pool their storage together as a sort of virtual NAS, with each computer running Drive Pool to access/manage the pool. But I see now that's not what Drive Pool is at all.
  13. Sorry, I mixed names. I'm talking about Google Cloud Storage (not Drive), and it's the latest version of StableBit, the one on the website And I did try and got the same Google Cloud Storage account to work fine with NetDrive2.
  14. I've tried to read all I can find described about Drive Pool, but I haven't seen a real explanation of how Drive Pool handles a drive in the pool being disconnected for long periods of time. Let's say I wanted to have a drive which is periodically connected and then removed to act as an offsite backup. Or let's say I had an external drive connected to my laptop which houses primarily games and I don't generally need those when I'm disconnected, but would still like it to be part of the pool for other content. I'm just not clear how drive pool knows how to re-sync things. Related to this
  15. Anyone have any idea? Is there somewhere to see errors? I just have no idea what to do it just fails after seeming to work with the 'Security Error' message. I noticed in NetDrive2 the flow is a little different, it asks me for my "projectid" before doing the auth with Google, not sure if StableBit asks this later or is making some invalid assumptions having not asked or something.
  • Create New...