Search the Community

Hi there I've been using Drivepool for a couple of years now and it's been really stable and has generally great. However, I have noticed an issue over the past few months in relation to file watches. Specifically, in relation to Subsonic server that is running on my machine. The scenario is as follows: I have 7 data disks in my pool and most of my music collection is placed only on disk 1, as per a file-placement rule (see attached screenshot). Subsonic (which is a Java application) has code that keeps a watch on the filesystem so that when new music files are added into my music folder, it will automatically detect it, scan the files and add to my music libary. This was working fine, but I noticed that sometimes the files were never detected, even after I forced a scan. Long story short - because disk 1 was getting full, some music files were being placed onto disks 2 and 3 when I copied them to my pool drive. Subsonic a) didn't notice the new files and b) would not recognise the files as new even when I forced a scan. Now, my assumption was that the software used NTFS file watches to detect new files, but that doesn't explain why files are not detected on a forced scan, which I believe from looking at the code is based on file/folder last modified timestamps. If I manually move the music files from disks 2 or 3 on to disk 1, or clear up space so that the file placement rules move the files when I re-balance, then Subsonic detects the files. My hypothesis is that Drivepool isn't properly reporting timestamps or filewatch system events when files are placed on to disks that are not the one(s) chosen in file placement rules. It's taken months to work this out and I spent ages on the Subsonic forums (and talking to its developer) because I assumed that it was a problem with Subsonic. I've now conclusively (and repeatably) shown this is a Drivepool issue. Thanks, Steve. PS: I'm running Windows Server 2012R2 with all the latest updates. I have no AV installed at the moment (I got rid of it while testing this, just in case). I also use Snapraid for parity across my Drivepool disks, not that I expect that makes any difference!

Hi I' use the MS deduplication and DrivePool both since the beginning. I never had any major problem with them, aside some calculation glitches with older DP releases. Now I'm in troubles. The deduplication of Windows has changed a bit since the build 16299 or so. A disk previously deduplicated with Win10 or Win server 2016, after being touched by a recent W10/Server 1803/1809/Server 2019, will be silently upgraded and the deduped files become inaccessible by older incarnations. So downgrade/dual boot is not an option. DrivePool (I tested even the latest beta) will fight with the dedup filter and while DP itself still works, the deduplication does not. Before you ask, yes the option to skip the FS filter is correctly set, as usual, in my case This is what I get from powershell with a simple Get-dedupstatus (after DP installation and a reboot) This Is what I see in the deduplication section of event log Sorry messages are in Italian but I think are still pretty clear. So please fix DP asap to not ruin the good reputation of your product (and also to make my life easier ) P.S. FYI Drive Bender 2800 has the exact same behavior

Hello. I ihink that I might have encountered a bug in DrivePool behavior when using torrent. Here shown on 5x1TB pool. When on disk (that is a part of Pool) is created a new file that reserve X amount of space in MFT but does not preallocate it, DrivePool adds that X amount of space to total space avaliable on this disk. DrivePool is reporting correct HDD capacity (931GB) but wrong volume (larger than possible on particular HDD). To be clear, that file is not created "outside" of pool and then moved onto it, it is created on virtual disk (in my case E:\Torrent\... ) on that HDD where DrivePool decide to put it. Reported capacity goes back to normal after deleting that file:

Hey Guys - For the past couple of months, I've had an issue which I found out today only occurs with network file shares that are on my drive pool. I am able to connect to these file shares just fine as well as read from them, however; if i try to write to them or edit a file within one, the workstation (system that hosts the share) immediately bluescreens, bugchecks, dumps, then restarts. I run both DrivePool 2.2.0.906 as well as Scanner which scans as needed at night. I have all performance options enabled except for "Bypass file system filters" plus use the SSD plugin. Balancing is not occurring when the issue happens. Other than that, everything is pretty much default as I don't even duplicate anything. The pool is 43.5tb comprised of 12 platters and a single SSD. It works great other than this issue. I'm happy to submit and logs or whatnot from the app, but wanted to post first to see if this was a known issue with workaround. DrivePool aside, below is the evidence that I've collected from the OS which is Windows 10 1803 x64. Event Logs The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xffffe6871f9fd310 XML View - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-10-16T14:00:03.312566800Z" /> <EventRecordID>2223702</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>KelNetSVR</Computer> <Security /> </System> - <EventData> <Data Name="param1">0x00000019 (0x0000000000000020, 0xffffe6871f9fd310, 0xffffe6871f9fd380, 0x000000000407000c)</Data> <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data> <Data Name="param3">df4e3200-9e5b-48ca-a497-62ed9c91ce3e</Data> </EventData> </Event> Dump Files I loaded the dumps it created in WinDbg. It contains lots of data, but below is a summary - the 5th line from the bottom is what caught my eye. Microsoft (R) Windows Debugger Version 10.0.18239.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\101618-45984-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 17134.1.amd64fre.rs4_release.180410-1804 Machine Name: Kernel base = 0xfffff800`f6293000 PsLoadedModuleList = 0xfffff800`f6641170 Debug session time: Tue Oct 16 08:55:13.232 2018 (UTC - 5:00) System Uptime: 0 days 20:22:06.699 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................................ ................ Loading User Symbols Loading unloaded module list ................ ERROR: FindPlugIns 8007007b ERROR: Some plugins may not be available [8007007b] ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, ffffe6871f9fd310, ffffe6871f9fd380, 407000c} *** WARNING: Unable to verify timestamp for covefs.sys *** ERROR: Module load completed but symbols could not be loaded for covefs.sys *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : covefs.sys ( covefs+2eae1 ) Followup: MachineOwner --------- nt!KeBugCheckEx: fffff800`f643bca0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff850c`0c184b00=0000000000000019 Any thoughts or suggestions? Thanks!

Hi Christopher. Tonight I did some operation on the pool and it was pretty slow, so I went to have a look at the logs (found lots of "Incomplete file found" repeatedly, for the same file; not sure why it dumped the warning 20 times in the log) and had a look at the console too (it was "checking" when I looked, I forget the exact wording). Anyway, once DrivePool was finished "Checking" and "Balancing" everything went back to normal. I think something happened, but I can't say what, it's the first time it's ever gone "slow" on me. Anyway, what I DID notice is that the timestamps inside the logfiles all started at around 10pm. This is when I logoff from 1 user and switch to the Administrator user to do maintenance, install new software, etc. DrivePool is not appending to the log, it is overwritting it. I would definitively call that a bug; we need logs to persist (in fact it keeps daily logs for some days, so the intention *is* to persist). Can you raise a bug report? Thanks! Best Regards,

Hi, today I tried to update from 2.2.0.906 to 2.2.1.907 (so I could extend my beta license for another 30days) and it seems the installer may be broken. 2 (maybe related) Problems: First the update to .907 didn't stick (also later with trying to update from .896, it also didn't work). When installing .907 after deinstalling and deleting folders in `Program Files`, it can't start the service (error: couldn't find CoveFS). Second, when uninstalling .906 it doesn't actually delete files in `Program Files`, after an restart DP just opens again, just like I didn't uninstall it. The entry in "Program and Feature" is gone though. So to really uninstall I have to remove the files in `Program Files` manually I could upgrade from .896 to .906 though. Thx

Hi, today I installed a new 6TB to my 8TB pool. While balancing I looked at the pie chart and it seems it's ratios are wrong. Unusuable for duplication (~4TB/gray) should be smaller than free space (5TB/white). Also actually there are no other files on this hard disk than DP, so unusable for duplication is simply wrong. Later after balancing it corrected that accordingly. But measuring was already done at that point when I took this screenshot, so it still should not be wrong Thx

Hey, I have the Stablebit Scanner for over a year and I really like it . Last week I changed my backup HDD to a bigger size when I noticed a strange bug. The HDD is a Samsung Spinpoint M8 1TB and it has a standby time of a few seconds (when I check "automatic stanby" in the disk control menu). The normal standy timer seams to have no effect. Although I checked "Do not query if the disk has spun down", I heard the starting of the HDD motor every minute! The Power option only changes between "Standby" and "Active" when I enable "Query power mode directly from disk", but then there is an access every 10 seconds from the scanner and so the HDD starts every 10 seconds.... .Also enabling the option "do not query SMART" for the HDD does not prevent the HDD from starting. I can now thottle the SMART queries to 60 minutes and/or make the HDD 24/7 without standby, but because it is just a backup HDD which makes a backup every day for 30min, both things don't seam right. Is there an option I have overseen? Thanks in advance! Regards, Wonderwhy