limetech
Administrators
-
Joined
-
Last visited
-
With great sadness and shock I wanted to pass along the news that long-time Community Developer @bonienl has passed away last week. IRL Ronald van den Berg was a friend and colleague who I've known and worked with since 2010. Over the years we shared many emails and video calls. Mostly our discussions were technical but there were plenty of stories and some laughs as well. From a description he wrote himself: As you all know, Ronald was extremely diligent, always eager to help, and always friendly. He will be dearly missed. If you want to leave a note, please use this topic to do so. I will send a link to his family. -tom mortensen
-
The advantage of Unraid vs. RAID-5 are: With Unraid each data disk is its own file system. With RAID-5 (or with ZFS raidz pols or with btrfs raid1/5) your data is 'striped' across all the devices. This means if you want to read a single file or set of files within a directory, with Unraid typically only a single hard drive will spin up - the one containing your data. When writing only the target drive and parity need to spin up. With RAID-5 or ZFS zpools (or btrfs) all the drives must spin up. If all your hard drives are constantly spun-up of course this doesn't matter but for larger arrays in energy-conserving setups it can make a difference and save some wear and tear. If catastrophe happens, and for some reason 2 or more hard drives totally fail, then at least with Unraid you don't lose all your data - just the data on the drive(s) that failed. If you have 2 parity drives then you can tolerate 2 complete failures before possibly losing data. Disadvantage of Unraid vs other striping organizations: More effort may be required to keep collections of files on the same drive (this is where 'split-level' comes into play). Read/Write is definitely slower than striping. In the days of 1GB ethernet this hardly made any difference but with 10GB becoming more predominant this is a consideration. Something else that you can do with Unraid is this: Suppose you have "critical" files on disk1. You can Stop array, physically remove disk1 and store off-site. Then install a replacement drive, Start array and let server rebuild disk1 contents. You would set up your critical shares so that they exist only on disk1. Note if you end up routinely doing something like this I'd recommend have 2 parity devices just to be safe in case another drive fails during rebuild.
-
Unraid v7.1.x uses kernel v6.12.24 which has been patched. The patch included involved adding this: https://elixir.bootlin.com/linux/v6.12.24/source/fs/overlayfs/copy_up.c#L1158
-
Unraid 7.1.0-rc.3 is now available! Details in the release notes. (search the page for '-rc.3' to see changes from earlier rc's). Everyone running an existing beta or rc is encouraged to upgrade. The only change vs. 7.1.0-rc.2 is to revert the Linux kernel from v6.12.25 to v6.12.24. We identified a kernel regression which causes Docker or VM Manager to 'hang' if their corresponding loopback images are located on a ZFS volume. This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic in the Prereleases board. Be sure to include your diagnostics.zip. Upgrade steps for this release Read the release notes As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully. If you have a recent release or Unraid Connect installed: Open the dropdown in the top-right of the Unraid webgui and click Check for Update, then press More options and switch to the Next branch. You may be prompted to sign in to access the Next branch. Select the appropriate version and choose "View changelog to Start Update". More details in this blog post If you don't have the Check for Update option in the upper right corner: Either install the Unraid Connect plugin or upgrade to 6.12.10 first. Then check for updates as described above. Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic in the Prereleases board. Be sure to include your diagnostics.zip.
-
There is a possible fix for this in upcoming v7.0.1 release.
-
Do you recall if the CPU and Memory Load were being displayed and updated aporox every 3 sec on the Docker Tab?
-
We cannot reproduce this issue. One thing we were concentrating on was the Docker page. When you are on this page there is an nchan process started with publishes real-time docker container usage stats (cpu and memory usage). The process accomplishes this by continuously invoking 'docker stats' command. You can see this in /usr/local/emhttp/plugins/dynamix.docker.manager/nchan/docker_load This info is only displayed in 'Advanced' view but the process is running whether in 'Basic' or 'Advanced'. When you navigate away from the page, the process is terminated. As a side note this is something to be aware of: if you leave a browser sitting on Docker page, that process is running and consuming resources. Maybe not the best design Anyway tried opening the page in multiple browsers and tabs, switching pages, etc., could never see any memory leak which starts blowing up shared memory.
-
Thanks, one more, which browser are you using?
-
What Unraid version? What tabs do you have open?
-
Please open another tab and enter this in URL bar: tower.local/nchan_stub_status (of course use your hostname) It will display something like this: total published messages: 8625168 stored messages: 11 shared memory used: 72K shared memory limit: 131072K channels: 16 subscribers: 3 redis pending commands: 0 redis connected servers: 0 redis unhealthy upstreams: 0 total redis commands sent: 0 total interprocess alerts received: 0 interprocess alerts in transit: 0 interprocess queued alerts: 0 total interprocess send delay: 0 total interprocess receive delay: 0 nchan version: 1.3.7 I never see that "shared memory used" value get over 100K. If you see this number starting to grow, please post this output and let me know what tabs you have open on your server from all sources. thx
-
Just #1 which is necessary for all the other ones. To be totally safe, should upgrade to 6.12.15 which adds 'samesite=strict' to the session cookie.
