Ablatem

@trurl - parity drive still healthy after 3 days. I will continue to keep an eye on it. Thanks again for your help.

@trurl - thanks for your response. I did acknowledge the CRC and it says healthy as of now. I will watch it for a couple of days and if nothing changes, I will close this.

Hello, I have one 18 TB parity drive that is showing - UDMA CRC error count. It just passed a parity check with no issues. Should this drive be replaced? I have 2 other 18 TB drives in an array. Thanks in advance for your time.

Thanks @Kilrah and @JorgeB for your assistance. I have been able to recreate my original VM's with no issues using the steps I mentioned above in the comment I marked as the solution. I appreciate the help.

I was able to restore a 'test' vm which looks fine. I created a new vm and used the same name as before as assigned CPU and RAM. The Primary vDisk location is set to Auto since it was using a valid path - /mnt/user/domains/RedHat/vdisk1.img Network Source is virbrO Network Model is virtio-net I didn't make any other changes. So far so good - I will take another look at it and then try a restore of another VM. Does this sounds like the correct process to use as far as recreating the vm's? Note: I had to change the Network Source to br0 - Network Model - left this the same - virtio-net This change gave me network connectivity. I will use this setting going forward.

Thanks for the reply, @JorgeB. I do have the old libvirt and I am pointing to it but I can't get any vm's to be listed. The libvirt.img file I have is 1.07 GB. Is there a documented process for recreating the VM's using the existing vdisk file? I am making a copy of one of my existing VM's vdisk and then I was going to attempt to recreate it. Could the network error I am seeing in the libvirt log be causing a problem with not being able to see the existing vm's?

I deleted the new libvirt.img file and made sure VM Manager was set to point to the original location. I disabled Docker and VM then I rebooted. When it came back online, I confirmed that the VM Manager location was the same and it was. I started Docker and VM. When I checked VM, there were still no VMs listed. I looked at the libvirt log and I see an error about the Network interface being already in use by interface br0 - I don't know where this is coming from because in VM Manager, the Default network source is virbr0 I see this under Libvirt volume info - Should I check Correct file system errors and click 'scrub'?

Hello, @Kilrah, Thanks for your response. I did not move the existing file before so I thought that could be the issue. I wanted to go back to the original location and that is when I saw no VM's. I just tried restarting the array and that didn't make any difference so I took another look at the locations. I see a problem - in both locations (/mnt/vms_nvme and /mnt/vms2_nvme) there are libvirt.img files - so 2 image files. Both are the same size - 1.07 GB I thought about what you mentioned about the file size being only 1 GB and I decided that it could be left where it is and I can move VM's from the original nvme over to the new nvme to make a little extra space. With that being said, I assume that now I need to delete the libvirt.img file located in the new location: /mnt/vms2_nvme - then restart the array again. I know what happens when you assume so can you confirm that?

Adding some information from the libvirt log I see the Network error but in the VM Manager the Default Network Source is virbr0

Hello, My goal was to move the Libvirt storage location from /mnt/vms_nvme/libvirt.img to a new larger NVME - /mnt/vms2_nvme/libvirt.img. I did not delete the image file from the original location or delete any other files. I disabled VM using VM Manager and updated the location to /mnt/vms2_nvme/libvirt.img and then I enabled VM. When I checked VM's there was nothing there and then I thought it was because there was no libvirt.img file in the new location. I wanted to go back to the original location and when I did that, there were still no VM's listed. Is there a way I can restore my original setup? I have attached the diagnostics for your review. Thanks in advance for anyone who can help. frankenstein-diagnostics-20231208-1141.zip

I ended up updating the 'Folders' app and use 'FolderView' instead. I also updated to 6.12.6 which didn't affect the docker issue. Once I installed FolderView, I was able to mange the containers 'normally'. I could start, stop and pause and I can also create folders once again so I can organize my containers.

It looks like I have resolved this. I will do some additional tests and then update the ticket with what I did that resolved this issue.

fyi - I just updated to 6.12.5 and I see the same behavior

In Unraid 6.12.4, a couple of days ago, I noticed the folder structure I had created in Docker was 'gone'. It had reverted back to the standard list structure. The option to create a folder on the Docker screen was gone. In addition to this, I am unable to remove a container using the menu items when clicking on the Docker icon. When I click Remove, I see the 'Are you sure? window and I check the box to also remove image. Then I click 'Yes, delete it!' and nothing happens. The button highlights when I select it but when I click it - nothing happens. I am not able to start or stop a container using the corresponding item choices by clicking on the container icon. I restarted the Unraid server which made no difference. I manually stopped the parity check that started after the restart. I attached the diagnostics for your review. Thanks in advance for any help provided. frankenstein-diagnostics-20231126-1228.zip

I was able to test this on a Windows 2016 server that had the same issue. I generated a mac address and then made the network changes: I was able to Update this with no problem. I checked the Device Manager on the vm and the network connection was there and working fine! Thanks for your help!!! Rick