[DragonFlyBSD - Bug #2281] cryptdisks doesn't work right when booting

[Matthias Rampke via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2281 has been updated by Matthias Rampke.


does

    kldload dm_target_crypt; cryptsetup -a

work? does setting

    dm_target_crypt_load=yes

in /boot/loader.conf work around the issue?
----------------------------------------
Bug #2281: cryptdisks doesn't work right when booting
http://bugs.dragonflybsd.org/issues/2281

Author: Pierre Abbat
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 


I have a cryptdisk which is mounted as /crypt/. crypttab says it should try three times and timeout. It does timeout if I say nothing, but if I enter the right password, it aborts. Apparently it can't load the kernel module for the cipher. dmesg looks like this:

cd0: 33.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
Mounting root from hammer:serno/Y2P0C2BE.s1d
tryroot serno/Y2P0C2BE.s1d
HAMMER(ROOT) recovery check seqno=4233877a
HAMMER(ROOT) recovery range 3000000005d50088-3000000005d50088
HAMMER(ROOT) recovery nexto 3000000005d50088 endseqno=4233877b
HAMMER(ROOT) mounted clean, no recovery needed
Mounting devfs
disk scheduler: set policy of mapper/temporary-cryptsetup-34 to noop
dm: could not autoload module for target crypt
drm0: <Intel i865G GMCH> on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] AGP at 0xf0000000 128MB
info: [drm] Initialized i915 1.6.0 20080730
disk scheduler: set policy of mapper/temporary-cryptsetup-1001 to noop
dm_target_crypt: Successfully initialized
dm_target_crypt: Setting min/max mpipe buffers: 2/12
kthread 0xd1c248e0 mpipe_dm_crypt has exited
kthread 0xd1c24660 mpipe_dm_crypt has exited
disk scheduler: set policy of mapper/temporary-cryptsetup-1001 to noop
dm_target_crypt: Setting min/max mpipe buffers: 2/12
kthread 0xd1c24660 mpipe_dm_crypt has exited

Here is /etc/crypttab:

crypt1  /dev/serno/WD-WCAS80774005.s1d  none    tries=3,timeout=200


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account