You are not logged in.
I installed Arch Linux on an internal NVMe drive in my Dell Precision 7530 laptop two days ago. It was the first use of this drive, although the drive has been inside the laptop for a while, close to two years.
Installation details:
small separate boot/EFI partition
rest as a single LUKS partition, with LVM on top with separate root, home, and swap
It worked well for two days, but then today I was editing a text file and got a "read-only filesystem" message. Sure enough, both the /home and / partitions were mounted "ro" for some reason, and running various common commands started spitting out weird errors:
umount: input/output error
sudo su: input/output error
sudo reboot: can't talk to init daemon (or something like that)
The end of journalctl also had some errors related to the read-only filesystem, but I didn't get much insight from that. (In hindsight, I could have copied the whole thing to another disk...)
I couldn't think of anything to do but hard power-cycle, so I did that, and attempted to boot into the system again. That's when the fun begins:
Screenshot
(Sorry for the blurry image, but these are the error messages after attempting to unlock the drive:
IO error while decrypting keyslot.
Keyslot open failed.
Device /dev/nvme0n1p2 does not exist or access denied.
Device /dev/nvme0n1p2 does not exist or access denied.
(repeated)I did press Ctrl-C after waiting a few minutes, much longer than it normally takes, so I don't know if that did anything.)
Rebooting into a previously installed Ubuntu on a separate SSD in the same laptop, I attempted to unlock the drive again with
udisksctl unlock -b /dev/nvme0n1p2which appeared to hang for a couple minutes and then error out, at which point the entire SSD seemed to disappear from the system. GNOME's "disks" utility and lsblk no longer list that drive or any of the partitions on it. When I reboot the laptop and press F12 for the boot options, my GRUB on that SSD doesn't even show up, and I can only boot from the other disk, the one I'm currently using. However, when I ran BIOS diagnostics, it did list the problematic drive with the correct vendor and model number, but no other information that I can recall.
So I'm kind of at a loss at this point. Any ideas on what I could have messed up, or anything else I can try? I still have the Arch-ISO on my USB stick if I need to get to a (basic) running Arch system to run something.
Offline
The problematic drive mysteriously came back from the dead and disappeared again after a minute or so. I managed to get this output before it disappeared:
% lsblk -e7
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 200M 0 part
└─nvme0n1p2 259:2 0 931.3G 0 part
nvme1n1 259:3 0 477G 0 disk
├─nvme1n1p1 259:4 0 780M 0 part /boot/efi
├─nvme1n1p2 259:5 0 5G 0 part
└─nvme1n1p3 259:6 0 471.2G 0 part /nvme0n1 is the problematic SSD, with the 200M boot partition and 931.3G home/root/swap on LVM on LUKS. nvme1n1 houses the currently running system (Ubuntu).
This is the output now, without my doing anything:
% lsblk -e7
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme1n1 259:3 0 477G 0 disk
├─nvme1n1p1 259:4 0 780M 0 part /boot/efi
├─nvme1n1p2 259:5 0 5G 0 part
└─nvme1n1p3 259:6 0 471.2G 0 part /Offline