public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: DATACOM - Nedel <nedel@datacom-telematica.com.br>
To: linux-mtd@lists.infradead.org
Subject: Volume write-protected
Date: Wed, 08 Apr 2009 13:58:49 -0300	[thread overview]
Message-ID: <49DCD7C9.2050802@datacom-telematica.com.br> (raw)

Hi,

I've created a image with mkfs.ubifs and ubinize commands, as follow:

mkfs.ubifs -r ramdisk -m 2048 -c 8190 -e 126KiB -o image.temp
ubinize -o $(BUILT)/images/image.ubifs -m 2048 -p 128KiB -s 512 ubinize.cfg

ubinize.cfg content:
[ubifs]
mode=ubi
image=PD1200.temp
vol_id=0
vol_size=900MiB
vol_type=dynamic
vol_name=ubipart
vol_alignment=1
vol_flags=autoresize

After I flash the ubi image, with nand write u-boot command, I've tried 
to mount it:

# mount -t ubifs ubi0!ubipart /mnt/flash/
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
8188:512, written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
8191:512, written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
8190:512, written 0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 
8189:512, written 0 bytes
UBI error: ubi_io_write: read-only mode
UBI error: erase_worker: failed to erase PEB 8188, error -30
UBI error: do_work: work failed with error code -30
UBI error: ubi_thread: ubi_bgt0d: work failed with error code -30
UBIFS error (pid 6550): ubifs_write_node: cannot write 2048 bytes to LEB 
1:2048, error -30
mount: ubi0!ubipart is write-protected, mounting read-only

I can't find where this write-protected flag is set.
Sorry but when I try to run my kernel image with ubifs debug it hangs 
before u-boot initialization.

Thanks in advance,

-- 
Werner Maurício NEDEL

             reply	other threads:[~2009-04-08 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 16:58 DATACOM - Nedel [this message]
2009-04-09  6:09 ` Volume write-protected 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=49DCD7C9.2050802@datacom-telematica.com.br \
    --to=nedel@datacom-telematica.com.br \
    --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