1 |
Hi Jean-Marc, |
2 |
|
3 |
> Do you follow the installation guide from gentoo.org? |
4 |
|
5 |
There are several documents on Gentoo website. I followed 2 documents: |
6 |
|
7 |
Partitioning HD with LVM |
8 |
Gentoo LVM2 installation |
9 |
http://www.gentoo.org/doc/en/lvm2.xml |
10 |
|
11 |
Installation |
12 |
Gentoo Linux AMD64 Handbook |
13 |
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml |
14 |
|
15 |
|
16 |
> I mean, do you use a |
17 |
> "standard" scheme? |
18 |
|
19 |
I made some adjustment for my case. I did not emerge LVM2. |
20 |
|
21 |
If fail again. I'll run a final test according their HD config (w/o |
22 |
slave), not running LVM. |
23 |
|
24 |
B.R. |
25 |
SL |
26 |
|
27 |
|
28 |
|
29 |
> |
30 |
> |
31 |
> On 9/5/06, Stephen Liu <satimis@×××××.com> wrote: |
32 |
> > |
33 |
> > Hi Neil, |
34 |
> > |
35 |
> > > /usr/src contains the source to the kernel (as you'd expect form |
36 |
> the |
37 |
> > > name). The actual kernels live in /boot, this is the version that |
38 |
> > > must |
39 |
> > > match. |
40 |
> > |
41 |
> > Gentoo started booting after changing following line; |
42 |
> > kernel (hd0,0)/boot/kernel-2.6.17-gentoo-r7 root=/dev/hda2 |
43 |
> > to |
44 |
> > kernel (hd0,0)/boot/linux-2.6.17-gentoo-r7 root=/dev/hda2 |
45 |
> > |
46 |
> > But still having following problems; |
47 |
> > |
48 |
> > |
49 |
> > 1) |
50 |
> > Engine: Unable to open the engine block file /var/lock/evms-engine |
51 |
> : |
52 |
> > Read only filesystem. The engine is not protected against other |
53 |
> > instances of the Engine being opened at the same time. Error |
54 |
> returned |
55 |
> > from evms_commit_changes ( ) : No such device [!!] |
56 |
> > |
57 |
> > |
58 |
> > 2) |
59 |
> > Loading module 3c59x .... |
60 |
> > Failed to load 3c59x [!!] |
61 |
> > |
62 |
> > |
63 |
> > 3) |
64 |
> > All |
65 |
> > /dev/vg/usr |
66 |
> > /dev/vg/home |
67 |
> > /dev/vg/opt |
68 |
> > /dev/vg/var |
69 |
> > /dev/vg/tmp |
70 |
> > |
71 |
> > have same problem as listed follow; |
72 |
> > e2fsck: No such file or directory which trying to open /dev/vg/usr. |
73 |
> > The super block could not be read or does not describe a correct |
74 |
> ext2 |
75 |
> > filesystem. If the device is valid and it really contains an ext2 |
76 |
> > filesystem (and not swap or ufs or something else). There the |
77 |
> > superblock is corrupt, and your might trying e2fsck with an |
78 |
> alternative |
79 |
> > superblock : |
80 |
> > e2fsck -b 8193 |
81 |
> > |
82 |
> > # e2fsck -b 8193 /dev/vg/usr |
83 |
> > fsck.ext3: No such file or directory while trying to open |
84 |
> /dev/vg/usr |
85 |
> > |
86 |
> > Please advise how to fix them. TIA |
87 |
> > |
88 |
> > B.R. |
89 |
> > SL |
90 |
> > -- |
91 |
> > gentoo-user@g.o mailing list |
92 |
> > |
93 |
> > |
94 |
> |
95 |
> |
96 |
> -- |
97 |
> /JM |
98 |
> |
99 |
|
100 |
-- |
101 |
gentoo-user@g.o mailing list |