lafrance

Hi Jonathan In the end you were absolutely correct. With the pfsense VM down it was possible to access the unraid GUI via the fixed IP of the server. It was all a bit odd though as I'd first tried it with a Windows machine and no matter what I did it just kept coming up with the XXXXXXXXXXXXXXXXXXXXX.unraid.net. I then had another go with a machine running Ubuntu and that worked without any problems. Thanks for your help. La France

Thanks for the quick reply. When I try that the connection tries to resolve the SSL certificate that's initially needed for the disc encryption set-up. I thought initially that would be the simplest solution as well.

Dear All Here's a question that could definitely be a catch 22 which needs some creative thinking which is beyond my hands on experience. I have an unRAID server which is fully encrypted as per SpaceInvader's extremely well thought through instructions. Just recently I installed an ethernet quadboard into the machine and installed pfsense on a VM (again many thanks to SpaceInvader). Everything works just brilliantly. The pfsense LAN port is connected to the switch and the server ethernet port is connected to the same switch. As per SpaceInvaders instructions the pfsense ports are essentially physically separated from the server port. The issue I have came to light when we had a power outage (the machine is on a UPS but the time ran beyond the support time for the battery.). When the machine is restarted the discs and the services will only restart once the passphrase is re-entered. Without the VM starting it is not possible to log into the server. I set the machine up with a fixed IP. The server normally runs headless and my workaround has been to hook up a monitor and keyboard and start the machine from the OS GUI option. Has anyone any ideas that could point to a neater solution? If I've missed something obvious here I don't mind being called stupid!! A remote start option as described using an external FTP server won't work as the server hasn't any internet access until the pfsense VM starts. La France

I have exactly the same problem. The old server running 6.7.2 follows SpaceInvader's video exactly. When I've tried this on a test machine I have running 6.8.0-rc3 I get the same error.

OK. As soon as the system fails I'll upload the zip file.

Morning Frank1940 thanks for the reply. I'd taken the server back to 6.6.3 as a I mentioned and after the 3 hours I had the same problem occur. I've attached the diagnostics report as requested. Thanks for spending time on this. tower-diagnostics-20181204-0919.zip

I have tried those options and it hasn't made any difference. Thanks anyway for the suggestions.

Dear All I've been using unRAID now for over a year and apart from a few minor hiccups (usually caused by my stupidity) everything has worked seamlessly. It's just a great application. On Saturday I upgraded from 6.6.3 > 6.6.5. As always that ran without any drama. I'd run the update assistant before the install just to check everything was fine and it was. Everything was completely normal. The log in and web GUI ran just fine. After three hours though when I checked the web GUI opened showing the main menus but no content. I re-booted via the console and I then had access again. This morning the same problem existed where the web GUI opened but without content. I've just downgraded back to 6.6.3 without any issues and the GUI seems stable. The servers being used quite heavily at the moment. Has anyone else had the same experience? There have been some mentions that the Netdata docker or some of the Dynamix plugins might be a cause but that doesn't make any sense. If anyone had any ideas it would be a great help.

Hi Medikherb - its worth trying to get this to work. Now I have it all running it has marvelous utility. When I followed the video I couldn't launch Nextcloud either. I rechecked the domain settings via my DNS service and everything was fine. I use DynDNS rather than DuckDNS. My fix was to delete the path for /data and add the path again as new /data to /mnt/myfiles/nextcloud (I'd set up a share called nextcloud). Once I restarted the docker everything was fine. Hope this helps.

Dear Gridrunner - I've just got back to the office and your suggestion works brilliantly. Many thanks indeed for your suggestion it is exactly what I've been trying to achieve with Nextcloud.

Thanks for the reply. Apologies for dropping the post in the wrong support thread. I'll fix that when I get back to the office. I do have the external devices app installed. When I try to run run the app it just comes up with a message saying no permissions and no options to select any external sources. My user has admin permissions.

After following Space Invaders excellent video tutorial on setting up the Linux Servers Nextcloud docker I now have a fully functional server. I must say that it is really fantastic. I do however have one question. I have the /data mapped to a specific share as recommended by Space Invader. Rather than drag and dropping files into that share I'd ideally like to be able to mount an additional SMB share which is being constantly updated with some family research information that I'd like to be able to give people links to the various files. Nextcloud does have this function but it doesn't seem to be available in the docker. I haven't been able to figure out how to install the SMB client. Has anyone had any success with this? Any help or suggestions would be much appreciated. Many thanks in advance.

Bonienl Apologies for the tardy reply. This seems to have been a combination of things which I'm still figuring out. One of which as you say was an issue with what is in fact an old router coupled with a flaky ISP connection. Thanks for your help. LaFrance

Hi Johnnie Thanks for this as your suggestion made me check on a couple of things. LaFrance

Hi Unevent Thanks for this as the suggestions are very helpful. I'm away at the moment and will get back onto this when we return. LaFrance

Hi Joedotmac Apologies for the slow reply but work commitments got in the way. I really appreciate your help with this and will take a look in the next couple of weeks. I have a feeling this is a combination of a real problem coupled with me being a bit thick. I'm away at the moment and will get back on the case when I get back. The OS is really great and does everything we need in the house so fixing this has a priority. Again many thanks for your help. LaFrance

Thanks for the suggestion. I've actually tried this and it doesn't make any difference at all. Soon as the machine is rebooted if i set the IP address to 192.168.0.10 it reports: 192.168.0.1/24 dev br0 proto kernel scope link src 192.168.0.10 linkdown

Thanks for the reply unevent. I've attached the two files. 0824 is with DHCP set on unRAID and 0836 is when the IP is set at static 192.168.x.10. For the test rig the machine is the only thing connected to the router so there's no chance of any IP conflict. The router has a DHCP range set to 100 - 254. Best Regards Lafrance tower-diagnostics-20170427-0824.zip tower-diagnostics-20170427-0836.zip

Thanks joedotmac It is weird as my test rig is the only think connected to a router with a DHCP range set at 100 - 254. If I boot with unRAID set for DHCP it normally gets allocated .100. I can log into the GUI without problems and everything is fine as eth0 is linkup. If I then reset to static either in or out of the DHCP range the machine boots with link down. I can still get access to the GUI but no internet. If I reset to DHCP on unRAID everything is then fine. The ifconfig -a output looks like the below with DHCP set in unRAID: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2343 bytes 277060 (270.5 KiB) RX errors 0 dropped 7 overruns 0 frame 0 TX packets 2721 bytes 1119668 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2372 bytes 317176 (309.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2721 bytes 1119962 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 With the IP set to 192.168.0.10 as static using the default DNS: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 0.0.0.0 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 983 bytes 103099 (100.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959728 (937.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 988 bytes 117813 (115.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959836 (937.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 4 bytes 312 (312.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 312 (312.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Any ideas? Best Regards Lafrance

Thanks for the reply unevent. I've attached the two files. 0824 is with DHCP set on unRAID and 0836 is when the IP is set at static 192.168.x.10. For the test rig the machine is the only thing connected to the router so there's no chance of any IP conflict. The router has a DHCP range set to 100 - 254. Best Regards Lafrance tower-diagnostics-20170427-0824.zip tower-diagnostics-20170427-0836.zip

Thanks joedotmac It is weird as my test rig is the only think connected to a router with a DHCP range set at 100 - 254. If I boot with unRAID set for DHCP it normally gets allocated .100. I can log into the GUI without problems and everything is fine as eth0 is linkup. If I then reset to static either in or out of the DHCP range the machine boots with link down. I can still get access to the GUI but no internet. If I reset to DHCP on unRAID everything is then fine. The ifconfig -a output looks like the below with DHCP set in unRAID: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2343 bytes 277060 (270.5 KiB) RX errors 0 dropped 7 overruns 0 frame 0 TX packets 2721 bytes 1119668 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2372 bytes 317176 (309.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2721 bytes 1119962 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 With the IP set to 192.168.0.10 as static using the default DNS: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 0.0.0.0 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 983 bytes 103099 (100.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959728 (937.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 988 bytes 117813 (115.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959836 (937.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 4 bytes 312 (312.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 312 (312.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Any ideas? Best Regards Lafrance

Morning Squid Thanks for the reply but no. That's one of the things I checked. It is all very odd as I've now tried this on two completely different machines and got the same result.

I'm still experimenting with unRAID and it's capabilities seem endless. As things have gone well I'm just about to transfer everything to the main box and start setting up. However, I've just hit on an unusual problem and wondered if anyone else has seen this particular issue. On the network settings I've been running DHCP. Things have gone fine everyday. Ultimately I want the full time machine to be on a static IP. I'm running version 6.3.3 and as soon I fixed the IP and DNS addresses to Google when I rebooted the br0 link was reported as down. Initially I thought this could be a router problem and ran the machine up on a separate network with exactly the same result. In the sys log there is the following error. probe link rx_err and tx_err hw When I go back to DHCP on the IP address and DNS everything is fine. If I then opt for DHCP on the IP and static on the DNS addresses again everything is fine but as soon as I set a static IP the link is down. There's only one NIC on the test machie(s) I've tried and all display the same problem. There's nothing unusual in the BIOS either. Has anyone got any suggestions as to what a fix might look like? Your help would be very much appreciated.

I realise that this question has probably been asked before but now having discovered unRAID is there a feasible way to import a FreeNAS volume into unRAID without loosing data? Having now played around with the OS I am highly impressed and would really like to make the switch if possible. Many thanks in advance for any help with this. LaFrance