updated /etc/openswap.conf with /etc/openswap.conf.pacnew
updated the system (stable branch) with the current updates
reboot
Now the system (Thinkpad T14 Gen1) doesn’t come up and shows only the “Lenovo” logo at boot, three dots (rising an vanishing) and the Manjaro logo right under it.
I tried to Alt+F[1-12] to get a terminal, but no luck.
I tried to SSH into it, but my router has given no IP to the system.
I booted a live USB-system (with drivers) to open the root file system, but
[manjaro ~]# cryptsetup --debug open /dev/nvme0n1p3 n1p3
# cryptsetup 2.8.1 processing "cryptsetup --debug open /dev/nvme0n1p3 n1p3"
# Verifying parameters for command open.
# Running command open.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/nvme0n1p3.
# Trying to open device /dev/nvme0n1p3 with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device /dev/nvme0n1p3.
# Crypto backend (OpenSSL 3.6.0 1 Oct 2025 [default][legacy][threads][argon2]) initialized in cryptsetup library version 2.8.1.
# Detected kernel Linux 6.12.48-1-MANJARO x86_64.
# PBKDF pbkdf2-sha256, time_ms 2000 (iterations 0).
# Reading LUKS header of size 1024 from device /dev/nvme0n1p3
# Key length 64, device size 70537113 sectors, header size 4036 sectors.
# Activating volume n1p3 [keyslot -1] using token.
# dm version [ opencount flush ] [16384] (*1)
# dm versions [ opencount flush ] [16384] (*1)
# Detected dm-ioctl version 4.48.0.
# Device-mapper backend running with UDEV support enabled.
# dm status n1p3 [ opencount noflush ] [16384] (*1)
# Interactive passphrase entry requested.
Enter passphrase for /dev/nvme0n1p3:
# Activating volume n1p3 [keyslot -1] using passphrase.
# dm versions [ opencount flush ] [16384] (*1)
# dm status n1p3 [ opencount noflush ] [16384] (*1)
# Trying to open key slot 0 [ACTIVE].
# Reading key slot 0 area.
# Using userspace crypto wrapper to access keyslot area.
# Reusing open ro fd on device /dev/nvme0n1p3
# dm versions [ opencount flush ] [16384] (*1)
# dm status n1p3 [ opencount noflush ] [16384] (*1)
# Calculated device size is 70533017 sectors (RW), offset 4096.
# dm target-version crypt [ opencount flush ] [16384] (*1)
# device-mapper: target-version ioctl on crypt failed: Invalid argument
# dm versions [ opencount flush ] [16384] (*1)
# DM-UUID is CRYPT-LUKS1-2f5c30c0b0844f03a88269db91174e81-n1p3
# Udev cookie 0xd4d9f90 (semid 14) created
# Udev cookie 0xd4d9f90 (semid 14) incremented to 1
# Udev cookie 0xd4d9f90 (semid 14) incremented to 2
# Udev cookie 0xd4d9f90 (semid 14) assigned to CREATE task(0) with flags DISABLE_LIBRARY_FALLBACK (0x20)
# dm create n1p3 CRYPT-LUKS1-2f5c30c0b0844f03a88269db91174e81-n1p3 [ opencount flush ] [16384] (*1)
# dm reload (254:2) [ opencount flush securedata ] [16384] (*1)
device-mapper: reload ioctl on n1p3 (254:2) failed: Invalid argument
# Udev cookie 0xd4d9f90 (semid 14) decremented to 1
# Udev cookie 0xd4d9f90 (semid 14) incremented to 2
# Udev cookie 0xd4d9f90 (semid 14) assigned to REMOVE task(2) with flags DISABLE_LIBRARY_FALLBACK (0x20)
# dm remove n1p3 [ opencount flush securedata ] [16384] (*1)
# Uevent not generated! Calling udev_complete internally to avoid process lock-up.
# Udev cookie 0xd4d9f90 (semid 14) decremented to 1
# DM create task failed, dm_task errno: -22.
# dm versions [ opencount flush ] [16384] (*1)
# dm status n1p3 [ opencount noflush ] [16384] (*1)
# Device status returned -19.
# Data device /dev/nvme0n1p3 is OK.
# No referenced device missing, some device in use.
# Udev cookie 0xd4d9f90 (semid 14) decremented to 0
# Udev cookie 0xd4d9f90 (semid 14) waiting for zero
# Udev cookie 0xd4d9f90 (semid 14) destroyed
# dm target-version crypt [ opencount flush ] [16384] (*1)
# device-mapper: target-version ioctl on crypt failed: Invalid argument
# dm versions [ opencount flush ] [16384] (*1)
# dm target-version crypt [ opencount flush ] [16384] (*1)
# device-mapper: target-version ioctl on crypt failed: Invalid argument
# dm versions [ opencount flush ] [16384] (*1)
# Releasing crypt device /dev/nvme0n1p3 context.
# Releasing device-mapper backend.
# Closing read only fd for /dev/nvme0n1p3.
Command failed with code -5 (device already exists or device is busy).
I also tried a not correct password and the error message says something of “wrong password”, so it is the right password.
But this leads to where I started:
The system shows only the “Lenovo” logo at boot, three dots (rising an vanishing) and the Manjaro logo right under it.
(Yes, I have a backup, but I want to know the system better, so I invest time and effort in this.)
I appreciate any hints.
All the best from varomanja
P.S.: I did not add more tags, because I think it is not only “update” related.
Replacing that is not a good idea.
The .pacnew merely contains a default configuration - nothing specific to your machine.
Either leave it as it is or merge it in a meaningful way.
… too late now, I guess … if you don’t have a backup of that file
But it should be easy to recreate.
Are you sure that /dev/nvme0n1p3 is the encrypted partition?
n1p3 at the end of the command is just an arbitrary name - just saying
but it looks to me the device was already open - you did already chroot into it, it looks like, judging by the # root prompt
I do have a backup of the /etc/openswap.conf but it is on the encrpyted partition (and in the backup should be a correct version too).
The /dev/nvme0n1p3 was - as @linux-aarhus mentioned later - presumably the swap partition and /dev/nvme0n1p3 would be the correct object. I could have guessed this from the fdisk -l and the sizes of the partitions.
You can use the Manjaro ISO instead of bobs-rescue.
It’s probably easier.
At least the people here know what to expect - unlike with bobs-rescue (I have never heard of it).
But: any Linux will do for this task
It’s just that the manjaro ISO contains a tool (manjaro-chroot) to make the job significantly easier.
There are posts and wiki posts here describing the procedure.
Boot that, open a terminal, then
first, get a picture of what your partition layout looks like:
lsblk -f
post the output if you need help with interpreting what you see.
Based on that, you can proceed to open the encrypted container.
lsblk -f
again, after that
Then you can mount the partitions that are inside in the correct order.
Then you can chroot into the correctly assembled file system
using manjaro-chroot ...
and repair/update your system.
ps:
I was curious.
bobs-rescue seems to be a
bootable recovery disk based on the Windows Preinstallation Environment (Windows PE)
… Bob.Omb’s Modified Win10PEx64
Something ain’t right (duh)
either with your encrypted volume
or perhaps with your hardware
Which one it is I cannot tell.
Something goes wrong 20 lines after the password entry (the line with no # in front of it):
here is the same portion when I do the same:
(I created a new virtual disk in my VM, created a gpt partition on it and formatted it as a luks type 1 volume)
Using another ISO makes no difference - but you could try to reboot the system.
You cannot create two open containers from the same volume - only one.
Please use the rescue and recovery topic as reference for how to open and mount a luks volume.
When opening a luks container hosting a default Manjaro Installation it will be luks1 - this is not an issue as cryptsetup will open it correct even if you don’t provide a type.
Restart using the rescue ISO - you could also ensure that you have no active mapper crypt containers open - but it is easier to just restart.
On a default Manjaro system the layout is always
first partition is $esp
second partition is root
third partition is swap
So the process is
cryptsetup luksOpen /dev/<disk>2 system
Mount root partition
mount /dev/mapper/system /mnt
When mounted you check the content of /mnt to vefify it is correct - it should return a similar output (yours will not be identical)
$ ls /mnt
a home proc tmp
bin lib root tpm2_pkcs11.sqlite3
boot lib64 rootfs-pkgs.txt usr
desktopfs-pkgs.txt lost+found run var
dev miso sbin
efi mnt srv
etc opt sys
I may or may not have quite a few passwords , but I can easily remember them and try them all in turn.
My strategy:
a quote from some book I read or some people I know who I will always associate with a particular saying that they often use - which no one else will even guess,
then take that phrase and use for instance the first letter of each word of that phrase - this will be hard to guess for anyone even if one would know that there are only letters in that pretty long sequence - which they don’t.
It may be hit and miss a couple of times for you, but you’ll always be able to eventually remember that phrase that it is derived from.
You’ll never guess a random password …
, but I can easily remember them and try them all in turn.