GoFlex Home Off Network after Samba Enable.

[Illydth]

Ok so hopefully this is a quick one.

This all started with the saga of my idiocy forgetting steps on installation and fighting to get back into the GFH (thanks for the help on the other thread). Among the findings was that my GFH won't connect with my DHCP server (for whatever reason) and has to be statically IP'd to work. Not sure why but such it is.

I've finally managed to bring it online booting from the HD. Did the full system update and all the major stuff and starting installing some stuff that was needed...among which was Samba.

Configured Samba (created my config file, setup my disks, etc.) and rebooted, testing the GFH and samba access without a problem. I noticed samba didn't come up after boot so I did the following:

"systemctl enable smbd.service nmbd.service" (as per a wiki post somewhere mentioning this as how to activate samba on boot).

When I went to restart the GFH it refused to produce a network connection. The light went green, but it was NOT responding on the IP address I statically set it to. To my memory, the only thing I did with the potential to break it was the enable of the SMBD and NMBD Service AT BOOT. Note: I have had samba up and running without a problem. Turning it on does NOT fail the network connection...it continues to work just fine. It's only once I turned this on AT BOOT (or whatever Systemctl does) that the problem happened.

Confirmed that something changed by putting my bootable USB key back in the GFH base and booting off of it. (no issues, comes up on the static IP just fine...same static IP force set in both the HD boot version and the USB Boot version).

So, I've got the drive on another system and am looking at it. The enable didn't seem to have changed the network config at all (i thought that might be the issue). I am pretty sure it creates a link to /usr/lib/systemd/system/multi-user.target.wants/smbd.service and nmbd.service within the /etc/systemd/system directory, but I can't find anything else it did.

I've MANUALLY removed the two links in /etc/systemd/system, but rebooting does NOT bring the GHF back online. It's not THAT much work for me to back up the samba config file, blow away the installation and re-bring this thing back online but I'd REALLY like to know what it was that borked it in the first place.

What does the "systemctl enable" command do to the OS?

--Doug

[Illydth]

One more potentially related question.

When I went through the initial installation to the GFH base with UBoot I performed the ethaddr uu:vv:ww:xx:yy:zz using the MAC address from the bottom sticker of my GFH.

Upon booting and getting in via USB Key or Harddrive the MAC address read from ifconfig is NOT showing anything CLOSE to the ethaddr I supposedly forced the base to recognize. Are these two utterly separate things or is something on the UBoot environment not right and potentially causing network problems?

--Doug

[Illydth]

Looks like it's the samba installation not the enable that did it. I must not have rebooted after the installation like I thought I did.

Cut from my DHCP logs below. At 22:58:22 the system comes online after reboot to pick up statically assigned DHCP address, this goes without a hitch.

I then install samba, setup the smb.conf file, and reboot. That's where I get the 23:23:27 message (the reboot). After that, I get nothing...it doesn't even attempt to DHCP after that.

Nov 18 23:23:27 dhcpd: DHCPRELEASE of 192.168.100.8 from 02:50:43:0c:5c:d5 via bge0 (not found)
<snip>
Nov 18 22:58:22 dhcpd: DHCPACK on 192.168.100.8 to 02:50:43:0c:5c:d5 via bge0
Nov 18 22:58:22 dhcpd: DHCPREQUEST for 192.168.100.8 (192.168.100.254) from 02:50:43:0c:5c:d5 via bge0
Nov 18 22:58:22 dhcpd: DHCPOFFER on 192.168.100.8 to 02:50:43:0c:5c:d5 via bge0
Nov 18 22:58:22 dhcpd: DHCPDISCOVER from 02:50:43:0c:5c:d5 via bge0

[Illydth]

So, of all the stupid things I went through the installation steps again just to see what was causing the problem.

LVM is the culprit.

Formatted the second partition on the disk as LVM and created 2 LVM drives, told /etc/fstab to mount them and the system hung up on the next boot (solid green light, no DHCP or other networking attempt).

Not sure what's wrong with LVM + ArchLinux + GFH, but that's the culprit. Removed LVM, reformatted the disk as straight ext3/standard partition, mounted and all is great.

Looks like I FINALLY have a GFH up and running!

--Doug

[moonman]

You may want to take a look at this: viewtopic.php?f=30&t=4245 if you just wanted to unite multiple filesystems/drives