SOLVED! - Amahi 7 - Am I having a Fedora problem?

[apacnw]

Hi! I downloaded the Amahi 7 Express Install DVD and it installed just fine. Unfortunately, my HDA was never able to connect to Amahi.org to finish the install. When it finished rebooting, I could get to the HDA control panel, but couldn't install any apps.

I tried reinstalling the HDA a couple of times, deleting and creating new profiles on Amahi.org, and fiddling with my router. None of that made any difference. Checking the log, it looks like the Amahi scripts cannot initialize eth0. After a bit of digging around, I realized that's because I have no eth0! The Amahi Express Install disc (Fedora 19) discovers my ethernet interfaces as eno1 and eno2. They both work from Fedora's perspective, but it looks like the Amahi scripts are hard coded to look for eth0.

So here's the question: Is there a way to convince Fedora that eno1 = eth0? Or to convince the Amahi scripts just to use the first network interface in Fedora? Or to use another setup method? I noticed that work has been continuing on supporting Fedora/Ubuntu full installs, but they're still listed as beta/unsupported in the installation docs.

Thanks!

BTW, a little searching turned up the fact that this is not uncommon with Fedora. I haven't played with Fedora in years, so this seems kind of odd to me. Any suggestions would be appreciated.

[bigfoot65]

Did you see Network on the first screen when installing? Did it reflect eth0? I just installed a week ago and had no issues. Wondering if during the install process the network option on the installer will need updated before continuing with the install.

There is a way to change this I believe, but not a simple task. There might be some guidance in the wiki. If I find it, I will let you know.

[apacnw]

Thanks for the quick response. I've had to shut down Amahi for now since that interface is serving up DHCP, but none of the clients can get to anything other than the HDA once they get an address from it...

I've been looking into the problem on the Fedora forums and it seems to have something to do with the bnx2 driver. My server has Broadcom 5716 NICs, so that seems like a likely match. Still searching...

[apacnw]

Sorry, I didn't answer your original question. Yes, I saw Network on the install screen, but I can't remember if it showed eth0. I'll try another reinstall and let you know.

[cpg]

This is an intricate issue. Out of necessity, the installer forces the name of the first network device to be eth0, *during install*. After the system is up an running it could be a number of names: eth0, p1p2, em1, eno1, etc.

This smells like something we have grown to call it "expertitis" ..

That's an expert trying to do advanced things, bending things beyond what was expected, with perhaps (what it sounds like) hardware that it's either very new or very very old and does have great driver support built in. (no offense please)

In any case, if you can provide more about the hardware details we can take a look at the possibility of adding the drivers in the next release.

[apacnw]

No worries. I appreciate any help and am happy to provide any info I can to get this moving.

My server's a few years old, but is by no means ancient:
Dell PowerEdge T310
16GB RAM
PERC 6/i RAID controller with 4 disks, configured as individual volumes.
- the Amahi installer discovers the disks just fine. I selected the first one for install (and deselected the rest).
Dual Broadcom NetXtreme II 5716 NICs on the motherboard

I've had FreeNAS on here (it had trouble identifying the RAID card) as well as Windows Server 2008R2 (no problems except with NIC bonding), 2012 (no problems), Slackware 14 (that was a tweak-fest) and Ubuntu 12.04 (no problems).

I am *NOT* an expert, so don't worry about using small words with me I can learn, though. If you have any ideas about how to get this working, I'm excited to try Amahi on this machine too.

[cpg]

Suggestion 1: disable the second network interface in the bios.

Suggestion 2: install from the full DVD. this method has not been documented yet in docs.amahi.org but it's somewhere in the wiki. (anyone would like to clean it up and merge it into docs.amahi.org?)

The hardware is definitely expert level. I should point out we're flying without much detail here, so this could take forever.

[apacnw]

BTW, I tried your first suggestion right off the bat. The BIOS only allows me to disable both NICs at once or to configure them individually for "On", "On with PXE", or "On with iSCSI Boot Support."

I think I saw a full CD installation page somewhere. I'll look. Full installation with Fedora or with Ubuntu?

What kind of detail do you need? I can grab log files or whatever else might help, but I'm also a fan of just reinstalling if that's easier than grubbing through (no pun intended) scripts.

[apacnw]

OK, it looks like everything is working now. In the long term, it may be worth considering rewriting the install scripts to iterate through available interfaces rather than looking for eth0. With everyone starting to use biosdevname, things are going to continue to be interesting.

I followed this link: http://bitc.bme.emory.edu/~lzhou/blogs/?p=376

After disabling biosdevname and renaming my existing NICs to eth0 and eth1, I re-ran the install and it came right up after reboot.

One other note - the wiki and docs refer, variously, to hda-install, hda-new-install, and amahi-installer as the tools to restart the installation routine. I don't know if all of those names are still valid, but it was really hard to tell which one to use. None of the docs specify which version of the HDA contains which installer, so I had to keep poking around until I found one that works.

Thanks for all the help!

[cpg]

Just to be pedantic. Here is the suggestion:

Code: Select all

yum remove biosdevname add net.ifnames=0 to GRUB_CMDLINE_LINUX in /etc/default/grub grub2-mkconfig -o /boot/grub2/grub.cfg rename /etc/sysconfig/network-scripts/ifcfg-whatever to ifcfg-eth0 change to NAME=eth0 inside ifcfg-eth0

The thing is, this is for after a full install.

The initial installer *forces* the system to recognize the first ethernet as eth0, *during the duration of the install*.

The name becomes what fedora wants after the first reboot. The installer *then* runs, picking up the first network interface, whatever it may be.

So, in this case, what appears to be failing is the *forcing* of calling the device eth0 during the install.

One clue is the fact that there are two network devices. I think that could be a reason this might help. Noone can do the changes suggested above during the first install-time run, because those files do not even exist (let alone the packages, hence yum is not even there and cannot uninstall any non-existing packages).