That's another good reason to rely on UUID instead of the /dev device name. If you see how MD does things, and LVM internally, you'll find all device references are by UUID. Why not use that more foolproof method? As long as the device is online, it doesn't matter what bus id it gets. -- Peter H. Larsen -----Original Message----- From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On Behalf Of Till Wimmer Sent: Tuesday, September 15, 2009 1:35 PM To: LVM general discussion and development Subject: Re: RE: vg availability during boot > 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/
