On sobota, 23 stycznia 2021 01:42:32 CET Carlos E. R. wrote:
On 23/01/2021 01.12, J Leslie Turriff wrote:
On 2021-01-22 12:44:56 Carlos E. R. wrote:
|On 22/01/2021 15.13, J Leslie Turriff wrote: |> On 2021-01-22 05:34:05 Carlos E.R. wrote: |>> |On 22/01/2021 11.41, Daniel Bauer wrote: |... | |>> |> Why is an entry written to crypttab? Can I avoid that somehow? |>> | |>> |Maybe change some option to "noauto". :-? |> |> I have an external drive with several encrypted partitions for |> backups, which cause this same delay, even though the entries in |> fstab include 'noauto'. There is no such option for crypttab. |> Perhaps something in the boot initrd is cleverly being 'helpful', à |> la Windows' Clippy.>> | |According to the man page, the settings do exist, but I also have |problems with them: | | |man crypttab | | The fourth field, if present, is a comma-delimited | list of options. The following options are | | recognized: |... | | noauto | | This device will not be automatically unlocked on boot. | | nofail | | The system will not wait for the device to show up and be | |unlocked at boot, and not fail the boot if it does not show up.
Ah, that's right. I remember now, that I tried that just like you did, but it doesn't work. Bug report time? I'll have to check on next boot, because I changed one setting.
Do you remember to rerun dracut after you mess with /etc/crypttab? Apparently some script assembles a crypttab used by the initramfs at that time and if you don't regenerate it, your changes won't be reflected at boot time. Regards Radosław Wyrzykowski