Jump to content
Google Drive is Discontinued (FAQ added)

bb12489

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Posts posted by bb12489

    Newly created DP seemingly causes BSOD when exposed to intense read/write

    in General

    Posted

    Well, I'd recommend re-enabling realtime duplication. Especially if you're writing a lot to the pool. Or keeping files open. This will prevent them from getting out of sync.

     

    However, Network IO Boost does use more resources, and based on some of the stuff you've said, I suspect that this may be part of the issue here. 

     

    Read Striping is definitely optional, but it's good for boosting performance. But again, it uses a bit more resources.

     

     

    And if you haven't already, I would really recommend running an extended memory test of the system. (the extended option, and like 5 passes).

    http://wiki.covecube.com/StableBit_DrivePool_Q537229

     

    Also, I'd check to make sure the drivers are up to date, or see if anyone else is having issues with them. Especially network and disk drives.

     

    And you mention the ntfs.sys and older disks? If you have StableBit Scanner installed, you can run a burst test on the disks, which is a good way to troubleshoot issues with them.

     

    So I've run a memtest for 3+hours now. No errors detected. I'm beginning to think it may be a drive issue with this particular board. Server 2012 R2 has all the drivers for this board built in, so there are no other newer versions of drivers for it. I did receive an ntoskrn.sys bsod shortly after I replied that I've had non..... Go figure lol. Also all the hard disks have tested healthy. I think my only other option at this point is to re-install the OS. Maybe go with Server 2012 R2 standard with the essentials role instead of straight up 2012 R2 essentials itself. 

     

    Aside from that, the only hardware issue I can think of is one of two CPU's. I'll re-seat them and re-paste them just to see. Stranger things have happen right? lol.  

     

    I do have the memory dumps from the last two BSOD's, but I'd hate to take up your guy's time to look into them if it's not a problem with your software/drivers. 

    Newly created DP seemingly causes BSOD when exposed to intense read/write

    in General

    Posted

    Alex has looked at the dumps. It definitely looks like a memory related issue here:

    https://stablebit.com/Admin/IssueAnalysis/6255

    Just to report back. I believe i have solved my BSOD's so far. Ever since I've disabled the pool performance settings such as Network IO Boost, Read Striping, & Real Time Duplication, I have not had a single BSOD related to covefs.sys or ntoskrn.sys. I don't currently have duplication enabled since I need more drives for it, so I thought having the Read Striping enabled was kinda silly. Also I was seeing some errors in the event log related to the network controller, so I thought maybe I should also disable the Network IO boost as well. Obviously I've changed too many variables to know for sure if this helped at all, but so far so good! The only BSOD I've had is ntfs.sys, so I'm running a check on some of my older drives at the moment. 

    Newly created DP seemingly causes BSOD when exposed to intense read/write

    in General

    Posted

     

    Got it. 

     

    A quick look at the dump indicates memory corruption, actually:

     

    BugCheck 3B, {c0000005, fffff8005b2ecac6, ffffd00021d46170, 0}
 
Probably caused by : memory_corruption
 
Followup: memory_corruption
     
    If this is the case, then two things:
    1. upload the minidumps as well. Just in case. (select them all, right click, send to -> compressed folder).
    2. run a memory test (memory diagnostics) on the system to ensure that the memory modules you're using are 100%.

      http://wiki.covecube.com/StableBit_DrivePool_Q537229

       

    I've also flagged the dump for Alex, so that he'll take an in depth look at it.

     

    Ok I've uploaded the mini dumps as well. One of them is dated the 3rd of July when I know the covefs.sys BSOD happend. I hope that sheds more light on this. I'm starting my memory check now and will report back when it's finished. Thanks again for looking into this. 

    Newly created DP seemingly causes BSOD when exposed to intense read/write

    in General

    Posted

    WhoCrashed is a good utility for diagnosing what is the cause, but not for figuring out specifically what is going wrong.

     

    So, I do believe that CoveFS (the DrivePool driver) is definitely involved here, but to what extent is hard to tell.

     

     

    And no worries. Enjoy you trip. When you get back, or get a chance, please upload the dumps (and the minidumps too, if you don't mind) and we'll try to see what exactly is going on.

    Will do. I should be able to get them uploaded tonight. I've been checking on my server and its been up for over 2 days now with no bsod. But it's been pretty well idle in terms of disk activity.

    Newly created DP seemingly causes BSOD when exposed to intense read/write

    in General

    Posted

    @bb12489,

     

    Well, CoveFS.sys would definitely be us.....

     

     

    Could you upload the memory dumps.

    http://wiki.covecube.com/StableBit_DrivePool_System_Crashes

     

    Make sure you post a link to the forum URL.

     

    Also, please run a memory test on the system.

    http://wiki.covecube.com/StableBit_DrivePool_Q537229

     

     

    Also, do you have any antivirus installed (such as Avast)? Or disk imaging tools?

    I don't run any anti virus on my server, and I've run memtest on all the sticks. They all appear to be fine. I'll definetly upload the dumps when I get a chance. I'm currently up in the Adirondacks camping g lol.

     

    Most of the time the bsod is cause by ntoskrnl, but accompanied by covefs.sys. or so says WhoCrashed.

    Newly created DP seemingly causes BSOD when exposed to intense read/write

    in General

    Posted

    I don't mean to bump a slightly older thread, but I am having this exact same issue with my drive pool as well! It appears that whenever the disks are under heavy read/writes it will bsod and reboot my server. I've check to see whats causing this from the dumps and it says its either covefs.sys or ntoskrnl. I thought this was memory related at first, but i've gone through many different sets now with the same results. 

     

    I'm running.... 

     

    Windows Server 2012 R2 Essentials

    Dual Xeon E5530's

    8GB DDR3 ram

    Mostly onboard sata for the pooled drives

    SSD for OS connected to a startech sata card

    5 pooled drives total.

     

    And I know my PSU is up to the task. 

     

    I'm on the latest StableBit DP which is the 2.1 final release. 

     

    If you need anymore info from me let me know!

×
×
  • Create New...