ijf4unraid313

I'm having this as well. ... and yes, i did see the solution, i will ignore it for now.

This even happens in Safe Mode

deleting the cookies for unraid.net did it for me. thanks.

7.0.0 and also 7.1.3 (just updated and it still happens) While debugging an almost certainly unrelated issue, i noticed that something (a plugin?) is causing the disks to spin up every few minutes (shows in the logs as a read SMART). When the array is running, the disks stay down for long periods as expected. Not really an issue for me since my array is almost always up, but i thought it was peculiar. Here's a short snippet from the log: text error warn system array login Jun 8 07:14:18 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 07:14:18 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 07:14:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 07:14:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 07:29:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 07:29:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 07:29:21 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 07:29:30 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 07:30:19 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 07:30:19 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 07:30:28 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 07:30:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 07:45:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 07:45:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 07:45:21 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 07:45:30 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 07:46:19 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 07:46:19 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 07:46:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 07:46:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 08:01:02 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 08:01:02 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 08:01:21 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 08:01:29 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 08:02:18 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 08:02:18 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 08:02:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 08:02:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 08:17:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 08:17:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 08:17:20 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 08:17:29 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 08:18:19 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 08:18:19 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 08:18:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 08:18:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 08:33:02 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 08:33:02 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 08:33:21 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 08:33:30 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 08:34:18 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 08:34:18 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 08:34:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 08:34:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 08:49:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 08:49:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 08:49:20 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 08:49:29 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 08:50:18 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 08:50:18 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 08:50:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 08:50:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 09:05:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 09:05:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 09:05:20 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 09:05:29 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 09:06:19 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 09:06:19 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 09:06:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 09:06:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 09:21:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 09:21:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 09:21:21 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 09:21:30 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 09:22:18 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 09:22:18 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 09:22:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 09:22:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 09:37:03 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 09:37:03 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 09:37:20 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 09:37:29 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 09:38:18 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 09:38:18 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 09:38:36 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 09:38:36 [NameRedacted] emhttpd: read SMART /dev/sdc Jun 8 09:53:02 [NameRedacted] emhttpd: spinning down /dev/sdd Jun 8 09:53:02 [NameRedacted] emhttpd: spinning down /dev/sdb Jun 8 09:53:20 [NameRedacted] emhttpd: spinning down /dev/sde Jun 8 09:53:20 [NameRedacted] emhttpd: spinning down /dev/sdc Jun 8 09:54:19 [NameRedacted] emhttpd: read SMART /dev/sdd Jun 8 09:54:19 [NameRedacted] emhttpd: read SMART /dev/sdb Jun 8 09:54:27 [NameRedacted] emhttpd: read SMART /dev/sde Jun 8 09:54:36 [NameRedacted] emhttpd: read SMART /dev/sdc

okay.... THANK YOU! Switching the Win10 VM to use a Network Model of: 'virtio-net' seems to have "fixed" the issue. For those looking for a little background: I believe the release notes JorgeB is referring to are 6.12.13's (link). And to add a little context for those curious, I also found a 2021 discussion about virtio vs virtio-net on the unraid forums (here). (Most of this goes above my head, btw, so i appreciate the simple and direct answer above). If I'm reading both the release notes and previous forum discussion correctly, i should expect a network performance hit using virtio-net, but unraid is planning a resolution in a future release. Honestly I probably wont even notice the network performance difference (I'm so happy the fix was this easy, i dont even care about the top-end performance), but I'll still look forward to the fix and try to remember to test it out. Thanks again! -ijf

Hi everyone. I have a Windows 10 VM that i dont use all that often. I set it up back around 2019 and it has worked great every time i've used it until recently. Suddenly, when I write anything to a share (cache or array) from the VM everything grinds to a near halt. The write operation is excruciatingly slow and it seems to drag much of Windows down with it -- especially anything that access the Windows file system. When the copy/move operation completes or is canceled, Windows seems to return to its normal, snappy self. Shares are setup as mapped network drives in the Windows VM. Interestingly, writing to the Windows VM's primary vDisk (.img) -- downloads from the web for instance, it seems to run super fast like normal, but going directly to a mapped share is glacial (25KB/s ish -- its hard to gauge because it'll read 0KB/s for a while and then jump up a bit, then read 10KB/s for a while, then back to 0KB/s, etc). If i test a 5.8GB file from the array to cache using Krusader (Unraid docker, not through the VM), it goes in under a minute. Trying that in Windows VM it says "More than a day". I just updated the virtio drives in Windows -- thinking that might help, but it didnt. The network connection (to the unraid host) shows 10/10Gbps. No warnings in Device Manager. I'm sure this wasnt a problem several months ago (yes, its been a while since I've tried to use this VM). I'm kind of unsure where to even start looking. I've seen 1 or 2 similar post from earlier this year doing a search on Google, but most didnt have any responses. Would appreciate any debugging tips. EDIT to add that the vdisk1.img for the Win10 VM is on the same physical SSD cache pool that I'm trying to copy to ... so essentially in some cases I'm essentially using windows to copy from inside its own .img to an unraid-hosted share on the same physical media ... soooo, i dont think its a physical disk problem(?). I'm suspecting some setting i messed up, or a driver problem, ... maybe some Windows update that occurred in the last few months, etc. EDIT#2 to remove attached diagnostics now that the problem has been solved. Thanks -ijf