tr0910

It's quite common in China for updates and installs to hang for no reason. Then suddenly a week later, it will work fine. When you are behind the GFW, this is normal. Expect to be frustrated. I used to use Peter's plugin from China accessing my unRaid server in America. In 2014 that was good enough to access Facebook Google etc from China. But that is no longer the case. New tools are required now.

Might be my connection to docker hub. This server is in China behind the GFW. They might be blocking something new today....

With my dual 2670 rig with Intel 2600cp mb and 96GB ECC ram, the first boot of a 2 core 32GB Win10 Pro VNC is 8 seconds to TianoCore and further 78 seconds to login screen. This is with only 2 cores (6/22). Changing to 4 cores (6/22, and 15,31) drops the boot time to the login screen to 10 seconds after the same 8 seconds to TianoCore. Then bumping to 24 cores of 32 total allocated to this Win10VM drops boot time to 8 seconds to the login screen with the same 8 seconds to TianoCore . All testing done over VNC. Initial Memory: 32768 Max Memory: 32768 Machine: i440fx-2.10 BIOS:OVMF More memory and more cores are not slowing my VM boot speed at all. (Nothing is passed through to this Win10 VM. unRaid 6.50)

Anybody having trouble pulling the docker down. I downloaded the xml file and uploaded to flash as my-Diskspeed.xml After pulling the fs layer I get.... Error: error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/99/99f826b4904595eb9a74607c19a094bc081a5bce3207e8534dca548ccc98ec96/data?Expires=1522846668&Signature=ZkYgL1dLS1ZDM49hidy5hLFEDzDQ9Jzl~6rm8xelIOF-fBSHg4EnOeoRrPyvgwgbYyG26vCPTsBSvqjMB3AVBMcRwAzGcJXkMdqnFEvmxQzxLG~5Ri9-o1QDMX8iIlyfu-rZSarW8posR-LDANxYPfRh~_&Key-Pair-Id=APKAJECH5M7VWI: net/http: TLS handshake timeout

Just to clarify what johnnie.black says. You need Win 10 Pro on the VM on unRaid, but the laptop connecting in can be running the lowly Win 10 Home version. I do this all the time for Office and web browsing and really love the user experience over wired gbit and even over wifi.

Nice cleanup to my original ugly looking script. Interesting that you are able to eliminate the IPMI wakeup checks. Even locally, I would sometimes get a server started, but not available. Since it wasn't able to rsync, I would get lots or errors. A subsequent power cycle always seemed to fix things.

(above from dlandon) several days ago, but let me make the following clarification... You must have one drive in your array encrypted with the same password or keyfile that you want to use with an unassigned device. This is only because without that, unRaid won't even ask for any encryption credentials, and unassigned devices needs the ones from unRaid before it can mount an encrypted device. Other than that clarification, I haven't seen any issues with the implementation. Thanks @dlandon

Yep, seems to fix it....

yes

I have the disk attached as an array disk. It was showing in unRaid as an XFS in UD, not sure why as it is presently formatted as an unRaid array device as XFS Encrypted (and confirmed in the disk settings) and I am copying files to it at present. The drive shows the green padlock for encrypted and unlocked status. Is there some commands I can run on the disk to see why it isn't showing in UD correctly? Or I can start over with another smaller disk and see what happens?

I have a 8tb disk that has been formatted XFS_encrypted with a 70 char keyfile. Stopped the array and did a new config and then attempted to connect the encrypted drive via unassigned devices. Here is the log file resulting.... Doesn't seem to want to mount. After, I stopped the array again and reattached this encrypted disk via an unRaid array mount without problems. Does unassigned devices only support keyboard entered passwords and not support keyfiles at present? The 70 character keyfile uses A-Z, a-z, 0-9, !@#$%^&*() characters. unassigned.log

Great news....

Ok I recall @limetech expressed interest in taking over unassigned devices. Is this still planned? I appreciate that unassigned devices now can format drives in array compatible format. In my opinion, unassigned devices is the most critical add-on to unRaid. Well done @dlandon and others who have taken it this far.

So @limetech needs to fix something before @dlandon can fix unassigned devices to support encrypted drives? This won't be an easy fix??

Encrypted disks created as part of the array on 6.4rc17b and then removed from the array and connected by unassigned devices, doesn't seem to work. It correctly identifies the FS as crypto_LUKS, but doesn't want to mount the device. This is after starting the array and giving unRaid the passphrase the encrypted drive requires for proper mounting. Is it just me, or is this still not yet working?

You suggest only setting up a small vdisk for the vm. Yet you choose 70gb. I normally set mine up as only 30gb, and I still have 18gb free after getting Win10 N Pro 1703 creators update all set up. Yes Creators Update 1703 N only uses 12gb after install. Why do you want so much free space? You are suggesting a different install process than what is in the wiki. Adding the other virt io drivers later is faster, and it works well.. Should we be modifying the wiki for your new faster install process?? This will be a great help for the new unRaiders who want to try a Win10VM. All that is left to do is create an automatic script that does this all for us without intervention......

Apr 20 07:54:59 tower root: error: plugins/preclear.disk/Preclear.php: missing csrf_token Apr 20 07:55:09 tower root: error: plugins/preclear.disk/Preclear.php: missing csrf_token Apr 20 07:55:19 tower root: error: plugins/preclear.disk/Preclear.php: missing csrf_token Apr 20 07:55:29 tower root: error: plugins/preclear.disk/Preclear.php: missing csrf_token Apr 20 07:55:39 tower root: error: plugins/preclear.disk/Preclear.php: missing csrf_token Unraid 6.3.3 with preclear plugin 03/31/2017 and I uninstalled and reinstalled the plugin yet am still getting these errors. Server is behind the great firewall of China if that matters... drchina1-diagnostics-20170420-0807.zip

I have been using rsnapshot some v5. Very good once you get it properly configured. I never was happy with the top level mount point that it uses. /mnt/disk1/documents I wanted to go straight to /documents via mobile

Is this the right way to kill an VPN session to a server? It also hangs the bash terminal.. You need to press Ctrl C to continue, and then it seems to work fine again. pkill -SIGTERM -f 'openvpn --config /boot/openvpn/karli.ovpn' & How do I kill hung openvpn command line sessions? I want to script the following openvpn start do some stuff with the vpn active openvpn stop but hung sessions are causing a problem.

Running with a "&" suffix still results in the same hung terminal session. After pressing Ctrl C and checking ps nobody 14748 1 0 2016 ? 00:00:09 openvpn --writepid /var/run/openvpnserver/openvpnserver.pid --config /mnt/cache/appdata/myVPNserver/openvpnserver.ovpn --script-security 2 --daemon root 25180 127452 0 14:53 pts/2 00:00:00 openvpn --config /boot/openvpn/karli.ovpn root 33595 127452 0 15:09 pts/2 00:00:00 grep openvpn This shows that it is still running and I can ping the IPMI interface and the running remote unRaid server. However running ipmitool -I lan -H 192.168.1.179 -U ADMIN -P ADMIN chassis power status Error: Unable to establish LAN session Unable to get Chassis Power Status So it isn't really full connected?? My bad.... I was checking wrong ipmi ip address. This shows that it is correctly working even though the terminal is hung.... ipmitool -I lan -H 192.168.1.178 -U ADMIN -P ADMIN chassis power status Chassis Power is on

I have been using your server plugin successfully for several years to access my server remotely. Today, I want to have my unRaid to be a client to another network where a vpn exists for the purpose of doing remote backups. I control both ends of this connection. OpenVPN server is running on unRaid and I want to run OpenVPN client via script for a few minutes to kick off the backupl I already have the remote backups running via rsync ssh, but now I want to take it to the next level whereby my local backup script fires off an IPMI wakeup call to the remote server over the VPN. So all I need is for a VPN to be created briefly where unRaid can see the other network like this. # Start the VPN tunnel to the network where my backup server is and where a raspberry pi is running an OpenVPN server 24/7 openvpn --config load_my_opvn_file # Now that the network is accessible use IPMI to start the backup server at the remote location ipmitool -I lan -H 192.168.1.95 -U ADMIN -P ADMIN chassis power on # Wait for unRaid to boot remotely and check that it is up sleep 180 # Check if the remote backup server is up and working # If everything is good, close the VPN connection and continue the backup by SSH # Once the backup has completed successfully via IPMI tell the remote backup server to gracefully shut down. ipmitool -I lan -H 192.168.1.95 -U ADMIN -P ADMIN chassis power soft Does this seem to be a reasonable way to use this? (I know this is different than the way most of you are using the client.) I installed the client VPN on unRaid 6.2.4, and then attempted to use the following command to test; openvpn --config /boot/openvpn/karli.ovpn Mon Jan 9 11:11:54 2017 OpenVPN 2.4.0 x86_64-slackware-linux-gnu [sSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Dec 29 2016 Mon Jan 9 11:11:54 2017 library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.09 Mon Jan 9 11:11:54 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]23.127.yyy.xxx:1197 Mon Jan 9 11:11:54 2017 UDP link local: (not bound) Mon Jan 9 11:11:54 2017 UDP link remote: [AF_INET]23.127.yyy.xxx:1197 Mon Jan 9 11:11:55 2017 [server] Peer Connection Initiated with [AF_INET]23.127.yyy.xxx:1197 Mon Jan 9 11:11:56 2017 TUN/TAP device tun1 opened Mon Jan 9 11:11:56 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Mon Jan 9 11:11:56 2017 /usr/sbin/ip link set dev tun1 up mtu 1500 Mon Jan 9 11:11:56 2017 /usr/sbin/ip addr add dev tun1 10.8.0.2/24 broadcast 10.8.0.255 RTNETLINK answers: File exists Mon Jan 9 11:11:56 2017 ERROR: Linux route add command failed: external program exited with error status: 2 RTNETLINK answers: File exists Mon Jan 9 11:11:56 2017 ERROR: Linux route add command failed: external program exited with error status: 2 Mon Jan 9 11:11:56 2017 Initialization Sequence Completed ^CMon Jan 9 11:29:58 2017 event_wait : Interrupted system call (code=4) Mon Jan 9 11:29:58 2017 /usr/sbin/ip addr del dev tun1 10.8.0.2/24 Mon Jan 9 11:29:58 2017 SIGINT[hard,] received, process exiting After sitting locked up for 20 minutes, I cancelled by hitting Ctrl C. I know this .ovpn file is good as I can use it via the Windows client to get access to that network. What am I doing wrong?

ipmitool is giving a false positive The plugin powerdown-x86_64.plg is not known to Community Applications and is possibly incompatible with your server https://lime-technology.com/forum/index.php?topic=42507.0

I have 12 disks with between 50,000 and 300,000 files each. One disk has the ransomware plugin installed with close to 1MM files from it in the bait directories. It seems to me that the integrity file plugin is not getting all legitimate files. When I exported disk1, I only got 10,000 files exported keys hash file, but when I use create a listing of all the files on disk1 I get 35,000 files doing it this way... find /mnt/disk3 -type f -fprintf /mnt/disk3/disk3.filelist "%P\n" How is the best way to verify that the integrity plugin isn't missing files?? Might it have something to do with inotify limits?? (this disk13 is a snapshot drive with hard links containing millions of links to about 100,000 files). At the time this drive wasn't excluded. I've also bumped the size max_user_watches from 500,000 to 2,000,000 files but haven't restarted the server since I have done it. Dec 23 14:16:11 Kim inotifywait[14210]: Failed to watch /mnt/disk13; upper limit on inotify watches reached! Dec 23 14:16:11 Kim inotifywait[14210]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. Dec 23 14:16:18 Kim kernel: sd 1:0:1:2: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 23 14:16:18 Kim kernel: sd 1:0:1:2: [sdl] tag#0 Sense Key : 0x5 [current] Dec 23 14:16:18 Kim kernel: sd 1:0:1:2: [sdl] tag#0 ASC=0x20 ASCQ=0x0 Dec 23 14:16:18 Kim kernel: sd 1:0:1:2: [sdl] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Dec 23 14:16:18 Kim kernel: sd 1:0:0:3: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 23 14:16:18 Kim kernel: sd 1:0:0:3: [sde] tag#0 Sense Key : 0x5 [current] Dec 23 14:16:18 Kim kernel: sd 1:0:0:3: [sde] tag#0 ASC=0x20 ASCQ=0x0 (Background: I was using bunker before using this plugin. All disks were fully hashed with bunker prior to this plugin being installed but the disk with the missing files has had significant new files added over the last few months. This plugin was installed as soon as it was available. So, what I am saying, is there is legacy stuff here possibly hanging around from the olden days?? )

Answered here by @bonienl: http://lime-technology.com/forum/index.php?topic=37290.msg524470#msg524470 Inside "\\tower\flash\config\plugins\dynamix.file.integrity\integrity-check.sh" I find the following /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker -Vqj -n -L /mnt/disk1 >/dev/null What is the new -j option in bunker? I don't see it documented in the initial option run list. I'm guessing there are lots more undocumented features to bunker. You must have an exclude option now, and ... Pretty please could we have these documented???

Is the last bunker 1.16 still compatible with this tool? Using bunker for exporting and checking that files are not corrupted after rsyncing to 2nd server. I have an external backup unRaid server rsynced over the internet that I want to verify by exporting the keys from the production machine and verifying with. bunker -c -f /tmp/disk1_keys.txt Where the disk1_keys.txt is exported from the server running this plugin and the destination backup server uses bunker to validate the rsynced backup files. I have done this several times in the last year successfully, but I want to know if I am just lucky, or that this is expected behavior?