Leaderboard

Executing any kind of SMART operation increments both number I/O's to the device (in this case Reads) and number sectors transferred (in this case sectors read). This is true whether device is in standby or not. HOWEVER, I have a fix for this coming in 6.9.1

Yes that's the fix

I might have a simple fix, unless I'm missing something. sdg is Disk2 of my array. Here are diskstats for sdg and its only partition sdg1: root@NAS:~# grep sdg /proc/diskstats 8 96 sdg 980673 22075722 182230404 6487392 284407 19425162 157662544 2604401 0 6664111 9193913 0 0 0 0 1749 102119 8 97 sdg1 681558 22075722 182067420 1286206 282656 19425162 157662544 2491636 0 1400537 3777843 0 0 0 0 0 0 And here are diskstats after a smart call: root@NAS:~# grep sdg /proc/diskstats 8 96 sdg 980680 22075722 182230408 6487516 284407 19425

I'm having the same issue with drives not spinning down after upgrading to 6.9 I have spin down delay set to 15 minutes, and already confirmed that with Dynamix Auto Fan Control enabled, the drives wont spin down, with it disabled, the fans spin down within 15 minutes as they should. Also confirmed that the drives will stay down if manually spun down.

I'm also having this issue. Everything worked fine in 6.8 but since upgrading, drives will not spin down automatically (if the spin down button is pressed they do spin down okay). From reading the above, I have dynamix autofan installed but (like make others) disabling this is not an option with the set up as it is. Do we have any ideas when/if this is something that can be fixed?

You all might be pleasantly surprised coming up very soon

Feels like I'm on this page everyday just to see if they've released rc3

The absolute least amount of write-amplification, no pre-determined size of the image, but rather it'll grow / shrink according to its needs.

I just noticed that this was happening to me now that I have upgraded to Unraid 6.9. It's a real bummer that we have to do a work around in the meantime. My only hesitancy with this workaround is that I know I'll forget to remove the added code instructions once this resolves itself. I just submitted a feedback/bug report from within Unraid's dashboard and linked back to this post in the bug report. Hopefully the Unraid team pushes out an official patch. 🤞🏼

Spinning control was changed in 6.9 to handle multiple pools and SAS devices. Some plugins are incompatible with these changes, as noted, Dynamix Auto Fan Control. We're looking into fixing the plugin.

Yup.. it was the culprit.. system still running without an issue after disabling that plugin.

Your log is going to be winding up filling up due to atop. It is only recommended to install what packages you actually need via NerdPack. Do not install everything.

Don't apply it in "go" or user scripts or anything like that. It's a minor aberration, and if you forget you're patching the file then things might break on future releases.

Here are mine: lsscsi.txt lspci.txt

The root of your problem is Mar 2 21:38:00 Abee-EZ300 root: Fix Common Problems: Error: Unable to communicate with GitHub.com ** Ignored The plugins page if check for updates under Notification Settings is enabled will always check for updates when going to the page. Obviously, its taking its time to timeout on the check though. IE: Your server most likely cannot hit the internet

Go to Tools -> System Devices. Can you bind the controller for this drive to vfio-pci? Post a screenshot of this page if you aren't sure.

It works but I lose my SSD cache drive. It appears now in unassigned device. Maybe one of the bug origin. I will restore my cache drive and reboot 2 times to be sure the everything works again. No OS update for me now! Thanks a lot Jobine.

Bonding is enabled by default, even if you only have one NIC.

Spindown works only if I disable autofan and every other addon that queries smart data (telegraf, etc.) Once spun down these queries don't seem to wake them but too soon to say definitively.

You ought to reboot into safe mode and see if the disks spin down. If they do then some plugin is the cause.

maybe a stupid question but wouldn't libvirt.img also benefit from this change?

If you click spindown button on main do they spin down? Also autofan is reading temps. Not sure where it gets them from but if doing smartctl will spin up disks if not using -n standby. I think telegraf also created issues within betas are 6.9-rcs do you use that?

double Thanks for the temporary fix 😂

Work around is run in terminal sed -i 's/1000/3000/' /usr/local/emhttp/plugins/dynamix/include/Syslog.php

For now those of you who want the full syslog in the GUI can run: sed -i 's/1000/3000/' /usr/local/emhttp/plugins/dynamix/include/Syslog.php in the terminal to fix it (tested and working for me). Thanks to @SimonF for the command.

It's working, thank you very much!

I think there was a change of noVNC version, did you try to empty your browser cache ?

That means the tree block is corrupt, there are some recovery option here.

sysctl -w net.ipv6.conf.all.use_tempaddr=0 sysctl -w net.ipv6.conf.default.use_tempaddr=0

I could be wrong, but IIRC Unraid is based on Slackware. The delayed release of 6.9 may have something to do with this magical announcement : https://www.itsfoss.net/slackware-linux-15-0-alpha1-release/ This is pure speculation on my part. I'm super happy and excited to see my first Linux distro is still alive and well! Thank you Slackware for being such an amazing distro over the years!

When you give a container it’s own IP address then I think the host port setting is ignored and you can only use the port the container has configured. I could be wrong about that but that is my understanding.

I think the radeon module would be the one for this GPU. Both depend on what the docker container is trying to do and how it's built. Obviously software support needs to be built into the container. In the case of a container that wants to leverage the compute capability of an AMD GPU (such as a FoldingAtHome or BOINC container) the OpenCL subsystem - essentially a compiler - would need to be included. That's included in the amdgpu-pro driver package. For a container aimed at transcoding video (such as Handbrake) the Video Acceleration API (vaapi) needs to be included. Fr

I suggest you start a new thread in the General Help section and include your diagnostics zip file exactly as you retrieved it. It is anonymised by default. You're likely to have problems specific to your setup and you can get help in a separate thread without the noise of all the other conversations going on here.

Bingo, I knew I had seen it someplace.

@TexasUnraid Case-sensitive names is somewhat (to me) strangely under security settings for the Share. Shares > 'Click Sharename' then it's there under SMB Security Settings.

Definitely Soon.

Overclocking is not recommended for servers such as Unraid. You should validate this though, you'll get first place on some boards.

That was what I had been trying but never did manage to get it working, my entire system would crash every time I tried to boot a VM that had the APU attached. Regarding the docker containers, I had found someone on the Plex forums who had managed to get hardware transcoding working in a plex docker container on a Ryzen 7 4700U APU. Here's the link to the thread. I've just installed their fork of the linuxserver.io plex docker container and HW transcoding isn't immediately working for me, but I do get a response when I run vainfo from the docker container console. Also

As a matter of great interest, you presumably did that in an attempt to pass the GPU through to a VM? Did you have any success? I haven't and I don't think it's possible but I'd be happy to be proved wrong! As another matter of great interest have you found a docker container that can actually make use of the Radeon Vega's video encode/decode or compute capability? I know that the Linux version of Plex isn't built to make use of it and therefore the dockerized version can't, either. It's recognised as a GPU by the FoldingAtHome container but the necessary OpenCL subsystem isn't in

I have a server with a Ryzen APU. I'm not in a position to reboot it at the moment because it's busy but if I load the amdgpu module manually I get a /dev/dri folder: root@Pusok:~# ls -lR /dev/dri /bin/ls: cannot access '/dev/dri': No such file or directory root@Pusok:~# modprobe amdgpu root@Pusok:~# ls -lR /dev/dri /dev/dri: total 0 drwxr-xr-x 2 root root 80 Feb 9 20:38 by-path/ crw-rw---- 1 root video 226, 0 Feb 9 20:38 card0 crw-rw---- 1 root video 226, 128 Feb 9 20:38 renderD128 /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Feb 9 20:38 pci-0000:09:00.0-card -

Perhaps they will. I'm not disagreeing. I simply replied to someone who seemed annoyed by the apparent lack of developer comment in this thread.

Just wondering why UNRAID doesn't comment on this? I pay for a license, and my system gets slower with each update. The only people that care are other customers that have given money to UNRAID. Seems that it might be time to move on to another system? I'm very disappointed in the lack of concern and speed of UNRAID. Thanks to all those who have posted and spent hours and hours trying to fix a software problem that UNRAID doesn't seem to care about nor has any desire to fix.

@limetech Doesn't FUSE3 contain a buffer / chunk size setting? EDIT: What about testing different values for FUSE_MAX_PAGES_PER_REQ and FUSE_DEFAULT_MAX_BACKGROUND? https://chubaofs.readthedocs.io/en/latest/user-guide/fuse.html Several Fuse users said, that it will raise the througput: http://fuse.996288.n3.nabble.com/Default-read-write-block-size-td12678.html http://fuse.996288.n3.nabble.com/performance-bufsize-and-FUSE-MAX-PAGES-PER-REQ-td14806.html http://fuse.996288.n3.nabble.com/PATCH-v2-0-6-fuse-make-maximum-read-write-request-size-tunable-td

Well, it's been the normal behavior of the Nvidia drivers for a while. A "power limit" is enforced for the card by the vbios and drivers, and when the power drawn approaches this limit, the clocks are throttled. If you want to see what the power limits are and to which extent you can adjust them, you just have a look at the output of 'nvidia-smi -q' Mine looks like that on a P2000 (which is only powered by the PCIE slot, thus the 75W min & max) : Power Readings Power Management : Supported Power Draw : 65.82 W

I've done some digging on this - here's what I found. Mount unraid share system on my mac and check its spotlight status: [macbook-pro]:~ $ mdutil -s /Volumes/system /System/Volumes/Data/Volumes/system: Server search enabled. [macbook-pro]:~ $ But as best I can tell "server search" is not in fact enabled. Turns out samba 4.12.0 changed this search-related default: Note that when upgrading existing installations that are using the previous default Spotlight backend Gnome Tracker must explicitly set "spotlight backend = tracker" as the new default is "noindex

Just upgraded to Beta 30 I get this error when i click VNC Remote for my VM

For the upcoming version the default driver is changed to "virtio-net". This means newly created VMs will use the revised driver, but existing VMs need manual adjustment.

No worries! Not everyone is expected to be an expert in all things unRAID; especially not after just a couple of weeks of use. There are no stupid questions (well, actually that does happen from time to time 😀) just lack of understanding. Most people here are very happy to help improve understanding of unRAID.

I just ran into this myself, some googling I found this and "umount /var/lib/docker" was my fix as well. Which is odd since I stop all the dockers before I went to stop my array.. I'm guessing a docker really didnt stop or something?