Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ext3-fs error
Hello,
Since Saturday, the FG200B started to throw the following error:
EXT3-fs error (device sd(8,3)): ext3_readdir: bad entry in directory #456066: rec_len % 4 != 0 - offset=0, inode=13, rec_len=35, name_len=231
EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 1321618933, count = 1
And similar lines with diferent block numbers.
after that..
Assertion failure in journal_forget() at transaction.c:1257: " !jh->b_committed_d ata"
kernel BUG at transaction.c:1257!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0175441>] Not tainted
EFLAGS: 00210282
eax: 00000058 ebx: f5ee2540 ecx: 00000001 edx: 00000001
esi: c1bea3d0 edi: f7f1aa54 ebp: f7f1a9e0 esp: f6da5cfc
ds: 0018 es: 0018 ss: 0018
Process initXXXXXXXXXXX (pid: 69, stackpage=f6da5000)
Modules:
f8977000 f8977060 ftk
Stack: c02f0348 c02c3024 c02ee1dd 000004e9 c02ee2dc c1703f60 f5ee2540 f7f1a9e0
f5ee2540 f7030ea0 c01790dc f7030ea0 f5ee2540 00000000 00000001 f7f1a9e0
00010000 f6c73e20 f7030ea0 f6c73e20 c016a1ff f7030ea0 00010000 f5ee2540
Call Trace: [<c01790dc>] [<c016a1ff>] [<c014e8a4>] [<c016c7d3>] [<c0174a93>]
[<c016c997>] [<c016ccad>] [<c013b9c7>] [<c016cb00>] [<c016a39c>] [<c016d12c>]
[<c0173f09>] [<c01755d8>] [<c016a39c>] [<c016a410>] [<c016a530>] [<c016a410>]
[<c01500d7>] [<c014d4b2>] [<c0146079>] [<c0139288>] [<c0108d8f>]
Code: 0f 0b e9 04 dd e1 2e c0 e9 15 ff ff ff 89 f6 8b 44 24 04 8b
Can u help me?
I Formated the boot device, reload the firmware, but the problems continues.
Best regards, Federico.
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The FortiGate typically comes with 3 partitions. say 1,2,3. The 1 and 2 are used to store FortiOS. At any time only one of 1 or 2 is active but not both. 3 is always active. The Ext3 error shows the partition file system corrupted. However, if it is a problem on the partition 3, formatting booting device would not help.
You can format this partition in CLI with command ' exec disk format' . It will remove all logs stored on disk.
You may want to try burn the image to another image partition and boot from it. In FortiOS v4, you are able to select the non-active partition, and then upload and boot. In FortiOS v5, a upgrading from GUI will boot you into another partition.
li hou
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the CLI command (from Console window) is
exec formatlogdisk.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
