GeorgeJetson20

I did post a separate one for the VM.. it's 100% from the Guest Agent, and nothing to do with the networking but I need to get into the VM by Monday so I hope someone is able to help with that because everything i tried has failed and not sure why it crashes the server when the VM fails...I have a backup from March but I don't want to lose 1 month of data so i am in a slight but controlled panic.

Need some help here. I installed Virtio Guest Agent, then rebooted it and since then, when I try to start the Windows 11 VM, It crashes the whole server and I can go to the console and do "reboot" to get back up and all but not sure how to resolve this because it seems like the instructions have changed since Unraid with the responsive UI. In the instructions it says to change the Guest Agent dropdown to YES, but this is not present in the edit and there is no advanced view with this: See the following: I just need to remove this and get this VM running again but I can't remove the guest-agent because I cant get into the VM. Attached is my diagnostics. In Unraid 7.2.3, the Advanced View toggle has been moved and some settings may behave differently compared to earlier versions. If you cannot see the toggle, it is likely because the "responsive" UI of version 7.x hides it behind a menu or header. [1, 2] 1. Locating the Setting in Unraid 7.2.3 To find the QEMU Guest Agent dropdown without the visible "Advanced View" button: Navigate to the VMs tab and click on the icon of your Windows 11 VM to select Edit. Look at the top right corner of the page header (just below the main Unraid navigation tabs). In Unraid 7.x, the toggle is often a small slider or may be located within a "Settings" cog icon in that corner. If it is still missing, try expanding the VM details by clicking the VM name first. [1, 2] 2. Manual Removal (Since the VM won't boot) Since the agent is preventing Windows from booting, you must remove the configuration from the XML level to bypass the UI entirely. Go to the VMs tab and ensure the VM is Stopped. Click the VM icon and select Edit. Click the XML View button in the top right corner. Find and Remove the Agent Feature: Locate the <features> block. Find the line <qemu-guest-agent state='yes'/> and either change it to state='no' or delete the line entirely. tower-diagnostics-20260502-2224.zip

Not sure I should repost my problem in a new message. I am stuck now with this VM issue - I can't proceed

Now i ran into a new problem that I somehow created.. I added a Realtek 8156 USB, all of unraid works but when I try to start the VM - it looses the network connection to the server and I can go to console and do a reboot and get back up. Not sure what is causing this. Here is my diagnostics. All i did after adding the network usb 2.5g - changed the interface rule to the mac of the usb for eth0 Not sure how to resolve this because not really sure where the issue.Uploading Attachment... Actually, I also earlier today on the VM, but did not reboot or restart since. I loaded Virtio-guest-tools.exe I bet this is the issue, but how do i remove that now??

I agree with you.. I took a look on Amazon and not sure which to get because it does not really say MLC. I searched: mlc usb flash drive 16g - I'm in the US. If you can point me to one I should get or a few.. also, am I going to have a problem if I switch again to another USB drive with Unraid? Can you switch again without needing any assistance from support?

I had purchased a pack of 10, that is why i replaced with the same. As for internal boot, just don't update the bios often, i guess. But i would imagine, it will still prevent this type of issue.

Hey Jorge! tower-diagnostics-20260501-0854.zipI was just venting, i didn't need assistance itself but here is the file. What a week! When I first had problems, i thought it was LSI controller and went and changed that out, in the process of that, the data connector on the 14tb drive literally broke off which further complicated everything because I had to replace the drive (but i have spares thank god) lol. To get my new USB workling, i created a new 7.2.3 boot and copied my /config from the old usb over (i was able to read it without issue)

Had a CMOS battery fail which crashed the whole server. Replaced battery and got server back up, it did the partity rebuild 26 hours and done. The next morning the USB boot drive fails. Replaced it and back up and running but now It once again needs to do the whole unclean shutdown and parity rebuild again. I know USB's boot is soon to be replaced and hopefully this will resolve a good amount of these types of issues but arghhhhhh. This puts more wear and tear on the drives and stressing me out waiting for it to finish again - Worried if a storm or power fail and UPS runs out of juice, another unclean shutdown. I was in a VM and the whole remote desktop closed and the server main showed this: (2 screens to fit it in) But it was not shutting down and kind of stuck which is what was the problem.

Me too. I keep coming back on here each week and not seeing anything that gives me confidence in going from 7.01 to 7.13 at this time, although I really want to, but I can't take the chance of something happen where the system goes down for a length of time. I wish I would see 7.14 and it everyone posts, I installed it, and it's working perfectly. I really would like to see what is done with the VM and better graphics speed. But my currently system is stable and don't want to chance it.

I was about to upgrade my 3 servers but I think I will hold off. Reading the posts in this sub is worring me a bit. I was thiniing 7.1.2 would resolve some of the issues but can't chance it right now. I will check back in a week and see what other users report.

This is a new message that I keep seeing in the log every few minutes since I upgraded from 7.0.0 to 7.0.1 Mar 8 11:20:30 Tower nginx: 2025/03/08 11:20:30 [error] 9719#9719: *472 limiting requests, excess: 20.369 by zone "authlimit", client: 192.168.1.27, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.1.200" Do I need to be concerned with this as I never saw this before

Just a quick update here. Since the last report, it still did not crash or reboot. The only thing I did was (started docker) but did not start any containers, so possibly one of the containers must have been the issue but I will wait till this weekend and then slowly start one container and see how it behaves

I have not had any issues with the server in more than a week. I been checking logs and the only message I keep seeing 1 time per day is (Other than autofan). monitor_nchan: Stop running nchan processes What does this mean/indicate, is this anything??

So far it's been almost 3 days without any problems since I turned off the docker. I am going to let it stay up without touching it until next weekend and then delete the docker and recreate it and see it makes a difference.

Update: 12+ hours later - Still running without any reboot, parity finished last night and still running without any reboots - just disabled docker still. Quick update. After turning off docker, not seeing any reboot (after 4 of them yesterday). It's still finishing up parity check at 92%. Is there any chance that docker would causing the reboot? I thought it was all separate from the system itself. I am going to let it run as long as it doesn't reboot without docker and see what happens. But if a docker container or the vdisk had a problem, would that be enough to reboot the system, even though there is no warning about it in my syslog that I can see? If I need to rebuild the docker from scratch is no big deal but I will just leave it alone for a while until I see if the issue stops happening.

trurl, ((I made mistake, it's a 5700X not 3700X). I never caught that till now Not sure if that changes anything? I reviewed that but my system reboots to logon screen of unraid each time of the failure. This started after upgrading to .13 but I can't say 100%. I never had any issue with any reboots of any kind prior to that. I stopped docker services the last time it rebooted just to see if that had anything to do with it. But I really don't know if this is hardware related or something in unraid. I thought about just booting to Windows OS with the system and just leave it there and see if it reboots. If that happens, then it's the hardware but I am not sure really how to try to resolve this. I'll also run a memory test - any other ideas???

Unfortunately, The problem happened 2 more times. Both during the parity rebuilds. Here is the very latest log file. hopefully someone MUCH smarter then me can figure out where the issue is. This server was running good for over a 1 year without any issues until this rebooting issue started. My specs are in the bottom of my message for Node804. syslog-192.168.1.101.zip

Here is the zip file of it.syslog-192.168.1.101 - Copy.zip

It finished the parity check and then the same thing happened. Not sure where to go from here. please let me know how to figure this out.

Jorge, It's been a little more than 3 weeks since last the unclean reboot problem showed. It happened today and I did have the remote syslog running but I don't really see much there. Do you need to see it? Not sure if I should post that here or not. It's size 1582K I don't think it's related, but I did update from .14 to 7.0.0 yesterday (without any problems).

Thanks for the info, didn't see that in the release notes

Upgraded my 3 Servers from .6.12.14 to 7.0.0 without any issues. Even though during the first upgrade to 7, I was slightly worried but no issues. I do have 1 question about the VM snapshot, where is the snapshot being saved and how can I see how big it is?

not more than 30 seconds after posting this, it started happening again!!!!!!!

Not really sure what happened but after reinstalling sabnzb from scratch, it seems to be ok now. Not getting any of the permission errors. Will continue to test but I think this is resolved, although I don't know what caused the problem in the event it happens again.

I was looking at the system log and found this, not sure if it's related or not. Going to try to start fresh with sabnzb because I can't figure out the permissions issue. Might not have anything to do with anything but just wanted to post it. I will report back on if fresh starting resolves the weird messages from Sabnzb.