> Did this filesystem corruption happen only once, or more than that? It did happen every time I tried, with one exception. > Is just X crashing, or is the system completely unresponsive > (including over the network)? If the former, do you have > corresponding X and kernel logs?It's not like a freeze of X. For example I'm able to switch to a serial terminal but I can't login. The response is:
/bin/login: error while loading shared libraris: /lib/libpam_misc.so.0: invalid ELF header Ext3-fs error (device hda6): ext3_lookup: deletet inode referenced: ....On the other hand some tools like pwd might still work. However the system is unusable after a crash because it's impossible to start basic programs or even login and I guess it won't work over the network either. I didn't try that but samba didn't work anymore.
Anyway I'm going to add kernel and Xorg logs. Maybe you'll find something interesting in there.
One Crash happened Nov 7. approx 13:00 that one is in the kern.log >> ****************************WARN_ONCE******************************* >> File radeon_tcl.c function radeon_run_tcl_render line 499 >> Rendering was 405 commands larger than predicted size. We might >> overflow command buffer. >> ******************************************************************** >> drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command >> stream. See dmesg for more info. >> > That one can only be investigated with matching kernel log, I think. I'm not sure but i think that was on Oct 13. (kern.log.3) Greetings, Andy
Attachment:
kern.log.1.gz
Description: GNU Zip compressed data
Attachment:
kern.log.2.gz
Description: GNU Zip compressed data
Attachment:
kern.log.3.gz
Description: GNU Zip compressed data
Attachment:
kern.log.4.gz
Description: GNU Zip compressed data
Attachment:
kern.log.gz
Description: GNU Zip compressed data
Attachment:
Xorg.0.log.gz
Description: GNU Zip compressed data
Attachment:
Xorg.0.log.old.gz
Description: GNU Zip compressed data