UBIFS Corrupt during power failure

[Artem Bityutskiy]

On Tue, 2009-03-24 at 11:04 -0600, Eric Holmberg wrote:
> Hi Adrian,
> 
> > Please enable UBIFS debugging and set the UBIFS Default message level
> to 3.
> 
> Thanks for the response.  Enabling UBIFS debugging and setting to level
> 3 only provides slightly more information.  
> 
> [42949375.480000] UBIFS: recovery needed
> [42949376.450000] UBIFS error (pid 1): ubifs_scan: corrupt empty space
> at LEB 4:44512
> [42949376.460000] UBIFS error (pid 1): ubifs_scanned_corruption:
> corrupted data at LEB 4:44512
> [42949376.470000] UBIFS error (pid 1): ubifs_scanned_corruption: first
> 4096 bytes from LEB 4:44512
> [42949376.490000] UBIFS error (pid 1): ubifs_scan: LEB 4 scanning failed
> [42949376.540000] UBIFS error (pid 1): ubifs_recover_leb: corrupt empty
> space at LEB 4:480
> [42949376.550000] UBIFS error (pid 1): ubifs_scanned_corruption:
> corrupted data at LEB 4:480
> [42949376.560000] UBIFS error (pid 1): ubifs_scanned_corruption: first
> 4096 bytes from LEB 4:480
> [42949376.580000] UBIFS error (pid 1): ubifs_recover_leb: LEB 4 scanning
> failed
> [42949376.600000] VFS: Cannot open root device "ubi0:rootfs" or
> unknown-block(0,0)

There should be more, they are probably just not printed to the console.
Try typing dmesg or booting with "ignore_loglevel" option in the kernel
command line. For more information, please read the "Debugging messages"
here:

http://www.linux-mtd.infradead.org/faq/ubi.html#L_how_debug

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