Tom3

I was only able to access the tunnel endpoint (the UNRAID server) at 10.253.x.x when using the "Remote Tunneled Access" mode. That showed allowed IP as 0.0.0.0/0 Nothing else seemed reachable. Changing to "Remote Access to LAN" mode I was able to access the server and the local LAN, but not the internet attached to the local LAN. -- Tom

Hi Drackeo - you have first to make a decision: to use RJ45 / Cat 6A cable, or to use SFP+ based connectors. This will drive the kind of card you purchase. For RJ45 / Cat6A: Pros: * Connectorized cables are inexpensive and readily available, or you can make your own. Cons: * The modules with RJ45 are usually higher priced, * The latency is a (lot) more than SFP+ units, * The power is a higher than SFP+ units. * The reach is sometimes limited to 30 meters depending on the interface. Some SFP+ to RJ45 adaptors have such limited reach. For SFP+ : Cons: * You need a special cable. Can be DAC (Direct Attached Copper), Multimode fiber (several hundred meters) or Single mode fiber (about 10 km). * DAC copper usually limited in reach to maybe 10 meters. Pros: * The prices on 10G DAC and fiber have dropped dramatically recently. I saw DAC 3 foot for $15, MMF for $17 and SMF for $27. * SFP+ usually has much better latency and lower power. You should look at the total system cost (Cards, modules, cables, etc.). NICs with SFP+ and 10G switches with SFP+ can be significantly less expensive than RJ45. Note there are SFP+ adaptors that plug into SFP+ slot and provide RJ-45 interface. Check the reach of these as the less expensive ones have poor reach on CAT 6A. The power of the adaptor may limit how many you can plug into a SFP+ switch. But they are handy when you have a device and you have to convert. -- Tom

Having a simple way to persist the public key would be nice for SSH. If a similar method can also be used for root login, even better.

Hi On the MAIN page of UNRAID, under Array Devices, where the disks are listed... 1. The dot in front of each disk device spins that one disk up or down (toggling the state). Hover your mouse over the dot to see... 2. There are up and down arrows just below the list of devices (on the line Array of {number} devices) to spin down or spin up all devices. -- Tom

You may find it helpful to read on the Wiki about Parity drives: https://wiki.unraid.net/UnRAID_6/Storage_Management#Parity_Disks One possibility for identifying disks may be to spin down all the disks, then spin them up one at a time while looking at each disk activity indicator LED. -- Tom

I am not completely clear on your question. Spaceinvader One did a great video of OpenVPN-AS, with an update in 2019. https://www.youtube.com/watch?v=fpkLvnAKen0&t=363s This installs and runs well on UNRAID 6.9.0-rc2 for me. And another on routing docker containers through another VPN container: https://www.youtube.com/watch?v=znSu_FuKFW0&t=4s -- Tom

Had this same problem for a long time, reported once many months ago. Upgrading to 6.9.0-rc1 fixed it. Now on 6.9.0-rc2 and still working correctly. -- Tom

OK, 36V is an unusual UPS battery bank voltage. My numbers assumed a 48v bank. Does your server load increase when the UPS switches on? Sometimes the server starts a shutdown process which increases the load. The 36.9 minutes I think assumes the UPS goes to 0% charge. The table above appears to be to shutoff when the battery gets down to 25%, and MAXTIME of 1800 seconds (30 minutes). The table shows OUTPUTV of 0.0 volts. Not sure what that refers to, my UPS driver does not provide that parameter.

Not sure if the table above is right after the discharge event, or after the batteries have been charging for awhile. On the graphic it shows BATTV as 42.3 volts. For a 48V lead-acid battery at room temperature that's about 1% charged (99% discharged). The table also shows BCHARGE at 71 percent. Those two numbers disagree with each other. While float charging, the battery should sit at 54.4 volts for 100% capacity. Some Q&A at Dell Community says that R710 server supplies load-share, except when lightly loaded. https://www.dell.com/community/PowerEdge-Hardware-General/PowerEdge-dual-power-supply-and-power-load-balancing/td-p/3448711 -- Tom

HI SLimat - it appears you have the ownership set incorrectly. The user should be 'nobody' and the group 'users'. It looks like the user is 'users' and the group is blank. Not sure what happens when the group is unspecified. You can chown nobody:users on the affected directories/files. -- Tom

Hi Slimat - I would not change the UID/PID in the VM. The nobody/users ownership in UNRAID allows anonymous access, so changes should not be needed. You can recursively change permissions of the files. Pick whatever access attributes you feel comfortable, they need to apply also to the last field (i.e. not 770, but 777 or maybe 776 (R/W but not X) or 774 (read only). On my system I have the . and .. directories set to 777 and nobody/users, while the individual files are set to 444 read-only. You have multiple choices to meet your needs. -- Tom

Hi Slimat, root always has UID=0 (it doesn;t necessarily have to be called root, that could be changed). You may want to look at the permission for the share on the server. Just open a command line to /mnt/user/to_your_share then do a ls -la The will show you something like: dxwrxwrxwr 1 root root 4096 date ./ dxwrxwrxwr 1 root root 171 date ../ --wr-wr--- 1 root root 227594 date the_file_name ... etc ... If the owner and group are root root (as above) and the file permissions (the trailing --- above on the filenbame) prohibit wr access to the user then you won't have permission to read or write as UID=1000. Unraid uses nobody users to mean the anonymous owner/group. chown command changes the owner/group (lookup syntax via google) chmod command changes the permissions. If you want to open it up to anybody, chmod the permissions to 777 on the file(s). (again, lookup syntax via google). I use a share to backup my computers, using anonymous access because my backup program only understands that. Then I go in afterwards and change the backup files owner/group to root root and permissions to 444 (allowing read-only access). This makes the backup files usable for restoration, but they can't be changed. -- Tom

At the command prompt: root@Tower:~# id uid=0(root) gid=0(root) groups=0(root) root@Tower:~# Similarly at the VM's command prompt will probably give you something like UID=1000 PID=1000 Groups=1000 (typical for Ubuntu VM).

For me this turned out to be dependent on the exact browser type and version. It failed in Microsoft Edge (latest version at the time attempted a month ago). Worked OK in Chrome, failed in a previous version of Firefox, but the latest version of Firefox 84.0.2 seems to work OK. -- Tom

Do you have an Internet modem that is assigning addresses from a DHCP pool? Does that pool overlap your server address? Many (perhaps most?) modems will automatically build a table of MACaddr + IP address then reserve that IP address. That's so if you reboot some device, it gets the same IP address each time. I've had issues where the modem default was to have the DHCP pool be the entire /24 address space. So an old NIC's MAC address / IP address pair remains in it's table. It's called IP Reservation on some devices, Static Lease on others. My particular modem has a GUI to allow adding/dropping MAC addresses from that table, and that fixes such things for me. Your modem may vary... -- Tom

The 6.9-rc1 fixed multiple issues, many thanks to the team at Lime. 1. The disappearing VMs on Dashboard now works correctly. 2. noVNC on now works with both Firefox and Chrome (was: broken on Firefox). -- Tom

Firefox 83.0 was working earlier today with Unraid 6.8.3 / noVNC but not 6.9. I just tried Chrome and the VM comes up successfully in noVNC. -- Tom

In 6.8.3 I had a number of VMs that ran perfectly. Then upgraded to 6.9-beta-35 1. All VM's were completely dead. I deleted all VM's and disk images, then disabled VMs in the settings plugin. 2. In the settings / VM manager I disabled VMs then used the checkbox to delete libvirt.img. 3. Then enabled VMs in the VM Manger settings giving me what I hope is a completely clean slate. 4. At this point have tried multiple known-good ISO images (successful on 6.8.3) to create VMs. Then all create successfully and start, but Attempting to use noVNC to view any VM always results in noVNC error: noVNC encountered an error: SyntaxError: import not found: encodeUTF8 http://192.168.0.250/plugins/dynamix.vm.manager/novnc/core/rfb.js:12:9 no VNC So at this point I am unable to create or get any VM to run. Docker seems to run just fine. Are there suggestions how I might be able to get a VM to get past this noVNC error ? -- Tom

@JorgeB - thanks for the information! Are there know issues trying to run VM's created in a previous version of UNRAID? When I did the 6.7 to 6.8 upgrade my VM's had issues with noVNC. It appears again on the 6.8.3 to 6.9 upgrade. -- Tom

On upgrading from 6.8.3 to 6.9 beta 35 - having problems with VMs. Starting one VM suddenly makes half of the available VM's disappear from the dashboard, but they are all listed on the VMs page. Very strange. While the VM starts, attempts to connect using noVNC gives an an error about missing rightgutter missing. About half of the VMs were created in 6.7. Then upgraded to 6.8.0, 6.8.3. then the other half of the VMs were created. A wild guess -- do all VM's and docker containers need to be deleted then re-created in 6.9 in order to function? The need to upgrade from 6.8.3 to 6.9 is that the VMs and Dockers are hammering the lone nVME Cache BTRFS memory device. One week of uptime on a single (idle) VM did 129 million writes - about 5% of the cache lifetime. Starting any VM takes about 20,000 writes to cache. Leaving any VM or Docker running appears untenable in 6.8.3 due to the flash lifetime write limit. My hope was to upgrade to 6.9 to work around this issue. Downgrading from 6.9 beta 35 to 6.8.3 left the cache set as an unassigned device, and no VMs or Dockers. Fortunately stopping the array and re-assigning cache brought everything back under 6.8.3. -- Tom

Using a Xeon D-1541 (8 core / 16 thread) 2.1 GHz, motherboard is Supermicro X10SDV-TLN4F. Idle power runs between 21 and 25 watts. 32G ECC RAM, NVMe Cache.

I use NVMe as cache drive. It routinely would get to 75C during normal write activity. Added an after-market M.2 heatsink (available from Microcenter and others) to the NVMe M.2 stick. The temps now run normal on it. -- Tom

Unraid + UPS was fully tested this morning. One hour power outage. After hitting the time-on-battery limit, UNRAID cleanly shutdown automatically. The UPS alarmed after the timer, then shut itself down until the AC power returned. The server BIOS is (intentionally) set to NOT automatically reboot on power restoration. Powered-ON via IPMI, and all came back up with no reported errors. Kudos to Lime - this all worked perfectly. UPS: APC Back-UPS 650 -- Tom

Dynamix System Temp - update seems to have display issue. Previous Dynamix System Temp worked fine, displayed correct values. Updated to 2020.03.31 and now the motherboard temperature displays as infinty symbol (wow, that's really hot). The Processor temperature still displays correctly. Unraid 6.8.3 Attached is a screen clipping of just the bottom right part of the display. -- Tom

I had this issue as well, updating to UNRAID 6.8.x fixed. -- Tom