Boot problem after crash [solved]

Forum Forums New users New Users and General Questions Boot problem after crash [solved]

  • This topic has 2 replies, 2 voices, and was last updated Mar 20-8:47 am by andfree.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #79367
    Member
    andfree
      [...] blk_update_request: I/O error, dev fd0, sector 0
      [...] blk_update_request: I/O error, dev fd0, sector 0
      [...] Buffer I/O error on dev fd0, logical block 0, async page read
      rootantiX21 contains a file system with errors, check forced.
      rootantiX21:
      Inodes that were part of a corrupted orphan linked list found.
      
      rootantiX21: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
      (i.e., without -a or -p options)
      fsck exited with status code 4
      The root filesystem on /dev/sda1 requires a manual fsck
      
      BusyBox, v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
      Enter 'help' for a list of built-in commands.
      
      (initramfs) _
      • This topic was modified 1 year, 1 month ago by caprea.
      #79373
      Member
      ModdIt
        Helpful
        Up
        1
        ::

        Boot from a live medium, not the defective ystem.

        error is The root filesystem on /dev/sda1 requires a manual fsck so you need to do

        sudo fsck /dev/sda1

        When prompted, type y to fix the errors.

        You may find you have so many errors that repair is not possible. Hope that is not the case.

        • This reply was modified 1 year, 1 month ago by ModdIt.
        • This reply was modified 1 year, 1 month ago by ModdIt.
        #79413
        Member
        andfree
          Helpful
          Up
          0
          ::

          Boot from a live-usb & run

          sudo fsck /dev/sda1

          fixed the issue. Many thanks.

          • This reply was modified 1 year, 1 month ago by andfree.
          • This reply was modified 1 year, 1 month ago by andfree.
        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.