Amahi Forums

I am very inexperienced when it comes to Linux and servers both. I have had a few issues and have looked for some time for help resources but was unable to resolve them and may have actually made them worse, but hopefully not irreparably. I installed Amahi 8 over the Fedora 21 minimal install.

First issue was bug #1871 the SSH issue with minimal Fedora 21 install, but the walkthrough worked perfectly (with a little bit of assistance from the internet) so that has been resolved to my knowledge (have been able to SSH in to server)

I have two issues that seem like they would be somewhat of a simple fix:

1. home.net, the domain that I setup, brings up an external webpage whenever I try to open it in a browser. I had opened a forum topic on this initially, then it resolved on its own, but now has started happening again.

2. Not all the DHCP leases are showing up in the network tab. I had initially set fixed IPs for two of the networked computers, then deleted them both. One of the two showed back up and I set up a fixed IP for it, the other computer has not shown up again at all. It connects to the internet just fine, and from my router shows up with the fixed IP that I initially created, but will not appear through Amahi

I have also had some greyhole issues. I have 3 4TB NAS drives which I pooled and began transferring to, however the transfer size seemed to be limited to the amount of free space on the root directory. I then installed an external HDD in order to use this as my landing zone but could not figure out how to set it. In my flailing I changed share locations and now cannot find the original data that I had transferred to the greyhole pool. So my issues now are:

3. How can I set the LZ for all greyhole shares to use the entire external HDD

4. Can I recover the data that was originally moved to the greyhole pool after having switched share locations?

I know that is a lot, and may not be the best explanation, but I am really stuck and was hoping someone could help me with at least some of these issues. Thank you.

I have resolved issue 4, it was simply an incorrect name (capitalization) for the share location

1. home.net, the domain that I setup, brings up an external webpage whenever I try to open it in a browser. I had opened a forum topic on this initially, then it resolved on its own, but now has started happening again.

This is likely caused by the DNS not working properly. Recommend you check out the Network Troubleshooting section in the wiki. This may also be a consequence of your #2 problem.

2. Not all the DHCP leases are showing up in the network tab. I had initially set fixed IPs for two of the networked computers, then deleted them both. One of the two showed back up and I set up a fixed IP for it, the other computer has not shown up again at all. It connects to the internet just fine, and from my router shows up with the fixed IP that I initially created, but will not appear through Amahi

It sounds like you are using your router for DHCP and DNS as well as the HDA. That's taboo and should not be done. Only one DHCP and DNS server should be running per network subnet. Otherwise the client will get the DHCP lease randomly from one of the two and cannot be easily controlled. Recommend you use the HDA for all network traffic. See tradeoffs if you would like to only use some of the functionality.

3. How can I set the LZ for all greyhole shares to use the entire external HDD

Recommend you refer tothe Greyhole Landing Zone guidance in the wiki. There is documentation for moving it to another drive.

BTW, you will notice that the Amahi Wiki is our repository of tutorials and how to guidance that will be useful for new users.

Thank you for the reply. I made sure to disable DHCP after the install in the router as outlined and could not find anywhere to select for DNS so there may be an issue there, but after the initial install I selected the shutdown from the online interface for the HDA and believed it to be off and so reactivated DHCP through the router, ran into sever issues and realized that the HDA had not shutdown. So there was a time when both were active, but that was the only time they were both running simultaneously. I am trying to get help through the IRC channel now but there doesn't seem to be much activity. Here is a link to the result of the walkthrough: http://ur1.ca/ofszs

I have read through the greyhole guidance in the wiki several times, as well as several other wiki articles, and still have been unable to make progress. I don't know if it is the terminology or what, but the guide seems incomplete or at least not tailored to the novice. On the first step of the move, checking the greyhole log, I get permission denied when I am logged in as root user. I tried to press on regardless, step 4 of the process is "Move the LZ from it's old path to the new path. You can do so using the file browser in X" - I have no idea what X means.

It continues. "or using the command line (eg. mv /var/hda/files/videos /var/hda/files/drives/drive1/videos) Make sure the permission of the new directory is correct, especially if you created empty directory manually instead of moving old one. (eg. chmod 775 /var/hda/files/drives/drive1/videos)" so to clarify, if I am trying to move the landing zone (from who knows where it is now, how do I find this out? is it just the /gh of each of the physical drives?) to be able to use the entire space available on /dev/sde would the code be /var/hda/files/drives/GreyholeLZexternal (the mount point listed for dev/sde2 (and why is this sde2 and not sde1?)

I think all my other issues are moot at this point. I tried to format the external drive, because it was still showing a small partition available in the drives. It now boots into emergency mode every time and can't find that drive. I am going to reinstall.

I have reinstalled and have resolved issue 2 as well. I had setup fixed ip and dns server settings in that system during the time both the server and router were running and I was having internet issues. It is now showing up in the network tab of the dashboard.

I am still experiencing issue 1, when I type home.net into the address bar it brings up the internet site home.net. I am also having issues with Plex Media Server, I posted in another topic for that issue.

For the lz, I just want to see if maybe I am understanding how things work now. The share location listed under each of the various shares in the dashboard is the LZ for that share if it is pooled in greyhole. Once the daemon is able to process any data moved to that LZ it is then moved to some other location and not stored there, is that correct? So if I were to pool 3 4TB drives and 1 160GB external drive (/dev/sde1) and wanted to use the 160GB drive as a dedicated LZ I would pool all of those 4 drives, then pool the shares, then set the location for each of the pooled shares to the mount point of the 160GB (in this case /var/hda/files/drives/ExternalHDD)?

the sde thing is confusing to me because I have a 2 port SATA PCI card installed which shows up as /dev/sde under disks-devices in the dashboard into which my boot drive ssd is plugged. Then under disks-partitions my external HDD (I am assuming) shows up as /dev/sde1

I am still experiencing issue 1, when I type home.net into the address bar it brings up the internet site home.net.

Verify your client machine is using the HDA for DHCP and DNS server. For windows, open a command prompt and enter: The DNS server is not working correctly. Also ensure your browser cache is cleared as well.

For the lz, I just want to see if maybe I am understanding how things work now. The share location listed under each of the various shares in the dashboard is the LZ for that share if it is pooled in greyhole. Once the daemon is able to process any data moved to that LZ it is then moved to some other location and not stored there, is that correct? So if I were to pool 3 4TB drives and 1 160GB external drive (/dev/sde1) and wanted to use the 160GB drive as a dedicated LZ I would pool all of those 4 drives, then pool the shares, then set the location for each of the pooled shares to the mount point of the 160GB (in this case /var/hda/files/drives/ExternalHDD)?

Files are replaced with a symbolic link on the LZ. Basically it's a shortcut to the original file copy which would be located on one of the pooled drives.

DO NOT include the LZ in the storage pool. Doing so may dedicate some of it's space to real files and fill it up quickly. YOu will then have even more issues, possibly crashing your server.

The path for the shares would be the location on the LZ. As long as you are using a client machine to manipulate files, not further action is needed. If you intend to touch them on the actual server via command line or via an app, you will then need to install the mount shares locally script.

You are trying to do a lot of advanced things (Greyhole, adding drives, etc) here with little or no Linux experience. Recommend you check out the internet for some basic Linux commands and get more familiar if you intend to continue this path. It will help and potentially prevent you from making irreversible mistakes

Playing around is a way to learn, but sometimes it comes at great costs. I found that out quickly when I first started with Linux.

Sorry for the delayed response, I had major Time Warner issues and haven't had internet or TV for days. Ok, ok, I agree, I will stop messing around with greyhole until I learn more

I am still getting the problem with home.net though, and when I turn off my server, it automatically powers back on. I would like to get those two problems fixed if possible. I really appreciate the help. Here is the readout for ipconfig /all (not sure if any of this is sensitive info or not but hopefully not):

C:\Users\Matthew>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DailyDriver
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home.net

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : home.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : C0-3F-D5-4F-CE-EB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::84f4:f15e:6717:6870%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, January 25, 2016 3:41:11 PM
Lease Expires . . . . . . . . . . : Monday, January 25, 2016 7:41:11 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.10
DHCPv6 IAID . . . . . . . . . . . : 62930901
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-9D-CF-24-C0-3F-D5-4F-CE-EB
DNS Servers . . . . . . . . . . . : 192.168.1.10
192.168.1.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.home.net:

Connection-specific DNS Suffix . : home.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.3%5(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 67108864
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-9D-CF-24-C0-3F-D5-4F-CE-EB
DNS Servers . . . . . . . . . . . : 192.168.1.10
192.168.1.10
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:301e:292e:3f57:fefc(Preferred)
Link-local IPv6 Address . . . . . : fe80::301e:292e:3f57:fefc%11(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 117440512
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-9D-CF-24-C0-3F-D5-4F-CE-EB
NetBIOS over Tcpip. . . . . . . . : Disabled

DHCPv6 IAID . . . . . . . . . . . : 62930901
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-9D-CF-24-C0-3F-D5-4F-CE-EB

Does your router support IPV6?

Amahi does not and this could be the issue. It's important your router DHCP server is off. According to the info you provided, it appears it's getting DHCP and DNS from the HDA.

As for the server turning itself on, that's a BIOS issue. You must have Wake on LAN enabled or something similar that causes it to start up.

Does your router support IPV6?

Yes, it appears that it does. Under the IPv6 selection there is only the option for internet connection type, and it is set to "disabled". The other options are "auto detect", "6to4 Tunnel", "Pass Through", "Fixed", "DHCP", and "PPPoE".

It's important your router DHCP server is off.

The DHCP from the router is off as far as I can tell. I turn it back on when I turn off the server though (and then off again when the server is on).

As for the server turning itself on, that's a BIOS issue. You must have Wake on LAN enabled or something similar that causes it to start up.

I will check the BIOS settings, it happens even if the Ethernet is not connected though.