[Experimental] Slackware rootfs on a multi-device bcachefs
by 0XBF from LinuxQuestions.org on (#6N2Z7)
Disclaimer: bcachefs is a recent addition to the Linux kernel and still in experimental stages. For a stable production machine, you should use something well proven, like ext4. bcachefs on a "multi-device pool" also requires manually editing Slackware's init scripts, bootloaders, and initrd. If you want to experiment with bcachefs, feel free, but expect to be on the bleeding edge. I'm just here to document my experience so far, for myself and anyone else who's interested and following bcachefs development. I'm not recommending anyone else to follow me. ;)
Intro: I picked up some new HDD's and wanted to give the new bcachefs filesystem a test run in something with a bit more complexity to it. The plan is to use a pool of 3 x 4TB HDD's, and a 500GB M2 NVME SSD in a bcachefs formatted "pool" of drives. The idea being to use the NVME disk to cache read/writes for the larger pool of drives, and then take advantage of bcachefs features like compression, replication, and encryption.
Note: While Slackware-current now has bcachefs built into the kernel and bcachefs-tools to work with the format, bootloaders are a different matter, particularly when using a multi-disk pool of drives and the format it uses to specify the root "disk". For now the only viable way to use bcachefs as the rootfs seems to be by loading the latest kernel with an initrd, and performing the mount command from there. This kernel and initrd should be on another partition type that the bootloader can read from, e.g. an ext4 formatted /boot, or efi partition with elilo might work (untested). In my case I added the drives to an existing Slackware-15.0 system to "dual boot" with Slackware-current installed onto bcachefs. My plan is to continue managing the grub bootloader from Slackware-15.0, so I kept using Slackware-15.0's /boot directory to store the kernel and initrd for loading the Slackware-current on the bcachefs install.
Pre-Work:
1. Backup Slackware-15.0 files, prepare 15.0's fstab for removal of old storage disks, and ensure all mounts are done via LABEL in case the added disks change device node numbering.
2. Prepare a slackware64-current installer iso usb in order to test and use the added bcachefs-tools from the installer.
3. Shutdown, remove old disks, install new disks, reboot into installer usb.
Formatting the bcachefs drives with the Slackware installer:
After booting with the slackware64-current installation dvd/iso, 'lsblk' reports the following:
Code:NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
sdb 8:16 0 3.6T 0 disk
sdc 8:32 0 3.6T 0 disk
sdd 8:48 0 232.9G 0 disk
|-sdd1 8:49 0 500M 0 part
|-sdd2 8:50 0 16G 0 part
`-sdd3 8:51 0 216.4G 0 part
sde 8:64 1 7.5G 0 disk
|-sde1 8:65 1 4.1G 0 part
`-sde2 8:66 1 1.4M 0 part
nvme1n1 259:0 0 238.5G 0 disk
|-nvme1n1p1 259:1 0 260M 0 part
|-nvme1n1p2 259:2 0 16M 0 part
|-nvme1n1p3 259:3 0 237.2G 0 part
`-nvme1n1p4 259:4 0 1000M 0 part
nvme0n1 259:5 0 465.8G 0 diskSo the 3 x 4TB drives are sda, sdb, sdc, and the nvme drive is nvme0n1.
With that information, I used the following command to create the bcachefs system:
Code:# bcachefs format --compression=lz4 \
--encrypted \
--replicas=2 \
--label=ssd.ssd1 /dev/nvme0n1 \
--label=hdd.hdd1 /dev/sda \
--label=hdd.hdd2 /dev/sdb \
--label=hdd.hdd3 /dev/sdc \
--foreground_target=ssd \
--promote_target=ssd \
--background_target=hddNote: I added encryption, so bcachefs format prompted for a password after entering the above command.
Next mount the bcachefs formatted disks onto /mnt so we can proceed with the setup program:
Code:mount -t bcachefs /dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc /mntNote: If the bcachefs mount is encrypted, it will prompt for the passphrase to mount the drives onto mnt/.
Once mounted, start the installer with 'setup'.
Slackware's installer will "Scan for target partitions", but not find the bcachefs formatted disks. However, the bcachefs disks are already mounted on mnt/ from the previous command so once the installer starts, select "TARGET" and then just select continue. The installer will continue onward to select the source media and install to the mounted bcachefs in the /mnt location.
With a full install selected, the installer completed in several minutes.
Notes: I skipped making a swap partition; I will try adding a swapfile after installation if I find the need. For now it is suspending/resuming fine without, and the machine has 32G of RAM. I also skipped adding lilo/elilo bootloaders, since I am going to continue using grub from Slackware 15.0 as the bootloader.
Once the installer is finished, drop back to the shell and chroot into /mnt to make an initrd and patch the rc.S and rc.6 scripts:
Code:chroot /mntNote: If you're fresh out of the installer, the bind mounts for dev, proc, and sys are all still in place so the above chroot is all thats needed to chroot into the fresh system.
Once in the /mnt chroot, generate an initrd. While bcachefs is built into the kernel, mounting it with a multi-device path cant be done from grub, so were going to need the initrd anyway so we can properly mount the rootfs. Using an initrd with usb keyboard drivers will also be required to enter in passwords to unlock the encrypted bcachefs drive.
Note that to unlock an encrypted bcachefs drive we have to include the bcachefs binary in the initrd. This can be built into the chroot by copying it over the initrd-tree and building the initrd without the '-c' switch. We also have to modify the 'init' script in the initrd to allow unlocking the bcachefs encrypted disks, otherwise they will fail to unlock at boot and panic the kernel. If you skip encryption then these steps are not necessary.
Code:install -m755 /sbin/bcachefs /boot/initrd-tree/sbinCode:--- init 2024-05-26 16:56:42.065995648 -0500
+++ init.new 2024-05-26 16:56:21.321996461 -0500
@@ -322,6 +322,13 @@
# Switch to real root partition:
/sbin/udevadm settle --timeout=10
echo 0x0100 > /proc/sys/kernel/real-root-dev
+
+ # Unlock bcachefs disks if they are encrypted:
+ if [ "$ROOTFS" = "bcachefs" ]; then
+ BCACHEFSDISK1=$(echo $ROOTDEV | cut -d: -f1)
+ /sbin/bcachefs unlock $BCACHEFSDISK1
+ fi
+
mount -o ro${ROOTFLAGS:+,$ROOTFLAGS} -t $ROOTFS $ROOTDEV /mnt
if [ ! -r /mnt/sbin/init ]; thenNote: mkinitrd_command_generator.sh fails over trying to determine the filesystem type for the mkinitrd command when using a multi-device bcachefs (the drives are in a ':' delimited list and an individual drive must be separated out of this list to test what filesystem is in use with way the script is written).
I used the following command, after fixing up mkinitrd_command_generator.sh's output:
Code:mkinitrd -k 6.9.1 -f bcachefs -r /dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:bcachefs -u -o /boot/initrd.gzWhile still in the chroot, we need to fix /etc/rc.d/rc.S, otherwise Slackware on bcachefs will fail to boot when it attempts to fsck the rootfs and fails at that. I made the following edit to use bcachefs's "fsck on mount" feature:
Code:--- rc.S 2024-05-26 15:38:18.187973829 -0500
+++ rc.S.new 2024-05-26 15:37:41.617975328 -0500
@@ -204,6 +204,10 @@
if grep -q ' / f2fs ' /proc/mounts ; then
echo "Remounting root device with read-write enabled."
/sbin/mount -w -v -n -o remount /
+ # bcachefs can fsck itself at mount time:
+ elif grep -q ' / bcachefs ' /proc/mounts ; then
+ echo "Remounting root bcachefs device(s) with read-write enabled."
+ /sbin/mount -o remount,rw,fsck,fix_errors /
elif [ ! $READWRITE = yes ]; then
# Check the root filesystem:
RETVAL=0The shutdown script also needs a tweak for bcachefs because it fails to remount read-only and complains about the -n option:
Code:--- rc.6 2024-05-26 17:40:54.138996139 -0500
+++ rc.6.new 2024-05-26 17:40:34.883996929 -0500
@@ -291,8 +291,10 @@
# In spite of this, it seems that a JFS root partition will always be checked
# (and found to be clean) at boot:
/bin/sync
- echo "Remounting root filesystem read-only:"
- /bin/mount -v -n -o remount,ro /
+ if ! grep -q ' / bcachefs ' /proc/mounts ; then
+ echo "Remounting root filesystem read-only:"
+ /bin/mount -v -n -o remount,ro /
+ fi
fi
# This never hurts:The last thing left to do is get a copy of the kernel and it's matching initrd over to the /boot directory for grub. Since I'm dual booting from slackware-15.0, I mounted the slackware-15.0 disk at a temporary mount point, then copied the initrd.gz and kernel to the slackware-15.0's /boot directory with custom names to separate it from slackware-15.0's existing kernels and initrd:
Code:mount /dev/sdd3 /mnt/tmp
cp /boot/initrd.gz /mnt/tmp/boot/initrd-testing.gz
cp /boot/vmlinuz-generic-6.9.1 /mnt/tmp/boot/Exit the chroot and reboot the machine back into Slackware 15.0 to configure the bootloader. I used grub and have my own symlinking scheme to track kernels and initrds, so this part will differ for others. The general steps are:
1. Get grub to associate the new kernel and initrd from the bcachefs system, then run:
Code:grub-mkconfig -o /boot/grub/grub.cfg2. Edit the newly created /boot/grub/grub.cfg file, filling in the proper root device and rootfstype on the kernel command line with the following:
Code:echo 'Loading Linux testing ...'
linux /boot/vmlinuz-testing root=/dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc rootfstype=bcachefs
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-testingNote: I use symlinks for my kernels and initrds. In any case, the boot entry that correlates to kernel of the bcachefs system and its initrd should be entered similar to the above.
Remember to not overwrite this boot entry. Make backups and be able to remake this change if grub is updated from slackware-15.0.
Reboot and select the testing kernel from grub, this will mount the bcachefs multi-device root and boot the system from there, using the modified rc.S script. Shutdowns should also be clean with the modified rc.6 code. With encryption used, I had to enter my password twice: Once to mount the read-only rootfs from the initrd, and a second time when the rootfs remounts read-write from rc.S.
Here's a couple interesting outputs from the running bcachefs system:
Code:$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 32M 1.7M 31M 6% /run
devtmpfs 8.0M 0 8.0M 0% /dev
/dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc 11T 21G 11T 1% /
none 192K 69K 119K 37% /sys/firmware/efi/efivars
tmpfs 16G 0 16G 0% /dev/shm
cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup
tmpfs 3.2G 0 3.2G 0% /run/user/0
tmpfs 3.2G 0 3.2G 0% /run/user/1000Code:lsblk --fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848
sdb bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848
sdc bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848
sdd
sdd1 vfat FAT32 slack-efi A109-5E2F
sdd2 swap 1 slack-15-swap 3800b55f-5d00-4b8e-8fda-a92fed1f22ce
sdd3 ext4 1.0 slack-15-rootfs 693d27b0-7c59-4291-a478-2a6f5d0c7a85
sde iso9660 Joliet Extension Slackware-current DVD 2024-05-24-13-16-00-31
sde1 iso9660 Joliet Extension Slackware-current DVD 2024-05-24-13-16-00-31
sde2 vfat FAT12 C84C-EB11
nvme1n1
nvme1n1p1 vfat FAT32 SYSTEM A25D-26C4
nvme1n1p2
nvme1n1p3 ntfs Windows 9E6C5FE26C5FB42D
nvme1n1p4 ntfs WinRE_DRV 2AA4602FA45FFBA7
nvme0n1 bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848 10.3T 0% /With all that, the system is up and running for now. I'll be testing builds and running software on current with this install, so I'll see how the rootfs holds up I guess. ;)
Cheers,
Bob
Intro: I picked up some new HDD's and wanted to give the new bcachefs filesystem a test run in something with a bit more complexity to it. The plan is to use a pool of 3 x 4TB HDD's, and a 500GB M2 NVME SSD in a bcachefs formatted "pool" of drives. The idea being to use the NVME disk to cache read/writes for the larger pool of drives, and then take advantage of bcachefs features like compression, replication, and encryption.
Note: While Slackware-current now has bcachefs built into the kernel and bcachefs-tools to work with the format, bootloaders are a different matter, particularly when using a multi-disk pool of drives and the format it uses to specify the root "disk". For now the only viable way to use bcachefs as the rootfs seems to be by loading the latest kernel with an initrd, and performing the mount command from there. This kernel and initrd should be on another partition type that the bootloader can read from, e.g. an ext4 formatted /boot, or efi partition with elilo might work (untested). In my case I added the drives to an existing Slackware-15.0 system to "dual boot" with Slackware-current installed onto bcachefs. My plan is to continue managing the grub bootloader from Slackware-15.0, so I kept using Slackware-15.0's /boot directory to store the kernel and initrd for loading the Slackware-current on the bcachefs install.
Pre-Work:
1. Backup Slackware-15.0 files, prepare 15.0's fstab for removal of old storage disks, and ensure all mounts are done via LABEL in case the added disks change device node numbering.
2. Prepare a slackware64-current installer iso usb in order to test and use the added bcachefs-tools from the installer.
3. Shutdown, remove old disks, install new disks, reboot into installer usb.
Formatting the bcachefs drives with the Slackware installer:
After booting with the slackware64-current installation dvd/iso, 'lsblk' reports the following:
Code:NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
sdb 8:16 0 3.6T 0 disk
sdc 8:32 0 3.6T 0 disk
sdd 8:48 0 232.9G 0 disk
|-sdd1 8:49 0 500M 0 part
|-sdd2 8:50 0 16G 0 part
`-sdd3 8:51 0 216.4G 0 part
sde 8:64 1 7.5G 0 disk
|-sde1 8:65 1 4.1G 0 part
`-sde2 8:66 1 1.4M 0 part
nvme1n1 259:0 0 238.5G 0 disk
|-nvme1n1p1 259:1 0 260M 0 part
|-nvme1n1p2 259:2 0 16M 0 part
|-nvme1n1p3 259:3 0 237.2G 0 part
`-nvme1n1p4 259:4 0 1000M 0 part
nvme0n1 259:5 0 465.8G 0 diskSo the 3 x 4TB drives are sda, sdb, sdc, and the nvme drive is nvme0n1.
With that information, I used the following command to create the bcachefs system:
Code:# bcachefs format --compression=lz4 \
--encrypted \
--replicas=2 \
--label=ssd.ssd1 /dev/nvme0n1 \
--label=hdd.hdd1 /dev/sda \
--label=hdd.hdd2 /dev/sdb \
--label=hdd.hdd3 /dev/sdc \
--foreground_target=ssd \
--promote_target=ssd \
--background_target=hddNote: I added encryption, so bcachefs format prompted for a password after entering the above command.
Next mount the bcachefs formatted disks onto /mnt so we can proceed with the setup program:
Code:mount -t bcachefs /dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc /mntNote: If the bcachefs mount is encrypted, it will prompt for the passphrase to mount the drives onto mnt/.
Once mounted, start the installer with 'setup'.
Slackware's installer will "Scan for target partitions", but not find the bcachefs formatted disks. However, the bcachefs disks are already mounted on mnt/ from the previous command so once the installer starts, select "TARGET" and then just select continue. The installer will continue onward to select the source media and install to the mounted bcachefs in the /mnt location.
With a full install selected, the installer completed in several minutes.
Notes: I skipped making a swap partition; I will try adding a swapfile after installation if I find the need. For now it is suspending/resuming fine without, and the machine has 32G of RAM. I also skipped adding lilo/elilo bootloaders, since I am going to continue using grub from Slackware 15.0 as the bootloader.
Once the installer is finished, drop back to the shell and chroot into /mnt to make an initrd and patch the rc.S and rc.6 scripts:
Code:chroot /mntNote: If you're fresh out of the installer, the bind mounts for dev, proc, and sys are all still in place so the above chroot is all thats needed to chroot into the fresh system.
Once in the /mnt chroot, generate an initrd. While bcachefs is built into the kernel, mounting it with a multi-device path cant be done from grub, so were going to need the initrd anyway so we can properly mount the rootfs. Using an initrd with usb keyboard drivers will also be required to enter in passwords to unlock the encrypted bcachefs drive.
Note that to unlock an encrypted bcachefs drive we have to include the bcachefs binary in the initrd. This can be built into the chroot by copying it over the initrd-tree and building the initrd without the '-c' switch. We also have to modify the 'init' script in the initrd to allow unlocking the bcachefs encrypted disks, otherwise they will fail to unlock at boot and panic the kernel. If you skip encryption then these steps are not necessary.
Code:install -m755 /sbin/bcachefs /boot/initrd-tree/sbinCode:--- init 2024-05-26 16:56:42.065995648 -0500
+++ init.new 2024-05-26 16:56:21.321996461 -0500
@@ -322,6 +322,13 @@
# Switch to real root partition:
/sbin/udevadm settle --timeout=10
echo 0x0100 > /proc/sys/kernel/real-root-dev
+
+ # Unlock bcachefs disks if they are encrypted:
+ if [ "$ROOTFS" = "bcachefs" ]; then
+ BCACHEFSDISK1=$(echo $ROOTDEV | cut -d: -f1)
+ /sbin/bcachefs unlock $BCACHEFSDISK1
+ fi
+
mount -o ro${ROOTFLAGS:+,$ROOTFLAGS} -t $ROOTFS $ROOTDEV /mnt
if [ ! -r /mnt/sbin/init ]; thenNote: mkinitrd_command_generator.sh fails over trying to determine the filesystem type for the mkinitrd command when using a multi-device bcachefs (the drives are in a ':' delimited list and an individual drive must be separated out of this list to test what filesystem is in use with way the script is written).
I used the following command, after fixing up mkinitrd_command_generator.sh's output:
Code:mkinitrd -k 6.9.1 -f bcachefs -r /dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:bcachefs -u -o /boot/initrd.gzWhile still in the chroot, we need to fix /etc/rc.d/rc.S, otherwise Slackware on bcachefs will fail to boot when it attempts to fsck the rootfs and fails at that. I made the following edit to use bcachefs's "fsck on mount" feature:
Code:--- rc.S 2024-05-26 15:38:18.187973829 -0500
+++ rc.S.new 2024-05-26 15:37:41.617975328 -0500
@@ -204,6 +204,10 @@
if grep -q ' / f2fs ' /proc/mounts ; then
echo "Remounting root device with read-write enabled."
/sbin/mount -w -v -n -o remount /
+ # bcachefs can fsck itself at mount time:
+ elif grep -q ' / bcachefs ' /proc/mounts ; then
+ echo "Remounting root bcachefs device(s) with read-write enabled."
+ /sbin/mount -o remount,rw,fsck,fix_errors /
elif [ ! $READWRITE = yes ]; then
# Check the root filesystem:
RETVAL=0The shutdown script also needs a tweak for bcachefs because it fails to remount read-only and complains about the -n option:
Code:--- rc.6 2024-05-26 17:40:54.138996139 -0500
+++ rc.6.new 2024-05-26 17:40:34.883996929 -0500
@@ -291,8 +291,10 @@
# In spite of this, it seems that a JFS root partition will always be checked
# (and found to be clean) at boot:
/bin/sync
- echo "Remounting root filesystem read-only:"
- /bin/mount -v -n -o remount,ro /
+ if ! grep -q ' / bcachefs ' /proc/mounts ; then
+ echo "Remounting root filesystem read-only:"
+ /bin/mount -v -n -o remount,ro /
+ fi
fi
# This never hurts:The last thing left to do is get a copy of the kernel and it's matching initrd over to the /boot directory for grub. Since I'm dual booting from slackware-15.0, I mounted the slackware-15.0 disk at a temporary mount point, then copied the initrd.gz and kernel to the slackware-15.0's /boot directory with custom names to separate it from slackware-15.0's existing kernels and initrd:
Code:mount /dev/sdd3 /mnt/tmp
cp /boot/initrd.gz /mnt/tmp/boot/initrd-testing.gz
cp /boot/vmlinuz-generic-6.9.1 /mnt/tmp/boot/Exit the chroot and reboot the machine back into Slackware 15.0 to configure the bootloader. I used grub and have my own symlinking scheme to track kernels and initrds, so this part will differ for others. The general steps are:
1. Get grub to associate the new kernel and initrd from the bcachefs system, then run:
Code:grub-mkconfig -o /boot/grub/grub.cfg2. Edit the newly created /boot/grub/grub.cfg file, filling in the proper root device and rootfstype on the kernel command line with the following:
Code:echo 'Loading Linux testing ...'
linux /boot/vmlinuz-testing root=/dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc rootfstype=bcachefs
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-testingNote: I use symlinks for my kernels and initrds. In any case, the boot entry that correlates to kernel of the bcachefs system and its initrd should be entered similar to the above.
Remember to not overwrite this boot entry. Make backups and be able to remake this change if grub is updated from slackware-15.0.
Reboot and select the testing kernel from grub, this will mount the bcachefs multi-device root and boot the system from there, using the modified rc.S script. Shutdowns should also be clean with the modified rc.6 code. With encryption used, I had to enter my password twice: Once to mount the read-only rootfs from the initrd, and a second time when the rootfs remounts read-write from rc.S.
Here's a couple interesting outputs from the running bcachefs system:
Code:$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 32M 1.7M 31M 6% /run
devtmpfs 8.0M 0 8.0M 0% /dev
/dev/nvme0n1:/dev/sda:/dev/sdb:/dev/sdc 11T 21G 11T 1% /
none 192K 69K 119K 37% /sys/firmware/efi/efivars
tmpfs 16G 0 16G 0% /dev/shm
cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup
tmpfs 3.2G 0 3.2G 0% /run/user/0
tmpfs 3.2G 0 3.2G 0% /run/user/1000Code:lsblk --fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848
sdb bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848
sdc bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848
sdd
sdd1 vfat FAT32 slack-efi A109-5E2F
sdd2 swap 1 slack-15-swap 3800b55f-5d00-4b8e-8fda-a92fed1f22ce
sdd3 ext4 1.0 slack-15-rootfs 693d27b0-7c59-4291-a478-2a6f5d0c7a85
sde iso9660 Joliet Extension Slackware-current DVD 2024-05-24-13-16-00-31
sde1 iso9660 Joliet Extension Slackware-current DVD 2024-05-24-13-16-00-31
sde2 vfat FAT12 C84C-EB11
nvme1n1
nvme1n1p1 vfat FAT32 SYSTEM A25D-26C4
nvme1n1p2
nvme1n1p3 ntfs Windows 9E6C5FE26C5FB42D
nvme1n1p4 ntfs WinRE_DRV 2AA4602FA45FFBA7
nvme0n1 bcachefs 1.7 f088d57e-2004-4366-829b-90ca9fd0c848 10.3T 0% /With all that, the system is up and running for now. I'll be testing builds and running software on current with this install, so I'll see how the rootfs holds up I guess. ;)
Cheers,
Bob