dnLL

Is the SSD trim plugin dead for 6.11.x? Don't see it available at all. Is Unraid handling this by itself now?

Thanks for this! Only plugin I used before that isn't there: xinetd-2.3.15-x86_64-3.txz

Every torrent has been stuck to downloading metadata since a few days on my side with the PIA vpn. Nothing in the log, the UI works well, I get an IP from PIA without any issue. I tried changing the network card used by qbittorrent in the UI options between tun0 and eth0 without any luck. Seems to be related specifically with PIA? Edit: I fixed it by forcing an update of the docker even though there was no update. Very weird problem. I see other people commenting on issues with PIA and qBittorrent online (not specifically to Unraid), I'm positive there is an issue somewhere but anyways.

While I agree with this, the plugin was specifically marked as deprecrated on Community App (if I understand correctly). Maybe Community App could handle this better and warn the user about plugins that have not been updated since the last major version? This is one more reason to add an option to run Unraid as a VM within Unraid. This is something I've been doing for a while, I paid an extra licence for it to run correctly and have 2 flash drives instead of 1, but it's been a life saver for me. While Unraid isn't exactly your typical "production-ready" operating system, many of us homelabers start with the smallest of project only to eventually host projects that people do rely on. Having a test VM to see what changed and especially to test plugins against the new Unraid version saved me precious hours of uptime on my main system. Anyways. Hopefully this can be handled better in the future.

Hello y'all, My monitoring tools started showing my Unraid server was using a lot of shared memory. Here is the chart from the last 24 hours (with the server mostly idling): So, I did a little bit of search on the web and tried the following: root@server:~# free -m total used free shared buff/cache available Mem: 64191 30582 18970 13022 14638 19920 Swap: 0 0 0 root@server:~# ipcs -m ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status Not much to see here, except I do see there are indeed 12+ GB worth of shared memory. I then stumbled upon the following post (https://stackoverflow.com/a/40712727/1689179) and script: cd /proc for i in `ls -d * | grep -v self` do if [[ -f $i/statm ]];then echo -n "$i "; cat $i/statm | perl -lan -e 'print ($F[2] * 4096)'; fi done | sort -nr -k2 | head I got the following results: root@server:~# sh test 1034 49528832 19397 30261248 2919 29437952 1445 26116096 1062 24440832 5986 23838720 5598 23777280 5807 23760896 6567 23732224 6266 23629824 root@server:~# ps -p 1034 -p 19397 -p 2919 -p 25669 -p 1062 -p 5986 -p 5598 -p 5807 -p 6567 -p 6266 PID TTY TIME CMD 1034 ? 03:52:53 dockerd 1062 ? 01:44:31 containerd 2919 ? 00:08:48 mono-sgen 5598 ? 04:03:06 qemu-system-x86 5807 ? 15:12:03 qemu-system-x86 5986 ? 15:52:44 qemu-system-x86 6266 ? 2-19:39:15 qemu-system-x86 6567 ? 04:24:21 qemu-system-x86 19397 ? 00:41:01 Plex Media Serv So dockerd/containerd and qemu. I don't see anything relevant in the logs... what could have triggered the sudden raise of shared memory usage?

Has this been fixed?

I'm using the USB Manager plugin to run an Unraid VM within Unraid and since then, I'm getting this error every night: fstrim: /mnt/disks/UNRAIDVM: the discard operation is not supported I could uninstall the plugin and run the fstrim command only on my cache but a fix would be great. Not sure why it tries to trim my USB drive.

I want to monitor my Unraid licence status (trial expired or not, basic, standard or pro with X drives connected out of the Y limit). Is there a way directly on Unraid to do that from the command line interface? I started looking at /usr/local/emhttp/plugins/dynamix/Registration.page but I was wondering if there was a clever way to do that other than reverse engineer the PHP and try to run it from the CLI.

Link is dead, new link: https://ibracorp.gitbook.io/virtual-unraid/

I restarted the plugin and it now works. Any plan to add notifications?

I have the plugin enabled and the app works, however I don't see my UPS and the log section is empty. I made sure the plugin is enabled in my server settings as well. I don't see temperatures or fans either so I figured if works as if the plugin wasn't installed. What's wrong? Also, any plan to add notifications? I tested another app called Array that currently has notifications and UPS data with no plugin. The UI of ControlR is just miles ahead however and I need the support for multiple servers as well. Honestly the notifications is the only thing missing from ControlR IMO.

Randomly came around this thread, do you need to flash the firmware for this card or does it work out of the box? Or rather, is there any benefit to flash it? I'm not sure why yet but everytime I see anything about LSI, all I hear about is how you need to flash the card to some IT mode right off the bat, which is... stupid? Also, does this generate a lot of heat? I have a Fractal Design R5 with a bunch of fans so generally decent airflow but nothing on the PCI slots directly.

I'm currently using the Samsung BAR Plus and it has yet to break but it hasn't been a year yet, we will see. Anyways, I'm out of topic a little bit :] Point is, it could be improved especially for running Unraid as a VM within Unraid itself, but yes I'm sure it works fine with a different flash drive properly set up.

Yup, and flash drives aren't very reliable in 24/7 operation, I've tried plenty of makes and models and anytime I get 300+ days of uptime, I need to change the flash drive since it's corrupted and won't even properly reformat (sometimes it does but I don't trust it anymore). So I definitely don't want to duplicate that problem. You need to have a different flash drive model than the one running on your hardware as well. I guess I will wait for Limetech to come up with a solution that doesn't involve having a flash drive.

From the tutorial I saw... it seemed to involve a lot of tricks to make everything work as it should. Not being able to emulate the flash drive is an issue for me as well.

I was waiting for a couple of minor revisions before upgrading from 6.8.3, just did it this morning, straight to 6.9.2, the update was seamless. I even added a disk after I shut down for the update and it rebooted just fine with the update and detected the new disk that I added to the array. One issue is with the VNC browser viewer for VMs. same as here: Disabling adblock didn't help but clearing browsing history does the trick. For anyone interested, under Chrome, you don't have to clear your whole history (I definitely didn't want that), you can clear only the "Cached images and files" from all time and you're good to go. It won't change much in practice, it just forces Chrome to redownload everything it put in cache which is exactly what we want here. Other than that, I wish we had an easy way to test features in a non-production environment in Unraid without buying another license and having other dedicated hardware. Making Unraid work as a VM in Unraid requires a lot of workarounds currently.

For what it's worth I just decided to upgrade to Python3. So I uninstalled Python2, pip works fine with Python3, just had to update some other scripts I was using that weren't fully compatible with Python3 but I'm glad I made the switch.

I have python2 and pip installed, however... root@server:~# pip install docker -bash: /usr/bin/pip: /usr/bin/python3: bad interpreter: No such file or directory root@server:~# python -m pip /usr/bin/python: No module named pip Somehow pip is looking for Python3, which I don't have installed. If I install it well, it works but for Python3, I need pip for Python2. I noticed there is a pip3 command as well, not sure why the default pip command isn't configured correctly.

I'm happy to hear about this. I will wait for the stable version, hopefully soon. Sent from my Pixel 3 using Tapatalk

I'm having the same issue of high disk writes on btrs cache with dockers. This seems to be very well known... My SSDs are are 35 days old, my server didn't do much (the mover barely moves anything) and yet, 25 TBW on both SSDs. They're 500G SSDs, so that's 50x their size in a month with a server idling 99.999% of the time. Insane.

I noticed the docker doesn't ping anymore now that it's in a different subnet. I can access the webUI just fine, but pings don't work. I see the ICMP requests go through my pfSense, just no reply from the docker. It works with dockers that are in the same subnet as the host, and it also works for VMs that are in that specific separate subnet (which is a separate VLAN). Networking is so complicated. Trying to fix the ping issue for my monitoring server... eh... EDIT: it's only THIS specific docker that has the issue. And pings work fine if I disable VPN. So I guess it has something to do with the docker itself. It's all right, I'll just stop monitoring pings on a docker haha.

Just got it working without editing the routing table. I just edited the docker settings instead, enabling br0.2, then selected br0.2 for the qbittorrentvpn docker and changed the IP to 10.1.2.54 and done. It's now sharing that other dedicated VLAN with the developer VM. It would probably be a better idea for me to put it in its completely separate VLAN but that will do for now, as I would need to shut down all the VMs/shares to edit the network settings and I can't do that right now (hosting some semi-important stuff). Thanks for your help by the way, happy you immediately found the issue. I will probably do some network redesign next time I do a planned maintenance.

I'm still learning when it comes to networking (I started this pfSense project from scratch), what I currently have is my LAN network on 10.1.1.0/24 and I have a couple of VLANs on different /24 subnets. All of my "safe" LAN devices (such as my desktop, my server and most of its VMs and dockers) are in that same subnet. In Unraid, I have eth0 with "VLAN number" set to 2 because I have one VM using br0.2 instead of br0. That VM is in its own separate VLAN. When it comes to the routing table however, I only have what I consider to be the default settings: Not sure what to add/edit exactly. I wouldn't mind the docker to be in the 10.1.3.0/24 subnet but I guess it would require some additional route and/or something on the pfSense side since that subnet just doesn't exist currently for pfSense. I guess this is more of a general Unraid and routing question that has nothing to do with this thread at this point.

Ah, and why is that? It works with the other containers. I guess I'm just going to put it in a separate VLAN then. What if I change the lan network to a smaller subnet? I'm not using the default bridge because it's easier for me to monitor the docker when it has a different IP address than the server (I use CheckMK to monitor) and also because I would have other dockers trying to be on port 8080 which would be a problem as well (since most templates aren't designed to modify that setting even when it's there).