loqus
Members
-
Joined
-
Last visited
-
Unraid 6.12.13 (see note at bottom) I just removed a slower hard drive from my array (without replacing it) and had to rebuild parity. The parity SYNC notifications included the duration and speed statistics from the previous parity CHECK, not the parity SYNC that just completed. The attached screenshots are probably clearer, but I'll describe here in case of attachment issues: - Parity sync completed 2024-12-11. I received notifications via email and Pushover, that said the sync finished with 0 errors, taking 1 day 4 hr 9 min 13 sec, at 157.9 MB/s. - I checked Parity Operation History in Unraid and I see that the Parity Sync operation that finished on 2024-12-11 took 21 hr 59 min 17 sec at 202.1 MB/s. This does not match the notification. - My previous Parity Check operation finished on 2024-12-09 and took 1 day 4 hr 9 min 13 sec at 157.9 MB/s. These stats match perfectly with the latest notifications received. I checked my last few parity check notifications, and they appear to be correct, referencing the duration and speed from the current operation rather than the previous operation. I suspect the bug only affects parity sync notifications and not all parity-related notifications. I recognize that I'm reporting from v6.12.13 while v6.12.14 is available, but I don't see this issue mentioned in the .14 release notes as a bug fix, and I'm not going to do an unnecessary parity sync on my array to confirm a relatively minor bug. Perhaps someone who has recently done a parity sync (and has notifications enabled) on the latest version can confirm. Thanks for understanding!
-
Thanks for the reply. One of the things I'm trying to accomplish right now is to rebuild and replace that Win10 VM with more modern VM settings and OS. But if I can't start a new VM... Any recommendations for where to look or what to try re: resources and hardware? Thanks!
-
Unraid 6.12.13 (and earlier 6.12.x versions) I'm only running one Windows 10 VM 24x7 and it has been pretty stable for a few years. I've recently tried adding/starting other VMs and they're mostly hanging the Unraid server (completely unresponsive, although sometimes responds to pings; I have to power-cycle and endure a full parity check that takes over 24h), or occasionally crashes the other running VM. My running VM is a Q35-3.0 machine with OVMF bios, running Windows 10 with NO pass-through of GPU, USB, Unraid shares, etc. (I haven't had any luck with Unraid shares via Virtiofs, but that's a separate issue). It's running Blue Iris, connected to IP cameras and writing to virtual disks and occasionally moving files to the array via SMB share. The "new" VM type doesn't seem to make a difference; I can't seem to install Windows 11, Windows 10, or Ubuntu Server 24.x in a new VM without major issues with the Unraid host. They start to boot and go through the OS installation process before the host hangs or the other VM crashes. I think I have tried different machine/BIOS types but I didn't keep notes. I have attached diagnostics exported shortly after the latest issue, where the Unraid server hung during installation of Ubuntu Server (latest LTS version). The last message that I recall seeing in the VNC console during Ubuntu installation was "waiting for cloud-init" - I have no idea whether that's relevant. Thanks in advance for any help. At this point I'm waiting on the parity check and very apprehensive about trying to start or troubleshoot VMs without some clear guidance. argon-diagnostics-20241208-1334.zip