Jump to content
Covecube Inc.
  • 0
toxic

Measuring Every Boot, Very Slow During

Question

I've noticed every single time I reboot, the whole pool remeasures every disk, which takes ~3 hours to complete. During this time, the pool is borderline unusable. Launching a  Steam game installed to the pool may take 5 minutes or more to launch, and then stutter for a few seconds every 5 seconds or so (completely I/O starved). Even video playback can stutter, it seems the pool just has no leftover I/O to serve requests over the measuring. 

I understand that measuring has a high impact, but it doesn't seem like it should be this bad. It seems like outside I/O should have priority over the measuring. 

Secondly, I understand the pool shouldn't need to remeasure every reboot. Any way to troubleshoot why this is happening? It makes the machine pretty much unusable for hours after rebooting, which I need to do periodically for updates etc. 

The one thing I have which is a little unusual is the pool is all made of REFS disks. Is this possibly the culprit? Obviously moving back to NTFS would be quite an undertaking, though with Microsoft trying to drop support from the desktop versions of Win 10 it's certainly something I'm open to. 

Disks in the pool are: 

  • 1x8TB WD Red
  • 2x4TB WD Red
  • 1x4TB WD Black

EDIT: forgot to add that when the measuring is finished, the performance settles down and becomes pretty reasonable, comparable to a normal disk. So I've been trying to avoid reboots as much as possible not to have to render the machine unusable for hours at a time. 

I've also completely disabled the Windows Search Service (indexing), as I have no need for it and know it can cause performance impacts. 

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Measuring every boot is not typical, and indicates an issue.

Would you try installing this version?
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.3.953_x64_BETA.exe

If that doesn't help, enable boot logging, reproduce, and upload the logs:
http://wiki.covecube.com/StableBit_DrivePool_2.x_Boot_Time_Log_Collection

Also, if you could open a ticket at https://stablebit.com/contact

And then run the StableBit Troubleshooter on the system in question.
http://wiki.covecube.com/StableBit_Troubleshooter

Share this post


Link to post
Share on other sites
  • 0

Thanks Drashna, I've done as requested, the SR with attached logs and troubleshooter uploads (under suggested BETA version) should be in now. 

Share this post


Link to post
Share on other sites
  • 0

I still have a support job open about this, and I wasn't yet able to fix it. I've just been keeping the reboots to as minimum as possible and doing them as I go to bed when the measuring will not impact me. It's still a massive pain and I'd love to get it sorted. What filesystem are you using out of curiosity? 

I'm in the process of re-evaluating some things and may end up change my setup a bit. Issue being as well that Microsoft have blocked being able to format a drive REFS without the enterprise or 'pro for workstations' license, which I have neither. As such it's actually pretty difficult to format a new drive to add into the pool for me at the moment (running VM trial of enterprise to format the drive?). But If Microsoft are trying as hard as they are to stop me using REFS I'm a little hesitant to fight them on it and invest further. I'm sort of wondering what I should do next, maybe one by one redo the drives as NTFS and swap them back in (I have some juggle room to do this). Maybe recreate the pool from scratch as NTFS and migrate things over. 

I've also started using Snapraid for my largest and mostly static data, and that's given me a lot of extra space to play with, and Snapraid doesn't recommend using REFS https://www.snapraid.it/faq#fs either. I've also heard of REFS's failure mode in single drive mode is to just delete any damaged file silently (not likely an issue in a two way mirror in drivepool though), which would then be gone forever after the next snapraid sync, so I'd much rather have corrupt file so I can restore it. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...