andrewds

Just happened again.

@Christopher (Drashna), any thoughts?

Hello, Stable environment, suddenly got a couple of BSODs. Scanner reports all disks as healthy. 3 on USB, 6 on SATA. I'd appreciate any feedback on this. I realize I'm a version behind, but looking at the release log there are no driver changes between the two releases. Here's the dump analysis sans stack trace: 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_HEAP_CORRUPTION (13a) The kernel mode heap manager has detected corruption in a heap. Arguments: Arg1: 0000000000000011, Type of corruption detected Arg2: ffff9e8fa9c00100, Address of the heap that reported the corruption Arg3: ffff9e8fc0460710, Address at which the corruption was detected Arg4: 0000000000000000 Debugging Details: ------------------ Page 204be2 not present in the dump file. Type ".hh dbgerr004" for details unable to get nt!PspSessionIdBitmap KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 8156 Key : Analysis.Elapsed.mSec Value: 9286 Key : Analysis.IO.Other.Mb Value: 6 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 25 Key : Analysis.Init.CPU.mSec Value: 890 Key : Analysis.Init.Elapsed.mSec Value: 9998 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Analysis.Version.DbgEng Value: 10.0.27725.1000 Key : Analysis.Version.Description Value: 10.2408.27.01 amd64fre Key : Analysis.Version.Ext Value: 1.2408.27.1 Key : Bugcheck.Code.KiBugCheckData Value: 0x13a Key : Bugcheck.Code.LegacyAPI Value: 0x13a Key : Bugcheck.Code.TargetModel Value: 0x13a Key : Failure.Bucket Value: 0x13a_11_COFS_covefs!unknown_function Key : Failure.Hash Value: {cd27eee9-b3ef-7509-b9c5-8dd5120a90cb} Key : Hypervisor.Enlightenments.Value Value: 68669340 Key : Hypervisor.Enlightenments.ValueHex Value: 417cf9c Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 0 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 4722927 Key : Hypervisor.Flags.ValueHex Value: 4810ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 Key : SecureKernel.HalpHvciEnabled Value: 0 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 13a BUGCHECK_P1: 11 BUGCHECK_P2: ffff9e8fa9c00100 BUGCHECK_P3: ffff9e8fc0460710 BUGCHECK_P4: 0 FILE_IN_CAB: MEMORY.DMP FAULTING_THREAD: ffffd90f8888d040 POOL_ADDRESS: ffff9e8fc0460710 Paged pool FREED_POOL_TAG: COFS PROCESS_NAME: System STACK_TEXT: [redacted] SYMBOL_NAME: covefs+5462 MODULE_NAME: covefs IMAGE_NAME: covefs.sys STACK_COMMAND: .process /r /p 0xffffd90f8548a140; .thread 0xffffd90f8888d040 ; kb BUCKET_ID_FUNC_OFFSET: 5462 FAILURE_BUCKET_ID: 0x13a_11_COFS_covefs!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {cd27eee9-b3ef-7509-b9c5-8dd5120a90cb} Followup: MachineOwner ---------

Not sure why it was necessary but I after seeing the errors in the log I decided to reset the performance counters and restart WMI. Once I did that and reset the scanner service it started working.

v 2.6.7.4027, updated today Now no longer getting disk performance graph or active %, either in the main window or if I right-click a disk and select Disk Information. I rebooted after installing. I'd like to have this information back. Related, but in DrivePool I am also no longer getting information about which files in the pool are currently being accessed. Shows n number of open files, doesn't show which. Updated that today too. Thanks

To quote my response to Christopher: " If I'm understanding the rest of your explanation correctly, you're saying that anytime the application needs to retrieve a file from any disk in the pool all of the disks will wake up from sleep so that DrivePool can determine upon which disk a file is residing in order to deliver it back to the application. Is that correct?" Your response still doesn't answer it clearly. Is there caching or isn't there? Will the drives wake up any time there is an application that needs to retrieve a file from any disk, or does DrivePool mitigate that somehow? Should I expect to see disk activity on all disks any time a file on a single disk is retrieved or are there times when DrivePool can deliver file location information without waking every disk?

@Katz777I just went through this recently after setting it up several months ago. I use Scanner, DrivePool, and CloudDrive. I had to update my Scanner settings not to query SMART more often than once per hour, and not to wake drives to query. I also had to disable BitLocker detection in the JSON config file. I didn't need to do anything with CloudDrive. Once I made those changes and a couple of Windows config changes everything worked fine. Last time I updated DrivePool the BitLocker detection flag was reset to default and the drives wouldn't sleep anymore. I did need to enable options 13 and 15 as described in this post in order to set the power options that worked for me. https://www.thewindowsclub.com/configure-hidden-power-options-in-windows-10

Is that true? I asked for clarity on this exactly several days ago but never got a response.

Thanks @Christopher (Drashna). I have already disabled BitLocker to eliminate that activity. If I'm understanding the rest of your explanation correctly, you're saying that anytime the application needs to retrieve a file from any disk in the pool all of the disks will wake up from sleep so that DrivePool can determine upon which disk a file is residing in order to deliver it back to the application. Is that correct?

I've been diligently working on configuring my system so that spinning disks don't spin unnecessarily. I've got a SSD in place to serve up commonly accessed file types. Browsing the application being served retrieves files only stored on that SSD or the OS SSD. However, for some reason the spinning disks are also waking up when browsing. Does DrivePool store file location information directly on the disks? In other words, does it have to spin up the disks to determine where the requested files are located in the pool? Or is it caching those in the DrivePool application folders somewhere? I'm trying to determine if the disks are still waking up because DrivePool is retrieving information or if it's something about the application being served that's causing it? I don't actually see any disk activity from the application when this occurs so I'm leaning towards DrivePool. Thanks!

Nevermind, found it!

Sorry to confuse. I work in enterprise IT. Flash is used pretty commonly to differentiate from spinning disk. If I had meant a USB/thumb drive I would have said that.

@Christopher (Drashna)sorry what I mean is a flash SSD. Platform doesn't support NVME.

Figured it out. I re-scanned and was prompted to rebalance. It's now balancing the file types I selected out to the cache disk. I've answered this question myself.

I think I figured it out. I made a rule with a pattern match of * and selected all of the existing drives. I left unselected "When a new drive is added to the pool, files matching this rule should be placed on that drive." Now I will attempt to add the drive and craft the rest of the rules at a lower priority. Presumably everything will match to * at the top of the list and once I am ready I can remove that rule so new files will follow the rest of the rules. Now I just need to figure out how to force rebalancing so that the existing files are offloaded to the cache disk. I would still appreciate any thoughts or help.

Hello: I want to add a flash drive to a pool for cache usage but since I can't create rules for that drive until it's created I want to add it but not use it. I need to filter only certain file types to it. Any suggestions on how to do this? Thanks!

Each disk in a pool has several reparse files 3-5 months old. I don't recall seeing them before then. I'm not using symlinking for anything I'm doing with this volume. Is it something CoveFS is doing internally? When I look in the contents I see (amongst the encoded characters) that they all appear to be related to stable diffusion models, some of which can get quite large. Appreciate any thoughts.

@Shane@Christopher (Drashna)can I bug you for any thoughts here? Is it worth completely removing and reinstalling scanner? Seems like maybe some permissions got confused somewhere? Only reason I can think of for things suddenly not persisting.

I just wanted to say that @Christopher (Drashna)has been very helpful each time I've created a topic. I have found him and the others I've worked with to be thoughtful and professional in their responses. Thanks for all the work you all do. Now we can all stop seeing that other thread previewed every time we look at the forum home.

Thanks @VapechiK for the info. I actually was able to recover the information from records I have. However, that doesn't recover the most recent scan information which also reset. Something has happened that is preventing that information from persisting for some reason. I'd like to get to the bottom of that. As to UPS, I am on all (relatively affordable) consumer hardware so I'm not really worried about equipment failures due to power outage. I've got everything plugged into surge strips and worst case if a component fails I'll just replace it. Too many stories over the years of home UPSes catching fire. To me they're an unacceptable home fire risk. However, that power outage alarm you shared is pretty neat. Never seen one of those. We definitely use large enterprise grade UPS and generators in our datacenters at work though

@Shane @Christopher (Drashna) So today we had some bad weather come through and the server experienced a power loss. All of the drive location information is once again gone. I didn't have to perform a recovery on the OS, other software is still current, no restore point rollback or anything. Any idea what could be preventing this information from persisting? Some of the recent scan data is gone as well. Thanks.

Thanks @Christopher (Drashna)for the feedback. No raid, no raid controller, just pooled jbod. Alas the 9207/9307 are not available with mPCIe interface that I can find. This is a mini itx case with a GA-Z97N-WIFI wherein I've removed the wireless adapter (mPCIe) and replaced it with a 2 port SATA card so I could install 8 total disks (1 OS 2.5, 1 cache 2.5, 6 data 3.5). I'm planning to remove the 6 3.5 disks replace with 10 all flash 2.5. Same for the external iSCSI attached parity. Then I'll just have 2 traditional spinning for system image/backups. Built a custom bracket with rails to attach the existing storage, just going to redesign and do it again. Will give me a chance to inspect the wiring etc too. Unnecessary, could just buy something new, but a fun challenge plus I like the case.

Hello: Two of the disks in my pool are on a pci express mini to 2 port sata controller. I want to replace that controller with a 4 or 6 port one. Am I correct that I can do a straight replacement without informing DrivePool in any way? It should automatically recognize the 2 disks (poolpart) when the system boots after the card swap, correct? Thanks.

Thanks @Christopher (Drashna). I don't think that inconsideration of my preferred security posture and the limited use case for this software that the cloud solution is a good fit for me. Ideally the software would have preserved the information about past scans and existing disks during the upgrade process. But, I have added the pertinent files to nightly delta backups to mitigate future risk. I did also manage to recover enough information through another tool I use and, aligning it with the information still present in Scanner I reconstructed everything without having to shut it all down. Bugs happen, it's not a huge deal. Thank you for your help.

I don't have an earlier version of the files unfortunately, or I would have just pulled the info I need from them. The ProgramData folder is only included in the system image and only two of those are retained. Two backups had run since the version update so the info is gone. Oh well, I'll just have to shut the thing down and re-trace the serials.