View previous topic :: View next topic |
Author |
Message |
yalu2 n00b
Joined: 12 Aug 2007 Posts: 1
|
Posted: Sun Aug 12, 2007 11:25 am Post subject: root on lvm2: can't find logical volumes |
|
|
I am trying to install Gentoo on my Sun Ultra5 with the root fs on lvm. Problems arise when I boot the kernel. I built a kernel and initrd with lvm support.
My silo.conf:
Code: |
partition=1
root=/dev/mapper/aardbei-root
timeout=50
default=linux
read-only
image = /kernel-genkernel-sparc64-2.6.21-gentoo-r4
label=linux
initrd=/initramfs-genkernel-sparc64-2.6.21-gentoo-r4
append="video=atyfb:off udev root=/dev/ram0 real_root=/dev/aardbei/root init=/linuxrc"
|
Last messages when it boots:
Code: |
>> Loading modules
>> Activating mdev
>> Scanning for Volume Groups
Reading all physical volumes. This may take a while...
Found volume group "aardbei" using metadata type lvm2
>> Activating Volume Groups
0 logical volume(s) in volume group "aardbei" now active
>> Determining root device...
!! Block device /dev/aardbei/root is not a valid root device...
!! the root block device is unspecified or not detected.
Please specify a device to boot, or "shell" for a shell...
boot() :: _
|
Also, I can't type "shell" and enter a shell. It seems as if the keyboard is dead. my only option is to power off... |
|
Back to top |
|
|
djscribble Tux's lil' helper
Joined: 03 Aug 2005 Posts: 116
|
Posted: Fri Aug 17, 2007 4:39 am Post subject: |
|
|
Is your boot partition on your in your vg?? if so, then you have some serious problems (IMHO) however if it is not, then you need to change your initial root= line from /dev/mapper/aardbei-root to be root=/dev/[boot device] |
|
Back to top |
|
|
nixnut Bodhisattva
Joined: 09 Apr 2004 Posts: 10974 Location: the dutch mountains
|
Posted: Fri Aug 17, 2007 5:17 pm Post subject: |
|
|
Moved from Installing Gentoo to Gentoo on Sparc.
Sparc stuff, so moved here. _________________ Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
Back to top |
|
|
SStreet n00b
Joined: 06 Aug 2004 Posts: 11
|
Posted: Tue Aug 28, 2007 3:34 pm Post subject: |
|
|
From the looks of the kernel mesages kicked out, specifically: Quote: | ">> Scanning for Volume Groups
Reading all physical volumes. This may take a while...
Found volume group "aardbei" using metadata type lvm2
>> Activating Volume Groups
0 logical volume(s) in volume group "aardbei" now active " |
It appears that dm-mod is not in the kernel (perhaps you have it in as a module?) You'll need to rebuild the kernel with that built-in to have root as a lvm managed volume -- though not recommended.
All of my setups on the 3 archs I run (PPC, Sparc64, and x86) each has a root as a mirrored (md) partition, and a second mirror partition that holds the PV for LVM.
ie: on my sparc64:
(/dev/sda) (first disk)
Disk /dev/sda (Sun disk label): 255 heads, 63 sectors, 8922 cylinders
Units = cylinders of 16065 * 512 bytes
Device Flag Start End Blocks Id System
/dev/sda1 0 12 96390 83 Linux native
/dev/sda2 12 134 979965 fd Linux raid autodetect
/dev/sda3 0 8922 71665965 5 Whole disk
/dev/sda4 305 8922 69216052+ fd Linux raid autodetect
/dev/sda5 134 305 1373557+ fd Linux raid autodetect
(/dev/sdb)(second disk)
Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 8922 cylinders
Units = cylinders of 16065 * 512 bytes
Device Flag Start End Blocks Id System
/dev/sdb1 0 12 96390 83 Linux native
/dev/sdb2 12 134 979965 fd Linux raid autodetect
/dev/sdb3 0 8922 71665965 5 Whole disk
/dev/sdb4 305 8922 69216052+ fd Linux raid autodetect
/dev/sdb5 134 305 1373557+ fd Linux raid autodetect
on each disk sda1 and sdb1 are copies of the boot partition (silo hates mirrored disks, I'm convinced of it!), so they are ext2 filesystems, I just dd /dev/sda1 to /dev/sdb1 if I change kernels or update silo.
/dev/sda5 and /dev/sdb5 are the two parts for /dev/md1 ( / )
/dev/sda2 and /dev/sdb2 are the two parts for /dev/md2 (swap); I'm using an old Ultra 60 with 2 72G 10k RPM drives, which are prone to breakage - I hate my system to crash just because a disk dies...
/dev/sda4 and /dev/sdb4 are the two parts for /dev/md4 (lvm); this is then broken down into
LV VG Attr LSize Origin Snap% Move Log Copy%
distfiles rootvg -wi-ao 4.00G
home rootvg -wi-ao 10.00G
opt rootvg -wi-ao 4.00G
portage rootvg -wi-ao 2.00G
tmp rootvg -wi-a- 2.00G
usr rootvg -wi-ao 8.00G
var rootvg -wi-ao 4.00G
vartmp rootvg -wi-ao 6.00G
then mounted as:
Filesystem Size Used Avail Use% Mounted on
/dev/md/1 1.4G 141M 1.2G 11% /
udev 11M 295k 11M 3% /dev
/dev/sda1 96M 5.9M 85M 7% /boot
/dev/mapper/rootvg-usr
8.5G 2.4G 5.8G 29% /usr
/dev/mapper/rootvg-portage
2.2G 279M 1.8G 14% /usr/portage
/dev/mapper/rootvg-distfiles
4.3G 700M 3.4G 18% /usr/portage/distfiles
/dev/mapper/rootvg-home
11G 173M 9.9G 2% /home
/dev/mapper/rootvg-opt
4.3G 143M 3.9G 4% /opt
/dev/mapper/rootvg-var
4.3G 329M 3.7G 9% /var
/dev/mapper/rootvg-vartmp
6.4G 13M 6.1G 1% /var/tmp
shm 1.1G 0 1.1G 0% /dev/shm
|
|
Back to top |
|
|
|