Slow VM tab and virNetSocketReadWire error in logs

[TurkeyPerson]

 Hi all,

My VM tab has been loading very very slowly and I can't seem to figure out why. 

Furthermore, and I'm not actually sure if the two issues are related, I noticed the following error constantly repeating in my logs: 
 

virNetSocketReadWire:1791 : End of file while reading data: Input/output error

I did some research and I found that a few people have posted about this error over the last three or so years, but they either never get a response, or mysteriously stop responding when asked to post their diagnostics. I've attached my diagnostics to break the cycle!

In the interest of providing a maximum of information I'll mention a few seemingly unrelated issues I've run into in the last two years or so: 
- Corrupted USB (has happened 3 times -- I actually switched USBs and it happened again)
- Some SMART errors -- I think these were related to a loose cable
- Corruption in my dockers -- deleted and recreated

In fact, writing all that out makes me feel like I should probably do some tests on my ram -- thoughts? (sorry for the tangent!)

Your help is greatly appreciated!

tower-diagnostics-20230121-1753.ziptower-diagnostics-20230121-1753.zip

[JorgeB]

There are multiple apps segfaulting in the log, good idea to run memtest.

[TurkeyPerson]

Thank you, I'll get on that this week and report back.

 

Where did you see the errors BTW? Would be useful for me to check more regularly I think.

 

The dashboard and vms stopped responding so I restarted. I checked syslog after and found this:

 

Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.4:   device [8086:a294] error status/mask=00000001/00002000
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.4:    [ 0] RxErr                 
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:09:00.0: hcc params 0x0200ef80 hci version 0x110 quirks 0x0000000000800010
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:09:00.0: xHCI Host Controller
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:09:00.0: new USB bus registered, assigned bus number 6
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:09:00.0: Host supports USB 3.1 Enhanced SuperSpeed
Jan 22 18:04:19 Tower kernel: hub 5-0:1.0: USB hub found
Jan 22 18:04:19 Tower kernel: hub 5-0:1.0: 2 ports detected
Jan 22 18:04:19 Tower kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Jan 22 18:04:19 Tower kernel: hub 6-0:1.0: USB hub found
Jan 22 18:04:19 Tower kernel: hub 6-0:1.0: 2 ports detected
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:0a:00.0: xHCI Host Controller
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:0a:00.0: new USB bus registered, assigned bus number 7
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.6:   device [8086:a296] error status/mask=00000001/00002000
Jan 22 18:04:19 Tower kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                 
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:0a:00.0: hcc params 0x0200ef80 hci version 0x110 quirks 0x0000000000800010
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:0a:00.0: xHCI Host Controller
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:0a:00.0: new USB bus registered, assigned bus number 8
Jan 22 18:04:19 Tower kernel: xhci_hcd 0000:0a:00.0: Host supports USB 3.1 Enhanced SuperSpeed

Edited January 22, 2023 by TurkeyPerson

[JorgeB]

11 hours ago, TurkeyPerson said:

Where did you see the errors BTW?

In the syslog

[TurkeyPerson]

Hi, 

 

As it turns out, I got many errors within the first hour running memtest.

 

Second RAM issue in the lastt year (other one was a different PC) - never had bad ram prior, perhaps I got hit with some savage solar radiation or something. Anyway, going to RMA and to avoid downtime, take the opportunity to upgrade!

 

Quick follow up: what should I do after?

I believe unraid has a method of checking the arrays for corruption. I suppose I should do that, recreate my VMs, and run diskcheck (or whatever else as the case may be) from inside each VM? Is there a better approach?

 

Thanks again!