2008-05-01 18:35:43     e2fsck Question

Document created by Aaronwu Employee on Aug 6, 2013
Version 1Show Document
  • View in full screen mode

2008-05-01 18:35:43     e2fsck Question

David Kasper (UNITED STATES)

Message: 55355   

 

I have a compact FLASH with a single EXT2 partition that has a corruption.  However, when I try to fix it by typing "e2fsck -p /dev/hda1" the command fails and I get the following output.  Does anybody have any suggestions?  Note I am using the 2007 R1.1-RC3 kernel.

 

e2fsck -p      /dev/hda1

e2fsck 1.25 (20-Sep-2001)

/dev/hda1 was not cleanly unmounted, check forced.

PasUndefined instruction

blocks, and sizes

 

- May be used to emulate instructions that are not defined for

a particular processor implementation.

 

CURRENT PROCESS:

 

COMM=e2fsck PID=83

TEXT = 0x00fc0040-0x00fdbc80  DATA = 0x00fdbc84-0x00fe4744

BSS = 0x00fe4744-0x00fe4bb4   USER-STACK = 0x00ffff70

 

return address: 0x00ffff04; contents of [PC-16...PC+8]:

ffff ffff 0000 0000 0000 0000 0000 0000

0000 0000 6004 0038 f840 00fd 623c 0038 X

ff34 00ff 8b1c 00fd 0000 0000 ff74 00ff

 

RETE:  00000000  RETN: 031c8000  RETX: 00ffff04  RETS: 00ffff04

IPEND: 0030  SYSCFG: 0036

SEQSTAT: 00060021    SP: 031c7f24

R0: 00000001    R1: 00000011    R2: 00003004    R3: 00000ffc

R4: 00ffff00    R5: 00000001    R6: 00000000    R7: 0033581c

P0: 00fe4460    P1: 00386004    P2: 00fe4b1c    P3: 00386004

P4: 0038623c    P5: 00fc112e    FP: 00ffff04

A0.w: 00000000    A0.x: 00000000    A1.w: 00000000    A1.x: 00000000

LB0: 00fd6a69  LT0: 00fd6a66  LC0: 00000000

LB1: 00fcf815  LT1: 00fcf814  LC1: 00000000

B0: 00000000  L0: 00000000  M0: 00000000  I0: 034bb004

B1: 00000000  L1: 00000000  M1: 00000000  I1: 00000000

B2: 00000000  L2: 00000000  M2: 00000000  I2: 0000000a

B3: 00000000  L3: 00000000  M3: 00000000  I3: 00000000

 

USP: 00fffdbc   ASTAT: 02002000

DCPLB_FAULT_ADDR=00386014

ICPLB_FAULT_ADDR=00ffff04

 

 

Hardware Trace:

0 Target : <0x0000455c> { _trap_c + 0x0 }

   Source : <0xffa00c48> { _exception_to_level5 + 0xb4 }

1 Target : <0xffa00b94> { _exception_to_level5 + 0x0 }

   Source : <0xffa00b92> { _ex_trap_c + 0x4e }

2 Target : <0xffa00b44> { _ex_trap_c + 0x0 }

   Source : <0xffa00ce8> { _trap + 0x28 }

3 Target : <0xffa00cc0> { _trap + 0x0 }

   Source : <0x00fc1554> [ e2fsck + 0x1514 ]

4 Target : <0x00fc1542> [ e2fsck + 0x1502 ]

   Source : <0x00fd8c48> [ e2fsck + 0x18c08 ]

5 Target : <0x00fd8c48> [ e2fsck + 0x18c08 ]

   Source : <0x00fd8c44> [ e2fsck + 0x18c04 ]

6 Target : <0x00fd8b84> [ e2fsck + 0x18b44 ]

   Source : <0x00fd436c> [ e2fsck + 0x1432c ]

7 Target : <0x00fd4362> [ e2fsck + 0x14322 ]

   Source : <0x00fd4350> [ e2fsck + 0x14310 ]

8 Target : <0x00fd4340> [ e2fsck + 0x14300 ]

   Source : <0x00fc9682> [ e2fsck + 0x9642 ]

9 Target : <0x00fc9672> [ e2fsck + 0x9632 ]

   Source : <0x00fc968e> [ e2fsck + 0x964e ]

10 Target : <0x00fc968e> [ e2fsck + 0x964e ]

   Source : <0x00fd1cf6> [ e2fsck + 0x11cb6 ]

11 Target : <0x00fd1cee> [ e2fsck + 0x11cae ]

   Source : <0x00fd423e> [ e2fsck + 0x141fe ]

12 Target : <0x00fd4236> [ e2fsck + 0x141f6 ]

   Source : <0x00fd4228> [ e2fsck + 0x141e8 ]

13 Target : <0x00fd4220> [ e2fsck + 0x141e0 ]

   Source : <0xffa0124e> { __common_int_entry + 0xd8 }

14 Target : <0xffa011ec> { __common_int_entry + 0x76 }

   Source : <0xffa0148c> { _evt_system_call + 0x64 }

15 Target : <0xffa0148c> { _evt_system_call + 0x64 }

   Source : <0xffa00e70> { _system_call + 0xb8 }

Stack from 031c7f04:

        00000000 ffa00c4c 00148710 00148710 0014870c 00000ffc 00ffff00 00fd4220

        00ffff04 00000030 00060021 00000000 031c8000 00ffff04 00ffff04 00ffff04

        00000001 02002000 00fcf815 00fd6a69 00fcf814 00fd6a66 00000000 00000000

        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

        00000000 0000000a 00000000 034bb004 00fffdbc 00ffff04 00fc112e 0038623c

Call Trace:

[<00003004>] _do_signal+0xf8/0xc8c

 

Error while scanning inodes (0): The inode is from a bad block in the inode table

Illegal instruction

root:~>

 

 

 

I also tried typing "fsck /dev/hda1" and got the following:

 

root:~> fsck  /dev/hda1 [J

fsck 1.25 (20-Sep-2001)

WARNING: couldn't open /etc/fstab: No such file or directory

e2fsck 1.25 (20-Sep-2001)

/dev/hda1 was not cleanly unmounted, check forced.

Pass 1: Checking inodes, blocks, and sizes

EUndefined instruction

- May be used to emulate instructions that are not defined for

a particular processor implementation.

 

CURRENT PROCESS:

 

COMM=fsck.ext2 PID=85

TEXT = 0x01fc0040-0x01fdbc80  DATA = 0x01fdbc84-0x01fe4744

BSS = 0x01fe4744-0x01fe4bb4   USER-STACK = 0x01ffff6c

 

return address: 0x01ffff00; contents of [PC-16...PC+8]:

ffff ffff 0000 0000 0000 0000 0000 0000

0000 0000 f004 0013 f840 01fd f23c 0013 X

ff30 01ff 8b1c 01fd 0000 0000 ff70 01ff

 

RETE:  00000000  RETN: 01f06000  RETX: 01ffff00  RETS: 01ffff00

IPEND: 0030  SYSCFG: 0036

SEQSTAT: 00060021    SP: 01f05f24

R0: 00000001    R1: 00000011    R2: 00003004    R3: 00001be8

R4: 01fffefc    R5: 00000001    R6: 00000000    R7: 031bec10

P0: 01fe4460    P1: 0013f004    P2: 01fe4b1c    P3: 0013f004

P4: 0013f23c    P5: 01fc112e    FP: 01ffff00

A0.w: 00000000    A0.x: 00000000    A1.w: 00000000    A1.x: 00000000

LB0: 01fd6a69  LT0: 01fd6a66  LC0: 00000000

LB1: 01fcf815  LT1: 01fcf814  LC1: 00000000

B0: 00000000  L0: 00000000  M0: 00000000  I0: 031c2418

B1: 00000000  L1: 00000000  M1: 00000000  I1: 00000000

B2: 00000000  L2: 00000000  M2: 00000000  I2: 0000000a

B3: 00000000  L3: 00000000  M3: 00000000  I3: 00000000

 

USP: 01fffdb8   ASTAT: 02002000

DCPLB_FAULT_ADDR=0013f23c

ICPLB_FAULT_ADDR=01ffff00

 

 

Hardware Trace:

0 Target : <0x0000455c> { _trap_c + 0x0 }

   Source : <0xffa00c48> { _exception_to_level5 + 0xb4 }

1 Target : <0xffa00b94> { _exception_to_level5 + 0x0 }

   Source : <0xffa00b92> { _ex_trap_c + 0x4e }

2 Target : <0xffa00b44> { _ex_trap_c + 0x0 }

   Source : <0xffa00ce8> { _trap + 0x28 }

3 Target : <0xffa00cc0> { _trap + 0x0 }

   Source : <0x01fc1554> [ fsck.ext2 + 0x1514 ]

4 Target : <0x01fc1542> [ fsck.ext2 + 0x1502 ]

   Source : <0x01fd8c48> [ fsck.ext2 + 0x18c08 ]

5 Target : <0x01fd8c48> [ fsck.ext2 + 0x18c08 ]

   Source : <0x01fd8c44> [ fsck.ext2 + 0x18c04 ]

6 Target : <0x01fd8b84> [ fsck.ext2 + 0x18b44 ]

   Source : <0x01fd436c> [ fsck.ext2 + 0x1432c ]

7 Target : <0x01fd4362> [ fsck.ext2 + 0x14322 ]

   Source : <0x01fd4350> [ fsck.ext2 + 0x14310 ]

8 Target : <0x01fd4340> [ fsck.ext2 + 0x14300 ]

   Source : <0x01fc9682> [ fsck.ext2 + 0x9642 ]

9 Target : <0x01fc9672> [ fsck.ext2 + 0x9632 ]

   Source : <0x01fc968e> [ fsck.ext2 + 0x964e ]

10 Target : <0x01fc968e> [ fsck.ext2 + 0x964e ]

   Source : <0x01fd1cf6> [ fsck.ext2 + 0x11cb6 ]

11 Target : <0x01fd1cee> [ fsck.ext2 + 0x11cae ]

   Source : <0x01fd423e> [ fsck.ext2 + 0x141fe ]

12 Target : <0x01fd4236> [ fsck.ext2 + 0x141f6 ]

   Source : <0x01fd4228> [ fsck.ext2 + 0x141e8 ]

13 Target : <0x01fd4220> [ fsck.ext2 + 0x141e0 ]

   Source : <0xffa0124e> { __common_int_entry + 0xd8 }

14 Target : <0xffa011ec> { __common_int_entry + 0x76 }

   Source : <0xffa0148c> { _evt_system_call + 0x64 }

15 Target : <0xffa0148c> { _evt_system_call + 0x64 }

   Source : <0xffa00e70> { _system_call + 0xb8 }

Stack from 01f05f04:

        00000000 ffa00c4c 00148714 00148714 0014870c 00001be8 01fffefc 01fd4220

        01ffff00 00000030 00060021 00000000 01f06000 01ffff00 01ffff00 01ffff00

        00000001 02002000 01fcf815 01fd6a69 01fcf814 01fd6a66 00000000 00000000

        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

        00000000 0000000a 00000000 031c2418 01fffdb8 01ffff00 01fc112e 0013f23c

Call Trace:

[<0013f004>] _tcp_init+0x44/0x27c

[<0013f004>] _tcp_init+0x44/0x27c

[<00001be8>] _dump_thread+0x78/0x104

[<00003004>] _do_signal+0xf8/0xc8c

 

inodes (0): The inode is from a bad block in the inode table

Warning... fsck.ext2 for device /dev/hda1 exited with signal 4.

root:~>

 

 

 

Thanks for any suggestions,

 

David Kasper

QuoteReplyEditDelete

 

 

2008-05-01 18:48:55     Re: e2fsck Question

Mike Frysinger (UNITED STATES)

Message: 55356   

 

make sure e2fsck isnt overflowing its stack

QuoteReplyEditDelete

 

 

2008-05-01 19:14:19     Re: e2fsck Question

David Kasper (UNITED STATES)

Message: 55357   

 

Mike,

 

Thanks for your response.  But how do I determine if that is happening?

 

Dave

QuoteReplyEditDelete

 

 

2008-05-01 19:19:22     Re: e2fsck Question

Mike Frysinger (UNITED STATES)

Message: 55358   

 

http://docs.blackfin.uclinux.org/doku.php?id=debuging_applications#stack_checking

Attachments

    Outcomes