HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: machine crash
Operating System - Linux
1828355
Members
3049
Online
109976
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2004 09:05 PM
09-07-2004 09:05 PM
machine crash
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
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:[
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
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2004 10:44 PM
09-07-2004 10:44 PM
Re: machine crash
What is your HW/SW configuration?
I suggest to boot from Linux rescue disk and fsck all partitions.
I suggest to boot from Linux rescue disk and fsck all partitions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2004 03:35 AM
10-14-2004 03:35 AM
Re: machine crash
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!
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2004 05:28 AM
10-14-2004 05:28 AM
Re: machine crash
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
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP