1 |
Hi Neil, |
2 |
|
3 |
> /usr/src contains the source to the kernel (as you'd expect form the |
4 |
> name). The actual kernels live in /boot, this is the version that |
5 |
> must |
6 |
> match. |
7 |
|
8 |
Gentoo started booting after changing following line; |
9 |
kernel (hd0,0)/boot/kernel-2.6.17-gentoo-r7 root=/dev/hda2 |
10 |
to |
11 |
kernel (hd0,0)/boot/linux-2.6.17-gentoo-r7 root=/dev/hda2 |
12 |
|
13 |
But still having following problems; |
14 |
|
15 |
|
16 |
1) |
17 |
Engine: Unable to open the engine block file /var/lock/evms-engine : |
18 |
Read only filesystem. The engine is not protected against other |
19 |
instances of the Engine being opened at the same time. Error returned |
20 |
from evms_commit_changes ( ) : No such device [!!] |
21 |
|
22 |
|
23 |
2) |
24 |
Loading module 3c59x .... |
25 |
Failed to load 3c59x [!!] |
26 |
|
27 |
|
28 |
3) |
29 |
All |
30 |
/dev/vg/usr |
31 |
/dev/vg/home |
32 |
/dev/vg/opt |
33 |
/dev/vg/var |
34 |
/dev/vg/tmp |
35 |
|
36 |
have same problem as listed follow; |
37 |
e2fsck: No such file or directory which trying to open /dev/vg/usr. |
38 |
The super block could not be read or does not describe a correct ext2 |
39 |
filesystem. If the device is valid and it really contains an ext2 |
40 |
filesystem (and not swap or ufs or something else). There the |
41 |
superblock is corrupt, and your might trying e2fsck with an alternative |
42 |
superblock : |
43 |
e2fsck -b 8193 |
44 |
|
45 |
# e2fsck -b 8193 /dev/vg/usr |
46 |
fsck.ext3: No such file or directory while trying to open /dev/vg/usr |
47 |
|
48 |
Please advise how to fix them. TIA |
49 |
|
50 |
B.R. |
51 |
SL |
52 |
-- |
53 |
gentoo-user@g.o mailing list |