>>> On 10/30/2009 at 1:23 AM, Paul Raulerson <[email protected]> wrote: -snip- > Has anyone else ran into this?
Not without some error messages and the like to go on. LVM doesn't care about device names, or DASD address ordering, etc. All it cares about is if it can find the UUIDs it expects for all its PVs. Those are written on the disk volumes when pvcreate and vgextend is done. If it can't find all those UUIDs, then it will throw a fit. Usually that means that a PV was added to the VG, and that volume was not available at the next reboot. Most often that's the result of not re-running mkinitrd and zipl. (YaST will do that for you automatically if you use it, otherwise you have to remember to do it. Not sure if Red Hat has a similar mechanism to keep things in synch.) Mark Post
