I spent four days messing with this before I found this procedure for rebuilding initrd, which worked for me. This howto talks specifically about switching to RAID, but it also worked for me switching to LVM on RAID: http://www.howtoforge.com/software-raid1-grub-boot-fedora-8 -- Ray Morris support@bettercgi.com Strongbox - The next generation in site security: http://www.bettercgi.com/strongbox/ Throttlebox - Intelligent Bandwidth Control http://www.bettercgi.com/throttlebox/ Strongbox / Throttlebox affiliate program: http://www.bettercgi.com/affiliates/user/register.php On 09/15/2009 12:35:18 PM, Till Wimmer wrote: > > Did you rebuild initrd? During boot, initrd uses staticly linked > modules to load what otherwise would be kernel modules. It does, if > LVM is enabled, do a vgchange -y a as part of that process. Since LVM > is part of the default initrd, it may be the drivers for your SAN > that > you need to get in place - remember to include the high-end Ethernet > drivers too that your NAS (I presume?) uses. > > > Hi, > > i have a quite similar problem with my server. But in my case, it > occurs from time to time only. > Before i had another issue with mounting the root partition because > of > swapped SCSI IDs (sda becomes sdb, sdc, becomes sda, and so on). But > i > could solve this with ext2fs labels. > > I'm using Debian Lenny. > > Is the vgchange -ay in initrd executed for every volume group or is > this hard coded by update-initrd? > > Could the swapping of SCSI-IDs be the reason for this issue, too? > > > Thank you, > TW > > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > > _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
