Re: cannot ubiupdatevol squashfs image

[David Oberhollenzer <david.oberhollenzer@xxxxxxxxxxxxx>]

On 9/19/19 1:54 PM, Boris Stein wrote:
> Hi,
> below are errors of unsquashfs for ubiblock.
> 
>From your logs you seem to be getting the same errors as for mounting
the image.

> Is there anything else that can help debug this?
> 

Browsing through the last mail, saw that you generate the image with
the -noI option, which means that inodes are uncompressed. So they
could in theory be corrupted but still partially readable, leading to
accessing the data area at off locations or trying to access non existent
fragments.

Can you try it without the -noI option? If the meta data gets corrupted,
you should get an error about that before the kernel tries to access the


Could you try out the following, to check if UBI causes the damages to
your SquashFS image:

 - Create a fresh SquashFS image
 - Verify that you can also unpack the original image again without errors
 - Write it to ubiblock
 - Dump it back from the ubiblock
 - Check again on the dumped image
 - compare checksums of the original and the dumped image


Again, there are a bunch of non-standard messages in your kernel boot log.
Do you use any 3rd party out-of tree modules that could potentially be
interfering?


Regards,

David

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/