Description of problem: When generating an initrd for a luks device using sha1/256/512 hash, the modules arn't loaded Version-Release number of selected component (if applicable): mkinitrd-6.0.93-23.1.mga1 How reproducible: Alway Steps to Reproduce: 1. cryptsetup -c aes-xts-plain -h sha256 -s 256 luksFormat /dev/sdXY /tmp/key 2. cryptsetup luksOpen /dev/sdXY root 3. echo '/dev/mapper/root / xfs rw 0 0' > /etc/mtab 4. echo 'UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx / ext2 defaults 1 1' > /etc/fstab 5. mkinitrd -f -v /boot/initrd-2.... 2....
(In reply to comment #0) > Description of problem: > When generating an initrd for a luks device using sha1/256/512 hash, the > modules arn't loaded > Version-Release number of selected component (if applicable): > mkinitrd-6.0.93-23.1.mga1 > > How reproducible: > Alway > > Steps to Reproduce: > 1. cryptsetup -c aes-xts-plain -h sha256 -s 256 luksFormat /dev/sdXY /tmp/key > 2. cryptsetup luksOpen /dev/sdXY root > 3. echo '/dev/mapper/root / xfs rw 0 0' > /etc/mtab > 4. echo 'UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx / ext2 defaults 1 1' > > /etc/fstab > 5. mkinitrd -f -v /boot/initrd-2.... 2.... I dreamt very vividly about invisible fonts after reading bug 2995, so now I tend to think the modules got loaded OK, but you just can't see them ;) @ tmb @ funda Can one of you try to reproduce, please?
CC: (none) => fundawang, marja11, tmb
@ Colin same question as in the other mkinitrd bug: now that mkinitrd is per default replaced by dracut in cauldron, what to do with this bug report?
CC: (none) => mageia
(In reply to comment #2) > @ Colin > > same question as in the other mkinitrd bug: now that mkinitrd is per default > replaced by dracut in cauldron, what to do with this bug report? Of course, ask Raphael whether dracut solves this bug for him :) @ Raphael Can you please try generating an initrd for your luks device again, but now with dracut, and tell us whether that fixes the problem?
Keywords: (none) => NEEDINFO
Raphael, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to use dracut instead of mkinitrd If this issue turns out to still be reproducible with the latest update of dracut, please open a new bug report with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD