You are not logged in.
I have installed Arch on a btrfs raid1 array using two identical drives. When I try to boot into the system only one of the partitions will decrypt, and then the other fails and drop me into a rootfs shell:
registered: /dev/mapper/cryptlvm1
mount: new_root: fsconfig system call failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.
ERROR: Failed to mount '/dev/mapper/cryptlvm1' on real root
I am able to manually decrypt the other partition and then mount the subvolumes and get the system going from there, but of course i need to resolve the actual issue for this to be usable. What am i missing here? I see others have created a keyfile to manage decryption, however Id prefer to just enter two passphrases instead. any suggestions?
/etc/crypttab:
https://0x0.st/8MCT.A7oUN2VM
/etc/mkinitcpio.conf:
https://0x0.st/8MCu.ozlB6kXZ
ls -la /mnt/btrfs/@
https://0x0.st/8MCr.wlktr1Co
btrfs subvolume list /mnt/btrfs
https://0x0.st/8MCz.8GOVL2p3
btrfs filesystem show /mnt/btrfs
https://0x0.st/8MCi.EJI3xTDZ
btrfs device usage /mnt/btrfs
https://0x0.st/8M7M.wEjbGUEX
/etc/default/grub
https://0x0.st/8MCq.KANnnctm
/etc/fstab
https://0x0.st/8M7J.LThSne9x
Last edited by qherring (Yesterday 17:52:35)
Offline
I have zero experience with raid1 while basic knowledge of btrfs. So if the problem is with those 2, then I'm way out of my league.
However, your /etc/crypttab contains an entry for cryptlvm1 which if I'm understanding correctly contains your root partition. If you look at the top of the /etc/crypttab file:
# NOTE: Do not list your root (/) partition here, it must be set up
# beforehand by the initramfs (/etc/mkinitcpio.conf).This may be a superficial error and not the cause of the problem.
-----
Are you using btrfs on top of lvm? If this is the case then you are missing the lvm2 hook on /etc/mkinitcpio.conf.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt btrfs filesystems btrfs fsck)-----
I didn't really look at the btrfs stuff since there are people here more qualified than me to comment on them.
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline
I have zero experience with raid1 while basic knowledge of btrfs. So if the problem is with those 2, then I'm way out of my league.
However, your /etc/crypttab contains an entry for cryptlvm1 which if I'm understanding correctly contains your root partition. If you look at the top of the /etc/crypttab file:
# NOTE: Do not list your root (/) partition here, it must be set up # beforehand by the initramfs (/etc/mkinitcpio.conf).This may be a superficial error and not the cause of the problem.
-----
Are you using btrfs on top of lvm? If this is the case then you are missing the lvm2 hook on /etc/mkinitcpio.conf.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt btrfs filesystems btrfs fsck)-----
I didn't really look at the btrfs stuff since there are people here more qualified than me to comment on them.
im not using lvm, just use that for naming my mapped since im used to it from prior system
i tried with and without that top entry in crypttab - made no noticeable difference
Offline
what ended up working is this:
for grub:
GRUB_CMDLINE_LINUX= "rd.luks.uuid=<UUIDofDev#1> rd.luks.uuid=<UUIDofDev#2> rootflags=degraded,subvol=@ rw"
might be able to get rid of degraded option but i havent gotten around to removing it to test
for mkinitcpio.conf
HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole block sd-encrypt btrfs filesystems fsck)
My /etc/crypttab.initramfs has both encrypted partitions listed
essentially i copied my current crypttab over and uncommented out the two lines
the setup uses systemd to unlock two drives at startup
Last edited by qherring (Yesterday 17:55:37)
Offline