1 |
You'll want the forums. Take the elevator back down to the third |
2 |
floor, http://forums.gentoo.org . If you want a more interactive |
3 |
responce, take it down to the lobby and hook up on the FreeNode IRC |
4 |
Tram. It should take you to #gentoo. |
5 |
|
6 |
On 5/15/06, Joe Harvell <jharvell@××××××.net> wrote: |
7 |
> I am in the process of installing Gentoo on an x86 from the 2006.0 |
8 |
> installer CD using the 2.4 kernel profile. I created an LVM2 volume |
9 |
> group with logical volumes / filesystems for '/', '/usr', '/var', |
10 |
> '/opt', and '/home'. I had no problems mounting those filesystems and |
11 |
> then chrooting into that environment and performing the base install. I |
12 |
> compiled the 2.4.32-r4 kernel from gentoo-sources with no problems, and |
13 |
> created the initial ram disk by hand so that I could bring up the LVM2 |
14 |
> volumes. |
15 |
> |
16 |
> The problem I am having is when I boot into the initrd. I run vgscan |
17 |
> with no apparent problems, and it finds the volume group. When I run |
18 |
> 'vgchange -ay <vgname>, I notice three problems: |
19 |
> |
20 |
> 1. There are entries in /dev/mapper/<vgname>-<lvname>, but no symlinks |
21 |
> in the form /dev/<vgname>/<lvname> --> /dev/mapper/<vgname>/<lvname>. I |
22 |
> run 'lvm vgmknodes' and it remedies this. |
23 |
> |
24 |
> 2. I see five complaints from 'vgchange -ay <vgname>' (one for each LV) |
25 |
> as follows: |
26 |
> |
27 |
> on stderr: device-mapper: table ioctl failed: Invalid argument |
28 |
> on console (from dm-mod driver): device-mapper: one of name or uuid must |
29 |
> be supplied, cmd (12) |
30 |
> |
31 |
> I ran vgchange under strace and here is the following snippet: |
32 |
> |
33 |
> open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 9 |
34 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
35 |
> address) |
36 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
37 |
> address) |
38 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
39 |
> address) |
40 |
> mlockall(MCL_CURRENT|MCL_FUTURE) = 0 |
41 |
> brk(0x8936000) = 0x8936000 |
42 |
> brk(0x8b1e000) = 0x8b1e000 |
43 |
> getpriority(PRIO_PROCESS, 0) = 20 |
44 |
> setpriority(PRIO_PROCESS, 0, -18) = 0 |
45 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
46 |
> address) |
47 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
48 |
> address) |
49 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
50 |
> address) |
51 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
52 |
> address) |
53 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
54 |
> address) |
55 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
56 |
> address) |
57 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
58 |
> address) |
59 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
60 |
> address) |
61 |
> ioctl(9, DM_DEV_STATUS, 0x8109958) = -1 ENXIO (No such device or |
62 |
> address) |
63 |
> stat64("/dev/ide/host0/bus0/target0/lun0/part10", {st_mode=S_IFBLK|0600, |
64 |
> st_rdev=makedev(3, 10), ...}) = 0 |
65 |
> stat64("/dev/ide/host0/bus0/target0/lun0/part11", {st_mode=S_IFBLK|0600, |
66 |
> st_rdev=makedev(3, 11), ...}) = 0 |
67 |
> stat64("/dev/ide/host0/bus0/target0/lun0/part12", {st_mode=S_IFBLK|0600, |
68 |
> st_rdev=makedev(3, 12), ...}) = 0 |
69 |
> ioctl(9, DM_DEV_CREATE, 0x8109958) = 0 |
70 |
> ioctl(9, DM_TABLE_STATUS, 0x8109958) = -1 EINVAL (Invalid argument) |
71 |
> write(2, " ", 2) = 2 |
72 |
> write(2, "device-mapper: table ioctl faile"..., 51) = 51 |
73 |
> write(2, "\n", 1) = 1 |
74 |
> |
75 |
> 3. When I try to mount the filesystem in that LV, it fails. I tried |
76 |
> with different filesystem types and it's the same result. From within |
77 |
> the 2.4 kernel based initrd, it fails. If I reboot into the 2.6 kernel |
78 |
> based installer environment, no problem. |
79 |
> |
80 |
> This looks like an incompatibility between the lvm2 and/or device-mapper |
81 |
> library code and the kernel device-mapper code. Here are the versions |
82 |
> installed in the new installation and its initrd: |
83 |
> |
84 |
> lvm2-2.02.05 |
85 |
> device-mapper-1.02.03 |
86 |
> gentoo-sources-2.4.32-r4 |
87 |
> |
88 |
> livecd 2.4 # ls -l /etc/make.profile |
89 |
> lrwxrwxrwx 1 root root 51 May 11 18:09 /etc/make.profile -> |
90 |
> /usr/portage/profiles/default-linux/x86/no-nptl/2.4 |
91 |
> |
92 |
> -- |
93 |
> gentoo-embedded@g.o mailing list |
94 |
> |
95 |
> |
96 |
|
97 |
|
98 |
-- |
99 |
Kelly "STrRedWolf" Price |
100 |
http://strredwolf.furrynet.com |
101 |
|
102 |
-- |
103 |
gentoo-embedded@g.o mailing list |