From: Pintu Agarwal <pintu.ping@gmail.com> To: phillip@squashfs.org.uk Cc: open list <linux-kernel@vger.kernel.org>, sean@geanix.com, linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org Subject: Re: [RESEND]: Kernel 4.14: SQUASHFS error: unable to read xattr id index table Date: Mon, 17 May 2021 17:04:57 +0530 [thread overview] Message-ID: <CAOuPNLhn90z9i6jt0-Vv4e9hjsxwYUT2Su-7SQrxy+N=HDe_xA@mail.gmail.com> (raw) In-Reply-To: <1762403920.6716767.1621029029246@webmail.123-reg.co.uk> On Sat, 15 May 2021 at 03:21, Phillip Lougher <phillip@squashfs.org.uk> wrote: > > Your kernel (4.14.170) was released on 5 Feb 2020, and so it won't > contain any of the above commits. The xattr -id code in 4.14.170, > was last updated in May 2011, and so it is much more likely the > problem is elsewhere. > Okay this seems to be UBI volume flashing issue then. I will also try with non-squashfs image (just ubifs). See the result in the end. > The xattr id index table is written to the end of the Squashfs filesystem, > and it is the first table read on mounting. > Okay this gives me a clue that there are some corruptions while writing the leftover blocks in the end. > 1. Check the Squashfs filesystem for correctness before writing it to > the flash. You can run Unsquashfs on the image and see if it reports > any errors. > Can you give me some pointers on how to use unsquashfs ? I could not find any unsquashfs command on my device. Do we need to do it on the device or my Ubuntu PC ? Are there some commands/utility available on ubuntu ? > 2. You need to check the filesystem for integrity after writing it to > the flash. Compute a checksum, and compare it with the original > checksum. > Can you also guide me with an example, how to do this as well ? BTW, I also tried "rootfs" volume flashing using "ubifs" image (non squashfs). Here are the results. a) With ubifs image also, the device is not booting after flashing the volume. b) But I can see that the "rootfs" volume could be mounted, but later gives some other errors during read_node. These are the boot up errors logs: {{{ [ 4.600001] vreg_conn_pa: dis▒[ 4.712458] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode [ 4.712520] UBIFS (ubi0:0): LEB size: 253952 bytes (248 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes [ 4.719823] UBIFS (ubi0:0): FS size: 113008640 bytes (107 MiB, 445 LEBs), journal size 9404416 bytes (8 MiB, 38 LEBs) [ 4.729867] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB) [ 4.740400] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID xxxxxxxxx-xxxxxxxxxx, small LPT model [ 4.748587] VFS: Mounted root (ubifs filesystem) readonly on device 0:16. [ 4.759033] devtmpfs: mounted [ 4.766803] Freeing unused kernel memory: 2048K [ 4.805035] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node type (255 but expected 9) [ 4.805097] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node at LEB 336:250560, LEB mapping status 1 [ 4.812401] Not a node, first 24 bytes: [ 4.812413] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................ }}} Seems like there is some corruption in the first 24 bytes ?? Thanks, Pintu
WARNING: multiple messages have this Message-ID (diff)
From: Pintu Agarwal <pintu.ping@gmail.com> To: phillip@squashfs.org.uk Cc: open list <linux-kernel@vger.kernel.org>, sean@geanix.com, linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org Subject: Re: [RESEND]: Kernel 4.14: SQUASHFS error: unable to read xattr id index table Date: Mon, 17 May 2021 17:04:57 +0530 [thread overview] Message-ID: <CAOuPNLhn90z9i6jt0-Vv4e9hjsxwYUT2Su-7SQrxy+N=HDe_xA@mail.gmail.com> (raw) In-Reply-To: <1762403920.6716767.1621029029246@webmail.123-reg.co.uk> On Sat, 15 May 2021 at 03:21, Phillip Lougher <phillip@squashfs.org.uk> wrote: > > Your kernel (4.14.170) was released on 5 Feb 2020, and so it won't > contain any of the above commits. The xattr -id code in 4.14.170, > was last updated in May 2011, and so it is much more likely the > problem is elsewhere. > Okay this seems to be UBI volume flashing issue then. I will also try with non-squashfs image (just ubifs). See the result in the end. > The xattr id index table is written to the end of the Squashfs filesystem, > and it is the first table read on mounting. > Okay this gives me a clue that there are some corruptions while writing the leftover blocks in the end. > 1. Check the Squashfs filesystem for correctness before writing it to > the flash. You can run Unsquashfs on the image and see if it reports > any errors. > Can you give me some pointers on how to use unsquashfs ? I could not find any unsquashfs command on my device. Do we need to do it on the device or my Ubuntu PC ? Are there some commands/utility available on ubuntu ? > 2. You need to check the filesystem for integrity after writing it to > the flash. Compute a checksum, and compare it with the original > checksum. > Can you also guide me with an example, how to do this as well ? BTW, I also tried "rootfs" volume flashing using "ubifs" image (non squashfs). Here are the results. a) With ubifs image also, the device is not booting after flashing the volume. b) But I can see that the "rootfs" volume could be mounted, but later gives some other errors during read_node. These are the boot up errors logs: {{{ [ 4.600001] vreg_conn_pa: dis▒[ 4.712458] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode [ 4.712520] UBIFS (ubi0:0): LEB size: 253952 bytes (248 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes [ 4.719823] UBIFS (ubi0:0): FS size: 113008640 bytes (107 MiB, 445 LEBs), journal size 9404416 bytes (8 MiB, 38 LEBs) [ 4.729867] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB) [ 4.740400] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID xxxxxxxxx-xxxxxxxxxx, small LPT model [ 4.748587] VFS: Mounted root (ubifs filesystem) readonly on device 0:16. [ 4.759033] devtmpfs: mounted [ 4.766803] Freeing unused kernel memory: 2048K [ 4.805035] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node type (255 but expected 9) [ 4.805097] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node at LEB 336:250560, LEB mapping status 1 [ 4.812401] Not a node, first 24 bytes: [ 4.812413] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................ }}} Seems like there is some corruption in the first 24 bytes ?? Thanks, Pintu ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-05-17 11:35 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAOuPNLjgpkBh9dnfNTdDcfk5HiL=HjjiB9o_=fjrm+0vP7Re2Q@mail.gmail.com> 2021-05-14 11:41 ` Kernel 4.14: SQUASHFS error: unable to read xattr id index table Pintu Agarwal 2021-05-14 11:41 ` Pintu Agarwal 2021-05-14 12:37 ` [RESEND]: " Pintu Agarwal 2021-05-14 21:50 ` Phillip Lougher 2021-05-14 21:50 ` Phillip Lougher 2021-05-17 11:34 ` Pintu Agarwal [this message] 2021-05-17 11:34 ` Pintu Agarwal 2021-05-20 4:30 ` Phillip Lougher 2021-05-20 4:30 ` Phillip Lougher 2021-05-23 16:44 ` [RESEND]: Kernel 4.14: UBIFS+SQUASHFS: Device fails to boot after flashing rootfs volume Pintu Agarwal 2021-05-23 16:44 ` Pintu Agarwal 2021-05-23 17:31 ` Sean Nyekjaer 2021-05-23 17:31 ` Sean Nyekjaer 2021-05-24 6:12 ` Pintu Agarwal 2021-05-24 6:12 ` Pintu Agarwal 2021-05-24 7:07 ` Phillip Lougher 2021-05-24 7:07 ` Phillip Lougher 2021-05-25 9:22 ` Pintu Agarwal 2021-05-25 9:22 ` Pintu Agarwal 2021-05-25 5:37 ` Sean Nyekjaer 2021-05-25 5:37 ` Sean Nyekjaer 2021-05-31 2:54 ` Pintu Agarwal 2021-05-31 2:54 ` Pintu Agarwal 2021-06-01 6:52 ` Sean Nyekjaer 2021-06-01 6:52 ` Sean Nyekjaer
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='CAOuPNLhn90z9i6jt0-Vv4e9hjsxwYUT2Su-7SQrxy+N=HDe_xA@mail.gmail.com' \ --to=pintu.ping@gmail.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=phillip@squashfs.org.uk \ --cc=sean@geanix.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.