On Wed, 1 Oct 2008, dave peck wrote:

<snip>
>
> Well, precisely the same thing as the package install/update did:
>
> $ rpm -q --scripts kernel | grep mkinit
> /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install 2.6.18-92.1.10.el5 || exit $?
> /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install 2.6.18-92.1.13.el5 || exit $?
> $
> $ sudo /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install 2.6.18-92.1.13.el5
> /sbin/mkinitrd: line 368: cd: slaves: No such file or directory

That line is trying to cd into a dm-*/slaves sub-directory.  I don't see 
why it is failing (the dm- directory must exist to pass the test 3 lines 
above the cd).

What does running:

   ls -ld /sys/block/dm-*/slaves

show on the systems which fail?

The mkinitrd script should probably check that the cd worked, but to be 
honest I've yet to see a /sys/block/dm-*/ directory without a slaves 
sub-directory...

(line 368 is near the top of the definition of findstoragedriverinsys() 
which gets called from findstoragedriver() at least some of the time).

  -- Jon