CLOSED: New Amahi 9 Install - connectivity after transfering drive

[iamhives]

I've been running Amahi 7 for as long as its been out with now problems and decided to upgrade to Amahi 9 - clean install.

This is a headless install using an old HP Media Smart server. So I connected the drive up to a spare computer and did the install seemingly successfully. Successfully entered my install code.= etc

My problem comes when I transplant the drive from my temporary install PC to the final hardware. I can't get network connectivity to the server. Do I need to adjust the network settings> If so, how?

I used the following instructions I believe for my Amahi 7 install. I believe its the hard drive transplant portion I need help with and am not sure if the technique is similar/same with Amahi 9/Fedora23

http://www.howtogeek.com/63253/upgrade- ... ith-amahi/

Do I need to do similar for this time around or will the network adapter and settings get configured automatically for the final hardware? While I'm somewhat technical I'm no Linux guru so step by step instructions beyond the standard install Amahi 9 instructions regarding teh transplant of the driver (which I tried to follow exactly) would be welcome!.

Thanks PMH

[bigfoot65]

This is a headless install using an old HP Media Smart server. So I connected the drive up to a spare computer and did the install seemingly successfully. Successfully entered my install code.= etc

So you installed Amahi before transplanting the drive? If so, that was not the correct procedure according to the Installing HDA on HP Mediasmart Server guidance.

You should only install the OS, then move the drive. The Amahi install should occur on the server which might be part of your issue.

BTW that guidance you followed is quite old. You should always check the Amahi wiki as that will have the most complete and updated guidance. This was contributed by a user and may be out of date as well.

We do not provide official support for this type of install. However, the wiki guidance may help and I will do what I can.

[iamhives]

Thanks for the quick response. You're right, the instruction I followed are very old but since they worked for me last time (and I'd bookmarked them) I thought I try them again with whatever changes I came up with to adapt the fedora 23/Amahi 9. I didn't find the 'Installing HDA on HP Mediasmart Server' guidance so thanks for linking that. You're right, I did install Amahi before doing the transplant as per the old instructions which is different in that regard than the instructions you linked to. The challenge with the instructions you pointed to is that they are based on Ubuntu and obviously Fedora is different since the files that its points to needing to be edited don't exist in Fedora - and I haven't found them in any other folders either so I can't follow them precisely. However, some adapted version of them might work.

So right now I've been trying to get the install I have running before perhaps trying again following the instructions you provided. I've been partially successful in that the server shows up as running in the Control panel but the IP address seems to be the external IP address of my gateway vs my router so the static IP address assignment isn't working. To get it partially working like this, I copied the ifconfig-xxx file that was created in the original install and created an ifcnfg-eth1 version since eth1 is apparently the adapter that is assigned on the HP Mediasmart. This got me to my current partial solution. At least there is some form of network connectivity now. I've also tried editing in the ifcnfg-eth1 file to make the settings in the instructions I followed and this doesn't seem to help.

So basically I think I need to edit/clone the Fedora network configuration settings in order to work with eth1 which is the adapter the Mediasmart seems to use.

Anyone with enough Fedora 23 knowledge to help identify the files/changes that need to be made (whether before or after the Amahi install)

Thanks

[bigfoot65]

In Fedora, the adapter is not identifed as eth0 or eth1. If you do the following command, you can see the adapter name:

Code: Select all

ip address

Once you identify the adapter name (i.e. ens18 or similar), that's the file you need to tweak to match the wiki.

The guidance should be very similar for Fedora.

[iamhives]

Based on the information you (Bigfoot65) provided I started again. This time I installed Fedora23 and before installing Amahi I transplanted the drive to the HP Mediasmart. Upon reboot, this picked up an IP address and I was able to login via Putty and install Amahi 9 and use the install code. Rebooted and can access via Putty with the IP address I specified in the Control panel. The adapter its using appears to be named the same as the one it created when I installed Amahi on my spare computer.

SO some progress, however, right now Putty seems to be the only way I can access Amahi. http://hda , http://xxx.xxx.xxx.xxxx:9090 don't work and the control panel shows 'Awaiting Install'

I do currently have my router proving dhcp and DNS and understand the limitation that causes. Is dhcp activated on the HDA by default?.

While I seem to have basic network connectivity, obviously somethings still nit right..

[iamhives]

I am now able to get into the into: https://192.168.1.xxx:9090/system/services

and notice that dnsmasq.service and httpd.service are 'failed'

[bigfoot65]

Try doing:

Code: Select all

sudo dnf update

Once updates installed, reboot.

[iamhives]

Catch 22.

Failed to synchronize cache for repo 'updates' from 'https://mirrors.fedoraproject.org/metal ... rch=x86_64': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metal ... rch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]

[iamhives]

These are the error in the error log:

21:07
FAILED to start up dnsmasq
21:07
only one tag allowed at line 5 of /etc/dnsmasq.d/amahi-dhcp.conf dnsmasq
21:07
Unable to sync browse lists in this workgroup. nmbd
21:07
Unable to find the Domain Master Browser name AMAHI.NET<1b> for the workgroup AMAHI.NET. nmbd
21:07
find_domain_master_name_query_fail: nmbd
21:07
[2016/09/01 21:07:00.326163, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) nmbd
21:07
***** nmbd
21:07
nmbd
21:07
Samba name server HDA is now a local master browser for workgroup AMAHI.NET on subnet 192.168.1.xxx nmbd
21:07
nmbd
21:07
***** nmbd
21:07
[2016/09/01 21:07:00.325921, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) nmbd
21:06
STATUS=daemon 'smbd' finished starting up and ready to serve connections smbd
21:06
[2016/09/01 21:06:38.994504, 0] ../lib/util/become_daemon.c:124(daemon_ready) smbd
21:06
FAILED to start up dnsmasq
21:06
only one tag allowed at line 5 of /etc/dnsmasq.d/amahi-dhcp.conf dnsmasq
21:06
STATUS=daemon 'nmbd' finished starting up and ready to serve connections nmbd
21:06
[2016/09/01 21:06:37.287254, 0] ../lib/util/become_daemon.c:124(daemon_ready) nmbd
21:06
started asyncdns process 1087 nmbd
21:06
[2016/09/01 21:06:37.138738, 0] ../source3/nmbd/asyncdns.c:158(start_async_dns) nmbd
21:06
Failed to start The Apache HTTP Server. systemd
21:06
Failed to start LSB: Bring up/down networking. systemd
21:06
Device: /dev/sda [SAT], 35 Offline uncorrectable sectors smartd
21:06
Device: /dev/sda [SAT], 43 Currently unreadable (pending) sectors smartd
Reboot

[bigfoot65]

Those types of errors typically mean there is no network connectivity.

Did you make any modifications after the Amahi install?

Can you ping any IP addresses or google.com?