All Activity

a couple of things to add to that, I do recommend running "netsh int tcp set global autotuninglevel=highlyrestricted" from an elevated command prompt on any Windows system. The normal "autotuning" setting is overly aggressive and causes a lot of issues, in my experience (sadly, this has been an issue since even the Vista days). Also, on your network adapter, disabling options like "green ethernet", any settings with "checksum" or "offload" in the name, "interrupt modulation", may help with performance and reliability. I'd like to say "reportedly bugged".

No, it dosen't have any preference. But if you have read striping enabled, it should use that to optimize the reads. However, you might be able to use the file placement rules to hack this. Eg, add a rule for "\.covefs\*" should work (or at least, dosen't error out). This should allow you to specify a drive (and testing this, it looks to be respected)

You can also do this with power shell, and with "two" commands. In both cases, this gets a list of disks -> checks for any items that have the "read only property" -> and for each, run the command to disable read only. These are safe to run, and I have verified that they cause no issue on my personal system/server.

To jump in late here, yeah, this sounds very much like a disk issue. A bad cable, connection or even drive may be the culprit here. I would recommend reseating the cables for the drives having issues, or even replacing them (I've actually had SATA cables "burn out", in the past ...). And if that doesn't help, disconnect the drive. If keeping it disconnected clears up the issues, there may be an issue with drive itself (such as the pcb controller on it), and you may want/need to RMA this drive (sooner rather than later).

@Shane thanks, I'll have a look at this setup when I get the chance, but it sounds like I would be playing with fire with such a setup because it's as if I'm creating a software raid 1 where Cloud drive (zod) is a virtual drive on a cloudpool mirror (alpha), so my data cannot be read except by clouddrive (due to block translation), so my data would be at clouddrive's mercy, and as reliable as clouddrive is, that would be risky I believe.

''Problems occurred between the communication of the disk and the host 56 times'' would seem to indicate to me a cabling/connection/enclosure problem. For my setup, a re-install would be days of work, so an absolute last resort. (That's why daily image backups are invaluable.) I hope your problem remains resolved!!

I have reinstalled window 11, drivepool and hd sentinel so far stable no any issue. I think something in my computer have conflict with the software. So far I have not see any ''Ultra ATA CRC Error count'' but I have see ''Problems occurred between the communication of the disk and the host 56 times'' in one of the hard drive in the same enclosure. I have not reinstall stablebit scanner and crystaldisk info yet, I think I will reinstall later if no more issue...

There's no mention of such in the changelog, which I'd expect if it had been.

Salim, what you're asking for isn't simple. To try to use a bad car analogy to give you an idea: "I don't know how this truck works that can tow multiple trailers with the abilities to redistribute the cargo between trailers and even switch out whole trailers, safely, while the truck is still being driven on the highway, but I would assume it can't be difficult to make it so it could also/instead run on train tracks with the press of a button." However looking at your previous thread: Presuming you still want this, on Windows, AND hardlinks, I'm again going to suggest a CloudDrive-on-DrivePool setup, something like: Create a DrivePool pool, let's call it "Alpha", add your "main drive" as the first disk (let's call it "Beta") and your "single drive" as the second disk (let's call it "Gamma"), enable real-time duplication, disable read-striping, set whole-pool duplication x2 (you could use per-folder only if you knew exactly what you were doing). note: if you plan to expand/replace Beta and/or Gamma in the future, and don't mind a bit of extra complexity now, I would suggest adding each of them to a pool of their own and THEN add those pools instead to Alpha to help with future-proofing. YMMV. Connect "Alpha" as a Local Disk provider in CloudDrive, then Create your virtual drive on it, let's call that "Zod"; make sure its chosen size is not more than the free space of each of Beta and Gamma (so if Beta had 20TB free and Gamma had 18TB free you'd pick a size less than 18TB) so that it'll fit. There might be some fiddly bits to expand upon in that but that's the gist of it. Then you could create hardlinks in Zod to your heart's content and they'll be replicated across all disks. The catch would be that you couldn't "read" Zod's data by looking individually at Alpha, Beta or Gamma because of the block translation - but if you "lost" either Beta or Gamma due to physical disk failure you could still recover by replacing the relevant disk(s), with Zod switching to a read-only state until you did so. You could even attach Gamma to another machine that also had CloudDrive installed, to extract the data from it, but you'd have to be careful to avoid turning that into a one-way trip.

Since you don't use/haven't used drivepool I would suggest learning more about how it works so you can see why supporting hardlinks isn't as simple as you might think, and also why having drivepool try to support them conditionally isn't a great idea either. I've been using drivepool for about 12 years now myself. I have full confidence that if there was a simple way for Alex to add support for hardlinks on the pool it would have been done a long time ago. I also want to be 100% clear that I'd love to see hardlinks supported on the pool myself, but I also understand why it hasn't happened yet.

Hmm. Try the following from a command prompt run as an administrator: diskpart list volume Then for each volume: select volume # (e.g. select volume 1) attributes volume attributes disk You are looking for any and all volumes and/or disks that are Read-only. Each time you find such, if any, try: attributes volume clear readonly (and/or as appropriate) attributes disk clear readonly (then repeat attributes volume and/or attributes disk as above to check that it cleared) If you don't find any such then I'm currently out of ideas.

Why would there be balancing if a pool is set up as a mirror and everything is mirrored selectively onto another drive? I'm not sure how drivepool is setup exactly (I haven't used it yet because of the lack of hardlink support), but I would assume you can set up a pool as a mirror or jbod and maybe other types. So if a pool is set up as a mirror with selective mirroring (I select which folders are mirrored onto which disks), I don't see the need for balancing and I don't see why hardlinks can't be supported in such a setup. And if drivepool doesn't support the creation of different pool types, why not add this option and allow the creation of a pool type that supports hardlinks, but with limitations on balancing and adding/removing drives (and anything that can break hardlinks)?

Balancing can happen on any pool regardless of duplication level or number of drives (obvious minimum of 2 drives in the pool for balancing to occur) Balancing can/will occur based on critera set be the balancing options, the enabled plugins (the order of the plugins also affects how data will be balanced), any user file placement rules, adding/removing a drive from the pool, etc. Hardlinks would need to be 100% compatible and guaranteed not to break with any pool regardless of disk layout, balancing settings or duplication settings. I'll say it again, trying to support hardlinks under certain conditions and preventing them under others is just a really bad idea when those conditions can change at any time.

Forgot to mark it as solved, the solution is one of these i guess since i havent tried the rest.

Whew, i don't know which one actually fixed it, but it suddenly showed up on my pool! I did everything above until the poolpart.guid cannot be renamed, so i tried putting the drive offline and online DP said one of the disk is missing, thats when i noticed it's back on the pool. Many thanks Shane saved me from massive headache of copying 20tb files! I almost reinstalled DP as well, i was too focused on finding the missing drive on the non-pooled Iist I didn't notice it's back on the pool

One other thing, since you run HD Sentinel, is to check the log for the drive, and look for errors, particularly Ultra ATA CRC Error count, which indicates a possible cabling/connection/enclosure problem. I usually have a bunch of these before a drive starts acting up to the point of dropping out of the pool. Yes, I also run Stablebit Scanner too, I do use Crystal disk info, but only on demand (performance tests), not in the background. I also use a Fan control program called Argus, which also accesses HD SMART information too, but I like HD Sentinel for that.

My logic should work on pools with any number of disks if it only allows hardlinks to be created when files are on the same disk. Afaik, balancing is only performed when using a JBOD setup where there's no duplication, maybe hardlinks would be a bad idea in such a setup, yeah. But my scenario is a mirrored setup where most (if not all) files are mirrored onto another drive (files in Folder A on Disk A are mirrored onto Disk B, and files in Folder B on Disk A are mirrored onto Disk C), so there can be multiple disks, but it's always a mirror. So if hardlinks are gonna be a problem in a JBOD setup, then only allow it in a mirrored setup where there's no balancing involved.

Thank you for your suggestion Shane, but I keep getting hit with the write protection, in both methods mentioned in that link. SetACL finished with error(s): SetACT error message: The call to SetNamedSecurityInfo () failed Operating system error message: The media is write protected.

My first guess would be that the pool's file permissions have been messed up by the bad disk. I would first try the solutions linked/described here: https://community.covecube.com/index.php?/topic/5810-ntfs-permissions-and-drivepool/#findComment-34550

Try running the following in a command prompt run as administrator: dpcmd refresh-all-poolparts And where poolpartPath is the full path of the poolpart folder of the missing drive: dpcmd unignore-poolpart poolPartPath for example, dpcmd unignore-poolpart e:\poolpart.abcdefgh-abcd-abcd-abcd-abcdefgh1234 And where volumeid is that of the "missing" drive (you can use the command 'mountvol' to get a list of your volume identifiers): dpcmd hint-poolpart volumeid for example, dpcmd hint-poolpart \\?\Volume{abcdefgh-abcd-abcd-abcd-abcdefgh1234}\ while poolparts and volumes happen to use the same format for their identifying string they are different objects If that doesn't help, you may try one or more of the following, in no particular order of preference: repairing DrivePool (windows control panel, programs and features, select StableBit DrivePool, select Change, select Repair) uninstalling, rebooting and reinstalling DrivePool (may lose configuration but not duplication or content, and keep your license key handy just in case) resetting the pool (losing balancing/placement configuration, but not duplication or content): Open up StableBit DrivePool's UI. Click on the "Gear" icon in the top, right-hand corner. Open the "Troubleshooting" menu, and select "Reset all settings..." Click on the "Reset" button. Alternatively, you may try manually reseeding the "missing" drive: if - and only if - you already had and have real-time duplication enabled for the entire pool and you just want to get going again ASAP: remove the "missing" drive from DrivePool quick format it (just make sure it's the right drive that you're formatting!!!) re-add the "missing" drive, let drivepool handle re-propagating everything from your other drives in the background. otherwise: open the "missing" drive in Windows File Explorer (or other explorer of your choice) find the hidden poolpart.guid folder in the "missing" drive rename it from poolpart.guid to oldpart.guid (don't change the guid) remove the "missing" drive from DrivePool if the "missing" drive is now available to add again, proceed to: re-add the "missing" drive move all your folders and files (but not $recycle.bin, system volume information or .covefs) from the old oldpart.guid folder to the new poolpart.guid folder that's just been created tell the pool to re-measure once assured everything is showing up in the pool, you can delete the oldpart.guid folder. else if the "missing" drive is still not available to add again, proceed to: copy your folders and files (but not $recycle.bin, system volume information or .covefs) from the old oldpart.guid folder to the pool drive duplicates of your folders/files may exist on the pool, so let it merge existing folders but skip existing files you may need to add a fresh disk to the pool if you don't have enough space on the remaining disks in the pool check that everything is showing up in the pool if all looks good, quick format the "missing" drive and it should then show up as available to be re-added.

FileID has not been fixed in DrivePool as of v2.3.12.1683.

Update : tried running chkdsk on mountpoint of the drive but it found no errors, restarting DP afterwards but it still wont show up Also here's the service log at the time the pool went missing DrivePool.Service.exe Warning 0 [Store] Event ItemRemoved took too long (00:00:08.4538480) on Sample. 2025-06-25 18:30:27Z 10659034984513 DrivePool.Service.exe Warning 0 [Store] Event ItemRemoved took too long (00:00:08.4538640) on PoolPerformanceSample. 2025-06-25 18:30:27Z 10659034992258 DrivePool.Service.exe Information 0 [Disks] Got Volume_Depart (volume ID: bf9dd6b0-e735-4cf0-a933-869eac4bb6ec, plex ID: 00000000-0000-0000-0000-000000000000, %: 0)... 2025-06-25 22:01:38Z 10785749148378 DrivePool.Service.exe Information 0 [Disks] Got Disk_Depart (disk ID: b676580d-d87f-44d6-91eb-f81079434746)... 2025-06-25 22:01:38Z 10785749151177 DrivePool.Service.exe Information 0 [Disks] Got Pack_Depart (pack ID: 18fb5a1f-466d-4b37-ab1e-205692d63646)... 2025-06-25 22:01:38Z 10785749153308 DrivePool.Service.exe Warning 0 [PoolPartUpdates] Lost existing pool part A1B0B694-23A3-46EE-90BE-ED075FEA47AC (isCloudDrive=False, isOtherPool=False) 2025-06-25 22:01:39Z 10785753531981 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-25 22:01:39Z 10785753546004 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeReadOnly, PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-25 22:01:39Z 10785753547764 DrivePool.Service.exe Information 0 [Disks] Updating disks / volumes... 2025-06-25 22:01:39Z 10785759159288 DrivePool.Service.exe Warning 0 [RemoveDriveFromPool] Error removing \\?\Volume{f2894a3e-fa41-45d1-8d65-b6f395096a44}\PoolPart.80817d65-727d-49e9-9d62-f542610785a9\ from the pool. Removal canceled 2025-06-26 00:41:13Z 10881492181069 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeReadOnly, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:41:13Z 10881492377531 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeReadOnly, PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:41:13Z 10881492379096 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeReadOnly, PoolModeNoMeasure (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:41:13Z 10881492383791 DrivePool.Service.exe Information 0 [MetadataDuplicationConsistency] Pool parts missing on pool '\\?\GLOBALROOT\Device\HarddiskVolume69\'. Can't check metadata duplication consistency. 2025-06-26 00:41:13Z 10881492557218 DrivePool.Service.exe Information 0 [Main:13] Pre-shutdown started. 2025-06-26 00:44:02Z 10883185062617 DrivePool.Service.exe Information 0 [Main:13] Pre-shutdown complete. 2025-06-26 00:44:02Z 10883185135339 DrivePool.Service.exe Warning 0 [RemoteControlKeepAliveListener] Error receiving. A blocking operation was interrupted by a call to WSACancelBlockingCall 2025-06-26 00:44:06Z 10883227910320 DrivePool.Service.exe Information 0 [Main] StableBit DrivePool 2.2.4.1162 2025-06-26 00:47:21Z 589331673 DrivePool.Service.exe Information 0 [Main] Microsoft Windows NT 10.0.17763.0 2025-06-26 00:47:21Z 589356198 DrivePool.Service.exe Information 0 [Main] Loading settings... 2025-06-26 00:47:21Z 589365412 DrivePool.Service.exe Information 0 [Main] No legacy pool ID found. Will not upgrade legacy pools. 2025-06-26 00:47:21Z 589789060 DrivePool.Service.exe Information 0 [Main] Checking StableBit CloudDrive start status... 2025-06-26 00:47:21Z 589789859 DrivePool.Service.exe Information 0 [Main] Not waiting for the StableBit CloudDrive system service. Service CloudDriveService was not found on computer '.'. 2025-06-26 00:47:21Z 589804010 DrivePool.Service.exe Information 0 [Main] Loading lifetime statistics... 2025-06-26 00:47:21Z 589805296 DrivePool.Service.exe Information 0 [Main] Starting remote control... 2025-06-26 00:47:21Z 589829516 DrivePool.Service.exe Information 0 Comm server started on: tcp://127.0.0.1:27525/Comm1 2025-06-26 00:47:21Z 589849152 DrivePool.Service.exe Information 0 [Main] Starting running file... 2025-06-26 00:47:21Z 590157693 DrivePool.Service.exe Information 0 [Main] Starting user feedback... 2025-06-26 00:47:21Z 590165034 DrivePool.Service.exe Information 0 [Main] Starting root tasks... 2025-06-26 00:47:21Z 590170843 DrivePool.Service.exe Information 0 [Main] Enumerating disks... 2025-06-26 00:47:21Z 590253733 DrivePool.Service.exe Information 0 [Disks] Updating disks / volumes... 2025-06-26 00:47:25Z 633514898 DrivePool.Service.exe Information 0 [Main] Starting disk metadata... 2025-06-26 00:47:50Z 878984860 DrivePool.Service.exe Information 0 [Main] Starting CoveFs... 2025-06-26 00:47:50Z 880350307 DrivePool.Service.exe Information 0 [CoveFs] Waiting for pools to mount... 2025-06-26 00:47:50Z 880394909 DrivePool.Service.exe Information 0 [CoveFs] All 1 pools mounted. 2025-06-26 00:47:50Z 880418117 DrivePool.Service.exe Information 0 [CoveFs] Waiting for pool parts to arrive... 2025-06-26 00:47:50Z 880419330 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:47:50Z 880503631 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:47:55Z 930637421 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:00Z 981414380 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:05Z 1031833538 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:10Z 1082077807 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:15Z 1132505116 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:20Z 1183422072 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:25Z 1233984510 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:30Z 1284461038 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:35Z 1335154648 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:40Z 1385327360 DrivePool.Service.exe Information 0 [CoveFs] Pool 1d1285e5-0867-4d83-bb98-e09fd936e5b0 is missing some pool parts. Waiting... (Expected: 25, Found: 24) 2025-06-26 00:48:45Z 1436106451 DrivePool.Service.exe Warning 0 [CoveFs] Timed out waiting for all pool parts to arrive. Continuing startup... 2025-06-26 00:48:50Z 1481282688 DrivePool.Service.exe Information 0 [CoveFs] Pool found on: \\?\GLOBALROOT\Device\HarddiskVolume67 (pool ID=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:48:50Z 1481307892 DrivePool.Service.exe Information 0 [Disks] Updating disks / volumes... 2025-06-26 00:48:50Z 1481405407 DrivePool.Service.exe Information 0 [Rebalance] Loading balancers (LoadBuiltIn=True)... 2025-06-26 00:48:50Z 1481909237 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNormal (lastKey=CoveFsPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:48:50Z 1483414805 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:48:50Z 1483611264 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeReadOnly (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:48:50Z 1483624127 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeMissingDisk, PoolModeReadOnly, PoolModeNoMeasure (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:48:50Z 1483638304 DrivePool.Service.exe Information 0 [MetadataDuplicationConsistency] Pool parts missing on pool '\\?\GLOBALROOT\Device\HarddiskVolume67\'. Can't check metadata duplication consistency. 2025-06-26 00:48:51Z 1489739972 DrivePool.Service.exe Information 0 [Main] Updating free space... 2025-06-26 00:49:02Z 1602316751 DrivePool.Service.exe Information 0 [Main] Starting notifications... 2025-06-26 00:49:02Z 1602349648 DrivePool.Service.exe Information 0 [Main] Starting performance samplers... 2025-06-26 00:49:02Z 1602401755 DrivePool.Service.exe Information 0 [Main] Starting notification tasks... 2025-06-26 00:49:02Z 1602411531 DrivePool.Service.exe Information 0 [Main] Starting notification UIs... 2025-06-26 00:49:02Z 1602417131 DrivePool.Service.exe Information 0 [Main] Service started. 2025-06-26 00:49:02Z 1602511435 DrivePool.Service.exe Information 0 [Main:6] Opened DrivePool_PreShutdown (CreatedNew=False) 2025-06-26 00:49:02Z 1602533286 DrivePool.Service.exe Information 0 [Main:6] Opened DrivePool_PreShutdownStarted (CreatedNew=False) 2025-06-26 00:49:02Z 1602534347 DrivePool.Service.exe Information 0 [Main:6] Opened DrivePool_PreShutdownComplete (CreatedNew=False) 2025-06-26 00:49:02Z 1602535275 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeReadOnly, PoolModeNoMeasure (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:05Z 4036064523 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNoMeasure (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:05Z 4036066379 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNormal (lastKey=PoolPartUpdate, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:05Z 4036068055 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeOverrideAllowCreateDirectories (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:20Z 4188013468 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:20Z 4188015415 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:20Z 4188016565 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 00:53:20Z 4188017589 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 04:24:36Z 130941216138 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 04:24:36Z 130941218615 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 04:24:36Z 130941220124 DrivePool.Service.exe Information 0 [FsControl] Set overall pool mode: PoolModeNormal (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=1d1285e5-0867-4d83-bb98-e09fd936e5b0) 2025-06-26 04:24:36Z 130941221495 DrivePool.Service.exe Information 0 [Disks] Updating disks / volumes... 2025-06-26 14:06:25Z 480030359947 Seems like it lost that pool when i tried to remove a drive..

Hi! So I had a drive going bad (overheating) and entered into RAW state. I tried restoring the partition, without wiping it, but to no luck, so I decided to replace the drive with the same model and then I'll have to deal with the defective drive later on. I added it to the pool, removed the missing drive and then I wanted to enable pool file duplication, but was met with an error saying read-only. I'm not sure how I can remove this, so I can enable the file protection and start to re-balance the pool. Googling gave me nothing, so hopefully someone here knows something, that I can benefit from!

Your examples seem to only take a 2 disk pool into consideration. Adding a 3rd drive (or more) into the pool immediately complicates things when it comes to the balancing and duplication checks that would be needed to make this possible. Also, even if you try to control the conditions under which hardlinks are allowed to be created, those conditions can change due to adding/removing a drive or any automatic balancing or drive evacuation that takes place. Allowing hardlinks to be created under certain conditions when those conditions could change at any point afterwards probably isn't a good idea. Any implementation to fully support hard links has to work properly and scale with large pools without any (or at least minimal) performance penalties, and be 100% guaranteed to not break the links regardless of dupication, balancing, etc.

I have OneDrive on a separate volume, but am curious to know if it’s been fixed in the latest update.