Christopher (Drashna)

Well, if this happened within the last 7 days, then could you run the StableBit Troubleshooter on the system in question? http://wiki.covecube.com/StableBit_Troubleshooter use 3970 as the contact request ID.

I hope so!

Awesome, glad to hear it!

No idea. The service is what handles most everything. The only thing that the UI does would be the performance stats. So... maybe open up resmon, and open the disk tab, and see if that works?

Okay, the crash does look like it may have been triggered by the DrivePool service (eg, the removal). https://stablebit.com/Admin/IssueAnalysis/28007 As for that error, check disk management, and see what it says on the disk. You may need to manually configure the page file, remove it from that drive, and reboot the system.

haha, ... /cries Yeah, that's disappointing. I know that Alex was planning on looking at better supporting ReFS in StableBit CloudDrive. And if he's able to, maybe find a way to better recover it. But that's a long shot.

Yes, it will. StableBit DrivePool places new files on the disk(s) with the most available free space. That means that the Google Drive will be the primary drive that it wants to place data on. Because 70TBs is more than the rest of the pool. Also, I'm guessing that you used the "Disk Usage Limiter" balancer, and unchecked "duplicated" for all of the drives but the CloudDrive disk. If so.... that doesn't do what you think it does. StableBit DrivePool has no concept of "original" or "copy". Both files are 100% identical, and can be used interchangeably. So bu unchecking "duplicated data" for the other disks, you've created a situation where the only valid location for duplicated data is a single drive. It wants to move the rest of the data off of the other disks, as much as possible. No, what I think you want to do is ... remove the CloudDrive disk from the pool, then add that disk, and the D:\ pool into a new pool. Enable duplication on that pool, (and optionally, remove it on D:\), that way, one copy is on the CloudDrive disk, and another is on the local pool.

It may be worth getting a crash dump here. http://wiki.covecube.com/StableBit_DrivePool_System_Crashes Also, it may be worth upgrading to the latest beta, and see if that helps: http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.3.950_x64_BETA.exe

Because that's not how the software works. StableBit CloudDrive doesn't show you the existing contents of the cloud provider you're connecting to. Instead, it creates a virtual drive, mounts that, and then stores the raw disk data on the provider, instead. So, if you wanted to see those files, you'd need to download them, and copy them to the drive. But data on the drive won't be accessible on your Google account.

That's .... very odd. Well, maybe. If you replaced the disk, then StableBit DrivePool will want to give it a new, random block, and not the old name. So, this may very well be normal.

Try this: http://wiki.covecube.com/StableBit_DrivePool_Q5510455 But with just the folder in question, not the entire drive. If that doesn't work, then you may need to do some special stuff to remove the disk.

AppData is for user accounts, ProgramData is for services and the like. And if you want, upgrade to the latest beta version, as it should help prevent this: http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3220_BETA.exe

That's odd. Though, this may be a simple fix: http://wiki.covecube.com/StableBit_DrivePool_F1655 If you have issues moving stuff around because of the inaccessible folders/files, then you may want/need to do this: http://wiki.covecube.com/StableBit_DrivePool_Q5510455

Welcome!

Oh no! TestDisk and Recuva may be able to recover the partition data, and that may be what you want to do, actually. That said, 4TB may be fine, actually. StableBit DrivePool doesn't fill up the drive sequentially, normally. So, it likely wasn't completely full.

StableBit DrivePool only remeasures if there was a missing disk. So more than likely, it's dropping connection and reconnecting them. To be blunt, I am NOT a fan of HighPoint stuff. It's cheap quality stuff, with horrible OEM firmware. The IcyBox is using USB, as well? If so, are they both connected to the same USB controller on the system? If so, that may be your culprit.

^ This. Both of the posts. That said, if you absolutely must know, there is the "dpcmd" too, and "check-pool-fileparts" command: Additionally, you could remove two of the disks from the pool, add them to a separate pool, and then add both of those pools to a new pool. This would help you to ensure that you know what disk the files are on, but it is a much more complicated setup.

Add the new drive to the pool, and remove the old drive. Just do that.

This depends on your balancing settings, specifically. Try changing the ratio to 100% and then change the balancing frequency: https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing Settings

Make sure the disks are "online" in Disk Management (diskmgmt.msc). If they are, then you may need to do this: http://wiki.covecube.com/StableBit_DrivePool_F3540

Probably not, then. RClone is a good product though.

It sounds like it's very dependant on how it's being used, then. I've added this info to the ticket, as this may actually be very helpful. Otherwise, if you get get new logs with the issue, and a precise time of the error occurring.

You should turn both systems off first, ideally. Otherwise, you can set the disk as "offline" in disk management. That closes all handles to the disk, and prevents anything from accessing them. You can then safely "hot pull" the drive (eg, pull it while plugged in), in theory.

No, This is hard coded behavior. But this should be pretty small in size, so shouldn't be an issue. When they're accessed, when duplication setting change, when the pool is measured. So, yes. But we do so in a very lightweight way, that minimizes disk usage. As for the second part, if you're using Task Manager to look at this. DON'T. 100% utilization could mean 1B/s, or 500MB/s. it's based on the last 60 seconds of activity. So, it is very likely that it will be 100% most of the time. A better way to tell how pegged it is, is to look at the disk queue length. Generally, you want it at or below 1 per platter in the drive. So, if it's a 2-3 for a long time, then the disk is being worked hard.

For that specific plugin, no. But we do have an example/sample source for creating balancers. http://wiki.covecube.com/StableBit_DrivePool_-_Develop_Balancing_Plugins But no, this isn't in development either, as the balancing framework doesn't really support this sort of control or filtering, IIRC.