Jump to content
Covecube Inc.

Erik Wright

  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Erik Wright

  1. I actually have WinDBG installed and attempted to analyze the dumpfiles myself, but only see covefs.sys in my analysis.


    Then again, bugchecks are a little out of my territory, and I know they're not always correct, so I'll leave it to Alex to take a look at.



    Just for giggles, I moved my DropBox folder to the only internal HDD not in a DrivePool disk pool and I get no bluescreens, so this further confirms the suspicion that DropBox is making calls that DrivePool doesn't like.


    Anywho, I'll keep an eye on this thread when you guys have an update or a beta release for me to test. No need to reply until then though. :) Thanks!

  2. @Erik,


    Looks like the process that triggered this was dropbox, in your case.


    That said, troubleshooting Insider builds is problematic, at best, because the issue may be resolved in the next build (we've seen happen a few times, actually). 


    However, if this is still occurring on the build, then let me know and grab the dumps again. 


    Hey @Christopher, thanks for looking into my bugcheck - I know Insider Builds can be rather difficult to diagnose because things change a lot.

    The Event Viewer does show a lot of errors related to DbxSvc, so I'm with you there. It seems to be a DropBox conflict of some kind.

    • Failed to connect to the driver: (-2147024894) The system cannot find the file specified.
    • Failed to open file: C:\WINDOWS\Minidump\fd50d22e-5d8d-473d-85e0-c35cbd90b141.dmp, error: (2) The system cannot find the file specified.
    • Failed to get ANSI path for file: C:\WINDOWS\Minidump\fd50d22e-5d8d-473d-85e0-c35cbd90b141.dmp


    I rebooted to install Windows 10 Version 1703 Build 16188.rs_prerelease.170430-1928 after disabling the DrivePool service, just in case. It installed fine.

    After logging in, I went to check this forum thread, and enabled the DrivePool service. DropBox was running at the time too. I BSOD'd twice.


    Since then, I have done the following:

    • Enabled the DrivePool service in services.msc and checked to see that it's running via the DrivePool app
    • Closed and completely exited DropBox from the system tray, and disabled the DbxSvc from services.msc

    I've also attached the 2 additional bugchecks in another ZIP from lunchtime today, just in case they help shed some light on the situation.


    If you don't mind my asking, what revealed it was DropBox in my bugchecks?

    I want to head on over to their support community and let them know about the issue so they can fix it, as I use DropBox for work, so I kind of need it... :P


  3. Well, the CoveFS.sys is definitely the pool driver. 


    This is for StableBit DrivePool, correct? 

    If so, could you try this version: 




    This version addresses a number of issues, including some that can cause BSODs. 



    As for the "WUDF" error, this is normal, and harmless. And the linked version may actually fix this issue as well. 


    I hate to be that guy who posts in someone else's thread rather than starting my own, but I too just recently started having the exact same issues so I figured I'd tack on my two bits.


    Now, to be fair, I'm running the Fast Ring Insider Build of Windows 10, specifically Windows 10 Version 1703 Build 16179.rs_prerelease.170414-1642 so that might have something to do with it.

    I've had 3 BSOD's today alone (they're actually Green Screens of Death due to running Insider Preview Builds, but I digress) all pointing to covefs.sys as the culprit.

    If I manually disable the StableBit DrivePool service from my services.msc list, I don't experience the crashes, so that really points things in the right direction.


    Here's what I'm going to do though:

    • I'll update DrivePool from 2.2.676 to the latest beta, in this case, and report back with my results.
    • I should also check my event log as @chamelious has done to make sure nothing weird is going on, so I'll do that next reboot.
    • Tonight I'm going to install Insider Build 16188.1000 as well, so we'll see how that goes with the updated DrivePool software.

    Attached is a zip containing my Minidump files and other diagnostic information as collected by the DM_log_collector tool from tenforums.com, just in case you wanted to take a look.


  4. Just to make sure about hard links.

    All the drives in my server, that belong to the pool - they are not mounted to drive letters. I have them mounted to folders in D:\Drives

    So, how would DrivePool react/handle these 2 situations, below. Bare in mind, I would create the hardlinks manually and I would not do it through the pool, but through the individual mountpoints in D:\Drives. Which I guess, should work, as I would be on the same drive?

    1. hardlinks from files inside the pool to inside the pool, eg........:   D:\Drives\drive01\PoolPart.xxxxx\Sports\F1\original.mkv  -->  D:\Drives\drive01\PoolPart.xxxxx\Sports\Whatever\linked.mkv
    2. hardlinks from files inside the pool to outside of the pool, eg..:   D:\Drives\drive01\PoolPart.xxxxx\Sports\F1\original.mkv  -->  D:\Drives\drive01\Whatever\linked.mkv

    I guess in the first scenario, there may be trouble with duplication, and/or used/free space calculations?

    Although in the second scenario, I can't find the reason, why it should not work without problems?

    Chris, some wisdom, please :)


    I've been trying to live without hardlinks for over the year now, since I started using DrivePool - and it sucks. TBH, if drivepool does not support hardlinks at all (even in any of these two scenarios), I'm afraid it's gonna be a deal breaker for me, sooner rather than later...


    Thanks in advance for any help.


    I currently have 2 hardlinks between my Dropbox folder, located on the pool, and AppData folder, located on my Windows Boot SSD, not part of any pools.

    The purpose is to keep a games' data folder (in AppData) syncronized with DropBox (stored on one of my pools) as it contains recording files for said game.

    I also created a couple of hardlinks from folders within a pool for the purposes of testing that functionality as well.


    I have not yet noticed any issues or oddities with this setup, nor have I noticed duplicated duplicate problems either.

    Bear in mind that I have my pools mapped as drive letters, so that may affect your results.


    Edited Update: I tried mounting my pooled drives in C:\_DISKS\d03_3TB-SERIALNO\PoolPart.PARTNO and C:\_DISKS\d04_3TB-BKP-SERIALNO\PoolPart.PARTNO to test things out.

    The mapped hardlinks appeared to work just fine, both updating between folders on the pool, and from the AppData folder on my Windows Boot SSD.

  5. To build upon @B00ze's question, how would one use 2 SSD's and 1 HDD to maintain the best possible write speeds with 3x file duplication enabled?


    Specifically, I have dual 500GB Crucial MX200 SSD's and a single 500GB Hitachi Deskstar P7K500 HDD in my system, configured as a single pool.

    I've added the 500GB HDD (hooked up over eSata) to keep a 3rd external copy of my data that I can grab and go in case of fire or other emergency.


    Before adding the HDD to the pool, I consistently got around 500MB/s write and 1100MB/s read speeds (with read striping enabled) on the pool.

    Even with configuring the SSD optimizer, I cannot obtain fast write speeds without disabling 3x duplication on the pool, or disabling real-time duplication.

    I understand this is by design, or I've possibly configured the pool settings incorrectly, however...


    Is there a way to tell DrivePool to write all the initial data ONLY to the SSD's, and then write the 3rd copy of the data to the slower HDD later?

    Or should I just remove the HDD from the pool, and use some other backup software to create weekly backups from the pool to the HDD separately?

  6. I'd like to remove my external Seagate USB 3.0 hard drive from it's case (probably have to destroy the case it to do this) and stick it into my Orico eSATA 5-bay.  Will drive pool see this drive correctly?


    This depends heavily on the conroller/bridge chip for the enclosure. 


    I believe that it shouldn't be an issue, but can't be sure.  

    Specifically, as long as the contents can be seen on the other enclosure, there will be no issue. But if the enclosure is "messing" with the data, then you'd need to remove the drive from the pool, move it and then re-add it to the pool.


    From my 5 years both selling consumer electronics and repairing computers in a retail situation, I've yet to come across a Seagate drive with any fancy trickery going on under the hood.

    Usually its the Western Digital drives that have circuit boards with hardware encryption chips built in that cause the drive to appear scrambled when not used inside its' original enclosure.


    A useful feature for data security and encryption for sure, but very annoying if say the enclosure or drive begins to fail and you want to try to save the data...


    *Western Digital drives that have these logic boards can be used outside of their enclosures, but they must be re-formatted once taken out of their enclosure.

  • Create New...