Tweak3D
-
Posts
2 -
Joined
-
Last visited
Posts posted by Tweak3D
-
-
I started having an issue a few days ago and i'm not sure of the exact cause, but the crash is indicating that covefs.dll is causing my problem. I've noted twice now while read and writing at the same time to the disk, after some time, the system bluescreens and reboots. Here are some details
File Server is a virtual machine (esxi), its running Server 2012 R2 with all applicable updates.It was moved a few weeks ago from one host to another. This was when I began using drivepool (which I am overall very happy with). I am running the beta version 2.2.0.651. The normal version was giving me some issues. If the suggestion is downgrading to the stable version, that is acceptable, but I wanted to report this none the less.
Here are the details from the crash and windows dump file:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000047, 0xfffff800dfb0d7dc, 0xffffe00011db6d70, 0x0000000000007183). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 010116-30359-01.
Microsoft ® Windows Debugger Version 10.0.10586.567 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [N:\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is:Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64Product: Server, suite: TerminalServer SingleUserTSBuilt by: 9600.18146.amd64fre.winblue_ltsb.151121-0600Machine Name:Kernel base = 0xfffff800`dfa14000 PsLoadedModuleList = 0xfffff800`dfce8630Debug session time: Fri Jan 1 22:54:24.978 2016 (UTC - 8:00)System Uptime: 0 days 14:19:44.344Loading Kernel Symbols...........................................................................................................................................................Loading User SymbolsLoading unloaded module list..................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1E, {ffffffffc0000047, fffff800dfb0d7dc, ffffe00011db6d70, 7183}*** ERROR: Module load completed but symbols could not be loaded for covefs.sysProbably caused by : covefs.sys ( covefs+361bd )Followup: MachineOwner---------2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000047, The exception code that was not handledArg2: fffff800dfb0d7dc, The address that the exception occurred atArg3: ffffe00011db6d70, Parameter 0 of the exceptionArg4: 0000000000007183, Parameter 1 of the exceptionDebugging Details:------------------DUMP_CLASS: 1DUMP_QUALIFIER: 401BUILD_VERSION_STRING: 9600.18146.amd64fre.winblue_ltsb.151121-0600SYSTEM_MANUFACTURER: VMware, Inc.VIRTUAL_MACHINE: VMwareSYSTEM_PRODUCT_NAME: VMware Virtual PlatformSYSTEM_VERSION: NoneBIOS_VENDOR: Phoenix Technologies LTDBIOS_VERSION: 6.00BIOS_DATE: 09/30/2014BASEBOARD_MANUFACTURER: Intel CorporationBASEBOARD_PRODUCT: 440BX Desktop Reference PlatformBASEBOARD_VERSION: NoneDUMP_TYPE: 1BUGCHECK_P1: ffffffffc0000047BUGCHECK_P2: fffff800dfb0d7dcBUGCHECK_P3: ffffe00011db6d70BUGCHECK_P4: 7183EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.FAULTING_IP:nt!RtlRaiseStatus+18fffff800`dfb0d7dc 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]EXCEPTION_PARAMETER1: ffffe00011db6d70EXCEPTION_PARAMETER2: 0000000000007183BUGCHECK_STR: 0x1E_c0000047CPU_COUNT: 4CPU_MHZ: 893CPU_VENDOR: GenuineIntelCPU_FAMILY: 6CPU_MODEL: 3eCPU_STEPPING: 4CPU_MICROCODE: 6,3e,4,0 (F,M,S,R) SIG: 428'00000000 (cache) 428'00000000 (init)DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: SystemCURRENT_IRQL: 0ANALYSIS_SESSION_HOST: DESKTOP-JUSTINANALYSIS_SESSION_TIME: 01-02-2016 08:33:30.0292ANALYSIS_VERSION: 10.0.10586.567 x86freLAST_CONTROL_TRANSFER: from fffff800dfb91b8f to fffff800dfb628a0STACK_TEXT:ffffd000`20e749f8 fffff800`dfb91b8f : 00000000`0000001e ffffffff`c0000047 fffff800`dfb0d7dc ffffe000`11db6d70 : nt!KeBugCheckExffffd000`20e74a00 fffff800`dfa89dd4 : 00000000`00000000 00000000`0003fc88 ffffa768`6fccda0f fffff800`c0aa4829 : nt! ?? ::FNODOBFM::`string'+0x1edcfffffd000`20e750f0 fffff800`dfb631db : 00040054`ffffffff ffffe000`10eaba00 ffffe000`10ea9880 ffffe000`10eaba00 : nt!KiRaiseException+0x1a4ffffd000`20e75230 fffff800`dfb6e0b3 : ffffd000`20e75750 fffff800`c0c29180 ffffe000`1160b840 00000000`00000000 : nt!NtRaiseException+0x7bffffd000`20e75370 fffff800`dfb0d7dc : fffff800`c0c29180 00000000`00000002 00000000`c0000047 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13ffffd000`20e75510 fffff800`dfb9c620 : ffffe000`16e421b0 ffffe000`1328d880 00000000`00000000 ffffe000`100952c0 : nt!RtlRaiseStatus+0x18ffffd000`20e75ab0 fffff800`c099c1bd : fffff800`00000000 ffffe000`00000001 ffffe000`00000000 fffff800`c099bb60 : nt! ?? ::FNODOBFM::`string'+0x29860ffffd000`20e75b70 fffff800`c04d2b1e : ffffe000`10f96040 ffffe000`12ce2160 ffffe000`12ce2168 ffffe000`12ce2190 : covefs+0x361bdffffd000`20e75c30 fffff800`c04d10c2 : ffffd000`20e75cf0 ffffe000`10f41390 ffffe000`1230d3b0 ffffe000`12ce2160 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2ceffffd000`20e75cd0 fffff800`c21400b2 : ffffe000`1230d6d0 ffffe000`1230d6d0 ffffd000`20e75e80 ffffe000`1230d3b0 : fltmgr!FltpDispatch+0xb2ffffd000`20e75d30 fffff800`c213ea86 : ffffd000`20e75e80 fffff800`c2135010 ffffe000`13642a38 ffffe000`1230d6d0 : srv2!Smb2ExecuteRead+0x1c2ffffd000`20e75dc0 fffff800`c213e607 : ffffe000`1230d3b0 ffffe000`1230d3b0 ffffe000`11c8f830 ffffe000`1230d3b0 : srv2!Smb2ExecuteProviderCallback+0x56ffffd000`20e75e20 fffff800`c213c19f : ffffe000`11c8e160 ffffe000`11c8e160 00000000`00000002 ffffe000`1230d3b0 : srv2!SrvProcessPacket+0xedffffd000`20e75ee0 fffff800`dfb661f7 : ffffe000`11c8e160 ffffe000`00000001 ffffe000`00000004 d30726b6`000000a3 : srv2!SrvProcpWorkerThreadProcessWorkItems+0x18fffffd000`20e75f80 fffff800`dfb661bd : fffff800`c213df01 00000000`0000c000 00000000`00000003 fffff800`dface16d : nt!KxSwitchKernelStackCallout+0x27ffffd000`20749a00 fffff800`dface16d : 00000000`00000012 fffff800`c213df01 00000000`00000006 ffffe000`1328d880 : nt!KiSwitchKernelStackContinueffffd000`20749a20 fffff800`c20fc926 : fffff800`c213c010 ffffe000`11c8e160 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x2fdffffd000`20749b10 fffff800`dfaa34bf : fffff800`c213dfdc ffffe000`1328d880 ffffe000`11c8e1b8 00000000`00000000 : srv2!SrvProcWorkerThreadCommon+0x66ffffd000`20749b50 fffff800`dfb10554 : ffffd000`20749c80 ffffe000`1328d880 00000000`00000080 ffffe000`1328d880 : nt!ExpWorkerThread+0x69fffffd000`20749c00 fffff800`dfb68ec6 : fffff800`dfd12180 ffffe000`1328d880 ffffe000`0ff62040 fffff800`dfaf8f63 : nt!PspSystemThreadStartup+0x58ffffd000`20749c60 00000000`00000000 : ffffd000`2074a000 ffffd000`20744000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND: kbTHREAD_SHA1_HASH_MOD_FUNC: 5a288c5295cacb528a1b5792210a27b37096b3f9THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d1e647a267c887b7d4a11a9b33a3fd37c66b9aaaTHREAD_SHA1_HASH_MOD: dbe42daf39ced1d826bb55701a412aab928b12deFOLLOWUP_IP:covefs+361bdfffff800`c099c1bd 488d4c2478 lea rcx,[rsp+78h]FAULT_INSTR_CODE: 244c8d48SYMBOL_STACK_INDEX: 7SYMBOL_NAME: covefs+361bdFOLLOWUP_NAME: MachineOwnerMODULE_NAME: covefsIMAGE_NAME: covefs.sysDEBUG_FLR_IMAGE_TIMESTAMP: 5600cdcaBUCKET_ID_FUNC_OFFSET: 361bdFAILURE_BUCKET_ID: 0x1E_c0000047_covefs!Unknown_FunctionBUCKET_ID: 0x1E_c0000047_covefs!Unknown_FunctionPRIMARY_PROBLEM_CLASS: 0x1E_c0000047_covefs!Unknown_FunctionTARGET_TIME: 2016-01-02T06:54:24.000ZOSBUILD: 9600OSSERVICEPACK: 0SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK: 272PRODUCT_TYPE: 3OSPLATFORM_TYPE: x64OSNAME: Windows 8.1OSEDITION: Windows 8.1 Server TerminalServer SingleUserTSOS_LOCALE:USER_LCID: 0OSBUILD_TIMESTAMP: 2015-11-21 08:42:09BUILDDATESTAMP_STR: 151121-0600BUILDLAB_STR: winblue_ltsbBUILDOSVER_STR: 6.3.9600.18146.amd64fre.winblue_ltsb.151121-0600ANALYSIS_SESSION_ELAPSED_TIME: 606ANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x1e_c0000047_covefs!unknown_functionFAILURE_ID_HASH: {08ffa9ab-93bb-e569-dbe3-f1f7b741b09a}Followup: MachineOwner---------Are there any other logs or details I can provide to assist with this issue? Its difficult to reproduce, but has occurred twice in the past 2 days to me.Thanks,Justin
Internal and external storage question
in General
Posted
I had a thought the other day and wanted to see how this would play out.
Say I have an HBA and a SAS expander. I have 8 bays in my server and I add 8 more externally. Say the external devices gets powered off for some reason. What happens? Will the internal try to rebuild its contents immediately? Will the data ont hose drives just become unaccessible until the power is restored?
Thanks,
Justin