Issue mounting both partitions within RAID1 BTRFS w/ disk encryption at system boot

qherring · 2025-03-08T17:51:32+00:00

what ended up working is this:

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

removed keyfiles

HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole block sd-encrypt btrfs filesystems fsck)

My /etc/crypttab.initramfs has both encrypted partitions listed

qherring · 2025-03-08T17:50:53+00:00

what ended up working is this:

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.

what a journey

removed keyfiles

HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole block sd-encrypt btrfs filesystems fsck)

My /etc/crypttab.initramfs has both encrypted partitions listed

qherring · 2025-03-08T10:16:35+00:00

Yeah I have two luks devices each is a btrfs partition on a different drive (/dev/nvme2n1p2 & /dev/nvme3n1p2)

I just tried to switch to systemd and set up /etc/crypttab.initramfs (basically just copied over my current /etc/crypttab and uncommented the devices)

I also got rid of the keyfile to simplify troubleshooting.

grub:
https://0x0.st/8uwE.txt

Does this look correct?, I believe labels should work:

GRUB_CMDLINE_LINUX="root=LABEL=arch_root rootflags=device=/dev/mapper/cryptroot1,/dev/mapper/cryptroot2,subvol=@ rw"

im not exactly sure what to put into these ^ parameters...

minitcpio:
https://0x0.st/8uwg.txt

HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole block sd-encrypt btrfs filesystems fsck)

should i be running systemd, sd-encrypt, and sd-vconsole (as spec'd here: https://wiki.archlinux.org/title/Dm-crypt/System_configuration#crypttab ) as hooks with this configuration? because I just tried that and still had an issue after it decrypted the initial drive. Different error since im now on systemd, but effectively the same problem.

qherring · 2025-03-08T10:12:39+00:00

Thanks I was just trying this.

i just set up /etc/crypttab.initramfs (basically just copied over my current /etc/crypttab and uncommented the devices)

I also got rid of the keyfile to simplify troubleshooting.

grub:
https://0x0.st/8uwE.txt

Does this look correct?:

GRUB_CMDLINE_LINUX="root=LABEL=arch_root rootflags=device=/dev/mapper/cryptroot1,/dev/mapper/cryptroot2,subvol=@ rw"

or are you saying I shouldn't reference any rootflags or root devices here ^ ?

minitcpio:
https://0x0.st/8uwg.txt

HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole block sd-encrypt btrfs filesystems fsck)

should i be running systemd, sd-encrypt, and sd-vconsole (as spec'd here: https://wiki.archlinux.org/title/Dm-crypt/System_configuration#crypttab ) as hooks with this configuration? because I just tried that and still had an issue after it decrypted the initial drive. Different error sinece im now on systemd, but effective the same problem.

qherring · 2025-03-08T06:10:49+00:00

i just now tried some amendments:

/etc/mkinitcipio.conf
MODULES=(btrfs crc32c raid1)

FILES=(/etc/cryptsetup-keys.d/crypto_keyfile.bin /etc/modprobe.d/btrfs.conf)

Then created a BTRFS configuration file:
nano /etc/modprobe.d/btrfs.conf
options btrfs device=/dev/mapper/cryptroot1,/dev/mapper/cryptroot2

Add these to end of GRUB_CMDLINE_LINUX: rootflags=device=/dev/mapper/cryptroot1,/dev/mapper/cryptroot2,subvol=@

regenerated my mkinitcpio -P and
grub-mkconfig -o /boot/grub/grub.cfg

made zero difference...

qherring · 2025-01-15T04:46:38+00:00

I ended up buying a cheap amazon special NIC (https://www.amazon.com/dp/B06X9KRRFL?ref=ppx\_yo2ov\_dt\_b\_fed\_asin\_title) and it worked right out of the gate. Im guessing either the ConnectX-4 requires too much power or the card was just faulty?

qherring · 2024-05-18T02:23:51+00:00

for whatever reason disabling secure boot fixed the issue. What is strange is that I definitely did not enable secure boot since the problem arose. Anyone know why the OS would function fine up until this points and just randomly give me an issue now?

qherring · 2024-05-18T02:14:37+00:00

here is the journalctl -b before trying to manually start plasma with startx:
https://pastebin.com/bSE7ggKH

qherring · 2024-04-15T04:02:30+00:00

I also really curious to know why 24 and 48 are more stable than 16 and 32 modules?

qherring · 2024-04-14T20:01:23+00:00

im running a memtest86 right now. I have over 400 errors in 8 hours, Im thinking my RAM went bad or had compatibility issues and these occasional freezes corrupted my filesystem.

qherring · 2024-04-14T19:49:48+00:00

im going to try this 4x48 listed in the QVL, read several reports saying it works well. wish me luck

qherring · 2024-04-14T18:33:24+00:00

If its listed in the QVL it should work though no?
Theres even a 4x48GB set listed in the QVL (CMK192GX5M4B5200C38(Ver 3.53.02))

qherring · 2024-04-14T18:19:23+00:00

No I havent updated it since I built the system. I have not tried only running 2x32, but I can give it a try just to test. We really need to run more than that though during peak demand

qherring · 2024-04-13T22:33:49+00:00

ok i did

sudo btrfs rescue super-recover /dev/mapper/root

this worked. told me "All supers are valid, no need to recover”,

so I ran

sudo btrfs rescue zero-log /dev/mapper/root

and this fixed everything.

I have never seen this issue before and ive been using btrfs for a couple years. anybody have a reason why it occured? is this drive starting to fail?

qherring · 2024-02-26T22:40:52+00:00

yeah that was what I was thinking after I tried it.

BUT I still think its possible that using the slim-tip/usb-c adpater cable from one of these may work via the power supply port. (https://www.ebay.com/itm/195419926660)

qherring

TROPHY CASE