Leaderboard

Reparse point information is stored in the .covefs folder in the root of the pool. Worst case, delete the link, remove the contents of the .covefs folder, and then reboot.

I don't think the behaviour that results from using read striping will result in optimal behaviour, because both a slow hard drive and a fast SSD would be in the same priority category ("Standard drive"), and therefore DrivePool would apply read striping across the two drives the slow drive could be the one with "the least outstanding requests" yet it could still be slower to use the drive for a new incoming request. Would you consider adding a feature that allows the user to control that mirrored files should always be read from the highest-priority drive, with priority being specified by the user? This would be a great addition for mirroring pools that use mixed drive types.

Drive pool did find two corrupt files.....I can get those from my cloud backup. Thanks.

After re-enabling "Realtime Duplication", which I had previously disabled because I have just one SSD for the landing zone, these checks have disappeared completely. According to the documentation it says that if "Realtime Duplication" is disabled, the Duplication will be ensured to be consistent "at night". So it seems it was exactly that and there is no schedule to plan what "at night" is and when exactly it will happen. My suggestion to the developers: give Drivepool an option to let the user schedule when the Duplication consistency check is being performed. Some of us are working at night and so do I, and just force performing this check at a time the developer thinks is good, is not the best way at all. Thanks.

You have to set it to the following. "CreateDrive_AllowCacheOnDrivePool": { "Default": true, "Override": true },

New to StableBit DrivePool, how do I ensure drives will sleep when unused. I have a basic setup and drives are not sleeping according to smartctl. I do not have BitLocker enabled. Note: this is something I want to validate before buying Windows 10 Pro Power Profile - Balanced - has 5 min Drive Sleep enabled Drives are Internal SATA (5 x 8TB WD, 3 x 6TB WD)

Yea, unraid was/is a non starter for me due to existing data and the filesystem difference etc. i have a few hundred TB and it would be all kinds of incomprehensible mess I dont have time for with kids. Now had i saw this whole data obsession/hobby thing becoming what it was.. i definitely would have taken a different path if i was starting from scratch but it is what it is. I will concur that the stablebit suite is without parallel windows side. its served me well for quite some time and I honestly hope it will serve me well until that fateful day hopefully some time a reaaaaally long time from now lol. I love it. that being said, the spindown issue is not inconsequential. when youre looking at a chassis with 30x7200rpm disks crammed within a half an inch of one another in an upstairs office spinning 24/7, the summer months prove a huge issue. I just cant run my air cold enough without making the rest of the house a fridge. Theres also the power savings however miniscule from letting them spin down. The age old argument surrounding which is the lesser evil for longevity etc. i know until i began using drivepool, i always had my drives spin down and would still be doing so if i were able.

I ended up moving to unraid to solve this problem. I still maintain that DrivePool (and Scanner) is one of the best pieces of software I ever purchased on Windows, but it is a shame to see this remain unresolved.

yea this was discussed previously and i'd tried it in the past, does not work for me either. just edited both json and restarted. set my spindown to 1m. drives keep on spinning away. only time i can get them to spindown is stopping the service(s) entirely.

Thanks to you both for the prompt and detailed response.

You also opened a ticket for this. But to repeat what I said there, and echo what vapechiK said, This is perfectly normal, and expected. In all cases, here. the pool drive itself is fully virtual, but doesn't have any blocks/data on the drive. All of the data is "reverse proxied" to the underlying disks, and handled invisible. So CHKDSK won't work on the drive, and it does not appear in StableBit Scanner. And the size is normal, as Windows needs a size before that can be properly read, so the 2TB size is a placeholder.

Given you've already chosen not to keep personal data, at this point personally I'd do a bare metal install of Windows - that is using external install media (e.g. USB or DVD) and choosing to delete the existing OS partition entirely so it doesn't retain any system files/configuration at all from the previous install.

StableBit have very promply got back to me and said you can do it via Powershell and specifically this command: Set-Disk -Number X -isReadOnly $true They will also pass on my RFE to the developer for consideration.

It contains internal data for the drive. Primarily, information about reparse points on the pool (junctions, symlinks, etc). If you have none of this (you can check by opening the folder), then it should be okay. But if you do, then messing with the folder can/will break the reparse points.

No worries! Sometimes, internet stuff .... But glad that we got it sorted.

Issue Resolved Steps Taken (for anyone else who may run into this issue) Uninstalled DrivePool (*backup License key if needed) Rebooted System Reinstall DrivePool Removed drive from pool (*backup or move data from pool directory on drive to root if needed) Recreated Pool The last two steps maybe all that is needed, but I wanted to list all the steps that I took. Note: Uninstalling DrivePool does not destroy the data in the Pool and the Pool will automatically detected on reinstall, making this process non-destructive. Interesting observation: An alternative method, not recommended, would have been to create a second pool using the first pool as a drive. Even though the drive was detected incorrectly on the first pool, the storage space matched the drive size correctly when added to the second pool. Unfortunately, and obviously, this is not an ideal solution as it creates unneeded layers of complexity and points of possible failure going forward.

I've done this before without issue. Here's a post that describes the process;

Thanks for answering @shane. Turns out I had a disk that was failing and needed to pull it from the pool and replace it. Support helped me through the process and the software worked exactly as it should have. Victory!

I understand the concern. I use DP with x2 duplication and Windows Server Backup and that indeed relies on VSS. So what I have done is I created two Pool (Q:\ and R:\) with x1 (so no) duplication and then created another Pool P:\ that consists of Pools Q:\ and R:\ and Pool P:\ does have x2 duplication. This way I have the best of both worlds I guess, I got x2 duplication and x1 backup. It would work similarly with x3 duplication, i.e., create three Pools without and then add them to a Pool with x3 duplication etc. It is not without its compromises, you would want, for instance, each underlying Pool to be roughly the same size and as if and when a disk in the Pool that is being backed up fails, you may need to review the backup settings (as it may need to point to a replacement disk).