Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: system crash, trying to locate new superblock

  1. #1
    Join Date
    Jan 2009
    Location
    Denmark
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    system crash, trying to locate new superblock

    Hi all
    Yesterday i had a system crash and today my laptop boots into busybox (initramfs).

    I am running ubuntu 20.04 with LUKS for full disk encryption.

    I have tried to run fsck.ext4 /dev/mapper/system-root but i am getting a dm-1 error on block 118518768
    try and run e2fsck -b block device

    I dont know what block size Ubuntu is installed with, to try and locate a new superblock i can boot from.
    Is there a way from busybox that i can list all possible superblocks if i know the block size?

    I rarely ever deal with fsck so my experience with it is extremely limited.

    When i type exit in busybox i get the error

    buffer i/o error on dev dm-1 logical block 110518768 async page read
    fsck.ext4 input/output error while trying to open /dev/mapper/system-root
    The superblock could not be read or does not describe a valid ext2/3/4 filesystem
    Any and all suggestions are most welcome!

    Best regards!
    Last edited by Drenriza; 4 Weeks Ago at 03:05 PM.

  2. #2
    Join Date
    May 2010
    Beans
    1,053

    Re: system crash, trying to locate new superblock

    Try:
    Code:
    e2fsck -b 32768 /dev/whatever
    The superblock is very important and there are multiple copies across the drive

  3. #3
    Join Date
    Jan 2009
    Location
    Denmark
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: system crash, trying to locate new superblock

    Hi ActionParsnip

    Doing so gives the error

    e2fsck 1.45.5
    buffer_io_error: 4 callbacks suppressed
    Buffer I/O error on dev dm-1, logical block 2048, async page read
    Buffer I/O error on dev dm-1, logical block 4096, async page read
    Buffer I/O error on dev dm-1, logical block 8193, async page read
    Buffer I/O error on dev dm-1, logical block 16386, async page read
    Buffer I/O error on dev dm-1, logical block 32772, async page read
    e2fsck: input/output error while trying to open /dev/dm-1

    The superblock could not be read or does not describe a valid ext2/3/4
    (initramfs) _

  4. #4
    Join Date
    Jan 2009
    Location
    Denmark
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: system crash, trying to locate new superblock

    Hi all
    Anyone who can advice on how i can resolve my above problem?

    Thanks in advance
    Best regards!

  5. #5
    Join Date
    May 2010
    Beans
    1,053

    Re: system crash, trying to locate new superblock

    Did you search the web for the error you see?

  6. #6
    Join Date
    Jun 2018
    Beans
    141

    Re: system crash, trying to locate new superblock

    Does the device unlock correctly? If not, do you by change have a backup of the LUKS header? Is it a SSD or a HDD?

    This might be helpful.

  7. #7
    Join Date
    Jan 2009
    Location
    Denmark
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: system crash, trying to locate new superblock

    > Did you search the web for the error you see?
    Yes and so far i have not been able to resolve it.

    > Does the device unlock correctly?
    I believe it unlocks correctly, but how can i verify this?

    > do you by change have a backup of the LUKS header?
    I do not

    > Is it a SSD or a HDD?
    It is a SSD

    Thanks for the guide!
    I tried it out, but in initramfs i dont have access to
    sudo mke2fs -n /dev/xxx

    to see my superblock locations and all the blocks i have tried to far gives me the message of that its not a valid superblock.
    Last edited by Drenriza; 4 Weeks Ago at 10:52 AM.

  8. #8
    Join Date
    Jun 2018
    Beans
    141

    Re: system crash, trying to locate new superblock

    SSD's are notoriously known for corrupting if exposed to sudden power loss before the write cache is properly flushed, so that's bad news. If possible, I would try to access the drive from another system running Ubuntu/Linux (eg. a bootable USB stick) - I do not think you will be able to get any further from within a broken system.

  9. #9
    Join Date
    Jan 2009
    Location
    Denmark
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: system crash, trying to locate new superblock

    Quote Originally Posted by dinkidonk View Post
    SSD's are notoriously known for corrupting if exposed to sudden power loss before the write cache is properly flushed, so that's bad news. If possible, I would try to access the drive from another system running Ubuntu/Linux (eg. a bootable USB stick) - I do not think you will be able to get any further from within a broken system.

    I tried to live USB into ubuntu 20.04, was able to decrypt the disk and load the LVM volume.
    Ran a fsck on the LVM group and fsck came back with

    "still contains errors"

    after it was done. Tried to run fsck a second time, but than i got prompted again with bad superblock immediately.

  10. #10
    Join Date
    Jun 2018
    Beans
    141

    Re: system crash, trying to locate new superblock

    Did you try the guide from #6 while booted into the live USB?

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •