Hi,

 

Recently I have a lot of strange issues with my server. For one, libvirt does not start ever since v6 b12. I have to invoke it using /etc/rc.libvirt start. When I do this, the VM manager doesn't start and I lose the dashboard.

 

Also scheduled parity checks at the beginning of the month are not running.

 

I had a few power outages recently and the server did not shutdown.

 

I am also not getting any emails with notifications of any of these events.

 

It seems to me like my entire plugins are totally broken.

 

I've installed a lot of betas and I think there must be remnants of all sorts of things on the server which are causing this. It seems like the best thing to do is to start fresh with a clean install of 6.13.

 

I know I need my disk.cfg and share.cfg. I'll backup my flash drive also...just wondering if there is anything I am missing before I do this. Thanks.

Actually you don't need anything except your key file (Pro.key).

 

You DO need to know which disk is the parity disk and which disk(s) are used for cache.

 

Other than that you can assign the data disks in any order you want [if you want them to have the same #'s as now, just save a copy of your Web GUI display showing all of the disk assignments -- a good idea to do that anyway].

 

Then simply save your key file;  reformat the USB flash drive (be sure the label is "UNRAID"); copy the v6.1.3 download to it; and run make_bootable from an elevated command prompt (i.e. run the command prompt with administrative privileges).    Then copy the key file to the config folder; and you can then boot to the flash drive and assign all of your disks.

 

If you run a parity check BEFORE doing all that and have zero sync corrections, you can also check the "Parity is already valid" box after you've assigned the disks and before you start the array.

 

Thank you Gary!

As to the notifications and monthly parity check, 6.1 introduced a number of changes for security reasons, that impacted them.  Just go into Notifications and change something and re-apply, and do the same in the Monthly Parity Check schedule.  That should reset them correctly, and get them working again.

As to the notifications and monthly parity check, 6.1 introduced a number of changes for security reasons, that impacted them.  Just go into Notifications and change something and re-apply, and do the same in the Monthly Parity Check schedule.  That should reset them correctly, and get them working again.

 

Thanks, looks like they are working again. Any ideas why libvirt has to be started manually?

As to the notifications and monthly parity check, 6.1 introduced a number of changes for security reasons, that impacted them.  Just go into Notifications and change something and re-apply, and do the same in the Monthly Parity Check schedule.  That should reset them correctly, and get them working again.

 

Thanks, looks like they are working again. Any ideas why libvirt has to be started manually?

 

Starting and stopping the array will also start and stop libvirt, there shouldn't be any need to do this manually.

 

As to the notifications and monthly parity check, 6.1 introduced a number of changes for security reasons, that impacted them.  Just go into Notifications and change something and re-apply, and do the same in the Monthly Parity Check schedule.  That should reset them correctly, and get them working again.

 

Thanks, looks like they are working again. Any ideas why libvirt has to be started manually?

So did you actually do a clean install, or did you just get things mostly working?

So did you actually do a clean install, or did you just get things mostly working?

 

I haven't yet because things are now mostly working. If I could solve the libvirt issue then I think I would be ok. The UPS stuff seems to have sorted itself also by the same trick with the notifications and parity check.

 

Starting and stopping the array will also start and stop libvirt, there shouldn't be any need to do this manually.

 

 

Interesting, I'll give this a shot. Why would libvirt not start when unraid boots?

What do you get with

virsh --version

What do you get with

virsh --version

 

1.2.18

So did you actually do a clean install, or did you just get things mostly working?

 

I haven't yet because things are now mostly working. If I could solve the libvirt issue then I think I would be ok. The UPS stuff seems to have sorted itself also by the same trick with the notifications and parity check.

 

Starting and stopping the array will also start and stop libvirt, there shouldn't be any need to do this manually.

 

 

Interesting, I'll give this a shot. Why would libvirt not start when unraid boots?

 

Maybe this helps someone at some point. I did end up figuring out what the problem was which was causing libvirt to not start. It turns out that my /boot/config/plugins/domains.cfg file had somehow got corrupted. I deleted it and allowed unraid to recreate it. Everything is good now and I can control my VMs through the webgui and I don't need to start libvirt manually.