Parity errors if a VM with unassiged drive is running


Michael_P

Recommended Posts

I had a bunch of problems last year after setting up my server - but after I stopped assigning "unassigned devices" drives to my VMs the server completed monthly parity checks without any more problems. Until today that is. Over the weekend, I installed a 3TB WD Purple and assigned it to my Windows 10 VM for Blue Iris to use. No bubbles, no troubles.

 

Today, immediately at the start of the monthly parity check, Unraid drops disk 2 with 4096 errors.  Being the impatient hot-head that I am, I didn't grab diags before starting the rebuild, sorry.

 

If the VM with the UA drive is stopped, the partiy check finishes no errors. If a VM is up with a UA drive attached, it will drop a disk. Every time. And it's a different drive every time. Tested with a WHS 2011 VM and now a W10 VM.

 

Server runs fine if I'm not using unassigned devices, but I really would like to use a VM to run Blue Iris than build a machine just for it. Especially when the server is sitting close to idle all the time.

 

Thoughts?

 

Initial problems outlined in this thread

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  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.