Peter Jones wrote:
On Wed, 2006-09-13 at 15:49 -0400, Dave Jones wrote:
> Ok, the important difference is this ..
>
> Loading dm-snapshot.ko module
> -Making device-mapper control node
> -Scanning logical volumes
> - Reading all physical volumes. This may take a while...
> - Found volume group "VolGroup00" using metadata type lvm2
> -Activating logical volumes
> - 3 logical volume(s) in volume group "VolGroup00" now active
> Trying to resume from /dev/VolGroup00/LogVol01
>
> Peter, any recent mkinitrd changes that could explain this ?
Not really - though I have seen some reports similar to this. Generally
it's happening when lvm segfaults during mkinitrd -- that manifests as
not having any volume groups active, which means we don't include lvm
(and thus don't start your volume group) during bootup.
There is a empty logical disk on this raid controller I haven't put into
use yet - could this have anything to do with things? It's of course the
same under both kernels.