Hi Folks,

 

I posted this in the Preclear plug in thread but I am not sure this is a Preclear issue.

 

I was preclearing a drive and when I started up the Windows 10 VM Preclear stopped.  This is my first time using Preclear.  This is also the first time I am using a new LSI 9211-8i controller card in IT mode for this drive although it seems to be operating nominally.

tower-diagnostics-20170721-1434 (3).zip

TOWER-preclear.disk-20170721-1427 (2).zip

This is what I see from your post

 

Preclear was running

You started a VM, and preclear stopped.

 

This is what I see from your diagnostics

 

You attempted to start a VM, and the VM never actually started

The 9211 appears to have reinitialized itself at the time the VM tried to start.

You have a 1080i video card attached.

 

This is what I'm inferring:

 

This is the first time you've attempted to start the VM since installing the 9211.  Previously the VM was working.  

 

When you installed the 9211, it has bumped up the address of the 1080i from what was originally 03:00.0 & 03:00.1 to now be 04:00.0 and 04:00.1 but the VM is still referencing 03:00.x (which is now the 9211)

 

Edit the VM, and re-set up the video card passthrough and everything should be good to go. 

Edited July 23, 20178 yr by Squid

The VM runs with the 9211 installed and the new drive shows up as Unassigned.  However, when I run Preclear and launch the VM, the VM runs but I now get the message "no unassigned disks available" in Unassigned Devices instead of a preclear progress indicator for the new drive.  Once I reboot the drive shows up again in Unassigned Devices with no way to resume preclear.  BTW I previously modified the VM so that the video card is now showing 04:00.0 and 04:00.1 and the controller card is at 03:00.0 per you advice here.

 

I replicated the event and reran diagnostics

tower-diagnostics-20170723-1250.zip

TOWER-preclear.disk-20170723-1251.zip

On 7/22/2017 at 5:17 PM, Squid said:

 

This is what I see from your diagnostics

 

The 9211 appears to have reinitialized itself at the time the VM tried to start.

You have a 1080i video card attached.

 

Can you point out where in the log you see this.  Does it also show up in the more recent logs I posted above.

 

Mike

Just to follow up:

 

Prior to Squid's post above, I had previously edited the VM and selected the "Graphics Card" at 04:00.0 and "Sound Card" at 04:00.1 with the controller card showing up as 03:00.0 in "Other PCI Devices".  Both the VM and the controller card worked independently.  However, whenever I started the VM during Preclear, Preclear would stop.  Having not received an answer to this issue, I decided to just go ahead and use Preclear without using the VM until it was complete.  That worked and I have added the new drive to the array.  However, now when I look at the VM, the controller card is no longer showing up in "Other PCI Devices" and is blank.  Everything seems to be working fine now.  I'll try again whenever I add a new drive and if it doesn't work I will just be resigned to using Preclear without using the VM.

tower-diagnostics-20170728-1042.zip

First, let me say that I don't believe this was a problem with the Preclear plugin but was a problem with the controller card pass through.  Of course this is speculation on my part and I defer to the experts.

 

The problem (revised)

 

I mounted the new drive to the array and the system rebuilt/parity checked it taking about 13 hours.  The disk showed up as a green dot on the Main page when that completed.  I then ran the Windows 10 VM at which time I got a red X on the new drive.  Before running the VM the controller card was not showing up in the VM under "Other PCI Devices".  After running the VM and getting the red X the new controller card showed up under "Other PCI Devices".  

 

What I did

 

I removed the controller card from the VM by unchecking the box next to it in "Other PCI Devices".  I then unmounted the new drive and remounted it forcing a rebuild.  The drive then showed up as a green dot again.  Now I can launch the VM or reboot the system and the new drive seems to be nominal.  The new controller card no longer shows up as a host device at 03:00.0 in the XML but is still assigned to that slot in the IOMMU groupings.

 

Question

 

Is what I did OK or have I created another problem?  I ran Fix Common Problems and it shows no problems.

 

I would appreciate it if someone could take a quick look and let me know if I am good to go.

 

tower-diagnostics-20170731-1012.zip