-
Posts
729 -
Joined
-
Last visited
-
Days Won
64
Everything posted by Shane
-
The error "oplock request is denied" means that something else is locking the file. Check for other applications that may be directly scanning or modifying files within the hidden poolpart folder(s) at the time (e.g. a virus scanner or media organiser); if possible, consider excluding the hidden poolpart folders from being directly accessed by those applications (instead have them accessed via the pool drive).
-
Check your balancing settings (plugins and placement rules) to see if something has higher priority than whatever option you have set that should be sending files to that drive rather than any other(s)? The default setting is to send files to the drive with the most free space.
-
In the download sections for DrivePool or Scanner tick the EULA checkbox and you will be able to expand the OS/version sections, which will mention the version number as well as links to the changelogs for DrivePool (currently 2.3.4.1542) and Scanner (currently 2.6.6.4003) respectively.
-
To exclude a drive from automatic scanning, right-click the drive in Scanner and choose Disk Settings then tick "Never scan surface automatically"; you may also wish to tick "Never scan file system automatically" as well. I am not aware of any way to re-order scanning, however if it helps you it is possible to use Disk Settings to set specific drives to scan on a slower or faster schedule than the defaults established by Settings -> Scanner Settings -> Scanner.
-
If the drives were repeatedly dropping out in the middle of writing to them, it's possible the file system on those drives (or on those sharing a controller with them) have been corrupted. I would recommend using chkdsk on them, and you might need to reset their permissions as described here.
-
Proper method is basically to use the Manage Pool -> Balancing... -> Settings / Balancers / File Placement menus; some tweaking may be required if you try for something complex, and it can help to read the manual and the pop-up tooltips that many of the options have if you rest the mouse cursor over them. Pool measuring knocking the disk offline is (in my experience) an indicator that the controller can't handle load, as the measuring process is quite intensive when it happens (it is used to help DrivePool's determination of what to balance, whether files are in the correct locations, whether it needs to adjust balancing ratios, etc).
-
Uh... I suspect DrivePool is unable to apply them simply because the drive keeps dropping out (as whenever a drive is unavailable DrivePool will change to read-only mode to avoid risk of pool corruption), but you may wish to check the logs (gear icon in the upper right -> Troubleshooting -> Service Log) for whatever details of the problem are being reported by DrivePool.
-
CloudDrive drives take up a certain amount of space on a provider's service even when "empty", expanding as required to accommodate data uploaded to the provider; that minimum is determined by a combination of the drive metadata and the API of the provider. That said, 1TB would be way (way, way, way) too high for a brand new empty 2TB drive. Is that actually the size that Google is claiming is being used specifically by the CloudDrive folder* within your Google Drive account, or as VapechiK suggests do you have other files already stored elsewhere in your Google Drive account that would represent most of that? *(for file-based cloud storage, e.g. Google Drive, basically the CloudDrive drive you see on your computer is translated to and from a bunch of a files kept inside a unique folder on your storage provider's drive by the CloudDrive software)
-
Unfortunately no, DrivePool works at a file level and can't automatically import a set of drives that have been spanned (e.g. via Windows Disk Management or Storage Spaces), so you will have to transfer the data manually (and each drive will have to be converted back to a basic disk before it can be added to a pool).
-
What is the procedure if a drive is about to fail?
Shane replied to Jasper9080's question in General
Depends on what you mean by clone (and presuming the drive lasts long enough to clone everything on it). If you're cloning the whole drive, then you'll want to stop the drivepool service while both are connected or clone it on a different machine so you don't confuse drivepool (and then Remove the old drive from the pool after you've disconnected the old drive). If you're adding the new drive to the pool then manually copying/moving the content from the old poolpart folder to the new one, you'll want to stop the drivepool service or at least turn off balancing/placement while you're doing that (and then Remove the old drive from the pool after you've disconnected the old drive). If you're just Adding the new drive to the pool then Removing the old drive from the pool, letting DrivePool handle moving everything (perhaps with the option to handle damaged drives ticked), then you don't need to stop the service, though this is slower than the above methods (unless the old drive had Duplication enabled in which case you can use the option to re-duplicate later which makes it much faster at the cost of temporarily lowering your duplication). -
Hmm. What happens if you shut down, disconnect all drives except your boot drive (C: presumably) then boot up? Do you still see the COVECUBECoveFsDisk___ "drives"? Whether if so or if not, what happens if you then use Disk Management -> Action -> Rescan Disks? If not, after the Rescan Disks, do they come back when you reconnect all the drives again?
-
I delete files on the Cloud drive, but the changes are not reflected in the software
Shane replied to MitchellStringer's question in General
Cloud Drive works by creating a virtual reproduction of a basic volume and drive on the remote cloud service, down to and including the sector level; its consumption of actual physical space starts at a minimum point and expands up to the designated capacity as data is written to it, much like the VHDX virtual volumes as used in HyperV and similar environments. Thus when you delete a file on CloudDrive the drive itself does not shrink on the cloud service, any more than when you delete a file on a physical drive the drive itself does not shrink inside your computer. Similarly, just like a physical drive, the sectors occupied by the data of deleted files remain available for re-use by new files (or for recovery in case of accidental deletion); when you delete a file on the drive, the "free" space of the drive itself goes up just like on a physical drive inside your computer. If you wish to free up actual space on your cloud provider's service for non-drive purposes, you should be using the Resize option of CloudDrive to shrink the drive; CloudDrive will automatically follow the Resize with a Cleanup afterwards to safely free up any excess used space on the cloud provider's service that is no longer required to support the drive. To pre-answer "why can't CloudDrive automagically free up de-allocated space in the background and/or without resizing", I'd presume that doing so safely would require significant additional coding (I know VHDX has an option to compact without resizing, but not AFAIK while writable!) and the task itself would slow down the drive for users when it was happening so IMO it becomes a question of "can StableBit get enough ducks lined up in a row that it's worth adding this rather than doing something else". But if you'd really like to have it do that, you can submit feature requests directly to StableBit via the Contact form. -
Other than perhaps reporting it via opening a support ticket, not that I'm aware of.
-
Yes, the Cloud app does seem to be incorrectly adding them together as separate pools even though it seems to have detected there's a hierarchical arrangement.
-
I believe it's used when DrivePool has a choice of drive(s) to pick; a seek penalty will influence which are chosen. E.g. if you tell it to open a file (e.g. a movie) that's stored on more than one drive in the pool, it will look at which of those drives are busy and which have no penalty. So if your file was on a SSD and a HDD it would prefer to open it from the SSD unless the latter was already busy with something else. The update means this now also applies to nested pools; in such situations (e.g. a pool consisting of a pool of SSDs and a pool of HDDs) the combined pool can now know which of it's comprising pools have no seek penalty.
-
If the SSD was tested on the same port on the PC as the Syba then that would rule out the PC (at least in theory; in practice it could still be a combination of the interaction between the particular chipsets), leaving only the Syba as the common factor. Otherwise while I too would suspect the Syba here, we couldn't entirely rule out the PC.
-
If you have drives X and Y comprising pool Z, then directly accessing X:\PoolPart or Y:\PoolPart yourself rather than through Z:\ means you're not using DrivePool - so if you're still getting the same capped total speed then the problem isn't DrivePool. You might need to look at the USB 3.x controller you're using, perhaps there is an issue there / a driver update available? What is the brand/model of the DAS?
-
I know that Windows will always check the available space against the total size of the folders/files to be copied, or when moving those between different drives, but I'm surprised that's happening when moving files within the same pool as I'm under the impression that should appear to Windows to be the same "drive".
-
Q. "I use File Juggler for this, as I saw no way at all to do this via balancing rules (file date, file size is not present). Unless I'm mistaken?" A. Correct, DrivePool's balancing doesn't support balancing by file date or file size, only by file name. Q. "I have mounted the SSD and the HDD pool to empty NTFS folders, and file juggler interacts with those. Will this mess up my pools at all? I would assume not?" A. If the File Juggler program is pointed at a pool, there shouldn't be any issue. If the File Juggler program is pointed at a poolpart (one of the hidden folders that comprise a pool) then it could mess up DrivePool's measuring which could in turn affect balancing; if you find this is happening and File Juggler can run a command or script after it completes a juggle then you may wish to have it order DrivePool to perform a re-measure (DrivePool may also automatically initiate a re-measure if it notices the discrepancy). Q. "Regarding my HDD pool, I would like it if the balancing is only done with newly written files. So no files get moved from one disk to another. Is this possible?" A. Given what you've described, for the "HDD Pool" I would remove Disk Space Equalizer and would suggest using Prevent Drive Overfill instead.
-
I can't comment officially as I'm just a volunteer mod (see my sig below). Having another look, the Notifications menu entry in DrivePool being missing when it's not linked to the Cloud service seems like a bug? New versions of DrivePool, Scanner and Cloud were just released yesterday so check if those make a difference, and if they don't then I'd suggest opening a support request with StableBit directly.
-
Were you able to figure this out? I also use Firefox and save to a network share (well, a mapped drive of a network share) that is a DrivePool pool on the other end but haven't encountered this error, fwiw.
-
Scanner detected bad sectors. Need help understanding.
Shane replied to taflemer's topic in Nuts & Bolts
Drive might still be usable - sometimes you get lucky and the bad sectors don't breed, and if so chkdsk /r will at least mark those sectors to not be used by the file system - but if you don't want the risk that you'll end up with more and more bad sectors then yeah wipe and bin/rma the drive. -
Perhaps a combination of CyLog's FillDisk (does what it implies: fills a disk with files full of zeroes) and StableBit's Scanner (scans drive sectors to verify they're readable)? There's also utilities such as Seagate Tools and HDDScan.
-
VapechiK is correct; StableBit's DrivePool is not a parity RAID system, it will not "self-heal" a damaged file. StableBit's Scanner is able to detect and attempt to repair damaged files, and if you have that plus DrivePool's duplication you can manually replace a non-repairable file with its good duplicate when alerted. Some users combine DrivePool with SnapRAID to get parity healing capability (albeit not fully automated). As VapechiK indicates, you can also pool sets of RAID volumes to let those provide duplication/parity.
-
DrivePool does not automatically remove empty folders from poolparts during balancing (basically for redundancy reasons; some pool metadata is stored as AD streams attached to the folders and the "space cost" of this is normally very low). The upshot is that so long as the "abracadabra" folder tree is showing 0 bytes (as an administrator) and does not contain any hidden system folders (e.g. $recycle.bin or system volume information) then it can be safely removed manually while the DrivePool service is stopped; the only thing you'd "lose" is some extra redundancy.