From: Raghavan.Anurag@in.bosch.com (Anurag Raghavan (RBEI/ETW11))
To: linux-arm-kernel@lists.infradead.org
Subject: ubi_io_read: error -74 (ECC error)
Date: Fri, 6 Jan 2017 10:07:29 +0000 [thread overview]
Message-ID: <38f0cfac3dbe4ea89da84c7fbf667833@SGPMBX1023.APAC.bosch.com> (raw)
Hi All,
My appdata partition could not be mounted or where the partition was not able to be used. Anyone can help me to find out the root cause of this. What are the possibilities of this ubifs corruption. Any patched are available to fix this issue.
I am using the kernel version-30.3.5
Any kernel patches are available to solve this issue...??
Error logs:
[ 1.797141] UBI error: ubi_io_read: error -74 (ECC error) while reading 253952 bytes from PEB 445:8192, read 253952 bytes
[ 1.808274] UBIFS error (pid 491): ubifs_scan: corrupt empty space at LEB 489:233760
[ 1.816037] UBIFS error (pid 491): ubifs_scanned_corruption: corruption at LEB 489:233760
[ 1.828660] UBIFS error (pid 491): ubifs_scan: LEB 489 scanning failed
[ 1.835215] UBIFS warning (pid 491): ubifs_ro_mode: switched to read-only mode, error -117
[ 1.843502] UBIFS error (pid 491): make_reservation: cannot reserve 58 bytes in jhead 2, error -117
[ 1.852569] UBIFS error (pid 491): do_writepage: cannot write page 0 of inode 76584, error -117
dpkg: error: unable to sync new file '/var/lib/dpkg/arch-new': Structure needs cleaning
Best regards
Raghavan Anurag
RBEI/ETW1
Tel. +91(422)667-4001 | Mobil 9986968950
next reply other threads:[~2017-01-06 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 10:07 Anurag Raghavan (RBEI/ETW11) [this message]
2017-01-06 11:30 ` ubi_io_read: error -74 (ECC error) Boris Brezillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38f0cfac3dbe4ea89da84c7fbf667833@SGPMBX1023.APAC.bosch.com \
--to=raghavan.anurag@in.bosch.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox