Skip to main content
Minor formatting improvements.
Source Link
AdminBee
  • 23.6k
  • 25
  • 55
  • 77

Using the existing answers, I had trouble finding the mount point I need to use for the root. In my case, on ArchLinux, it was /new_root. The full steps for resuming boot (assuming a bad crypttabcrypttab) were:

cryptsetup open /dev/nvme1n1p2 root
mount /dev/mapper/SomeVolGroup/root /new_root
CTRL+D
cryptsetup open /dev/nvme1n1p2 root
mount /dev/mapper/SomeVolGroup/root /new_root

Then, press CTRL+D

Using the existing answers, I had trouble finding the mount point I need to use for the root. In my case, on ArchLinux, it was /new_root. The full steps for resuming boot (assuming a bad crypttab) were:

cryptsetup open /dev/nvme1n1p2 root
mount /dev/mapper/SomeVolGroup/root /new_root
CTRL+D

Using the existing answers, I had trouble finding the mount point I need to use for the root. In my case, on ArchLinux, it was /new_root. The full steps for resuming boot (assuming a bad crypttab) were:

cryptsetup open /dev/nvme1n1p2 root
mount /dev/mapper/SomeVolGroup/root /new_root

Then, press CTRL+D

Source Link
Fadeway
  • 183
  • 7

Using the existing answers, I had trouble finding the mount point I need to use for the root. In my case, on ArchLinux, it was /new_root. The full steps for resuming boot (assuming a bad crypttab) were:

cryptsetup open /dev/nvme1n1p2 root
mount /dev/mapper/SomeVolGroup/root /new_root
CTRL+D