All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cal Page <pagcal@runbox.com>
To: linux-mtd@lists.infradead.org
Subject: ubiattach fails with bad VID header offset 2048, expected 512 ???
Date: Thu, 11 Dec 2008 08:41:30 -0500	[thread overview]
Message-ID: <4941188A.30303@runbox.com> (raw)

ubiattach fails with bad VID header offset 2048, expected 512 ???

The is the first thing out of the box. It reads block 0 to get the 
ubi_ec_hdr then parses it.

Our system reads/writes 2048 byte blocks with only 32 bytes available in 
the oob area per block.

For my system, is vid_hdr_offset supposed to be 2048, ie point into the 
oob area?

How do I get it working?

Thanks,
Cal Page

here's the log

UBI DBG (pid 2785): ctrl_cdev_ioctl: attach MTD device
UBI: attaching mtd12 to ubi0
UBI DBG (pid 2785): io_init: min_io_size      2048
UBI DBG (pid 2785): io_init: hdrs_min_io_size 512
UBI DBG (pid 2785): io_init: ec_hdr_alsize    512
UBI DBG (pid 2785): io_init: vid_hdr_alsize   512
UBI DBG (pid 2785): io_init: vid_hdr_offset   512
UBI DBG (pid 2785): io_init: vid_hdr_aloffset 512
UBI DBG (pid 2785): io_init: vid_hdr_shift    0
UBI DBG (pid 2785): io_init: leb_start        2048
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI DBG (pid 2785): ubi_scan: process PEB 0
UBI DBG (pid 2785): ubi_io_read_ec_hdr: read EC header from PEB 0
UBI DBG (pid 2785): ubi_io_read: read 64 bytes from PEB 0:0
UBI DBG (pid 2785): ubi_io_read: read: addr = 0, len = 64, 
ubi->mtd->read = 0xc0
cfe16c
UBI error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
Erase counter header dump:
        magic          0x55424923
        version        1
        ec             1
        vid_hdr_offset 2048
        data_offset    4096
        hdr_crc        0x7f585319
erase counter header hexdump:
00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 01 00 00 08 00 00 
00 10 0
0 00 00 00 00 00 00 00 00  UBI#............................
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 0
0 00 00 00 00 7f 58 53 19  .............................XS.
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_attach_mtd_dev: failed to attach by scanning, error -22

             reply	other threads:[~2008-12-11 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 13:41 Cal Page [this message]
2008-12-11 19:28 ` ubiattach fails with bad VID header offset 2048, expected 512 ??? Artem Bityutskiy

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=4941188A.30303@runbox.com \
    --to=pagcal@runbox.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.