Squashfs Error Unable To Read Id Index Table

Table of Contents

Updated

1. Download ASR Pro

2. Run the program

3. Click "Scan Now" to find and remove any viruses on your computer

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.

Updated

Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!

Copy link

Employee

Mdhorn Commented December 5, 2019

@ sn99 This is usually always a sign that the ISO is never written properly to USB tape or is not syncing properly before ejecting.
We will definitely post these photos before starting, plus I just checked it again.

Can you verify that the checksum is correct and reprogram the image to a USB stickhealer?
Ideally, you should use one of our proven methods:
https://docs.01.org/clearlinux/latest/get-started/bootable-usb.html

If you use any other method remember that it always fails, share your custom process.

@ 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

squashfs error unable to read id index table

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:

squashfs error unable to read id index table

  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: