FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › NSLU2 1523 Broken ? — RESOLVED
- This topic has 10 replies, 4 voices, and was last updated 17 years, 2 months ago by Darth Nemo.
-
AuthorPosts
-
09/04/2007 at 2:26 PM #1254sonichouseParticipant
I get the following Input/output error
2007-04-09 15:17:34 (00000400): Firefly Version svn-1523: Starting with debuglevel 3
2007-04-09 15:17:34 (00000400): Plugin loaded: ssc-script/svn-1523
2007-04-09 15:17:34 (00000400): Plugin loaded: daap/svn-1523
2007-04-09 15:17:34 (00000400): Plugin loaded: rsp/svn-1523
2007-04-09 15:17:34 (00000400): Starting rendezvous daemon
2007-04-09 15:17:34 (00000400): Starting signal handler
2007-04-09 15:17:59 (00000400): Error opening pidfile (/var/run/mt-daapd.pid): Input/output error
2007-04-09 15:17:59 (00000400): Rendezvous socket closed (daap server crashed?) Aborting.
2007-04-09 15:17:59: Abortingbash-3.2# rm /var/run/mt-daapd.pid
rm: cannot remove `/var/run/mt-daapd.pid’: No such file or directorybash-3.2# touch /var/run/mt-daapd.pid
touch: /var/run/mt-daapd.pid: Input/output errorAny ideas ?
09/04/2007 at 9:06 PM #9914sonichouseParticipantLooks like my file system was corrupt.
I ran e2fsck and rebooted – all fine now.
10/04/2007 at 2:36 AM #9915rpeddeParticipant@sonichouse wrote:
Looks like my file system was corrupt.
I ran e2fsck and rebooted – all fine now.
I’d say that was good, because it looked inexplicable otherwise. π
— Ron
10/06/2007 at 12:16 AM #9916crowmanParticipantHi Sonic … this looks to be exactly the same issue as I currently have – how exactly did you run e2fsck as I need to do the same and can’t quite work it out (also using an NSLU2 and have an issue with the same file).
Thanks.
10/06/2007 at 3:15 PM #9917sonichouseParticipantLokking through my bash history I found these commands
e2fsck -n -v /dev/sda1
e2fsck -p -v /dev/sda1The first just checks without making changes to the fle system.
The second command performs the check.
I hope this works for you.
Steve
10/06/2007 at 8:23 PM #9918crowmanParticipantCheers Steve – Tried those and got messages about pointers being screwed up so did a bare “e2fsck /dev/sda1” and rebooted which seems to have sorted the problem. A lot of errors got fixed including the one with the pidfile. On reboot mt-daapd has come up a treat. Thanks for the help fella …. pointed me in the right direction.
10/06/2007 at 8:31 PM #9919sonichouseParticipantGlad to hear it worked π
I was pulling what is left of my hair out when it happened to me .. I couldn’t bear to be without my tunes.
11/06/2007 at 4:54 AM #9920rpeddeParticipant@sonichouse wrote:
Glad to hear it worked π
I was pulling what is left of my hair out when it happened to me .. I couldn’t bear to be without my tunes.
craaazy. surprised that happened to two people. π
11/06/2007 at 12:25 PM #9921crowmanParticipantThat’s what I thought when I saw Steve’s post …. same file, same symptoms and same logfile readout. In a strange way I was happy to see that someone else had the same problem … especially as he had got it working again π
Once the unit had done its e2fsck (with me answering ‘yes’ to every question) I just rebooted the unit and everything came up perfectly (I have mt-daapd set to autostart) … I was surprised at this as I thought I would need to reinstall mt-daapd as a minimum.
23/07/2007 at 11:06 AM #9922Darth NemoParticipantI’ve got the same problem – running svn 1586 – I’m running the checks at the moment – never had a problem before – weird – I’ll post if it works
-
AuthorPosts
- The forum ‘Nightlies Feedback’ is closed to new topics and replies.