AnsweredAssumed Answered

SATA corruption

Question asked by karan bhagoji on Apr 20, 2016
Latest reply on Aug 8, 2016 by karan bhagoji

Hello all,

We have custom boards with imx6 quad processor with android jelly bean running on 3.0.35 kernel with SATA boot , size 30 gb .  After using the board for some time we are getting a SATA corruption messages, the errors are different for different boards, like eg

1->

EXT4-fs error (device sda4): ext4_lookup:1044: inode #22: comm er.ServerThread: deleted inode referenced: 69

Aborting journal on device sda4-8.

Kernel panic - not syncing: EXT4-fs (device sda4): panic forced after error

CPU0: stopping

[<c0131f84>] (unwind_backtrace+0x0/0x138) from [<c01243a8>] (do_IPI+0x1d4/0x208)

2->

ata1.00: exception Emask 0x1 SAct 0x1f SErr 0x0 action 0x6 frozen

ata1.00: irq_stat 0x40000000

ata1.00: cmd 60/08:00:00:90:84/00:00:02:00:00/40 tag 0 ncq 4096 in

         res 40/00:18:60:e5:80/00:00:02:00:00/40 Emask 0x1 (device error)

3->

DVFS driver module loaded

rtc-m41t80 0-0068: setting system clock to 2055-09-11 10:21:10 UTC (2704270870)

Freeing init memory: 1136K

4->

binder: 4716:4716 transaction failed 29189, size 80-4

binder: 4716:4716 transaction failed 29189, size 212-4

 

We getting stuck in this error. Due to these errors the displays hangs at splash screen with no android UI prompt .All the errors indicate that the SATA cards are getting corrupted. Is there any error with the JB android /  kernel/ anything  which is causing this corruption?

Kindly advice , also suggest solutions if any.

 

Regards,

Karan

Outcomes