On Thu, 2006-04-06 at 15:50 -0500, Boyd Stephen Smith Jr. wrote: > On Thursday 06 April 2006 11:44, Fredrik Tolf <[EMAIL PROTECTED]> wrote > about '[gentoo-user] LVM boot problem': > > I'm having a bit of a problem with LVM2 on Gentoo. See, I have a > > computer with a couple of hard drives in an LVM, and when it boots, I > > can see it loading the driver modules for the controller cards properly > > (I've added them to /etc/modules.autoload.d), but then when it comes to > > initializing the LVM, it complains that it cannot find all the PVs to > > initialize the VG. In fact, it complains about _all_ the PVs, as though > > it found none. > > Is / on LVM? Are you using an initrd / initramfs?
Nope. Here's my fstab (minus pseudo-FS:s): /dev/hda2 / ext3 defaults,acl,user_xattr 0 1 /dev/hda1 none swap sw 0 0 /dev/vg1/newhome /home reiserfs defaults,acl,user_xattr 0 2 /dev/vg1/dlwsroot /srv/dlwsroot xfs defaults 0 3 /dev/vg1/site /usr/site xfs defaults 0 4 > Does your early userspace start a /dev daemon? If you mean udev, yes. > Does your early userspace have a different lvm.conf then your final userspace? Nope. > > Later, when the system is booted, I can log in as root and just run > > "vgchange -ay" to get the VG up. Note that I don't have to run pvscan > > first, which I'm assuming has to mean that it has somehow managed to > > find the PVs somewhere in the meantime. > > Are all of your pvs standard disks or disk partitions? Partitions. Here's the output of pvs: PV VG Fmt Attr PSize PFree /dev/hde1 vg1 lvm2 a- 111.79G 0 /dev/hdf1 vg1 lvm2 a- 111.79G 0 /dev/hdg1 vg1 lvm2 a- 111.79G 0 /dev/hdh1 vg1 lvm2 a- 111.79G 60.68G /dev/sda1 vg1 lvm2 a- 186.30G 186.30G /dev/sdb1 vg1 lvm2 a- 279.46G 0 /dev/sdc1 vg1 lvm2 a- 279.46G 0 > What modules are being loaded by the gentoo /etc/modules.autoload system? pcspkr pdc202xx_new sata_sil sd_mod rpcsec_gss_krb5 > What is your RC_VOLUME_ORDER in /etc/conf.d/rc? RC_VOLUME_ORDER="raid evms lvm dm" > Does your /lib/rcscripts/addons/lvm-start.sh > contain "/sbin/vgscan --mknodes --ignorelockingfailure >/dev/null"? Yep. > > This problem is quite annoying, since it means that I have to restart > > NFS and boot the system without the network cable plugged in (if it was, > > the NFS clients would try to reconnect and get handles to the wrong > > filesystem, which makes them mark the mount points as stale). > > You might investigate the mpt= /etc/exports option to only export > filesystems that have been successfully mounted, at least temporarily. Interesting. I'll definitely use that. For completeness, though, I should mention that looking at the manpage, it seems to be named "mp" rather than "mpt". Thanks! Fredrik Tolf -- [email protected] mailing list
