All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Rickard X Andersson <Rickard.Andersson@axis.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	 Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: SV: ubi2 error: scan_pool: unable to read EC header! PEB:569 err:1
Date: Fri, 14 Jan 2022 19:49:39 +0100 (CET)	[thread overview]
Message-ID: <568190792.260787.1642186179042.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <d1e8b25b76df4e7aa428a411bceabdb3@axis.com>

----- Ursprüngliche Mail -----
> Von: "Rickard X Andersson" <Rickard.Andersson@axis.com>
> An: "richard" <richard@nod.at>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>, "Artem Bityutskiy" <dedekind1@gmail.com>
> Gesendet: Mittwoch, 12. Januar 2022 17:25:57
> Betreff: SV: ubi2 error: scan_pool: unable to read EC header! PEB:569 err:1

> Thanks for the quick answer!
> 
> Too me it looks like fastmap is happy and everything is working well, see log
> below.
> 
> <3>[    8.017720][  T306] ubi2 error: scan_pool: unable to read EC header!
> PEB:569 err:1
> <3>[    8.017900][  T306] ubi2 error: ubi_scan_fastmap: Attach by fastmap
> failed, doing a full scan!
> <5>[   10.456601][  T306] ubi2: scanning is finished
> <5>[   10.477819][  T306] ubi2: attached mtd5 (name "data", size 512 MiB)
> <5>[   10.477980][  T306] ubi2: PEB size: 131072 bytes (128 KiB), LEB size:
> 126976 bytes
> <5>[   10.478064][  T306] ubi2: min./max. I/O unit sizes: 2048/2048, sub-page
> size 2048
> <5>[   10.478147][  T306] ubi2: VID header offset: 2048 (aligned 2048), data
> offset: 4096
> <5>[   10.478292][  T306] ubi2: good PEBs: 4092, bad PEBs: 4, corrupted PEBs: 0
> <5>[   10.478376][  T306] ubi2: user volume: 1, internal volumes: 1, max.
> volumes count: 128
> <5>[   10.478524][  T306] ubi2: max/mean erase counter: 9666/740, WL threshold:
> 4096, image sequence number: 581957443
> <5>[   10.478668][  T306] ubi2: available PEBs: 0, total reserved PEBs: 4092,
> PEBs reserved for bad PEB handling: 76
> <5>[   10.478825][  T337] ubi2: background thread "ubi_bgt2d" started, PID 337
> <5>[   10.482212][   T16] ubi2: Starting ubi_update_fastmap
> <5>[   10.522300][   T16] ubi2: Finished ubi_update_fastmap
> 
> I do not think the interruption was by a power-cut, but I am not sure. Do you
> think the interruption could be caused by a linux reboot using the
> reboot/restart command?

If you interrupt UBI by software, you can face the same situation too.
I guess you don't run ubidetach upon reboot?

Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      parent reply	other threads:[~2022-01-14 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 13:20 ubi2 error: ubi_refill_pools: no free eraseblocks Rickard X Andersson
2020-05-28  6:59 ` Richard Weinberger
     [not found] ` <0ce6e992f6f24238bcb599f84aef243d@axis.com>
2022-01-12 11:21   ` ubi2 error: scan_pool: unable to read EC header! PEB:569 err:1 Richard Weinberger
     [not found]     ` <d1e8b25b76df4e7aa428a411bceabdb3@axis.com>
2022-01-14 18:49       ` Richard Weinberger [this message]

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=568190792.260787.1642186179042.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=Rickard.Andersson@axis.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.