A little help Please goflex stak200

[kevambert]

Hello all
Ive installed arch linux arm on my goflex net stak200 with a sata drive and everthing went well, i then installed the minidlna media server everything went well and i could see it on my neywork (Alarm), but to add files to the server ment I had to take out the drive and connect it to ubuntu.
so i installed samba everything went well but when i added “samba” to the DEAMONS rc.conf and reboot the goflex no longer gets an ip from the router.
I hooked up the sata to ubuntu and removed “samba” leaving “minidlna” from the list of DAMONS but its still the same its still not getting an ip
Where did I go wrong and can I fix it
Thanks

[kmihelich]

Samba on its own shouldn't be causing an issue. You can try hooking the drive back up to ubuntu and editing /etc/rc.conf and follow the example given in there to set up a static IP address for the device. More times than not it's just crappy consumer routers that cause issues with DHCP.

[kevambert]

Thanks kmihelich
I tried to edit the rc.conf for static ip but it did not work, the router is a Netgear wnr 200 v2 (flashed with DD-WRT v24-sp2 mini - build 14536M NEWD-2 K2.6 Eko) its an ok router.
I connected the sata drive (rootfs) upto ubuntu and downloaded and extracted to rootfs the ArchLinuxARM-arm5te-latest.tar.gz this seems to have given me back an ip.
But I ran minidlna back in and edited the rc.conf to start minidlna on startup but again I lost ip on reboot.
So I connected it back up to ubuntu and removed the “minidlna” from rc.conf reboot and I have ip again, but when I start minidlna it dosent show on my network

edit it has just shown up on my network after I stopped and restarted minidlna

what can i run with this to enable me to add files to the media server(minidlna) wihout having to stop and connect it to ubuntu

[kmihelich]

Minidlna does need to be configured properly, including considerations for permissions on files it's indexing and where it's database and (optionally) log are stored. Also, any extra daemons such as minidlna should be added to the end of the DAEMONS list unless otherwise specifically instructed elsewhere. This way their startup doesn't interfere with system-critical programs. And as noted in rc.conf, you can prepend a listed daemon with @ in order to start it in the background, thus letting any following daemon startups be executed right away.

However, even with a mis-configured minidlna, with the proper setup in rc.conf you should not be losing network connectivity.

[WarheadsSE]

this is enabled in my rc.conf i dont have minidlna in DAEMONS bus it is loading on boot
$this->bbcode_second_pass_code('', '
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Atlantic/Eire"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

MODULES=()

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

HOSTNAME="alarm"

interface=eth0
address=
netmask=
broadcast=
gateway=

DAEMONS=(hwclock syslog-ng network netfs crond sshd)
')

this is enabled minidlna.conf
$this->bbcode_second_pass_code('', '
db_dir=/var/cashe/minidlna
friendly_name=my_server
log_dir=/var/log
album_art_names=cover.jpg/albumart etc etc
inotify=yes
enable_tivo=no
strict_dlna=no
notify_interval=900
serial-12345678
model_number=1
')