ubiattach fails after mkvol with "vtbl_check: bad CRC..."

[Artem Bityutskiy]

On Tue, 2012-05-01 at 10:39 -0400, Shawn J. Goff wrote:
> Sorry if this is a double-post; I haven't seen a bounce-back, but I also
> didn't see it go on the list.
> 
> I am having trouble attaching an ubi device after creating a volume on
> it. My procedure is as follows (a full console log is at the end of
> this e-mail):
> 
> ubiformat /dev/mtd6
> ubiattach -m 6
> ubimkvol /dev/ubi0 -N root0 -s 11MiB
> ubidetach -m 6
> ubiattach -m 6
> 
> When I try to re-attach, the UBI module produces messages:
> 
> [ 2558.700000] UBI error: vtbl_check: bad CRC at record 0: 0x2863aedc,
> not 0xcd06c54d
> [ 2558.710000] UBI error: vtbl_check: bad CRC at record 0: 0x2863aedc,
> not 0xcd06c54d
> [ 2558.717500] UBI error: process_lvol: both volume tables are corrupted
> [ 2558.725000] UBI error: ubi_attach_mtd_dev: failed to attach by
> scanning, error -22
> 
> If I don't make a volume, but just format the mtd device, then I can
> attach and detach just fine; it's only after making a volume that it
> gives this problem. I've tried making the volume both static and
> dynamic, and I've tried writing a filesystem with ubiupdatevol; it
> always has this issue. The mtd device itself works fine. I can write
> and read data from it, I can run mtd_speedtest and mtd_stresstest with
> no problems.

Try to enable UBI I/O checks - they are in debugfs - chk_io file, write
1 there to enable the checks.

The http://www.linux-mtd.infradead.org/faq/ubi.html#L_how_debug section
is out-of-date :-(

-- 
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20120503/40af3340/attachment.sig>