FireFly Media Server (formerly mt-daapd) › Firefly Media Server Forums › Firefly Media Server › Setup Issues › So now I have gone and made soup of it all… › Reply To: So now I have gone and made soup of it all…
12 hours ago FF was up and running perfectly on my newly unlsung Slug…and HDD NAS setup. But I couldn’t leave well enough alone.. and unfortunately my Linux/skills and understanding are nonexistent.
Install was HDD only on port 2.. I wanted to a flash/HDD with Slug unlunsg to flash on port 2.. I made a huge mess of it and the Slug went to hell on me. I seem to have more or less recovered after a bunch or hair pulling and now it seems I am unslung to the flash on drive 2 and the HDD is recognized in drive 1. Both drives are mapped to my PC and come up and I can put file in them.. Here is a shot of my Slug GUI page.
I tried to install FF (nightly) and regular with no success (as an aside, I tried Twonky and got it installed no problem and it is working, but I don’t want Twonky I love FF).
When I do # ipkg install mt-daapd I get a bunch of errors:
Here is what it looked like with a nightly attempt:
First off this what I get when I telnet in:
LKG7BFC4D login: root
No directory, logging in with HOME=/
Welcome to Unslung V2.3R63-uNSLUng-6.8-beta
NOTE: THIS SYSTEM IS CURRENTLY UNSLUNG
BusyBox v0.60.4 (2005.03.22-06:52+0000) Built-in shell (ash)
Enter ‘help’ for a list of built-in commands.
I notice the no directory thing, in the first few lines and don’t think I have ever seen that before..
# echo “src firefly http://ipkg.fireflymediaserver.org/armeb” > /etc/ipkg/firefl
# ipkg update
Updated list of available packages in /usr/lib/ipkg/lists/cross
Updated list of available packages in /usr/lib/ipkg/lists/firefly
Updated list of available packages in /usr/lib/ipkg/lists/native
Updated list of available packages in /usr/lib/ipkg/lists/oe
So far so good, I think, but:
# ipkg install mt-daapd
Installing mt-daapd (svn-1586-1) to root…
Installing libid3tag (0.15.1b-1) to root…
Installing zlib (1.2.3-2) to root…
Installing libogg (1.1.3-3) to root…
Installing libvorbis (1.1.2-5) to root…
After a bit more then I start getting a ton of these:
ipkg: /opt/share/terminfo/n/ncr260intpp: No such file or directory
ipkg: /opt/share/terminfo/n/nsterm-m-s: No such file or directory
ipkg: Cannot create symlink from ./opt/share/terminfo/n/nwe501 to ‘../n/nwp513’:
No such file or directory
ipkg: /opt/share/terminfo/n/ncr260wy60wpp: No such file or directory
ipkg: Cannot create symlink from ./opt/share/terminfo/n/nsterm-7-m to ‘../n/nste
rm-m-7′: No such file or directory
ipkg: /opt/share/terminfo/n/nsterm-s-7: No such file or directory
ipkg: /opt/share/terminfo/n/nsterm-acs: No such file or directory
And it concludes with :
Unable to open the control file in set_flags_from_control
Could not open //usr/lib/ipkg/info/ivorbis-tools.list for writing: Input/output
Could not open //usr/lib/ipkg/info/libao.list for writing: Input/output error
Could not open //usr/lib/ipkg/info/libcurl.list for writing: Input/output error
Could not open //usr/lib/ipkg/info/libogg.list for writing: Input/output error
Could not open //usr/lib/ipkg/info/libvorbis.list for writing: Input/output erro
Could not open //usr/lib/ipkg/info/zlib.list for writing: Input/output error
WARNING: Unable to remove temporary directory: /tmp/ipkg-tUF42M: No such file or
Have I made a mess or is this something that can be cleaned up.
Ouch.. I am such an idiot some times… I need to stick to doing nothing but following directions.
Sounds like your opt directory is in the wrong place and it thinks you have packages installed that you don’t. Or something.
If that’s the case, you can move the /opt directory out of the way (/opt.old?) and symlink opt to the /opt directory on the hard drive.
That might work.
Or, look at “Upgrade challenge #2” on this page:
That may be what’s tripping you up, too — it’s trying to boot off your old drive.
See if the instructions there help.