Squashfs error unable to read page после установки

Ubuntu Documentation

SquashFS Errors

Problem Statement

Some users have reported being unable to boot from the Ubuntu LiveCD, due to SquashFS errors like this:

Example error when loading Xubuntu with Wubi on first boot:

Causes and Solutions

These errors can be due to a variety of reasons:

• bad memory modules (solution: use memtest86+ to check your memory)
• a bad dvd drive (solution: if possible, try using a different cd/dvd drive)
• bad data cable (solution: change it for a new one)
• bad media (solution: try burning the iso image to a new disc)
• a corrupted iso image (solution: run an md5 checksum, and if they don’t match, download the iso image again)

Temporary Workarounds

Some users have reported that adding the ide=nodma or acpi=off allowed them to work around this issue (which proved to be bad memory modules). You might want to give that a try

Successful boot was achieved by adding «all_generic_ide» to the grub boot line for the live CD.

You can add those lines to the grub entry, either in the grub.conf file or either entering letter ‘e’ on the grub menu and after editing Control+x to boot:

Add to the grub line:

Add to the kernel line:

More information about the problem in grub can be found here: https://bugs.launchpad.net/wubi/+bug/608941

If is not a HW problem and you can probe it

If you definitely found that is not a HW issue, add you comment with all the logs and evidence you can get to Launchpad bug #172937

SquashfsErrors (последним исправлял пользователь bump55 2010-07-23 10:40:22)

The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details

Источник

Ошибки SquashFS после установки

Недавно у моего компьютера возникла довольно загадочная проблема. После того, как я закончу установку Ubuntu, Ubuntu выкладывает ряд ошибок, по-видимому связанных с плохими блоками. Эти ошибки покрывают мой экран и требуют от меня принудительного отключения машины.

Эта ошибка довольно раздражающая, так как USB выглядит в хорошем состоянии.

Некоторые ошибки включают (но не ограничиваются ими) следующее:

• SQUASHFS error: Superblock in USB, cylinder 3
• SQUASHFS fatal error, SQUASHFS exited with error code 5

Я уже попробовал решения, изложенные в этих вопросах, но безрезультатно. Что я могу сделать, чтобы решить эту проблему?

(У меня есть ноутбук UEFI Toshiba. Тест SMART показал, что с диском все в порядке. Я также запустил memtest86. Никаких ошибок там нет)

РЕДАКТИРОВАТЬ: Я использовал ответ KazWolfe и обнаружил, что было превышено количество хэшей. Итак, я получил новую ISO, и на этот раз я установил 16.10 ISO.

Но это все еще приходит со спамом ошибок SQUASHFS.

4 ответа

Эта проблема часто возникает из-за аппаратного сбоя вашего накопителя (как указано в «Ошибка 5», которая почти всегда является ошибкой ввода-вывода) или из-за проблемы с образом используемого диска. В более редких случаях это может быть ошибка памяти, но это кажется маловероятным в вашем случае.

Вы можете устранить эту конкретную проблему, загрузив чистый ISO-файл с официального сайта Ubuntu, а затем проверив MD5-хеш файла, используя следующую команду:

Ниже вы можете найти действительные суммы MD5 для 16.04.1, полученные из этого файла. Убедитесь, что результаты команды, которую вы запустили, и этот файл (или ниже) точно такие же.

После того, как вы проверили, что MD5-хэши на самом деле ТОЧНО, как они отображаются здесь, вы можете приступить к его записи на заведомо исправную флешку. Вы можете проверить работоспособность флэш-накопителя, выполнив проверку только для чтения, указанную в принятом ответе на этот вопрос.

Убедившись, что ISO и ваша флешка работают правильно, вы можете использовать Ubuntu ISO Tool или просто dd записать ISO на флешку.

Это может быть вызвано рядом проблем (наиболее распространенной из которых является неисправность ОЗУ, которую вы можете проверить с помощью memtest86), за которой следует проблема с подключением (уровень платы или жгут USB в вашем случае) или, возможно, из-за поврежденного ISO

Временные обходные пути Некоторые пользователи сообщают, что добавление ide=nodma или же acpi=off позволил им обойти эту проблему (которая оказалась плохими модулями памяти). Возможно, вы захотите попробовать.

Успешная загрузка была достигнута путем добавления all_generic_ide к загрузочной линии grub для live CD.

Вы можете добавить эти строки в запись grub, либо в файле grub.conf, либо введя букву ‘e’ в меню grub, и после редактирования Control+x загрузиться:

Добавьте к линии grub:

all_generic_ide pci=nommconf Добавьте к строке ядра:

ide=nodma acpi=off Более подробную информацию о проблеме в grub можно найти здесь: https://bugs.launchpad.net/wubi/+bug/608941

Если вы подтвердили, что это не проблема с оборудованием, вы можете подписаться на эту давнюю ошибку

Если что-то в этом ответе неясно, пожалуйста, прокомментируйте, и я постараюсь уточнить.

На самом деле, вы ошибаетесь в одном:

Это довольно раздражает, на моем USB нет СУПЕР БЛОКОВ

Конечно, на вашем USB есть суперблоки, потому что он содержит файловую систему. Суперблоки — это структуры метаданных в файловых системах, и поэтому вы можете сделать ставку на тот факт, что squashfs имеет один или несколько суперблоков.

Первое, что нужно попробовать, — это взять другой USB-диск, сделать из него загрузочный USB-диск и посмотреть, продолжает ли проблема существовать. Это исключило бы, что ваш USB-диск на самом деле — в конце концов — проблемы. Вы не можете просто сделать вывод, что «это работает в Windows, следовательно, это хорошо», потому что к дефектным секторам просто невозможно получить доступ с помощью Windows, особенно если они не используются файлом, к которому у вас нет доступа.

Вы сказали, что после установки Ubuntu вы должны выключить компьютер, но никогда не говорили, что произойдет после того, как вы снова отключите USB от компьютера. Также вы не упомянули номер вашей модели Toshiba, который может иметь определенные сбои. Номер версии BIOS тоже может быть важен.

Вы сказали, что используете UEFI, но пробовали ли вы CSM? В BIOS отключите Secure Boot, а затем измените UEFI на CSM.

Во-вторых, поддержка USB 3 не встроена в BIOS на некоторых машинах, а драйверы загружаются ОС во время загрузки. Вы можете попробовать загрузочную флешку USB 2 вместо текущей загрузочной флешки USB 3.

Наконец, некоторые пользователи Toshiba утверждают, что для загрузки с USB на основе UEFI версию Windows Rufus следует использовать для форматирования USB и установки типа раздела «Схема GPT-раздела только для UEFI».

Не знать свою машину и видеть, что происходит, это все, что приходит на ум.

Источник

dmugtasimov_pro

Дмитрий Мугтасимов (профессиональный блог)

Вероятно, многим из читателей покажется странным, что такой тривиальный процесс, как установка Ubuntu 10.04 удостоился отдельного постинга. Наверное, в большинстве случаев Ubuntu устанавливается без каких-либо проблем путем выбора рекомендованных опции в визарде инсталлятора. У меня, например, было так, когда я ставил Ubuntu 8.x на Acer ZG5. Но в этот раз я устанавливал Ubuntu 10.04 на Dell Latitude D610.

Про SQAUSHFS: [Errno 5] Input/output error
Первая попытка установки началась с того, что я скачал Ubuntu Desktop Edition LiveCD iso-файл и записал его на CD-RW. Однако, в ходе установки (в процессе копирования файлов) возникла ошибка [Errno 5] Input/output error:

Как видно из снимка экрана, проблема может быть в следующем: неисправность CD/DVD диска, CD/DVD-привода, жесткого диска или перегрев компьютера.

Вариантов для научного тыка достаточно! Я прожег еще одну CD-RW болванку — не помогло, прожег CD iso-образ на DVD-RW — не помогло (но было интересно узнать, что загрузочный CD-образ можно прожигать DVD и он тоже будет загрузочным). Сделал из LiveCD LiveUSB — таже самая проблема сохранилась. При изменении исходного носителя суть проблемы сохранялась, менялся только процент выполнения копирования файлов, на котором возникала ошибка — было 24%, 35% и 40%.

Тогда я сделал вывод, что проблема, наверное не в исходном носителе, а в жестком диске ноутбука. Для того, чтобы обойти эту потенциальную проблему я попробовал создавать раздел с файловой системой Ext3 на разной удаленности от начала диска, чтобы избежать записи в потенциально физически дефектные сектора. Это не помогло.

Тогда было сделано предположение, что проблемы возникают из-за особенностей драйверов (модулей ядра), которые обеспечивают работу с диском, либо из-за каких-то других проблем на системном уровне. Для исключения их влияния были использованы следующие опции загрузки (boot options): acpi=off, noapic, nolapic, hw-detect/start_pcmcia=false (и возможно еще какие-то). Не помогло.

Еще я снимал неродной модуль памяти размером 1Гб, т.к. из-за перегрева (а в Москве в это время стояла ужасная жара) могли возникать ошибки в памяти. Не помогло.

Пробовал ставить Mint и Fedora — аналогичная проблема. Метод научного тыка оказался неэффективным. Нужно было исследовать проблему под микроскопом.

Когда я вернулся к установке Ubuntu, то обнаружил, что в момент возникновения ошибки “[Errno 5] Input/output error” в /var/log/syslog появляются следующие строки:
[ 288.909464] SQUASHFS error: zlib_inflate error, data probably corrupt
[ 288.909481] SQUASHFS error: squashfs_read_data failed to read block 0x11b3773e
[ 288.909490] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909494] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
.

То есть, проблема возникает при чтении из файловой системы SQAUSHFS и, конретно, из файла filesystem.squashfs, в котором она размещена в данном случае.

Для того, чтобы убедиться, что проблема не связанна с нестабильным чтением с USB-диска я скопировал на жесткий диск и смонтировал его оттуда. Попробовал скопировать все файлы со смонтированной файловой системы на соседний диск. Возникли аналогичные ошибки, но теперь я мог видеть, с какими конкретно файлами возникают проблемы. Это были какие-то help-файлы и часть FireFox. Все это можно было доустановить потом, когда основная часть системы установиться. Поэтому возникала идея как-то отключить контроль корректной распаковки SQAUSHFS, но либо это невозможно, zlib_inflate выдает ошибку не по причине сравнения контрольных сумм, либо я просто не нашел как это сделать.

Последнее упражнение с перемонтированием filesystem.squashfs привело меня к выводу, что проблема либо с цельностью filesystem.squashfs, либо возникают ошибки в вычислениях из-за аппаратных проблем (было жарко — CPU и память могли перегреваться), либо ошибка в реализации алгоритма распаковки.

Попробовал скачать CD ISO-образ еще несколько раз из разных источников. Посчитал MD5, но он не сходился с тем, что был на сайт. Только вот проблема в том, что MD5 я считал какой-то бесплатной утилитой под Windows, которой вряд ли можно доверять. Тогда я скачал еще одну, теперь у меня было три разных MD5-хэша: один на сайте Ubuntu и два посчитанные разными утилитами. Все он расходились. Можно было еще пойти дальше и скопировать CD ISO-образ под Linux, загрузившись под LiveCD, но это все-равно не решило бы проблему. Я бы только узнал, что у меня образ битый или что он нормальный. Ошибка SQAUSHFS все-равно осталась бы.

На каком-то из форумов я обнаружил, что при такой ошибке как у меня успешно происходит установка с Alternative CD в текстовом режиме. Тогда я скачал этот ISO-образ — он уже предназначался для записи на DVD, т.к. занимал примерно 4Гб. Чудесным образом установка удалась , однако меня ждала следующая (как оказалось потом) проблема GRUB не устанавливался и выдавал ошибку “error: unknown filesystem” и консоль grub rescue>.

Про GRUB: error: unknown filesystem
Пришлось начать с того, чтобы восстановить основную загрузочную запись (MBR) и загрузить хотя бы Windows XP. Сделать это нужно было из под Linux LiveCD командой sudo dd if=/usr/lib/syslinux/mbr.bin of=/dev/sda. Файл содержит первые 404 байт стандартного загрузчика, поэтому, во-первых, не затирает таблицу разделов, а, во-вторых, успешно восстанавливает исходное состояние системы. Еще после восстановления я на всякий случай сделал резервную копию всей MBR (включая таблицу разделов): sudo dd if=/dev/sda of=mbr.bak count=1.

Первое предположение (после того, как было сдалан вывод, что [Errno 5] Input/output error и error: unknown filesystem не связанны), почему не работает GRUB, заключалось в том, что GRUB, который размеще в Alternative CD не поддерживает файловую систему Ext4. Попытка установки Ubuntu на Ext3 привела к тому же результату.

Опять же на одном из форумов была обнаружена рекомендация создавать раздел с операционной системой ближе к началу диска. Пришлось немного поперетаскивать данные по диску и раздел с Ext3 был создан на отметке примерно 40Гб от начала диска. И это помогло! Видимо GRUB не умеет загружать Linux, если раздел этой файловой системы находится слишком далеко от начала диска (в моем случае примерно 200 Гб).

Источник

SQUASHFS error while booting from live cd

Bug Description

Some users have reported being unable to boot from the Ubuntu LiveCD, due to SquasFS errors like this:

[ 135.292409] SQUASHFS error: sb_bread failed reading block 0x9d7f3
[ 135.292411] SQUASHFS error: Unable to read fragment cache block [275faa28]
[ 135.292413] SQUASHFS error: Unable to read page, block 275faa28, size 23a7

These errors can be due to a variety of reasons:

* bad media (solution: try burning the iso image to a new disc)
* a bad dvd drive (solution: if possible, try using a different cd/dvd drive)
* bad memory modules (solution: use memtest86+ to check your memory)
* a corrupted iso image (solution: run an md5 checksum, and if they don’t match, download the iso image again)
* an optical drive connected via SATA instead of PATA and running in Enhanced mode (solution: change the IDE configuration to «compatible» in the BIOS)

Have you run the test to see if the burned disc had errors?

i have checked the disc and it has no errors.
i try a new one and post the results as soon as possible.

I have the same problem using Hardy Alpha 2.
I only get other hexadecimal values.

I get another error though:
Buffer I/O error on device sr0, logical block 267571. (the number doesn’t say much, because I get other numbers as well)

I’ll try reburning using another CD-writer.

Seems I have a bad CD-writer, using another one, the problem is fixed.

i am having the same problem w/ the live cd I ordered from ubuntu.

I am having the same issue with Hardy Alpha 2. I also get the SQUASHFS and BUFFER I/O errors. I will burn the iso using another burner and post my results.

Burning the iso using a different burner worked. Both times it was burned in WIndows. The first time using InfraRecorder the second time using Nero.

Description of problem:
Fails on install

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1.
2.
3.

Created attachment 294692
anaconda dump

Did you verify your media?

several times and every time it verified ok

Reassigning to kernel based on the following error messages, which are
indicative of driver problems, hardware problems, or media problems (which seem
to be ruled out by running media check):

SQUASHFS error: zlib_inflate returned unexpected result 0xfffffffd, srclength
65536, avail_in 630, avail_out 65536
SQUASHFS error: sb_bread failed reading block 0xd7a1
SQUASHFS error: Unable to read page, block 35e2988, size 5d76

Some hardware stats : Compaq Proliant 1600, 2x 500Mhz, 1Gb Memory, Smart Array
3200 Raid Controler, 1 floppy drive, 1 DVD IDE drive.

Tried Fedora 7 installs ok only mouse is not working, Fedora 3 installs ok
mouse works, will test other versions after download.

Fedora- 8-i386- DVD.iso — not working when English for language is used Keyboard
choice crash, Dutch language partitioning is reached.

F-7-i386-DVD.iso — during install no mouse.

FC3-i386-disc1.iso — floppy does not mount during install.

i have this problem in hardy beta
i am using virtualbox with the iso-file, so it is not a failure in the cd .. but i will try it with a new download of the iso-image .
if it is important: it is a x86-machine

ok, the iso-file was damaged .. no it’s working ..

Probably this error messages is caused by a variety of errors, that may be unrelated. I myself just experienced this issue with a downloaded iso; I burnt the cd and tried booting it in two different drives but had the SQUASHFS and Buffer I/O errors. I threw the CD in the trash basket and burnt the same iso to a new CD, and that time it worked.

However, I see in other bugs, others have reported the same error messages but it seems to be something other than bad media:

#200688 — when libdvdcss is not installed
#120389 — misdetected drive
#135094 — stalling due to missing floppy drive
#94119 — misdetected drive
#187807 — Some sort of DMA problem, only affects reading CD’s

I have a gut feeling that bug #110636 might have something to do with at least some of these bugs, but no solid clue.

Here’s a couple more with this error message:

162908 — Bad CD locks up SATA system
148466 — Bug in pata_serverworks kernel module, workaround with libata.pata_dma=1

These two bugs have some interesting suggestions that the issue is bad error handling in the SATA kernel module. Several bugs seem to be in systems with both SATA and PATA devices, so maybe there is a conflict or incompatibility between them?

I’ve gone ahead and followed up with the majority of those reports you listed. Having read all the comments here, it seems we can close this report out as the errors were either attributed to bad media or bad hardware. Thanks.

Also met this on a Tyan motherboard with Intel 5000 chipset.

F8 i386 & x86_64 both fail.

F9 i386 pre-release does work.

dmidecode being attached here for reference.

Created attachment 304393
dmi decode from TYAN-Tempest- i5000VS- S5372-LC/ LH

I’ve downloaded 8.04 desktop i386 and 64 twice (from MIT today and from Canadian mirror yesterday) and checked MD5 sum and all 4 matched. I’ve burned them using two different Windows machines. None of iso works and all of them report the same error «. SQUASHFS . unable to read page. » and I’ve been trying to install on two different computers started yesterday and I’m now giving up. Oh, and all CDs report problems with between 10 and 18 files. What’s interesting is that when I run check repeatedly it reports different number of problems every time. Of course, as a developer I’d jump on this to point out that there’s a problem with everything else but distribution, so you can close this if you want but also as a developer I can guarantee you that there’s a problem with this distribution for I had not a single problem with 7.10 nor with Fedora ISOs and I’m burning a dozen of both CDs and DVDs a week and have no problems at all. As for bad hardware, yeah, right: «it works on my box» I’ve heard this one and have to adim used it myself many a time. I guess I’ll have to put up a bit more with

I’m also having this problem. No CD burning problem, as I am using unetbootin through USB. So. what should I do? I don’t really think this bug should be closed. And I don’t believe that all of us got bad ISO files from the online repos. I checked the MD5 and matches. I am using Kubuntu 8.04.01 live CD.

Although I have not had a problem installing from and versions of the install CD, I have had this error with squashfs. I am using it for a running system, with aufs, so that the OS is reset to its original form after each reboot. Most of the time it is fine, but sometimes I get this error with a particular build of my system. If it works it will always work, but if I build one that comes up with this error, it always fails. The weird thing is that if I mount the filesystem via loopback on my normal system, it appears to be fine. Could this be a problem with the version of squashfs used in 8.04? Has it changed since 7.10? Unfortunately I can’t find anything in common with the versions of my system that don’t work, as opposed to those that do. I shall dig further.

Hmm bizarre. If I increase the block size with mksquashfs, the problem disappears. Even with the same file structure. I had tried re-running mksquashfs previously, to no avail. Definitely suggests a bug in squashfs. But is it a bug with the ubuntu build of squashfs, or upstream? The problem is it is so difficult to replicate. I will try building squashfs myself and testing against a file structure that failed before.

I have got the same error as the first post

I tried to add this option to the kernel
ide=nodma

and it worked for me but the error message appeared again for 25 times as the above error message.

shouldn’t this be assigned to the «casper» source package?

hmmm, it seems this might be related to bad memory modules (which would explain the ide=nodma solution).

can someone try running the memtest86+ from their grub menu and report back?

I get the SQUASHFS error: sb_bread failed reading block while trying to boot from a known good 8.04.1 LiveCD

. as per Dimitrios’ suggestion memtest shows that my second memory module has gone bad — doh!

Removed the bad module and all is now working.

So for me the error (same as for the original poster) _was_ due to bad memory.

I got this error to on a NetServer LH 6000 3U. I will test mem and report again.

I tested the memory and it is good. I woud like install ubuntu 8.04.1 server, but I get MD5SUM error. And the SQUASHFS logs error. (live cd and alternative cd don’t work too)

kaltsi, if you get an md5 sum error on the .iso file, you need to download it again (and check md5 again before burning it to a disc).

one thing you can do to avoid having to burn cds is use unetbootin to «burn» the iso to a flash disc

— for lieven and arqbrulo, the problem was caused by a bad dvd reader
— for ska.ndal, the iso image was corrupt
— for john blance it was bad memory modules
— tad1073 and nebojsa never got back to us

could everyone else try md5 sum, memtest86+, different media and a different drive? these seem to be the most common causes to the problem.

For me, it was also broken DVD reader, I can confirm it because it never worked again 🙂
unetbootin through USB was the only solution I could use.

I’m experiencing this with an «old» Pentium 4 desktop, and it’s not any of the above problems:

— I’ve tested with 5 (five!) different CD readers.
— I’ve successfully booted the CD in other computers, and verified both the iso image and final cd to be OK.
— I’ve checked the memory with memtest86+, both for the «default tests» and for the «bit fade test». All ok.

This problem exists with both 8.10 and 7.10 for the same pc.

I’ve had similar trouble with 7.10 on another PC, and an «all-generic-ide» option made it work. Unfortunately nothing that I’ve tried works for this one. I suspect it may have something to do with the fact that this PC’s motherboard has SATA support, but all the drives are PATA.

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora’s policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
‘version’ of ‘8’.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the ‘version’
to a later Fedora version prior to Fedora 8’s end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the ‘version’ of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release’s
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Sorry if people have already posted this solution. but.

I have a ASUS x83vm-x1 and tried to install Kubuntu 8.10 from a live CD. Would start the install and then give
[ 135.292409] SQUASHFS error: sb_bread failed reading block 0x9d7f3
[ 135.292411] SQUASHFS error: Unable to read fragment cache block [275faa28]
[ 135.292413] SQUASHFS error: Unable to read page, block 275faa28, size 23a7

Thinking it was a defect CD, I ran the check disk and check memory utilities which both reported no problems.

I then tried the an OFFICIAL CD UBUNTU 8.04 I recieved in the mail. It also reported the same errors.

I went into BIOS and changed the IDE settings to COMPATIBILITY MODE. Viola! It worked. Hope this helps someone else out.

PS — I HATE Vista! Thank GOD I got Kubuntu installed!

This problem was solved for me by changing the DVD reader. The first one was old, even it works fine with movies and songs.

I’ve looked through squashfs mailing lists and a lot of forums reports, and *almost* all the cases where caused by HW failure, i’ve just added to the wiki page the only case not described there (a faulty cable)

So if someone can give evidence that is not a HW issue would be more than welcome the corresponding logs and data.

Maybe as Bryce pointed out is a compatibility issue between sata and pata componentes on some motherboards.

Anyway i’ve opened a bug at sourceforge project’s page hoping that someone can take a look into this.

in order to avoid confusion, i’m marking this as «won’t fix», since this is not an ubuntu bug, but almost always a hw issue.

These errors are often caused by HW issues:
# bad memory modules (solution: use memtest86+ to check your memory)
# a bad dvd drive (solution: if possible, try using a different cd/dvd drive)
# bad data cable (solution: change it for a new one)
# bad media (solution: try burning the iso image to a new disc)
# a corrupted iso image (solution: run an md5 checksum, and if they don’t match, download the iso image again)

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

It seems like this error is often memory-related, but the error messages indicate it’s usually bad media. Is it possible to add the possibility of bad memory to the error message? The pop-up error I got was:

«The installer encountered an error copying files to the hard disk: [Errno 5] Input/output error
This is often due to a faulty CD/DVD disk or drive, or a faulty hard disk. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers), to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment.»

But dmesg had the following:
[ 1228.553400] kjournald starting. Commit interval 5 seconds
[ 1228.553598] EXT3 FS on sda5, internal journal
[ 1228.553605] EXT3-fs: mounted filesystem with ordered data mode.
[ 1349.994012] SQUASHFS error: zlib_inflate returned unexpected result 0xfffffffd, srclength 131072, avail_in 352, avail_out 92175
[ 1349.994024] SQUASHFS error: sb_bread failed reading block 0x77162
[ 1349.994029] SQUASHFS error: Unable to read fragment cache block [1dc4df1a]
[ 1349.994035] SQUASHFS error: Unable to read page, block 1dc4df1a, size a972

If the error message is going to be helpful enough to suggest a solution, it would help to include both probable solutions. Otherwise people are chasing the idea that the media is bad when it isn’t.

Hi,
I am trying to make that laptop computer work again, I hope this is the right place to post. I run windows, and it says that the partition cannot be recognized. I run the ubuntu installation with the acpi=off option, but the installation stops at 5%. But I can confirm that acpi=off helps, at least it goes on with the installation. A memtest86+ cannot be completed, the computer at a certain point goes off. It sounds to me that the hard disk is corrupted.
Question: I can buy a new hard disk, but how can I check that the memory modules (I have an additional external 1GB ram) are ok?
thanks

The solution I found was burn with Disc-At-Once mode (with cdrecord) when burning (the same) ISO file. Burning in Track-At-Once (TAO) mode made the CD unusable. Can’t tell if it’s the CD burner that burned it wrong the (several) times I burned it using default (TAO) mode, but, as I said, burning a single time with DAO made it work to boot up.

I had the same scenario as Rob York and can confirm that changing IDE mode to «Compatible» in the BIOS fixes the install issue (I had already tested my memory and the installation disc and both were fine). I have also been able to change the IDE mode back to «Enhanced» after installing (otherwise my existing windows installation won’t boot).

It appears that in some newer laptops the optical drive uses SATA instead of PATA and the installer can’t handle it properly. I have had this problem with 8.04, 8.10 and 9.04, but I’ve only tried this fix with 9.04

My PC had 2 sata harddrives, and the linux mint 2009 live CD booted perfectly and i was able to install Linux mint on my second sata harddrive no problems, but the pc that i actually want linux on is a lil bit older and only has IDE capabilities, no sata (and some other issues) :o( so off i go and put the IDE hard drive in my (sata capable) PC, and with this harddrive connected to the PC, im getting these ‘SQUASHFS error: unable to read page’ etc etc i have changed the IDE mode to «compatible» and run tests everything seems fine, im under the impression that the media was not the problem anyway as it worked fine with sata harddrives
any clues people. this is driving me insane. X(

Symptoms: DVD drive read errors when trying to load live distros, or play films under Linux.

For example:
SQUASHFS error: sb_bread failed reading block .
SQUASHFS error: Unable to read page, block . size .

end_request: I/O error, dev sr0, sector .
Buffer I/O error on device sr0, logical block .

Tests/Results: (I tried. )
(a) Ubuntu 7.04 ‘Fiesty Faun’ (DVD) live boot
OK (Note: treats DVD-Drive as device hdc.)

(b) Ubuntu 8.04 ‘Hardy Heron’ (DVD) live boot
BAD — errors like example above.

(c) Xubuntu 8.04 (CDR) live boot and media check
BAD — errors like example above.

(d) Ubuntu 8.10 ‘Intrepid Ibex’ (DVD) live boot
BAD — but errored later, after failing to start X.

(e) Ubuntu 9.10 ‘Karmic Koala’ (DVD) live boot
BAD — errors like example above.

(f) OpenSuse 10.2 (DVD) live boot and media check
OK

(g) OpenSuse 10.3 (DVD) live boot and media check
BAD

(h) OpenSuse 11.0 (DVD) live boot and media check
OK! A later version that works?!

(i) OpenSuse 11.1 (DVD) live boot
BAD

(j) OpenSuse 11.2 (DVD) live boot
BAD

(k) Knoppix 5.3.1
OK (Note: although kernel is late-ish 2.6.24.2 it still treats CD as device hdc. )

NOTE: Disks that do not work in the Test System DO work in a more modern PC.

Test System:
Advent 5480DVD
[SiS Chipset]
[Old circa 2000, PIII (Coppermine) 800MHz]
BIOS circa 2001
RAM upgraded to 512MB
DVD upgraded to Pioneer DVR KD08 (this is only 8months old from manufacture)
HDD upgraded to 40GB

Things tried that *DID* *NOT* solve problem:
— Used ‘regionset’ utility to set region on the new DVD drive.
— Apply kernel parameters mix’n’match of the following:
generic. all_generic_ ide=1
irqpoll
ide=nodma
apic=off
— Memory test — shows my SDRAMs are good.

Media Check Experiment:
Aborting install of OpenSuse 10.2 we get a menu including the media check option.
If I swap DVD for e.g. 10.3 then select this option, it successfully verifies DVD, even though 10.3 will not verify *itself* successfully. That is, aborting 10.3 install and doing media check on itself fails!
i.e. the Linux SW version running the media dictates whether the DVD works, not a media problem.

Windows Experiment:
Replace HDD with old HDD with Windows ME (!) on.
This can successfully play DVD movies.
After this, which confirms the region setting, the Linux DVD behaviour is no different — same problems.
(So the dead Windows ME or *old* Linux are my best bet for playing DVDs on this HW. Both are security risks so such a machine could NOT be connected to the net.)

Experimental Conclusions:
— There is nothing wrong with the media — it must be accepted that at least most of them are good — in fact I think they all are.
— There is nothing wrong with the DVD drive.
— There is nothing wrong with the computer HW in general.
— There *IS* something wrong with (newer) Linux DVD/CD driver SW on this HW.
— . — it is emergent on more recent Linux SW versions, possibly when IDE got wrapped to make it look like SCSI.

+++ Workaround Solution +++ :
After all else failed I finally find the libata.dma kernel parameter works when excluding DMA on CD i.e. [in the following manner]
(***Works o.

I hade the same problem on my MSi Wind U100 Netbook.
I tried with a CD with the ubuntu- 9.10-desktop- i386.iso image, doesn’t work.
After that I build a bootable USB Stick with unetbootin and the image above and got the same error.

I then changed in bios (version 10G) under Advanced the AHCI Mode from Disabled (default) to Enabled and then the bootable USB Stick works.

I have this problem with Ubuntu 10.04 on a HP nx6110 laptop. The boot options mentioned above didn’t work.

Checking the CD for errors reported 3 errors. OTOH, I used the very same CD to install Ubuntu on a desktop computer, and there it (eventually) worked. The best I got so far on the laptop is that it starts installing files on the harddisk, and stops at 22% with an I/O error dialog.

I tried to make new burns of the CD, using the computer where 10.04 is installed. The disk with the 3 errors was created with the default CD burning software of Ubuntu, so, for a change, I used k3b for my other attempts. I tried different speeds, and I also tried DAO. The new CDs are even worse than the first one. With the new CDs, the boot manager of the CD-ROM complains that it can’t read the CD-ROM, as soon as I press enter on an option like ‘install Ubuntu’.

I have a solution to this problem, that helped me, and may also help other people for who the above solutions didn’t work:

Use the Netboot installer!!

The netboot installer is a lot smaller than the live CD, because it doesn’t contain any packages: instead, it downloads these from the Internet while installing. This will help you if this problem is caused somehow by errors on the CD-R: the probability that the netboot installer hits one of these errors is lower, because of the smaller size of the netboot image. It worked for me!

Now that I have 10.04 on my nx6110(*), I used it to burn the live CD again. I used Brasero with 4x speed (the lowest possible), and I used a CD-R from a different series. To my surprise, the CD self-check didn’t report ANY errors! So I booted the CD, which it did (it still mentioned filesystem problems in the boot messages, but they didn’t seem to be a problem). I did not try the installer, because I didn’t want to disturb my current 10.04 installation.

That made me wonder whether my first series of CD-Rs was guilty of the problem. So, I took another CD-R from the old series, and made another live-CD burn with EXACTLY the same hardware, software and settings, and the result was: a CD with errors!

My conclusion: in my case, the problem was a bad series of CD-Rs. This was further confirmed by comparing the files on the failed CD-Rs with the files in the .iso image: there were differences.

My BAD series is:
Maxell CD-R «up to 52x» 20 pack 5mm case 700MB
Barcode 4 902580 349554

My GOOD series is:
Sony CD-R 700MB x30 (1x — 48x compatible)
Barcode 4 901780 808465

At least I didn’t waste half a dozen of GOOD CD-Rs on this issue! 🙂

(*) I forgot to mention: I installed an extra 1024MiB of RAM. However, Memtest86 doesn’t report any problems.

I experience the error when installing xubuntu using the Wubi method (after loading xubuntu from the windows menu starts installing and I get the error):

[ 29.679870] VIA 82xx Audio 0000:00:07.5: sharing IRQ 10 with 0000:00:0e.1
[ 29.679879] VIA 82xx Audio 0000:00:07.5: sharing IRQ 10 with 0000:00:0f.0
[ 29.680030] VIA 82xx Audio 0000:00:07.5: setting latency timer to 64
[ 31.769189] lp0: using parport0 (interrupt-driven).
[ 40.075068] eth0: no IPv6 routers present
[ 74.903804] NTFS driver 2.1.29 [Flags: R/O MODULE].
[ 81.190040] QNX4 filesystem 0.2.3 registered.
[ 81.364872] Btrfs loaded
[ 90.596351] Adding 261112k swap on /host/ubuntu/ disks/swap. disk. Priority:-1 extents:1 across:261112k
[ 104.800436] EXT4-fs (loop2): mounted filesystem with ordered data mode
[ 288.909464] SQUASHFS error: zlib_inflate error, data probably corrupt
[ 288.909481] SQUASHFS error: squashfs_read_data failed to read block 0x11b3773e
[ 288.909490] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909494] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909531] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909534] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909557] SQUASHFS error: Unable to 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: Unable to read page, block 11b3773e, size 17512
[ 288.909591] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909594] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909609] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909612] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909626] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909630] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909644] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909647] SQUASHFS error: Unable to read page, block 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

Источник

SquashFS Errors

Problem Statement

Some users have reported being unable to boot from the Ubuntu LiveCD, due to SquashFS errors like this:

SQUASHFS error: sb_bread failed reading block 0x9d7f3
SQUASHFS error: Unable to read fragment cache block [275faa28]
SQUASHFS error: Unable to read page, block 275faa28, size 23a7

Example 2:

[ 1228.553598] EXT3 FS on sda5, internal journal
[ 1228.553605] EXT3-fs: mounted filesystem with ordered data mode.
[ 1349.994012] SQUASHFS error: zlib_inflate returned unexpected result 0xfffffffd, srclength 131072, avail_in 352, avail_out 92175
[ 1349.994024] SQUASHFS error: sb_bread failed reading block 0x77162
[ 1349.994029] SQUASHFS error: Unable to read fragment cache block [1dc4df1a]
[ 1349.994035] SQUASHFS error: Unable to read page, block 1dc4df1a, size a972

Example error when loading Xubuntu with Wubi on first boot:

[ 81.364872] Btrfs loaded
[ 90.596351] Adding 261112k swap on /host/ubuntu/disks/swap.disk. Priority:-1 extents:1 across:261112k
[ 104.800436] EXT4-fs (loop2): mounted filesystem with ordered data mode
[ 288.909464] SQUASHFS error: zlib_inflate error, data probably corrupt
[ 288.909481] SQUASHFS error: squashfs_read_data failed to read block 0x11b3773e
[ 288.909490] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909494] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909531] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909534] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909557] SQUASHFS error: Unable to 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: Unable to read page, block 11b3773e, size 17512
[ 288.909591] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909594] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909609] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909612] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909626] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909630] SQUASHFS error: Unable to read page, block 11b3773e, size 17512
[ 288.909644] SQUASHFS error: Unable to read data cache entry [11b3773e]
[ 288.909647] SQUASHFS error: Unable to read page, block 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

Causes and Solutions

These errors can be due to a variety of reasons:

• bad memory modules (solution: use memtest86+ to check your memory)
• a bad dvd drive (solution: if possible, try using a different cd/dvd drive)
• bad data cable (solution: change it for a new one)
• bad media (solution: try burning the iso image to a new disc)
• a corrupted iso image (solution: run an md5 checksum, and if they don’t match, download the iso image again)

Temporary Workarounds

Some users have reported that adding the ide=nodma or acpi=off allowed them to work around this issue (which proved to be bad memory modules). You might want to give that a try

Successful boot was achieved by adding «all_generic_ide» to the grub boot line for the live CD.

You can add those lines to the grub entry, either in the grub.conf file or either entering letter ‘e’ on the grub menu and after editing Control+x to boot:

Add to the grub line:

all_generic_ide pci=nommconf

Add to the kernel line:

ide=nodma acpi=off

More information about the problem in grub can be found here: https://bugs.launchpad.net/wubi/+bug/608941

If is not a HW problem and you can probe it

If you definitely found that is not a HW issue, add you comment with all the logs and evidence you can get to Launchpad bug #172937

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх