Whenever I enable the VM manager in settings my CPU cores will spike and the system will freeze requiring an unclean shutdown to escape from it.  I was eventually able to disable the auto start (by editing config/disk.cfg on the flash drive) which allowed me to access the VM manager and shut that down too.  If I turn it on then it just grinds to a halt.

How did I get here?  I had some drive failure issues on my elderly server.  The cache with appdata and domain decided it had no data on it.  Despite the drive showing healthy and indicating it was full of data, searching it from the CLI revealed it to be empty.  Also the parity drive quit within a few days of that.  Since the old server was circa 2010 it was time for a new build so I put a new mobo in a new case and I'm trying to rebuild everything.   I plugged the offending cache into a different computer and saw my data was still there so I was able to recover it and I tried to move it back into the user shares via the cli.  Later I got into file tree hell in the appdata and added the ssd back to a new pool and the array could see the data again in the new system so I let the mover finish it off.

I've already let the mover put the system and domain shares onto the new zfs cache pools so I don't think it's slow array speeds causing the freezing or the cpu cores spiking

PLS HALP - I need services from unraid

fractaltower-diagnostics-20241026-1828.zip

Edited October 27, 20241 yr by clay_statue

Were any VMs autostarting?

FOR FUTURE THREAD HUNTERS AND INTREPID PROBLEM SOLVERS... THIS HAS BEEN SOLVED

 

As JorgeB suggested there were VM's autostarting, but I couldn't get to the VM screen to turn them off before it would freeze up.

To remedy autostarting from CLI (within /mnt/user/domains):
 

$mv yourVM/yourdisk.img disabled_yourVM/yourdisk.img

This didn't solve the problem but it may solve yours.

What was ACTUALLY my PROBLEM was that the system/libvirt/libvirt.img file must've been bad.  I deleted it from the advanced settings in VM Manager and now I need to rebuild all my VM xml files BUT it solved my problem!  I can now enable VM services without immediately borking my server.  At least this gives me a point to rebuild from vs being entirely unable to even interface with the server because it starts screaming as soon as I enable VM Manager

LESSON BEING CRITICAL BACKUPS FOR SERVICES -- APPDATA DOMAINS SYSTEM

My previous backup method of an external usb drive which got disabled because it was unplugged when the server was moved briefly to change the attic air filter so my backups are too far out of date to be useful.  New server will have raidz pools in cache so I can snapshot everything to the array and also rsync it to somewhere else.