You are here: Home » Topic » Server not running

Server not running

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

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1591

    Kevin
    Participant

    Hi

    Can’t get Firefly to run. It’s not a problem I’ve had before – looks as if it could be a bigger problem than just Firefly. Here’s the log:

    2007-07-27 23:17:20 (bac6a7d1): Starting with debuglevel 0
    2007-07-27 23:17:25 (bac6a7d1): Starting rendezvous daemon
    2007-07-27 23:17:26 (bac6a7d1): Error: enum_begin failed (error 1): Misc SQL Error: disk I/O error
    2007-07-27 23:17:26 (bac6a7d1): Can’t get db version. New database?
    2007-07-27 23:17:26 (bac6a7d1): Initializing database
    2007-07-27 23:17:26 (bac6a7d1): Error: enum_begin failed (error 1): ?
    2007-07-27 23:17:26 (bac6a7d1): Error: enum_begin failed (error 1): ?
    2007-07-27 23:17:26 (bac6a7d1): Full reload…
    2007-07-27 23:17:26 (bac6a7d1): Starting mp3 scan
    2007-07-27 23:17:26 (bac6a7d1): Query: pragma synchronous = off
    2007-07-27 23:17:26 (bac6a7d1): Error: disk I/O error
    2007-07-27 23:17:26: Aborting

    Any ideas?

    Thanks

    Kevin

    #11869

    rpedde
    Participant

    @kevin wrote:

    Hi

    Can’t get Firefly to run. It’s not a problem I’ve had before – looks as if it could be a bigger problem than just Firefly. Here’s the log:

    2007-07-27 23:17:20 (bac6a7d1): Starting with debuglevel 0
    2007-07-27 23:17:25 (bac6a7d1): Starting rendezvous daemon
    2007-07-27 23:17:26 (bac6a7d1): Error: enum_begin failed (error 1): Misc SQL Error: disk I/O error
    2007-07-27 23:17:26 (bac6a7d1): Can’t get db version. New database?
    2007-07-27 23:17:26 (bac6a7d1): Initializing database
    2007-07-27 23:17:26 (bac6a7d1): Error: enum_begin failed (error 1): ?
    2007-07-27 23:17:26 (bac6a7d1): Error: enum_begin failed (error 1): ?
    2007-07-27 23:17:26 (bac6a7d1): Full reload…
    2007-07-27 23:17:26 (bac6a7d1): Starting mp3 scan
    2007-07-27 23:17:26 (bac6a7d1): Query: pragma synchronous = off
    2007-07-27 23:17:26 (bac6a7d1): Error: disk I/O error
    2007-07-27 23:17:26: Aborting

    Any ideas?

    Thanks

    Kevin

    That sure looks like a physical error. A fsck is probably in order. Not sure how to do that with the slug. Possibly boot up with no drive attached, then attach the drives and e2fsck it once the system is booted without the drives mounted.

    Anyone?

    #11870

    fizze
    Participant

    There you go, since fsck or especially e2fsck isnt part of the unslung base system, iirc.

    You might be able to scan it through the linksys webthingy though. I have no clue which utlilty that uses. Or how “good” this is. *shrug*

    #11871

    rpedde
    Participant

    @fizze wrote:

    There you go, since fsck or especially e2fsck isnt part of the unslung base system, iirc.

    Really? That seems broken!

    I guess you could fsck it from a linux machine.

    Unless it’s a USB stick, in which case, you might be in for more failures coming up, if it’s hit its write limit.

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

You must be logged in to reply to this topic.