I went from a VERY old version of 5 to 6.5.5. It was an ESXi install with UNRAID as a VM. I wanted to try using UNRAID only. So now it boots and I see all my drives. I had to do a rebuild of one drive as I didn't realize it was in an error state being emulated. Docker didn't work at first and I had to set some paths and now that works. The VMS tab just shows 'Libvirt Service failed to start.' I've searched the forums and couldn't figure out what the deal is. I've attached my diag file.

 

Other things of note. the server has 72GB of memory but it is only showing 48GB. Not sure why on this?!?!?

 

Any help is appreciated. 

tower-diagnostics-20181127-1638.zip

Edited November 28, 20187 yr by jay2068
Marked Solved. Thanks!

Rebooted and reset my bios to a slower memory and now I have 60GB  so looks like i may have some memory issues after I upgraded the motherboard BIOS.

 

Still no luck on VMS  

Your parity disk is showing lots of read errors and needs to be replaced.

 

You're actually running version 6.6.5, not 6.5.5.

 

Linux is only seeing 48 GiB of RAM. Maybe you have an unsupported combination of DIMMs.

 

I don't see any attempt to mount the libvirt.img in your syslog. Perhaps disabling VMs and re-enabling them will fix.

libvirt.img location is not correctly configured, you need to specify the file, not a folder, currently it is:

 

IMAGE_FILE="/mnt/cache/"

it should be for example

IMAGE_FILE="/mnt/cache/system/libvirt.img"

 

 

 

Edited November 28, 20187 yr by johnnie.black

47 minutes ago, johnnie.black said:

libvirt.img location is not correctly configured, you need to specify the file, not a folder, currently it is:

 

IMAGE_FILE="/mnt/cache/"

it should be for example

IMAGE_FILE="/mnt/cache/system/libvirt.img"

 

 

 

That fixed it! Awesome! Thanks for the easy fix!

 

Yep I checked all my RAM and I have mismatched speeds so I need to slow it down or replace all the slower ones.

 

Thanks also on the Parity disk. I'll replace it ASAP.