So I'm struggling since hours

I had my server running for month on intel system with no issues

I've updated to a ryzen system with ryzen 7 2700 , gigabyte ga ax-370 gaming 5

system online, array is working, docker aswell

all drives seems good with no smart errors

parity is valid

BUT when I try to start libvirt it cause the array to crash with drives going faulty and VM and isos storage being unavailable.

all drives then go to unassign devices

 

I really don't understand what is happening

I've updated from 6.6.6 to 6.6.7 with no success

 

So if anybody can help it will be much appreciated

serveur-diagnostics-20190223-1956.zip

Edited February 23, 20197 yr by salora

Feb 23 20:18:28 Serveur kernel: md: disk0 read error, sector=972118240
Feb 23 20:18:28 Serveur kernel: md: disk1 read error, sector=972118248
Feb 23 20:18:28 Serveur kernel: md: disk2 read error, sector=972118248
Feb 23 20:18:28 Serveur kernel: md: disk3 read error, sector=972118248
Feb 23 20:18:28 Serveur kernel: md: disk4 read error, sector=972118248
 

I got this repeat after trying to start libvirt

And I attached another diag file from after the crash

serveur-diagnostics-20190223-2019.zip

Same in safe mode 😥

So I'm able to start libvirt and create VM's if I do not load my old VM's by changing the default storage path

So my guess is an "old" VM is causing the trouble

maybe I did let one in autostart

So new question how do I disable an autostart VM without starting libvirt?

thanks

are you doing a gpu passthrough? Is the config messed up where its trying to pass through your sata controller instead?

thanks

no there was no passthrough on the one that might be on autostart

but I figure this out by deleting the libvirt image and rebuilding all my vm's

so problem solved I would say

last time I had a server upgrade it was from an I3 to an I5 and it went smoothly

this time it's from I5 to Ryzen so it's a bit more complicated