Startup crash and wont re start

[davesanti]

Wow.. I hate being the kid always tugging at mom’s shirttails..

Running latest nightly.. on a Slug unslung to flash drive on disk 1 and HDD on disk 2.

During a scan Friday night, the Slug froze and I had to re-boot.
Reboot went ok..

Saturday morning tried again..froze..

One more try froze the Slug..

Nothing I can see in the logs (level 5)

Try to reboot.. this time though.. it killed the Slug (Slug poison 😀 )

Long story short after a full re flash and reload.. of 1586

Running again..

Start a scan (I didnt remember to change the debug level)..

Bam crash again — earlier then the previous time..

I was able to recover.. but I cant get FF running again..

I can’t find the log .. before the reflash.. I had created a logfile

I forgot this time.. and I cant read the log in the “messages” location comes back no readable or some such thing..

I am getting to the point where I am thinking I need to stop playing with stuff I dont know much about.. but I am close to up and running again and I really like FF.

Pleas ehelp me get it running again.. after that I’ll see if I cant get the scan thing sorted.

Dave

[davesanti]

In the vain of self help I also tried uninstall/reinstall to no effect…it doesnt appear to me that the uninstall is doing the trick.. here is what I get:

LKG2C9CE8 login: root
Password:
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.

# ipkg remove mt-daapd
Removing package mt-daapd from root…
killall: mt-daapd: no process killed
prerm script returned status 1
# ipkg update
Downloading http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/stable/Package
s.gz
Inflating http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/stable/Packages.
gz
Updated list of available packages in /usr/lib/ipkg/lists/cross
Downloading http://ipkg.fireflymediaserver.org/armeb/Packages
Updated list of available packages in /usr/lib/ipkg/lists/firefly
Downloading http://ipkg.nslu2-linux.org/feeds/optware/nslu2/native/stable/Packag
es.gz
Inflating http://ipkg.nslu2-linux.org/feeds/optware/nslu2/native/stable/Packages
.gz
Updated list of available packages in /usr/lib/ipkg/lists/native
Downloading http://ipkg.nslu2-linux.org/feeds/unslung/modules/cross/6.8-beta/Pac
kages.gz
Inflating http://ipkg.nslu2-linux.org/feeds/unslung/modules/cross/6.8-beta/Packa
ges.gz
Updated list of available packages in /usr/lib/ipkg/lists/oe
# ipkg install mt-daapd
Installing mt-daapd (svn-1586-1) to root…
Downloading http://ipkg.fireflymediaserver.org/armeb/mt-daapd_svn-1586-1_armeb.i
pk
Configuring mt-daapd

chown: /opt/var/mt-daapd/songs.db-journal: Input/output error
chmod: /opt/var/mt-daapd/songs.db-journal: Input/output error

To complete this installation, make any necessary changes
to the config file in /opt/etc/mt-daapd/mt-daapd.conf, and
start the daemon by running /opt/etc/init.d/S60mt-daapd

#

I think what I need here is a Linux for dummies explanation of how to uninstall and/or force a reinstall of the FF to get rid of the problems.. I am getting more confident that is is an issue in the database file

Dave

[davesanti]

This what I get when I try to force a reinstall (I am not even certain if it is close to being done right)

LKG2C9CE8 login: root
Password:
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.

# ipkg -force-reinstall install mt-daapd
Reinstalling mt-daapd (svn-1586-1) on root…
Downloading http://ipkg.fireflymediaserver.org/armeb/mt-daapd_svn-1586-1_armeb.i
pk
conffile_has_been_modified: conffile /opt/etc/mt-daapd/mt-daapd.conf has no md5s
um
Configuring mt-daapd

chown: /opt/var/mt-daapd/songs.db-journal: Input/output error
chmod: /opt/var/mt-daapd/songs.db-journal: Input/output error

To complete this installation, make any necessary changes
to the config file in /opt/etc/mt-daapd/mt-daapd.conf, and
start the daemon by running /opt/etc/init.d/S60mt-daapd

#

Dave

[kellyharding]

The input/output error might be worth looking into.

Either the flash drive or the hard drive has an issue perhaps?

[davesanti]

The root is all in the flash drive so I think )hope) the HDD is fine. I can boot fine and the slug runs fine.. I just cant get FF running again.

Dave

[fizze]

erm, what does

df -h

report?
Maybe your flash drive ran out of space?

I’d advise to put the DB of mt-daapd on the HD, btw.

[davesanti]

Fizze,

I don’t have access to the Slug right now, so I will try the “df -h” when I get home. It is a 2gb flash drive and the only thing I have done with it is unsling to it and load FF. I have not put any other files on it intentionally..
It seems unlikely that the drive is out of memory.

I will put the Db in the HDD and push the debug to 9 as soon as I can get FF running again.

Dave

[kellyharding]

Writing logfiles to a flash drive isn’t recommended as flash drives usually have a limited number of writes.

Making sure the db file and all log files are on the HD is best as others suggest.

Is there any diagnostic tools for the SLUG? to check nothing is wrong with the hardware? or run a filesystem check on both the SLUG’s flash drive and hard drive?

Another thing to check is permissions. You might not have permissions right for mt-daapd to access some files when it starts.

[davesanti]

Thanks Kelly… I will try to move all the db and log files when I get FF going again…

The Slug permissions are all read/write for all users (guest and admin) so I think that covers it..

I am starting to think that maybe slinging to the flash isn’t the best idea. I was initially slung to one drive, HDD in port 2 and it was working fine. It just wouldnt spin down and thats what prompted me to go onto this quest that has spun me around in many directions..

Dave

[rpedde]

@davesanti wrote:

Thanks Kelly… I will try to move all the db and log files when I get FF going again…

The Slug permissions are all read/write for all users (guest and admin) so I think that covers it..

I am starting to think that maybe slinging to the flash isn’t the best idea. I was initially slung to one drive, HDD in port 2 and it was working fine. It just wouldnt spin down and thats what prompted me to go onto this quest that has spun me around in many directions..

Dave

Check out the nslu2 install guide on the wiki http://wiki.fireflymediaserver.org, and it has tips for moving the db off, and minimizing flash writes.

I followed that slavishly, and my flash has been working pretty well.

WRT the original problem, if it won’t start, it likely is because the db is corrupt or something. (out of space?)

Delete the db (after moving it to the hdd), and start it again. It iwll re-create the db. If it dies again, likely it’s a song that’s crahsing it.

Delete the db *again* and set the log level to 9 via the web admin (or the config file, or by running “/opt/sbin/mt-daapd -d9 -f -c /opt/etc/mt-daapd/mt-daapd.conf” and watch where it dies. That will tell you what song is crashing it, and you can move it out of the way.

— Ron

[Author]

Posts