On Thu, Dec 23, 2010 at 07:55, Steven Haigh <netwiz(a)crc.id.au> wrote:
<snip>
Looking at this further:
# sh -x /usr/share/dracut/modules.d/90crypt/check
+ which cryptsetup
+ exit 1
# which cryptsetup
/usr/bin/which: no cryptsetup in
(/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
This looks to be failing as I no package supplying cryptsetup is
installed. If I understand the output correctly, it is saying cryptsetup
doesn't exist, therefore plymouth is failing?
If this is indeed the problem, then
$ yum whatprovides */cryptsetup
tells me that you need the package
cryptsetup-luks
Does it work if you install this package?
In
$ rpm -q --changelog dracut
I find the following entry:
-----
* Wed Oct 13 2010 Harald Hoyer <harald(a)redhat.com> 006-3
- plymouth dracut module should only depend on crypt module,
if cryptsetup exists
Resolves: rhbz#642617
-----
Perhaps this introduced an unexpected problem?
It seems that something should have a dependency on cryptsetup-luks if
that is a required dependency. I'm not sure which package should pull
in the dependency to make the kernel postinstall scripts work in this
case.
According to
$ rpm -q --whatrequires cryptsetup-luks
and
$ rpm -q --whatrequires /sbin/cryptsetup
the only thing that requires this package is hal
Best,
Kåre
--
Kåre Fiedler Christiansen