There has been another beta build from CoveCube! StableBit development marches on – now its beta M4 build 5805.

Here is how CoveCube describes this application:

• Combine all your hard drives into one big storage pool (except the system drive with the OS).
• Add and remove drives from the pool at any time without re-partitioning or manually moving folders.
• Create duplicated folders on the storage drive pool that are protected against single drive failure. If a drive fails on which a duplicated file was stored, the contents of that file will remain readable even without the drive.
• All your data is stored in standard NTFS files. You can always access your files even if the Windows Home Server completely crashes or this add-in can’t be used.

This version’s change log:

1.0.0.5805

* When removing drives from the pool, cleanly abort all duplication / re-balancing runs while the removal is in progress.

* After hashing files to verify consistency during duplication, if the files are identical, synchronize the last modification times to prevent hashing them again in a future duplication run. Having different file modification times on file parts from duplicated files would have lead to extremely long duplication times because the duplication process would hash each file part to verify consistency.

* When background duplication / de-duplication needs to hash files because of a file modification time mismatch, the hashing process should be abortable and completely transparent to other I/O.

* Do not crash the Dashboard if indexing services are disabled.

* Fixed null error on drive removal.

* Missing disk alert is now cleared if a pooled disk is disconnected, then system is shut down and the disk is reconnected before the next boot up. Previously, the alert would get stuck in the on state.

* Balance ratio is immediately re-calculated after a re-balance.

* [D] After manually deleting a pool part folder, the entire pool stopped working until the server rebooted.

* When re-balancing files or duplicating files in the background, if another application requests write access to the file we cleanly abort what we were doing and move on the the next file. The application that requested access is then given access without an error.