Re: Volume write-protected

[Artem Bityutskiy <dedekind@infradead.org>]

On Wed, 2009-04-08 at 13:58 -0300, DATACOM - Nedel wrote:
> # 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

-5 is EIO, Input/output error. UBI tries to write 512 bytes, which is
one subpage, to offset 512 (i.e., it writes the second subpage). And
the MTD layer returns 512. So the issue is somewhere below UBI.

Possibly, your flash does not support sub-pages, but it declares that
it does. You should look at your MTD driver. The other possibility is
to force UBI not to use subpages.

> 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

UBI attaches the volume in R/O mode, because of the write error.
UBI tries to be nice to you, and instead of totally refusing the
MTD device, it attaches it R/O.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)