Arthur Hagen wrote:

> Oops, my bad, going from memory. *It's actually "dmsetup ls", which should
> list all your dm devices, and give you an error if it can't communicate
> with the kernel device mapper.
>
> Regards,


No devices found.

You know I wonder if when I built a new kernel I didn't build in the device
mapper support correctly and it had been the other way.

But you said the baselayout is 1 not 2 now and the experimental enablement
doesn't sound like something I would do. Does it select the baselayout
based on whether udev is in the kernel maybe?

udevd started with trace instead of daemon provides no output when events
should be sensed. I assume it isn't wrong but whatever passes this info on.
There is also a udevmonitor which basically says the same thing, nothing
while on another system provides a full verbosity of events.
So a guess might be there is another setting in the kernel compile that I
totally missed. While the tail end of help on CONFIG_BLK_DEV_DM: does not
seem to indicate a missing option sometimes they are incomplete.

On this system I have raid but not raid on lvm, would that have become a
problem? There really is no lvm in usage right now so the 'dmsetup ls'
is not suprising to be empty unless it is also supposed to list udev stuff.

Thanks.
-Walt