Manjaro rootfs not mounting

Hello. I was using manajro xfce for a long time and suddenly it stopped to launch at all. (The manjaro logo and loading screen stuck forever, when I press “Esc”, the recovery shell is being displayed with message that device with UUID can not be mount.
I’ve tryed to chroot in my system via live cd, but there is the problem:

[manjaro manjaro]# mount /dev/sda5 /mnt/
mount: /mnt: can't read superblock on /dev/sda5.
       dmesg(1) may have more information after failed mount system call.

As long as the hdd is being detected by BIOS and starts to launch Manjaro itself, I think the HDD is still alive.
Here si lsblk output (/dev/sda is my HDD):

[manjaro manjaro]# lsblk
loop0    7:0    0 158.7M  1 loop /run/miso/sfs/livefs
loop1    7:1    0 852.4M  1 loop /run/miso/sfs/mhwdfs
loop2    7:2    0 926.3M  1 loop /run/miso/sfs/desktopfs
loop3    7:3    0 653.7M  1 loop /run/miso/sfs/rootfs
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   100M  0 part 
└─sda5   8:5    0 930.9G  0 part 
sdb      8:16   1  58.6G  0 disk /run/miso/bootmnt
├─sdb1   8:17   1   2.6G  0 part 
└─sdb2   8:18   1     4M  0 part 

fsck and other recover utilites return me an error that superblock can not be read, and also, sda1 and sda5 are dissapearing from lsblk output and there is no HDD size on it.
How can I make sure that my HDD is still alive and resolve the issue?

You can try to read the backup superblock on that drive.

@Keruskerfuerst Do you mean fsck -b backup_superblock_number? It does not work either.
Now, after manipulations with recovery tools, there is no grub at all and looks like bios ignores hdd (but bios still detects hdd itself)

You can copy the backup superblock to the defective superblock.

Please make sure that this is not a hardware error

A dying hard disk electronics can behave as described.

It cost me quite a bit of money because I didn’t react in time. Hard disks fall out one day. And not every hdd sends an email beforehand: “Attention, in 3 months I will be completely broken”

1 Like

Did you check that? :arrow_down:

sudo dmesg | less