takkkkkkk

Hi Team, I just installed the patch and mover stopped moving files now. am I expected to uninstall mover tuner with this patchj?

thank you! I think that must have been the issue. turned off all my VMs and they're no longer spining up. I'm going to move everything to ZFS and then slowly move them back to array one vdisk at a atime.

any way to easily find out what may be accessing the disks? I do have turbowrite and one of VM ISO in the domain folder. would that cause this??

installing it was one attempt I tried resolving this. uninstalling! update: uninstalled, and same issue... spins down for 10-20 seconds and then spins up...

Hi everyone, I'm hoping someone can help me with an issue I've been experiencing. I’ve been using Unraid for a while, and all my cache drives were XFS. A few months ago, I decided to switch to ZFS and performed a factory reset on my server (no hardware changes, just a reset). Since then, none of my array drives will stay spun down. When I manually spin them down, they do so for a few seconds, but then immediately spin back up. I’ve also been waking up every day to hundreds of error messages about my disks overheating, and I’m assuming these two issues are related. Was htinking I could just ignore, but getting to a point I'm worried about loosing HDDs, right now, I can't really afford replacing 22TB HDDs... I’ve been trying to figure out what’s causing this but haven’t had any luck so far. Has anyone else experienced this or have any idea what might be going on? Any help would be greatly appreciated! Thanks! zeus-diagnostics-20241004-1231.zip

Just read it on reddit that the development of nzbget was forked and resumed (https://github.com/nzbgetcom/nzbget). anyone know if this is true / reliable?

Figured out the issue, it was docker image sitting on array. I'm assuming since it was still doing read-check in, it was flipping IOs. Moved to directories and moved it to a share that has exclusive access, it seems to be ok now.

I'm looking for assistance with some challenging issues I've been facing with my recently set up Unraid NAS. Here's a breakdown of the problems: Slow UI Response: Anytime I try to make an edit to docker / app, there's a considerable delay, ranging from 2 to 5 minutes. During this time, I am completely locked out of the UI, which is quite frustrating. Plex Buffering Issues: I'm experiencing constant buffering on Plex, and it's not limited to high-resolution content. This happens with both 4K and 1080p videos. I primarily use a Shield for streaming, and the buffering issue persists irrespective of the video quality. High CPU Usage: I've noticed that thread 0 of my CPU is often maxed out at 100% for extended periods. This seems unusual and could be related to the issues above. To address these, I've isolated CPU threads 0 and 16, and pinned all Docker containers and VMs (including Home Assistant) to avoid using these threads. However, this hasn't resolved the issues. I've attached my diagnostic file for a more in-depth look into my setup. Any insights, suggestions, or similar experiences would be greatly appreciated. I'm hoping to resolve these issues and get my unraid running smoothly. Thank you in advance for your help! zeus-diagnostics-20231124-1945.zip

stupid me for not checking this site first... I nuked my docker thinking I changed my password and forgot, only then I decided to look here...

Would it be unsafe to move between user to a different folder within user0?

I'm trying to change my download procedure, and seeing if I can download temp files to user(cache) and have post processing procedure to move from user to user0 without waiting for mover to move. is this safe??

thank you!!! it looks like it is working. TBH I do think this is way more technical than it needs to be, but your instruction has greatly helped.

thank you, how do I know if I have successfully mounted? I have typed below in the terminal, and I didn't get any returns... root@ZEUS:~# mount /mnt/aegis/domains/test/vdisk.img /mnt/aegis/domains/test/test/ root@ZEUS:~#

I'm used to simple windows ways where mounting an image/iso would mean windows would simply create "C:" or "D:" so that I can access it, I never thought of being asked of "where do you want to mount to", it just doesn't really click to me that it wouldn't automatically get mounted as another unassigned devices. Once it gets mounted, does it act as folder within share? this concept seems really unusual to me...

Hi, thank you so much for the instruction, although it is relatively simple to follow, there are some instructions where I'm having issues following.. when you say mount the vdisk, where do you plug in below code? terminal? where would "/path/to/mount/" be, could it be any folder within a share? I tried mounting it via adding the vdisk in windows, but it didn't work... mount /path/to/vdisk.img /path/to/mount/