Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Mangled filesystem on SG-2100

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    5 Posts 2 Posters 641 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mspeculatrix
      last edited by

      I have an SG-2100 that suffered a power failure. (It was on a UPS - the failure happened when that ran out of battery and no-one was around to do anything about it.)

      Booting now gives:
      panic: ufs_dirbad: /: bad dir ino 91659 at offset 1024: mangled entry

      Then it reboots. Over and over.

      I managed to get a Marvell>> prompt, but nothing there seems to offer me a shell from which I could try fsck.

      What are my options here?

      S M 2 Replies Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @mspeculatrix
        last edited by

        There was a recent thread with that message.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        1 Reply Last reply Reply Quote 0
        • M
          mspeculatrix @mspeculatrix
          last edited by

          Okay, I'm moved my query to that post.

          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @mspeculatrix
            last edited by

            I didn't actually mean to move it sorry :) I was just pointing to a couple of possible solutions.

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

            M 1 Reply Last reply Reply Quote 0
            • M
              mspeculatrix @SteveITS
              last edited by

              No problem. It made sense to continue the discussion there. I got the problem sorted in the end. I'll post what happened over there.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.