topic Re: machine crash in Operating System - Linux

machine crash

Chakravarthi — Wed, 08 Sep 2004 04:05:36 GMT

Hi

Linux Server as soon as it boots gives the following error on console and hangs,

login: Assertion failure in __journal_remove_journal_head() at journal.
c:1771: "buffer_jbd(bh)"
kernel BUG at journal.c:1771!
invalid operand: 0000
CPU: 0
EIP: 0010:[] Tainted: P
EFLAGS: 00010286
eax: 0000005c ebx: f7417ca0 ecx: f715c000 edx: 00000001
esi: f64a9540 edi: f7417ca0 ebp: f64e7e5c esp: f64e7e40
ds: 0018 es: 0018 ss: 0018
Process kjournald (pid: 2680, stackpage=f64e7000)
Stack: c02e04c0 c02e0d27 c02e0491 000006eb c02e0d57 f64a9540 98393bc0 f64e7e6c
c01702cc f64a9540 f64a9540 f64e7fb8 c016c470 f7417ca0 f663a000 f64e6000
f663a050 f7417ca0 00000001 f64e6000 f663a094 00000000 00000fd4 f629002c
Call Trace: [] [] [] [] []
[]

Code: 0f 0b eb 06 91 04 2e c0 83 c4 14 90 39 33 74 2c 68 66 0d 2e

any idea why this is happening??

thanks
chakri

Re: machine crash

Vitaly Karasik_1 — Wed, 08 Sep 2004 05:44:41 GMT

What is your HW/SW configuration?

I suggest to boot from Linux rescue disk and fsck all partitions.

Re: machine crash

Ortwin Ebhardt — Thu, 14 Oct 2004 10:35:00 GMT

Hello,
I think you've got a problem with a sever damaged journal; so the advise with the rescue disc should work and solve it.

If the computer crashes while testing the journal, this mostly implies a hardware-related problem.

If you're not using reiserfs but ext3, you can try to start from the rescue-cd and change your /etc/fstab. With ext2 instead of ext3 the journal-check is "deactivated". (In fact is ext3 extremly similar to ext2, but has an aditional journal, so mostly this works.)

If this should work, there is something extremly damaged on your harddisk (namely some sectors holding the journal). So this workaround is just to save some data, not a real solution!

Re: machine crash

HGN — Thu, 14 Oct 2004 12:28:28 GMT

Hi

This looks like something happened to the OS, you can boot with the rescue cd and repair the OS filesystem. Hope this should take care of the problem. What caused the issue also needs to be investigated & fixed so that this will not happen another time, maybe some ahrdware caused the server to panic or some software application running on the server which also needs to be looked at.

Rgds

Gopi