Search the Community

So I've recently switched from a desktop setup with 3x 8TB HDDs storage and 1x 128GB SSD cache, to a laptop + eGPU setup with the same four drives in an external enclosure connected to the eGPU. Laptop is connected to eGPU through a single Thunderbolt 3 cable for charging and data, and the enclosure is connected to the USB-C port on the graphics card. Every time I shut down and turn on my laptop, or if I disconnect the TB3 cable and plug it back in (so basically every day after coming home from work), Drivepool starts measuring my entire 22TB pool from scratch, so I just have to wait until it's done (and it takes minutes). I understand that this is a safer approach because Drivepool doesn't know if the contents of the pool have changed from the last time it was "in touch", but in my case nothing else ever interacts with the drives; they're permanently plugged into the eGPU, which only connects to this laptop. Is there an option to disable this measuring every time I connect the TB3 cable? If not I may have to find another backup / pooling solution. Which sucks because I love Drivepool and the way I have it set up to distribute my essential files over three drives.

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!

I must have accidentally checked the box that stores the encryption key because now CloudDrive mounts my drive when the machine boots up (even after a full shutdown). How do I tell it to ask for my key again at startup? Thanks.