1 |
Am Donnerstag 29 September 2011, 09:11:09 schrieb J.Marcos Sitorus: |
2 |
> Hi Volker, |
3 |
> Thanks for the reply. |
4 |
> I have attach dmesg, xorg log, xsession-error, and kdm log. |
5 |
> |
6 |
> >So - get back to your last working versions - oh and those lvm volumes are |
7 |
> |
8 |
> on |
9 |
> new disks? |
10 |
> Nope. Previously I have two separate partition. Then I delete both partition |
11 |
> and create LVM from the free space. |
12 |
|
13 |
ok - did you check that the devices are error-free (with badblocks)? |
14 |
|
15 |
> |
16 |
> >You did not knock the ram loose while putting them in? |
17 |
> |
18 |
> What do you mean by knock the ram loose? |
19 |
> Sorry, English is not my mother language. |
20 |
|
21 |
M. Mol answered that. Since you did not put in new disks, you have hardly done |
22 |
any damage ;) |
23 |
|
24 |
|
25 |
btw the logs after a crash not after a clean boot are the usefull ones ;) |
26 |
|
27 |
A couple of questions: |
28 |
|
29 |
do you have any crashes when virtualbox was not started and no virtualbox |
30 |
modules are loaded? |
31 |
|
32 |
do you have any other odd behaviour - occasional segfaults etc? |
33 |
|
34 |
which options did you use when you run mkfs.reiser4? |
35 |
|
36 |
are you able to reproduce the problem with a vanilla kernel? Make sure you are |
37 |
using 2.6.38 - not .1 or greater. Reiser4 sometimes breaks with stable |
38 |
releases - and 2.6.38.X was very broken... |
39 |
|
40 |
-- |
41 |
#163933 |