Jebberino84

I logged onto other vms with the same user, but I guess it could have been something with this user on that VM? It's already deleted now, so no way to test it out further than logging onto other VMs.

I apologize. I guess I'm just really frustrated. I've tried everything I can think of and I don't understand what's happening. I'm nuking the disk and rebuilding the VM from scratch. Thanks for reading and posting and trying, JohnathanM!

Thank you for your comment on this thread, JonathanM. I'm not trying to be rude, (you have 16.1k comments so I believe you offer a lot of help on this forum and for that, I appreciate you) but I did mention in my first post that I already tried safe mode and unfortunately it made no difference. Something I did remembered now which I did not post about earlier is that I have other Windows 10 VMs on this device that started up just fine. This is the only VM that wouldn't restart after something went wrong with the whole server a few days ago. My last attempt was to do a windows 10 restore, (of which I only had 1 restore point available from 2 days ago which I don't remember making, so maybe this has something to do with why the whole server had issues but ???) and that didn't work either. So now, I am just going to delete the VM, reformat the hard drive, and start over. I give up. I will 100% be automating some sort of scheduled events to create more windows restore points, as well as snapshots of all my VMs, and Unraid flash drive backups, along with anything else I can think of to make sure this doesn't happen again. I probably should have done this earlier. Thanks again for anyone taking a look at this post. If anyone has any good theories on why or what happened, please feel free to comment as I may put off fixing this VM for a little bit.

Somewhat of an update, When I setup this VM, I passed through an entire hard drive which I dedicated to this VM. I was able to go into the BIOS of the Unraid server (ASUS Prime Z390-a Motherboard) and I changed the boot order so it would boot directly into windows. After doing this I was having the exact same error with the loading "welcome" screen after I enter in my credentials. To me, this seems to point towards an issue with windows and not Unraid or the VM setup. Knowing this, and after not getting any help here, I have decided to attempt finding other forums dedicated to windows 10 to see if anyone can help. I'm hoping there is a way to fix this without completely reformatting the drive and replacing the VM. I'll try to remember to post back here if I find a solution.

I'm still not entirely sure what happened, but I had an issue a few days ago and I lost some settings for my server. I was able to get the network back up and running, and then re-install Community Applications and all my dockers (Plex/Jellyfin/etc.) but now I've noticed some weird issues with one of my VMs. I run a Windows 10 VM on this server with Blue Iris on the Windows 10 VM. This entire server and this VM have been running fine for over a year, but it just started having issues a few days ago. When I try to run this VM it boots up, and I get past entering credentials, but while windows actually loads there is a "welcome" loading screen with the spinning dots. I've let the VM sit for over 6 hours and it never gets past this screen. I've attempted everything I can think of. Most forums here seem to indicate issues loading windows all-together and speak of the screen before you enter credentials. I am able to enter in my credentials, but after that it hangs up. At one point I did restart in safe mode (with internet), but that didn't do anything. Still got held up on the same screen. I've also tried not passing through the GPU, but that didn't help either. I've also tried updating the virtio drivers on unraid and on the VM settings. Nothing gets me past the windows "welcome" screen. I'm at a point now where if I don't figure this out, I believe I will have to scrap this VM and redo it from the beginning. Unfortunately, I did not create any snapshots so if I do this, it will have to be a completely new and fresh install. I'll also be looking into how to automate snapshots if I have to redo the whole VM. I'd like to not go that route though and I'm hoping someone will have some direction for me. This is my last resort to save the VM. I will include some logs to hopefully help. Unraid Diagnostics attached below. Logs from VM while it's stuck on loading screen: 2024-04-18 19:13:54.304+0000: starting up libvirt version: 8.7.0, qemu version: 7.2.0, kernel: 6.1.79-Unraid, hostname: JebsNAS LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME=/var/lib/libvirt/qemu/domain-1-Win10BlueIris \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-1-Win10BlueIris/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-1-Win10BlueIris/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-1-Win10BlueIris/.config \ /usr/local/sbin/qemu \ -name guest=Win10BlueIris,debug-threads=on \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-Win10BlueIris/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/018291b0-e041-9899-5b33-6243ef3ec348_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-i440fx-7.1,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \ -accel kvm \ -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 10,sockets=1,dies=1,cores=5,threads=2 \ -uuid 018291b0-e041-9899-5b33-6243ef3ec348 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pci.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pci.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pci.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pci.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x3"}' \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-WDC_WD84PURZ-85B2YY0_WD-CA37ANJK","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x4","drive":"libvirt-3-format","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows/Windows.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","unit":0,"drive":"libvirt-2-format","id":"ide0-0-0","bootindex":2}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.248-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","unit":1,"drive":"libvirt-1-format","id":"ide0-0-1"}' \ -netdev tap,fd=37,id=hostnet0 \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:0a:95:60","bus":"pci.0","addr":"0x2"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -device '{"driver":"vfio-pci","host":"0000:01:00.0","id":"hostdev0","bus":"pci.0","addr":"0x5"}' \ -device '{"driver":"vfio-pci","host":"0000:01:00.1","id":"hostdev1","bus":"pci.0","addr":"0x6"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) If any additional information is needed to help diagnose the issue, just let me know and I'll get on it ASAP. Thanks for taking a look! Unconfirmed 448532.crdownload

Thank you, JorgeB! I really don't think I ever would have guessed that was causing all the issues! I'm not 100% sure yet, but I believe the second NIC being configured was exactly what the issue was! I'm still downloading/installing community applications, and afterword I'll be re-installing my dockers, but right now it seems that I have a connection again and things are finally moving forward! I've marked your first comment as the solution. I'll also likely donate after I finish re-downloading and setting up the rest of the server. Thanks again!

I also just noticed that I spoke of Plex in this sentence, but I meant Unraid. When I speak of this server to my wife, I call it the Plex server because that is what she uses it for the most and what she recognizes it as. I doubt this did, but I apologize if this created any confusion.

My apologies. After posting all the other error messages and such, I should have in my last post. Here are the new Diagnostics. Unconfirmed 561677.crdownload

Thank you for suggesting this. I believed STP would just take over if the second NIC was still associated with the server and not a VM (which is what I planned on using it for) before I was able to setup and configure the VMs again. I did move the NIC to a different network and got rid of the second gateway, but this unfortunately did not fix my issue. Below is the error I get when I try to install the Community Applications plugin. I've let the server sit for more than 30 minutes after it stops on the last line but it never does anything else after executing the hook script. Not sure if this error message will help, but it does show that there is still an issue. plugin: installing: community.applications.plg Executing hook script: pre_plugin_checks plugin: downloading: community.applications.plg ... plugin: community.applications.plg download failure: Network failure Executing hook script: post_plugin_checks I am still able to ping my gateway, and other devices on my network, but I am unable to ping outside of my network as seen below. This is what doesn't make sense to me. I've obviously never set anything up like a firewall for this device, and I don't believe there is anything on my router that is administratively preventing the device from accessing the internet. If I am able to ping the router, it proves that there is a working connection to the router, and I am also able to access the outside internet from all other devices. The above solution I posted spoke of "wireguard" as being able to creep into the initial setup of the server's boot instructions and could somehow prevent the server from accessing the outside internet. Is there anything else that would have the ability to do this on Plex? root@JebsNAS:~# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.165 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.173 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.351 ms 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.299 ms 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.351 ms 64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.348 ms ^C --- 192.168.0.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5123ms rtt min/avg/max/mdev = 0.165/0.281/0.351/0.081 ms root@JebsNAS:~# ping 192.168.0.100 PING 192.168.0.100 (192.168.0.100) 56(84) bytes of data. 64 bytes from 192.168.0.100: icmp_seq=1 ttl=64 time=0.016 ms 64 bytes from 192.168.0.100: icmp_seq=2 ttl=64 time=0.011 ms 64 bytes from 192.168.0.100: icmp_seq=3 ttl=64 time=0.017 ms 64 bytes from 192.168.0.100: icmp_seq=4 ttl=64 time=0.016 ms 64 bytes from 192.168.0.100: icmp_seq=5 ttl=64 time=0.014 ms 64 bytes from 192.168.0.100: icmp_seq=6 ttl=64 time=0.012 ms 64 bytes from 192.168.0.100: icmp_seq=7 ttl=64 time=0.025 ms 64 bytes from 192.168.0.100: icmp_seq=8 ttl=64 time=0.012 ms ^C --- 192.168.0.100 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7148ms rtt min/avg/max/mdev = 0.011/0.015/0.025/0.004 ms root@JebsNAS:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.5.100 icmp_seq=1 Destination Host Unreachable From 192.168.5.100 icmp_seq=2 Destination Host Unreachable From 192.168.5.100 icmp_seq=3 Destination Host Unreachable From 192.168.5.100 icmp_seq=4 Destination Host Unreachable From 192.168.5.100 icmp_seq=5 Destination Host Unreachable From 192.168.5.100 icmp_seq=6 Destination Host Unreachable ^C --- 8.8.8.8 ping statistics --- 8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7181ms pipe 4 root@JebsNAS:~# Thanks again for helping me with this. If you or anyone else has any recommendations, please let me know.

So, unfortunately, deleting and re-creating the docker.img did not work. I did find this thread which seemed to help other users, but I had absolutely nothing in my "wireguard" folder on my flash drive: I tried the above, after I noticed that my server is accessible from within my own LAN, and I can ping it, but I am unable to reach the outside internet from my server. I can ping my gateway/router and other devices on my LAN from the server, but nothing outside the LAN. I can also access the web GUI for my server from 2 different computers from my LAN which is why this took me so long to realize was an issue. This is really confusing me. I'm still at a loss and need to move on to other chores/errands for the day. If anyone has any advice on what could possibly be causing me all these issues, please post ideas/possible solutions. As of right now, I'm completely at a loss and frustrated. Thank you!

Hello! I am a newbie with a lot of issues and would like some help. I noticed my plex and other services (Windows VMs) were no longer running on my Unraid server. I've also had issues rebooting so I initially thought my Flash drive was going bad, but I was able to plug it into a windows computer and run a repair which allowed me to boot unraid again. I was able to get my shares back up and running, and my VM's seem to be ok, but now my dockers (MacInABox, Plex, Jellyfin, etc.) are all listed as orphaned images. I've tried just adding these back with the "add container" button, but it fails every time. I've also noticed that my apps tab won't work (I get an error that says I could try fixing my DNS, which made me restart my router and this server, but to no avail) with an "Download of AppFeed failed" message. I also have had an error message of my Nvidia driver update failing. I know something catastrophic is happening, I'm just hoping someone can help me figure out what's going on before I loose a lot more data. I'm about to attempt deleting and re-creating my docker.img but if anyone has any other suggestions or can help me diagnose what's causing all of these issues, I'd really appreciate it. Thanks in advance for any help! Unconfirmed 355806.crdownload

I tell ya, it's mistakes like these that humble you. I was doing all this while researching and I think the real problem was that I just wasn't pressing any keys at the beginning to boot from a CD. Thanks again SimonF for letting me know I'm a dummy sometimes! I hope you all have a good day!

Thank you, SimonF! I changed the "OS Install CDRom Bus:" to SATA and then made sure to press a key to boot from CD and it worked! I'm now setting up and installing Windows!

Here is also a view of the settings I'm using to try to make a VM. I still can't figure out why this won't boot into windows setup.

I just realized that I never posted back on here. For anyone else who might read this, I wasn't able to recover the old information. I instead started over and created new VMs after replacing the Cache drive and creating a chache pool with 2 SSDs. Let this be a lesson to anyone out there with only 1 SSD and no redundancy! Try to get a second SSD so if one fails, you still keep all your data!