Parity drive reported as disabled when try to start VM

[fireplex]

Have a strange issue.

 

When I try and start one of my Windows VMs unRAID GUI reports an I/O error accessing the VirtIO drivers which are on a share /mnt/user/Downloads, and the VM fails to start.

 

Then, I see that the parity disk is disabled?.....

 

To try and resolve the issue I have already tried:

 

1. Shutdown & poweroff

2. Reseat all SATA cables

3. Stop array, unassign parity drive

4. Start array so parity drive forgot

5. Stop array, assign parity drive

6. After 7hrs odd parity drive is rebuilt with zero hours reported anywhere

 

After I try and start the VM I see in syslog:

 

Jul 25 22:19:10 Tower kernel: ata7.00: disabled
Jul 25 22:19:10 Tower kernel: print_req_error: I/O error, dev sdg, sector 244304594
Jul 25 22:19:10 Tower kernel: XFS (sdg1): metadata I/O error: block 0xe8fca92 ("xlog_iodone") error 5 numblks 64
Jul 25 22:19:10 Tower kernel: XFS (sdg1): xfs_do_force_shutdown(0x2) called from line 1232 of file fs/xfs/xfs_log.c.  Return address = 0xffffffffa023f5de
Jul 25 22:19:10 Tower kernel: XFS (sdg1): Log I/O Error Detected.  Shutting down filesystem
Jul 25 22:19:10 Tower kernel: XFS (sdg1): Please umount the filesystem and rectify the problem(s)
Jul 25 22:19:10 Tower kernel: sd 7:0:0:0: [sdg] Synchronizing SCSI cache
Jul 25 22:19:10 Tower kernel: sd 7:0:0:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00

 

sdg is my parity drive so:

 

7. Start drive maintenance mode, run a xfs_repair on the cache XFS drive - all OK

8. Run SMART test, all OK

 

 

Any ideas what is wrong, how to fix and especially why the parity drive is disabled when it appears the issue is related to my cache drive ?

 

Diagnostics attached.

 

Thanks.

 

edit: left the system running memtest86 overnight although a quick test everything seemed fine

 

tower-diagnostics-20180725-2222.zip

Edited July 25, 2018 by fireplex

[JorgeB]

My guess would be that you're wrongly passing though the Asmedia controller to your VM, so when it start's it causes problems with both devices there connected, parity and cache.

[fireplex]

I have been using this same VM config for over a year without any issues so doubt its that.

[JorgeB]

Did you change any hardware, including adding or removing PCIe devices, or did a bios update? If yes that can change the device numbers, check or post the XML, the Asmedia controller is device 06:00.0