VM crashing and VM share disappears

[blewstar]

Hello everyone,

 

I made the update version from 6.92 to latest version. My VM is crashing and I have noticed that my "Domain Share" is being removed. However, I reboot and it comes back. I can use the VM for hours and then walk away and it crashes. When I try to start the VM before rebooting I received the errors 

 

internal error: qemu unexpectedly closed the monitor: 2023-12-26T20:43:57.775837Z qemu-system-x86_64: Could not open '/etc/libvirt/qemu/nvram/30595530-640e-414c-535d-3361c45c54a0_VARS-pure-efi.fd': Read-only file system

 

The following error I just stayed at the log in screen:

 

internal error: process exited while connecting to monitor: 2023-12-27T01:48:33.861571Z qemu-system-x86_64: Could not open '/etc/libvirt/qemu/nvram/30595530-640e-414c-535d-3361c45c54a0_VARS-pure-efi.fd': Read-only file system

 

I believe this is refering to a full cache or disk. I really don't know how to properly read the storage to determine where I am having the problem. There was no issue before the update so scratching my head here. I have sinced removed all vm vdisk except the one I am using freeing up about 120 GB. The issue is still there. 

 

Could I ask the communitys help on what screen shots or tools I use to provide the information needed to troubleshoot this? I'm not sure if I use paint to copy the screen for main, domain, vm edit/xml etc...

 

Thank you for any help!

 

 

 

[christobaass]

Also running into this issue. You figure anything out?

[blewstar]

Thought I would update some information on this issue of what I have done so far. With a good friend of mine that is more knowledgable with unraid we started from scratch. 

 

1. Made sure that the VM has the right binds set up. This also looked at the grouping without separating the gpu in its own group

2. Disabled vm and docker as well as services

3. Checked settings> fix common problems (app) for errors. Found several files on both the array and cache. Moved files to cache and deleted. There were versions of libvirt(spelling) on both.  

4. Checked shares and noticed that appdata share was also being removed.

5. logs were checked, but for now doing the above and seeing if issue persist. 

6. Scan fixed common problems and have a new error that will be next to look at.

 

Error*** Unable to write to cacheDrive mounted read-only or completely full. Begin Investigation Here:

 

I have a mirrored cache 1TB nvme drives. I am begginning to think that the primary nvme is not working(stuck in read only). My solution for this is to switch them on the motherboard. If the issue is resolved then the nvme needs to be replaced. Will wait for friend before doing this. The cache is not full from what I see so issue is the physical drive.

 

Will update every 3 days or so 

 

blewstar-syslog-20231231-2232.zip

Edited December 31, 2023 by blewstar
Adding system log

[blewstar]

While troubleshooting the cache drive I unassigned the wrong one and wiped the drive. Possible to recover the data, but not much on it so ordered new SSD drives. I believe this is the solution. The drive is 5 years old and ran hot so failure was possible moreso. Will update this once up just making sure there is no other issues with updating to latest version of unraid.