I've followed the instructions, but when it comes to the "mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdh1" command, I get:

mdadm: partition table exists on /dev/sdh1

mdadm: partition table exists on /dev/sdh1 but will be lost or meaningless after creating array

mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90

Continue creating array?

...I answer no at that point, but what should I do?

My OS is AlmaLinux, but I would think the instructions would apply. It uses an LVM partition system, but other instructions I've found that include LVM have the same steps.

Thanks for any help.

@Some Guy: there exist backends to make directly-network-attached scanners available to the sane ecosystem. Look for "sane-escl" (part of core Sane project, airprint/airscan protocol) and/or "sane-airscan " (3rd party open source, airprint/airscan + Microsoft WSD "WEB Service for devices" ).

Debian Wiki goes into more detail: SaneOverNetwork > escl protocol

Sorry to interupt but what's about nftables?

I have not yet switched to nftables, though it's on my list. In other words, I don't know yet.

So is this done in the bare repo or where?

Yes, in the bare repo.

Hello - thanks for this info I've had the exact same issue and am now able to boot. Just struggling with the 2nd part of the fix;

system boots normally

fixing issue

edit /etc/crypttab

rename the first space delimited

occurrence with sameluksdrivenamethenappend_crypt

quit n save

finally run

root@ubuntu# update-initramfs -u -v

finally reboot

fixed.

I can't seem to edit the crypttab file to start with, do you know which viewer i should be using? And then is it simply a case of adding the _crypt to the first space delimited occurence?

Hello, Thank you for this very useful article!

Just to comment that for the UMASK change to take effect, it is necessary (in Debian 12) to add the module pam_umask.so to the file /etc/pam.d/common-session with the following line:

session optional pam_umask.so

References:

https://www.debian.org/doc/manuals/securing-debian-manual/ch04s11.en.html#id-1.5.14.19 https://salsa.debian.org/vorlon/pam/-/merge_requests/3

This document is about how to use SANE to share a USB scanner over the network, and it seems to use some SANE-specific protocol. All the comments in the relative configuration files are written as if the remote scanner was an instance of SANE on a Linux machine.

In my case, the scanner has built-in network support, and I haven't found any evidence that SANE supports this use case. That's unfortunate, since CUPS supports the printer portion of that device without much difficulty. I can't get the scanner close enough to my PC for a USB connection, so it looks like the only way I'm scanning from this thing from Linux is if I put a Raspberry Pi next to it just so it can serve SANE to me.

This suggested fix does not require a live OS.

# ramfs shell commands
(initramfs) blkid
#get the driver with LuKs crypt
(initramfs) cryptsetup luksOpen /dev/luksdrive sameluksdrivenamethenappend_crypt
(initramfs) vgchange -ay
(initramfs) exit
# system boots normally
# fixing issue
# edit /etc/crypttab
#rename the first space delimited
# occurrence with sameluksdrivenamethenappend_crypt
# quit n save
# finally run
root@ubuntu# update-initramfs -u -v
# finally reboot
# fixed.