Gentoo Archives: gentoo-server

From: aechols@××××××××××××.edu
To: gentoo-server@g.o
Subject: Re: [gentoo-server] LVM not working after reboot
Date: Fri, 12 Dec 2003 20:34:15
Message-Id: 1071282854.3fda7aa688466@webmail.physics.tamu.edu
In Reply to: [gentoo-server] LVM not working after reboot by Thomas Smith
1 To boot from a logical volume you must use an initrd. Use lvmcreate_initrd to
2 make it. Also make sure your kernel supports ramdisks and the default size is
3 large enough. More details here:
4 http://www.the-infinite.org/archive/docs/lvm/howto-boot-off-root-lv.txt
5
6 -Andy
7
8 Quoting Thomas Smith <tom@××××××××××××××.org>:
9
10 > I'm having a problem with LVM after rebooting my stage3 install of
11 > Gentoo. Here's the filesystem layout:
12 >
13 > /dev/md0 - RAID1 - /dev/hda1 & /dev/hdb1 - /boot
14 > /dev/md1 - RAID0 - /dev/hda2 & /dev/hdb2 - / & swap
15 > VG - vgroot
16 > LV - /dev/vgroot/swap & /dev/vgroot/root
17 >
18 > RAID & LVM are compiled into the Kernel (no modules). I also emerged
19 > (after chroot-ing to /mnt/gentoo) lvm-user, the LVM user-space tools,
20 > and created an initrd files for booting / from LVM.
21 >
22 > The problem occurs when the Kernel runs vgscan during boot. Here's the
23 > error:
24 >
25 > “vgscan -- reading all physical volumes (this may take a while...)
26 > cdrom: open failed.
27 > vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
28 > vgscan -- WARNING: This program does not do a VGDA backup of your volume
29 > group
30 >
31 > vgchange -- no volume groups found
32 >
33 > VFS: Cannot open root device "vgroot/root" or 00:00
34 > Please append a correct "root=" boot option
35 > Kernel panic: VFS: Unable to mount root fs on 00:00"
36 >
37 > I've confirmed that the RAID devices are properly loading from the
38 > output during boot.
39 >
40 > Ideas?
41 >
42 >
43
44
45
46
47 -------------------------------------------------
48 This mail sent through IMP: http://horde.org/imp/

Replies

Subject Author
Re: [gentoo-server] LVM not working after reboot Thomas Smith <tom@××××××××××××××.org>