You are here: Home » Topic » NSLU2 1523 Broken ? — RESOLVED

NSLU2 1523 Broken ? — RESOLVED

This topic contains 10 replies, has 4 voices, and was last updated by  Darth Nemo 10 years, 3 months ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #1254

    sonichouse
    Participant

    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: Aborting

    bash-3.2# rm /var/run/mt-daapd.pid
    rm: cannot remove `/var/run/mt-daapd.pid’: No such file or directory

    bash-3.2# touch /var/run/mt-daapd.pid
    touch: /var/run/mt-daapd.pid: Input/output error

    Any ideas ?

    #9914

    sonichouse
    Participant

    Looks like my file system was corrupt.

    I ran e2fsck and rebooted – all fine now.

    #9915

    rpedde
    Participant

    @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

    #9916

    crowman
    Participant

    Hi 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.

    #9917

    sonichouse
    Participant

    Lokking through my bash history I found these commands

    e2fsck -n -v /dev/sda1
    e2fsck -p -v /dev/sda1

    The first just checks without making changes to the fle system.

    The second command performs the check.

    I hope this works for you.

    Steve

    #9918

    crowman
    Participant

    Cheers 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.

    #9919

    sonichouse
    Participant

    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.

    #9920

    rpedde
    Participant

    @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. πŸ™‚

    #9921

    crowman
    Participant

    That’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.

    #9922

    Darth Nemo
    Participant

    I’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

    #9923

    Darth Nemo
    Participant

    Firefly seems to be working again, but when I run e2fsck I get this error

    /dev/sda1 contains a file system with errors, check forced.
    /dev/sda1: Inodes that were part of a corrupted orphan linked list found.

    /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)

    have now run fsck and fixed all the problems and its now working again.

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.