Christopher (Drashna)

That's ... really odd. Could you open a ticket at https://stablebit.com/Contact and then run the StableBit Troubleshooter, using the "DirectI/O" option. http://wiki.covecube.com/StableBit_Troubleshooter

Try running a CHKDSK pass of all the disks in the system. Try remeasuring the pool. If that doesn't help, then you may need to do this: http://wiki.covecube.com/StableBit_DrivePool_Q4142489 If this is with the file system scan (and it sounds like it is), you may want to update to the latest beta, as that has a fix for this issue. http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3259_BETA.exe Honestly, I'm not sure. It sounds like you may have accidentally disabled duplication, or removed the drive from the pool.

I've noticed this myself, and unmounting and remounting will fix that. To be honest, I think this is an issue with Apple's implementation of SMB/Samba/CIFS. I'm not sure there is much that can be done. But I'll look into this.

StableBit DrivePool places files on the disk with the most available free space (absolute, not percentage). If that's the case, then the "realtime placement limiter" arrow that you see is absolutely normal. It's trying to clear out the drive, to prevent data loss. If you clear the status and it comes back, then you should definitely consider replacing the drive. Especially if it's under warranty, as you should be able RMA it.

AWESOME!! I'm glad to hear that!!

@dan66215 it uses the disks in the pool to determine free space. Because you have one of the disks that is completely filled, that is likely the issue. Especially if you're using ordered file placement. That said, it may be worth installing the "Drive Space Equalizer" balancer plugin and enabling that. StableBit DrivePool Balancer Plugins

Yeah, it would, and it is something that we've talked about internally. But "complicated" is a bit of an understatement, and it would eat up a lot more bandwidth, etc. We should have a release for it out Very SoonTM

Ouch! sorry to hear about the issues. And yeah, that did sound like a disk issue, and not a pool issue, specifically. Just a heads up, StableBit DrivePool does have a notification option for when there are missing disks. Make sure that's set up. Additionally, for StableBit Scanner, grab the latest beta, as that will fix the issue with the lost settings: http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3259_BETA.exe

Oh no, I'm sorry to hear that! That really sucks! If you have a UPS/battery backup, it may help. However, I've heard of it not being enough. Which is not surprising, based on the amount of power that lighting brings down (well, really, up). The best bet is to unplug everything during a storm.

If you're using the latest beta, try using a build before that. We've had several people complaining about similar issues on the newest.

Yeah, as long as the drives show up correctly, then it will maintain the pool. As for the power savings, that entirely depends on the power consumption, both at peak and idle. And to be honest, you probably won't see a lot of power savings. The best way to get that savings is to use large capacity SSDs, which is what data centers do. However, they can be a LOT more expensive.

I think you've opened a ticket for this already. Try uninstalling and reinstalling StableBit DrivePool, and it should fix the issue.

To clarify a few things, here: The "unusable for duplication" is a red herring here. It isn't actually impacting you, one way or another. You can safely ignore it. For the write error, it looks like it is set to write to disk 8, which has very little space left. It's not overflowing to Disk 10, because of the balancing settings (and would only do so for duplicated data). You may need/want to change the disk order in the Ordered File Placement balancer plugin to fix this.

Specifically, "diskpart" is a command line utility that hooks into "VDS", the same way that Disk Management does, and allows a lot of control over the disks. As well as access to more features than Disk Management normally gives you. As for "automount", this setting controls the ... well, automatic mounting of disks on the system. Enabled is the default, but disabled means that any disk without a mount point is not automatically mounted, and therefore, is not accessible until it's mounted.

Just a heads up, even if you do turn on duplication for the drive, it won't duplicate all of the data, automatically. It will only duplicate data that is written to. So you'd need to rewrite the entire contents of the drive to properly duplicate the data. It may be simpler/better to create a new drive with duplication enabled and just move the data over, as much as a pain as that may be.