Reoccurring read errors on parity check

[Maddeen]

Hi, 

 

hope some one can help me because I dont understand it. 

 

For the time of my "normal" usage I doesn't get any errors. But on every parity check (timed for every month) I get read errors on Disk1 and Disk2.

Additionally the drives seems to bring themselves into an undefined state which results in millions of reads and writes - due to the GUI (see Screenshot) - constantly counting up. 

Not sure if this is "real" or just a bug. But after a reboot everything is fine -- for the following days until the next parity check

 

If I run SMART test (normal and extended) I dont get any errors.

 

I`m running 6.9.0 beta 30

 

Thanks for any help. Have a nice day.

 

v1ew-s0urce-diagnostics-20201214-0910.zip

[Vr2Io]

1 hour ago, Maddeen said:

Not sure if this is "real" or just a bug.

It is real not bug. Disk 1 and 2 connect to one of FCH SATA controller ( you have two ). Could you try disable IOMMU or some tweak relate AMD SATA controller about IOMMU.

 

Or disconnect SSD then connect both disk to those port, so all disk in same FCH SATA controller, then try parity check again.

Edited December 14, 2020 by Vr2Io

[JorgeB]

Disks 1 and 2 got dropped:

Dec 12 23:14:14 v1ew-s0urce kernel: ata3.00: disabled
Dec 12 23:14:14 v1ew-s0urce kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Dec 12 23:14:14 v1ew-s0urce kernel: sd 3:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Dec 12 23:14:14 v1ew-s0urce kernel: sd 3:0:0:0: [sdb] Stopping disk
Dec 12 23:14:14 v1ew-s0urce kernel: sd 3:0:0:0: [sdb] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
Dec 12 23:14:14 v1ew-s0urce kernel: ata4.00: disabled
Dec 12 23:14:14 v1ew-s0urce rc.diskinfo[8888]: SIGHUP received, forcing refresh of disks info.
Dec 12 23:14:14 v1ew-s0urce kernel: sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Dec 12 23:14:14 v1ew-s0urce kernel: sd 4:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Dec 12 23:14:14 v1ew-s0urce kernel: sd 4:0:0:0: [sdc] Stopping disk
Dec 12 23:14:14 v1ew-s0urce kernel: sd 4:0:0:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00

 

Because you're passing-though their controller to a Windows VM:

-device vfio-pci,host=0000:06:00.0,id=hostdev0,bus=pci.9,addr=0x0 \

 

 

[Maddeen]

@Vr2Io @JorgeB

Now you confuse me - I don't pass through the SATA device as far as I know - or see in the GUI. 

For my VM I just need to passthrough my nvme controller and my NVIDIA GPU - see screen. 

 

Maybe there is a difference between the GUI-View and the one in the cli-configuration. (maybe a bug??)

 

I cant disable IOMMU because then I cant use my Gaming-VM. That's not an option -.. or I misunderstood your advice.

 

For additional information about my VM I attached the xml for devices.

  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.185.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0xc'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0xd'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0xe'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
    </controller>
    <controller type='pci' index='9' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='9' port='0xf'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
    </controller>
    <controller type='pci' index='10' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='10' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:be:94:98'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/rtx2060s.dump'/>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x2'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x2'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x3'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x3'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>

 

 

Edited December 14, 2020 by Maddeen

[Maddeen]

15 minutes ago, Maddeen said:

<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev>

Ok... seems that this lines causes the error right? 
Not sure why them are in my config...but I had changed my mainboard and cpu .. and not checked the vm configuration. 

 

Can I just delete the lines within this <hostdev/></hostdev>?

[JorgeB]

58 minutes ago, Maddeen said:

<address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>

This is a SATA controller.

 

This one:

 

[Maddeen]

ok - i deleted it and start my vm. No problem for now.

Seems that this was a legacy from my previous build because I didn't check if any IOMMU entries has changed.

 

@JorgeB may I ask you one more question.

So after this problem, I think I need to check every entry in my vm-xml that reference to any IOMMU and doublecheck if this still needed, right?

 

 

[JorgeB]

From what I remember besides the SATA controller it was only passing-trhoug a USB controller and a GPU, so it should be fine, but you should check.