-
7.3.2 -> 7.3.3 + Unassigned Devices: not mounting previously mounted
Hotfix applied and is working. Much appreciated @dlandon !
-
7.3.2 -> 7.3.3 + Unassigned Devices: not mounting previously mounted
Yup. Just found the thread. Didn't apply the hotfix, but did revert to 7.3.2. When a new plugin is available, I'll upgrade back to 7.3.3.
-
7.3.2 -> 7.3.3 + Unassigned Devices: not mounting previously mounted
With unRAID 7.3.2 and Unassigned Devices: have been using an NVMe drive for years. After upgrading to 7.3.3, the device is recognized by unRAID, but is not mounted between unRAID and Unassigned Devices. unRAID is looking to Format this drive (noooooo), and I want it remounted.
-
New Win/linux VMs: all require Force Stop
Small update @JorgeB : week-ish of uptime switching video to VirtIO on VM. Correlation != causation, but I haven't changed anything else since. I am interested in trying the same change to a Win11 VM, just to see if it fixes the same issue.
-
New Win/linux VMs: all require Force Stop
1. When Ubuntu was last known to work and when it was first found unresponsive.This VM was built around a week-ish. I don't monitor it (not critical), but the web interface (unifi server) was responsive up until at least Tuesday. 2. Whether this followed a reboot, update, idle period, or workload.Idle period. 3. Whether the Windows VM has remained reliable since changing its video model to VirtIO.Stopped using the Windows VM entirely, migrated to using Ubuntu for unifi server. After cleanly stopping Ubuntu, change only its video model from QXL to VirtIO and test again. Leave its CPU, memory, storage, machine type, and network unchanged.Will do this now that the server is responsive.
-
New Win/linux VMs: all require Force Stop
Got another dead one here, but this is with Ubuntu server. virsh qemu-monitor-command --hmp "Ubuntu Server" "info vnc" default: Server: 0.0.0.0:5701 (ipv4 (Websocket)) Auth: none (Sub: none) Server: 0.0.0.0:5901 (ipv4) Auth: none (Sub: none) Display: video0 virsh qemu-agent-command "Ubuntu Server" '{"execute":"guest-get-osinfo"}' {"return":{"name":"Ubuntu","kernel-release":"7.0.0-31-generic","version":"26.04.1 LTS (Resolute Raccoon)","pretty-name":"Ubuntu 26.04.1 LTS","version-id":"26.04","kernel-version":"#31-Ubuntu SMP PREEMPT_DYNAMIC Sat Aug 1 04:26:38 UTC 2026","machine":"x86_64","id":"ubuntu"}} virsh qemu-agent-command "Ubuntu Server" '{"execute":"guest-get-time"}' {"return":1789252506843971000} virsh qemu-agent-command "Ubuntu Server" '{"execute":"guest-network-get-interfaces"}' {"return":[{"name":"lo","ip-addresses":[{"ip-address-type":"ipv4","ip-address":"127.0.0.1","prefix":8},{"ip-address-type":"ipv6","ip-address":"::1","prefix":128}],"statistics":{"tx-packets":2152670,"tx-errs":0,"rx-bytes":603841801,"rx-dropped":0,"rx-packets":2152670,"rx-errs":0,"tx-bytes":603841801,"tx-dropped":0},"hardware-address":"00:00:00:00:00:00"},{"name":"enp1s0","ip-addresses":[{"ip-address-type":"ipv4","ip-address":"192.168.11.9","prefix":24},{"ip-address-type":"ipv6","ip-address":"fd28:e9ff:3f5c:47d7:5054:ff:feea:8d07","prefix":64},{"ip-address-type":"ipv6","ip-address":"fe80::5054:ff:feea:8d07","prefix":64}],"statistics":{"tx-packets":1590215,"tx-errs":0,"rx-bytes":2664616098,"rx-dropped":1167,"rx-packets":3304886,"rx-errs":0,"tx-bytes":422377319,"tx-dropped":0},"hardware-address":"52:54:00:ea:8d:07"}]}Unsure when it stopped responding, but its not accessible via ping/ssh. Attempting to use VNC via unRAID shows a frozen screen. Attached is a diag. This also failed to stop via cli: root@Greyskull:~# virsh shutdown "Ubuntu Server" --mode agent error: Failed to shutdown domain 'Ubuntu Server' error: guest agent command timed out: guest agent didn't respond to command within '60' seconds greyskull-diagnostics-20260912-1537.zip
-
New Win/linux VMs: all require Force Stop
Reboots are rare to work and I managed to get far enough into a Windows 11 setup to complete guest tools installation. Another diagnostic added, as console is a goner and force stop is all I got. greyskull-diagnostics-20260903-1619.zip
-
New Win/linux VMs: all require Force Stop
Unraid is reporting as VM as "started", showing the green play icon. Close, open new. Same thing, no console. No ping or RDP. Confirm its IP via my DHCP server, it will not respond by assigned IP. Terminal outputs I wanted to install the guest agent on this Windows 11 machine, but ran Windows updates first. Diag attached. greyskull-diagnostics-20260903-1242.zip
-
New Win/linux VMs: all require Force Stop
Restarting a headless linux (ubuntu server) or Windows 11 VM from the VM will not return a VNC-capable console. Restart starts a reboot process (i.e. VNC console will go blank), but will not return a VNC-capable console. Stop will not return a VNC-capable console. Haven't tried rebooting unRAID server for VM, as force stop has worked. With Windows 11: the setup GUI screens are fine. With linux installer: whatever text installer is fine. I have full VNC console prior to a reboot attempt. 2-4: just got another hang, attempting to use console. Attaching a diagnostic. Oddly, a reboot after a force reboot worked. Guest agent installed on existing VM. greyskull-diagnostics-20260903-0917.zip
-
New Win/linux VMs: all require Force Stop
Attached diagnostics zip. greyskull-diagnostics-20260903-0801.zip
-
New Win/linux VMs: all require Force Stop
Method: Using guided GUI for Win 11. Pinned to cores/threads that aren't in use (i9 9900k), using 4 total. Initial/max memory: 8GB. Machine: i440FX-10.2. BIOS: OVMF-TPM. Hyper-V: Yes. Primary vDisk: custom location, as my NVMe isn't an Unassigned drive. Networking bridge (two NICs) No PCI pass through. No USB pass through. Have used "defaults" of creation for years, and the only change(s) are primary vDisk and amount of CPU/threads. Will get a diagnostic after next crash, which shouldn't take long.
-
New Win/linux VMs: all require Force Stop
unRAID: 7.3.2 Unsure which version this started with, but all my VMs aren't able to survive a reboot: force stop is required. This is for both Windows and linux VMs -- none of them have any pass through devices (did see an Nvidia reference). One of my VMs existed pre 7.3.x, and all my new 7.3.x created VMs are also showing this problem. At this point, I cannot complete creation of a Windows VM, as multiple reboots are required and Windows seems stuck in a setup loop.
stashtv
Members
-
Joined
-
Last visited