EndeavourOS/arch linux broken after poweroff - nvme drive not detected by any method

General system Newbie
1

After a forced poweroff, my system looks broken. The OS was installed in a BTRFS system

Booting endeavourOS normally will hang with

“A start job is running for /dev/disk/by-uuid/…” (forever)

cat /etc/fstab command simply outputs static information...

Booting with a live iso and tried everything (lsblk, blkid, fdisk, parted, /proc/mounts, and /etc/fstab), the NVME drive is not shown (as if it did not exist) by any method.
I could copy the outputs here, but there is no point, as it is very clear the drive is not detected.

Since it is not detected, all solutions with mounting methods i found online look useless, as I would not be able to manually mount / fsuck / chroot a drive that is a total ghost.

Is there an alternative?

2

I think it would still be helpful to show the output of some of these commands. What does it show for hardware from the live ISO also? Post the url

inxi -Faz | eos-sendlog

Edit: Did you try using gparted? You can download it on the live ISO. The ISO will also have KDE’s partition tool.

3

booting from a live iso, KDE will only show the live flash drive partitions.
inxi -Faz | eos-sendlog outputs nothing

4

I also phisically removed the drive and seated it again, still nothing. I suspect the drive is dead…

5

Well i suggest trying another drive then if that’s what you think. :wink:

6

I sought professional assistance. They were able to recover all the data with some specific software. The NVMe drive is in good health, and I am using it as an external drive with an USB-C enclosure now. Still cant boot with it. The internal NVMe was replaced and after a fresh install, everything is working fine. I had the dotfiles saved on Dropbox, so setup was smooth. Thanks, everyone.