Squashfs error unable to read xattr id index table

Hi,

This is regarding the squashfs mount failure that I am getting on my
device during boot time.
I just wanted to know if someone else has come across this issue, or
this issue is already fixed, or this is altogether a different issue?

Here are more details:
Kernel: 4.14.170 ; Qualcomm chipset (arm32 bit)
Platform: busybox
Storage: NAND 512MB
Filesystem: ubifs + squashfs
ubi0 : with 5 volumes (rootfs, usrfs, others)
Kernel command line: ro rootwait console=ttyMSM0,115200,n8
rootfstype=squashfs root=/dev/mtdblock34 ubi.mtd=30,0,30 ….

Background:
We are using ubifs filesystem with squashfs for rootfs (as ready only).
First we tried to flash «usrfs» (data) volume (ubi0_1) and it worked
fine (with device booting successfully).

Next we are trying to flash «rootfs» volume (ubi0_0) now. The volume
flashing is successful but after that when we reboot the system we are
getting below errors.

Logs:
[….]
[ 4.589340] vreg_conn_pa: dis▒[ 4.602779] squashfs: SQUASHFS
error: unable to read xattr id index table
[…]
[ 4.964083] No filesystem could mount root, tried:
[ 4.964087] squashfs
[ 4.966255]
[ 4.973443] Kernel panic — not syncing: VFS: Unable to mount root
fs on unknown-block(31,34)

[ 4.246861] ubi0: attaching mtd30
[ 4.453241] ubi0: scanning is finished
[ 4.460655] ubi0: attached mtd30 (name «system», size 216 MiB)
[ 4.460704] ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
[ 4.465562] ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
[ 4.472483] ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
[ 4.479295] ubi0: good PEBs: 864, bad PEBs: 0, corrupted PEBs: 0
[ 4.486067] ubi0: user volume: 5, internal volumes: 1, max. volumes
count: 128
[ 4.492311] ubi0: max/mean erase counter: 4/0, WL threshold: 4096,
image sequence number: 1
[ 4.499333] ubi0: available PEBs: 0, total reserved PEBs: 864, PEBs
reserved for bad PEB handling: 60

So, we just wanted to know if this issue is related to squashfs or if
there is some issue with our volume flashing.
Note: We are using fastboot mechanism to support UBI volume flashing.

Observation:
Recently I have seen some squashfs changes related to similar issues
(xattr) so I wanted to understand if these changes are relevant to our
issue or not ?

Age Commit message(Expand) Author
2021-03-30 squashfs: fix xattr id and id lookup sanity checks
Phillip Lougher
2021-03-30 squashfs: fix inode lookup sanity checks
Sean Nyekjaer
2021-02-23 squashfs: add more sanity checks in xattr id lookup
Phillip Lougher
2021-02-23 squashfs: add more sanity checks in inode lookup
Phillip Lougher
2021-02-23 squashfs: add more sanity checks in id lookup
Phillip Lougher

Please let us know your opinion about this issue…
It will help us to decide whether the issue is related to squashfs or not.

Thanks,
Pintu

Updated

Speed up your computer today with this simple download.

Sometimes your system may display an error that squashfs cannot read the ID index table. There can be several reasons for this problem.

Copy link

Employee

Mdhorn Commented December 5, 2019

@ sn99 This is often a sign that the ISO was not properly written to the USB media and was not properly synchronized before extracting.
We check many of these images before we start, and I just checked them again. You

Could you please check if the checksum is correct and reprogram the image to a USB stick?
Ideally, your business should follow one of the methods we mentioned:
https://docs.01.org/clearlinux/latest/get-started/bootable-usb.html

If you use a different method but it still doesn’t work, please let us know your process.

  [...] squashfs: Error: squashfs cannot read the index table with id xattr 

  mount /cdrom/casper/filesystem.squashfs /filesystem.squashfs Squashfs -t -o loop 

• Source

but if I run the command while Ubuntu is running, everything is fine:

  sudo mount /media/USER/UUI/casper/filesystem.squashfs fs-uui -r -o squashfs loop 

• The image that caused the specific error can be found here.
• To see the nature of the error when running the message, I removed these special splash and quiet options in the trainer command.
• md5 sums are good.

If you have instructions on how to debug this or create your own ISO image starting with efi, please leave a note.

EDIT 1:Currently, a specific workaround is to remove xattrs from the root filesystem using the -no-xattrs parameter:

  mksquashfs / "$ filesystem_location / filesystem.squashfs" -ef ./exclude.txt -wildcards -no-xattrs 

Description Of The Problem

Some users reported that they are unable to boot from the LiveCD due to SquashFS errors like this, like 8:

 SQUASHFS error: sb_bread could not read block 0x9d7f3SQUASHFS error: Unable to read chunk cache wood block [275faa28]SQUASHFS error: Could not read page 275faa28, size 23a7 

 [1228.553598] EXT3FS with sda5, internal log[1228.553605] EXT3-fs: The file system was mounted in ordered data mode.[1349.994012] SQUASHFS error: return home zlib_inflate unexpected result 0xffffffffd, srclength 131072, Avail_in 352, Avail_out 92175[1349.994024] SQUASHFS error: sb_bread has finished reading block 0x77162[1349.994029] SQUASHFS error: chunk cache block cannot be read [1dc4df1a][1349.994035] SQUASHFS error: Unable to read webpage, block 1dc4df1a, a972 

Sample size error when starting Xubuntu with Wubi on first launch:

[81.364872] Btrfs loaded[90.596351] Added replacement for 261112k to /host/ubuntu/disks/swap.disk. Priority: -1 Volumes: 1 from: 261112k[104.800436] EXT4-fs (loop2): mounted file system with ordered write mode.[288.909464] SQUASHFS error: zlib_inflate error, data is almost completely corrupted[288.909481] SQUASHFS error: squashfs_read_data could not read block 0x11b3773e[288.909490] SQUASHFS Error: Unable to read data cache entry [11b3773e][288.909494] Error: Could not read squashfs page, mouthful 11b3773e, size 17512[288.909531] SQUASHFS error: Unable to read data cache entry [11b3773e][288.909534] SQUASHFS Error: Failed to read page, limit 11b3773e, size 17512[288.909557] SQUASHFS error: n can read data cache entry [11b3773e][288.909561] SQUASHFS error: unable to read page, block 11b3773e, size 17512[288.909574] SQUASHFS Error: Unable to read data cache entry [11b3773e][288.909578] SQUASHFS error: read page, angle 11b3773e, size 17512[288.909591] SQUASHFS error: Unable to read data cache entry [11b3773e][288.909594] SQUASHFS error: read page, get stuck 11b3773e, size 17512[288.909609] SQUASHFS error: Unable to read data cache entry [11b3773e][288.909612] Error: Could not read squashfs page, zone 11b3773e, size 17512[288.909626] SQUASHFS error: Unable to read data cache entry [11b3773e][288.909630] SQUASHFS error: the page cannot be read, it is clogged with 11b3773e, size 17512[288.909644] SQUASHFS error: Unable to read data cache entry [11b3773e][288.909647] SQUASHFS error: to not read the page, exit 11b3773e, size 17512[288.909664] SQUASHFS Error: Unable to read data cache entry [11b3773e][288.909667] SQUASHFS error: unable to read page, block 11b3773e, size 17512

Reasons And Solutions

These errors can also be caused by different variables:

• faulty memory modules (solution: use memtest86 + for successful prochecking your memory)
• defective DVD version (solution: try one CD / DVD drive if possible)
• bad data cable (solution: replace it with a new one)
• bad new media (solution: try burning the ISO image to make it a new disk)
• a Notion ISO (solution: make md5 checksum and if they don’t match, load ISO reliability again) < / li>

Temporary Workarounds

Some users reported that adding ide = nodma or acpi = off allowed consumers to work around this issue (which caused faulty memory modules). You can take advantage of this

A successful boot was achieved by adding all_generic_ide to the Grub boot line for the Stay Alive CD.

You can add all lines to the grub entry either in this grub.conf file, or by typing the letter ‘e’ in grub and the menu after changing ctrl + x to run:

 all_generic_ide pci = confname 

 ide = nodma acpi = off 

More information on the Grub-Can issue can be found here: Squashfs 오류 ID 인덱스 테이블을 읽을 수 없음
Squashfs-Fehler Kann ID-Indextabelle Nicht Lesen
Ошибка Squashfs: не удается прочитать таблицу индекса идентификаторов
Błąd Squashfs Nie Można Odczytać Tabeli Indeksu Identyfikatorów
Erreur Squashfs Impossible De Lire La Table D’index D’identification
Squashfs-fout Kan ID-indextabel Niet Lezen
Erro De Squashfs – Incapaz De Ler Tabela De Índice De Id
Squashfs -fel Det Gick Inte Att Läsa Tabellen över ID -index