system crash, trying to locate new superblock

[Drenriza]

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!

[ActionParsnip]

Try:

e2fsck -b 32768 /dev/whatever

The superblock is very important and there are multiple copies across the drive

[Drenriza]

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) _

[Drenriza]

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

Thanks in advance
Best regards!

[ActionParsnip]

Did you search the web for the error you see?

[dinkidonk]

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.

[Drenriza]

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

[dinkidonk]

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.

[Drenriza]

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.

[dinkidonk]

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