Jump to content
Covecube Inc.
  • Announcements

    • Christopher (Drashna)

      Login issues   11/07/17

      If you have issues with logging in, make sure you use your display name and not the "username" or email.  Or head here for more info.   http://community.covecube.com/index.php?/topic/3252-login-issues/  
    • Christopher (Drashna)

      Getting Help   11/07/17

      If you're experiencing problems with the software, the best way to get ahold of us is to head to https://stablebit.com/Contact, especially if this is a licensing issue.    Issues submitted there are checked first, and handled more aggressively. So, especially if the problem is urgent, please head over there first. 
  • 0
Arman

Nested pool mounting late during Windows startup procedure causing programs that rely on pool to freak out

Question

Hello Drashna,

First some backstory and context. I have 4 physical hard drives connected to my onboard SATA ports 1 through 4 (excluding my SSD which is my OS drive on SATA port 0) called:

  • Data 1
  • Data 2
  • Data 3
  • Data 4

These 4 drives are then pooled as such:

  • Data Original (which is comprised of Data 1 and Data 2 drives)
  • Data Duplicated (which is comprised of Data 3 and Data 4 drives)

These 2 pools are then further pooled and mounted as my D: drive (this pool is called "Data"). The reason for this structure is because I wanted to control which drives are used for original files and which drives are used in the duplication process so that my backup software doesn't backup the duplicated files because I can specify which volumes to be backed up (I use Veeam Endpoint Backup - now called Veeam Agent for Windows).

Moving on, I also have another 3 drives connected via USB which are pooled and mounted as my E: drive (this pool is called "Backup").

In total I have 3 volumes mounted and showing up in Windows - OS (C:), Data (D:), and Backup (E:).

Now during the normal Windows startup, my OS and Backup volumes mount instantly, however my Data volume takes around 45 seconds to mount. This causes some issues with programs that rely on that drive to have been mounted during startup. I have notices that the Drivepool service takes the same amount of time as my Data volume being mounted to startup.

My question is, what can I do to mount Data as instantly as Backup (which is also a pool) so that programs don't get unhappy when they cannot find paths located on Data? Is there a way to instantly start the service on Windows boot but before Windows login?

I have attached my Boot time log if that helps.

Some more info about my system:

  • My system is running Windows 10 Pro Creators Update with the latest updates installed.
  • I recently reinstalled Windows and all of my programs due to significant hardware changes.
  • Stablebit Drivepool is on version 2.2.0.877 Beta.
  • I also have Stablebit Scanner version 2.5.2.3129 Beta installed.
  • I do not have CloudDrive installed.
  • My SATA ports are using the Intel chipset.

Hopefully that's enough info to help out. Thanks in advance!

DrivePool.CoveFs.etl

DrivePool.CoveFsDisk.etl

Share this post


Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0

Well, we recently added some code that "messes" with the startup process, and that is likely what you are seeing. 

Thank you for getting the logs, as well!

Though, if you could, please run the StableBit Troubleshooter, as well.
http://wiki.covecube.com/StableBit_Troubleshooter
(use 3254 as the contact ID)

Share this post


Link to post
Share on other sites
  • 0

Great. So I assume that this would require me to wait for a new build to be released with the fixes implemented right?

In that case, is there anything I can do in the now or nope?

Share this post


Link to post
Share on other sites
  • 0

Yes.  

And without knowing why its doing this, there isn't a lot that can be done.  

Checking the event log, I'm seeing a few issues.  Namely VDS stuff that may indicate an issue. 
It may be worth checking the drives for errors, and stress testing the connection (or swapping out SATA cables. 

 

Share this post


Link to post
Share on other sites
  • 0

Hmm, I don't see any errors in Scanner nor do I see any SMART problems on any of the drives in the pool.

Also, burst testing using Scanner seems to saturate my ports to its max of around 500MB/s on average. There shouldn't be any problems with the SATA controller or cables as I had this issue with my previous motherboard as well (cables were different).

Any indication as to what these VDS errors are so maybe I can isolate the cause?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×