dnLL

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.

State file handle errors happen on all my VMs for no apparent reason all the time. I know it's been a couple of months since your post but can you comment back on your milleage since August with nfsv4 in Unraid? The problem you describe (state file handle errors while and after restarting the array) isn't an issue for me (only using NFS for VMs hosted on Unraid, so rebooting the array means rebooting the VMs in my case).

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 deleted the docker directory and downloaded every docker 1 by 1. youtube-dl: 1.1 G duplicati: 3.4 G qbittorrentvpn: 7.5 G linuxserver/plex: 4 G Total of 17GB exactly. I'm a little bit confused because with the same dockers my docker.img was 4.1GB before updating to 6.9.X. I am... unsure what's going on exactly to say the least, especially if you have 30 dockers in less than 5G, that's insane in comparison.

Well if I go deeper I can see from one of the directory to another that similar lib files are here. root@server:~# ls -l /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/ | wc -l 52 root@server:~# du -sh /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/* | sort -hr | head 95M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/python3.9 90M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/libLLVM-11.so 53M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/libgo.so.16.0.0 36M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/dri 32M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/libgphobos.so.1.0.0 28M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/perl5 28M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/libicudata.so.69.1 20M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/libstdc++.so.6.0.28 19M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/udev 16M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr/lib/d3d I'm just very confused by what are the subvolumes exactly? I have 4 dockers but there are 52 subvolumes directories? Also, how do I know which subvolume belongs to which docker? At any rate, I don't really mind docker consuming 17G of space, it's curiosity more than anything else considering that all my dockers are configured to have their data into the appdata and they do consume 17GB right off after booting which seems like an insane amount of space for something that should theoretically be lightweight.

I have the exact same question as your first one, but I can reply to the other 2 since I made the switch following a recommendation in one of SpaceInvader's video (he doesn't say why however). It doesn't really use less space, at least for me. I'm not sure what's using 17GB of space honestly, I'm running 4 dockers: qbittorentvpn, plex, youtube-dl and duplicati. root@server:~# du -h /mnt/cache/system/docker/docker/ | sort -hr | head 17G /mnt/cache/system/docker/docker/docker/btrfs/subvolumes 17G /mnt/cache/system/docker/docker/docker/btrfs 17G /mnt/cache/system/docker/docker/docker 17G /mnt/cache/system/docker/docker/ 986M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init 986M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3 986M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/681dbb488afc61adc745b592f266b76ac9cd52b6689fe7a7bb9acd3eb117ad4f 964M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3/usr 964M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/f241e33ad5c10ab40fdc2f4c33e5a3cc6b8a0b7dffa7cad22188a348a9de96c3-init/usr 964M /mnt/cache/system/docker/docker/docker/btrfs/subvolumes/681dbb488afc61adc745b592f266b76ac9cd52b6689fe7a7bb9acd3eb117ad4f/usr As for whether you can transfer all the data... well, there is no data in your docker.img file technically, all you need are your customized user templates located in /boot/config/plugins/dockerMan/templates-user/. Then you just add your containers again, it should remember their configuration and boot normally.

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.

Fixed it by editing /etc/rc.d/rc.xinetd, changed all the en_us to en_us.utf-8. Now I need to script this to prevent this from happening again next reboot.

Something more interesting: root@server:~# cat /usr/bin/check_mk_agent #!/bin/bash locale root@server:~# /usr/bin/check_mk_agent LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF8" LC_NUMERIC="en_US.UTF8" LC_TIME="en_US.UTF8" LC_COLLATE="en_US.UTF8" LC_MONETARY="en_US.UTF8" LC_MESSAGES="en_US.UTF8" LC_PAPER="en_US.UTF8" LC_NAME="en_US.UTF8" LC_ADDRESS="en_US.UTF8" LC_TELEPHONE="en_US.UTF8" LC_MEASUREMENT="en_US.UTF8" LC_IDENTIFICATION="en_US.UTF8" LC_ALL= root@server:~# telnet localhost 6556 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US) locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US LC_CTYPE="en_US" LC_NUMERIC="en_US" LC_TIME="en_US" LC_COLLATE="en_US" LC_MONETARY="en_US" LC_MESSAGES="en_US" LC_PAPER="en_US" LC_NAME="en_US" LC_ADDRESS="en_US" LC_TELEPHONE="en_US" LC_MEASUREMENT="en_US" LC_IDENTIFICATION="en_US" LC_ALL=en_US Connection closed by foreign host. root@server:~# locale -a locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_COLLATE to default locale: No such file or directory C POSIX en_US.utf8 xinetd launching the bash script is trying for some reason en_us which isn't supported by Unraid.

Here is a full example: root@server:~# cat /usr/bin/check_mk_agent #!/bin/bash echo "test" root@server:~# /usr/bin/check_mk_agent test root@server:~# telnet localhost 6556 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US) test Connection closed by foreign host.

I tried editing my .bash_profile without any success. I tried adding export LC_ALL=C and export LC_ALL="en_US.UTF-8" but I still get the same error, it's as if the .bash_profile wasn't loaded when the script is started by xinetd.

I have a bash script that displays the following error before it even starts (the error is displayed as soon as bash is called/launched): /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US) I have to get rid of this error, the script is launched through inetd by my monitoring server and it can't parse the output because of that error at the beginning. So I checked locale: root@server:~# locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Seems like an easy fix would be to change LC_ALL to en_US.UTF-8 here. How do I do that in Unraid?

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.