public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Kaius Häggblom" <kaius@oliotalo.fi>
To: linux-mtd@lists.infradead.org
Subject: Re: Problem to attach NAND MTD-device to UBI
Date: Fri, 22 May 2009 16:11:07 +0300	[thread overview]
Message-ID: <4A16A46B.8030302@oliotalo.fi> (raw)
In-Reply-To: <4A169E16.6010305@oliotalo.fi>

If I use ubiformat with parameter -s512 I get the device attached, but 
still ubimkvol
fails:

/ # ./ubiformat /dev/mtd4 -s512
ubiformat: mtd4 (NAND), size 134217728 bytes (128\x030 MiB), 131072 
eraseblocks of 131072 bytes (128\x030 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 1023 -- 100 % complete 
ubiformat: 1021 eraseblocks are supposedly empty
ubiformat: bad eraseblocks: 29, 912, 991
ubiformat: formatting eraseblock 1023 -- 100 % complete 
/ # ubiattach /dev/ubi_ctrl -m4     
UBI: attaching mtd4 to ubi0
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: attached mtd4 to ubi0
UBI: MTD device name:            "NAND_Flash 1"
UBI: MTD device size:            128 MiB
UBI: number of good PEBs:        1021
UBI: number of bad PEBs:         3
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             1007
UBI: total number of reserved PEBs: 14
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 0/0
UBI: background thread "ubi_bgt0d" started, PID 497
UBI device number 0, total 1021 LEBs (131733504 bytes, 125\x036 MiB), 
available 1007 LEBs (129927168 bytes, 123\x039 MiB), LEB size 129024 
bytes (126\x030 KiB)

/ # ubimkvol /dev/ubi0 -m -N "TEST"
Set volume size to 129927168
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
1023:512, written 0 bytes
UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 
2147479551:0, PEB 1023
UBI: try another PEB
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
1022:512, written 0 bytes
UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 
2147479551:0, PEB 1022
UBI: try another PEB
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
1021:512, written 0 bytes
UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 
2147479551:0, PEB 1021
UBI: try another PEB
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
1020:512, written 0 bytes
UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 
2147479551:0, PEB 1020
UBI warning: ubi_ro_mode: switch to read-only mode
UBI error: ubi_io_write: read-only mode
UBI error: erase_worker: failed to erase PEB 0, error -30
UBI error: do_work: work failed with error code -30
UBI error: ubi_thread: ubi_bgt0d: work failed with error code -30
UBI error: ubi_create_volume: cannot create volume 0, error -30
ubimkvol error: cannot UBI create volume
error 30 (Read-only file system)

r,
kaius

  reply	other threads:[~2009-05-22 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 12:44 Problem to attach NAND MTD-device to UBI Kaius Häggblom
2009-05-22 13:11 ` Kaius Häggblom [this message]
2009-05-22 13:24   ` 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=4A16A46B.8030302@oliotalo.fi \
    --to=kaius@oliotalo.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox