![](https://seccdn.libravatar.org/avatar/62125288dd40f3bb08a59554fbf73db9.jpg?s=120&d=mm&r=g)
Am 23.01.21 um 01:12 schrieb J Leslie Turriff:
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?
Leslie
I added noauto to that entry in crypttab. No difference. My computer insists on waiting 1 minute and 30 seconds at boot. On bigbrother I found: https://bugzilla.redhat.com/show_bug.cgi?id=1524759 The last entry says: "To prevent that device from being unlocked automatically, you also need to disable the mount unit." But I have no idea what this could mean :-) a detail: I use several eternal USB-disks, all encrypted the same way, but this happens with only one of them (a WD_Elements). The only difference between those external disks is that this one is one with external power supply, while the others are connected only with USB. -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com