Bug 441728
| Summary: | rc.sysinit is trying to "cryptsetup create" on a LUKS partition | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> | ||||||||||||||||||
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||||
| Priority: | low | ||||||||||||||||||||
| Version: | rawhide | CC: | rvokal, symbiont | ||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||
| Hardware: | All | ||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||
| Last Closed: | 2008-04-15 17:27:37 UTC | Type: | --- | ||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||
| Embargoed: | |||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||
| Bug Blocks: | 235706 | ||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
Charles R. Anderson
2008-04-09 18:00:39 UTC
Created attachment 301868 [details]
screenshot of rc.sysinit running w/set -x
I booted with set -x in /etc/rc.sysinit. Here is a screenshot showing the
bootup sequence. cryptsetup isLuks is run on /dev/mapper/fedora.data-home,
which when I run it manually returns 0 (true) so I'm not sure why it is
choosing the "else" clause which runs cryptsetup create.
if [ -z "$makeswap" ] && cryptsetup isLuks "$src" 2>/dev/null ; then
if key_is_random "$key"; then
echo $"$dst: LUKS requires non-random key, skipping"
ret=1
continue
fi
if [ -n "$params" ]; then
echo "$dst: options are invalid for LUKS partitions," \
"ignoring them"
fi
/sbin/cryptsetup ${key:+-d $key} luksOpen "$src" "$dst" <&1
else
/sbin/cryptsetup $params ${key:+-d $key} create "$dst" "$src" <&1
2>/dev/null
fi
I don't think we're considering non-anaconda applyed crypto setups as release blockers for F9. Moving to target (unless bill disagrees and moves it back). This isn't non-anaconda applied. Anaconda created all of this, and the system fails to boot properly. Created attachment 301871 [details]
anaconda install.log
Created attachment 301874 [details]
anaconda install.log.syslog
Created attachment 301875 [details]
anaconda-ks.cfg
Created attachment 301876 [details]
fstab after commenting out /home
Created attachment 301877 [details]
/etc/crypttab
Created attachment 301879 [details]
anaconda.log
Created attachment 301883 [details]
[PATCH] fix for rc.sysinit to call init_crypto again after LVM init
The problem was that rc.sysinit wasn't handling the case where you have an
encrypted LV. Calling init_crypto again after LVM is activated fixes the
problem. Since anaconda now supports creating encrypted LV's, can you please
apply this fix to rc.sysinit? Thanks.
*** Bug 221304 has been marked as a duplicate of this bug. *** Added in git, will be in 8.70-1. http://git.fedorahosted.org/git/?p=initscripts.git;a=commit;h=1e610b947935fa07f427c06bb0490d92ab67a0ae |