Squashfs error xz decompression failed data probably corrupt

Same here, changed some config + reboot. Now the ER-X is stuck in Bootloop after running stable for ~2years

3: System Boot system code via Flash.
## Booting image at bfd40000 ...
   Image Name:   MIPS OpenWrt Linux-5.4.154
   Image Type:   MIPS Linux Kernel Image (uncompressed)
   Data Size:    2367034 Bytes =  2.3 MB
   Load Address: 80001000
   Entry Point:  80001000
.....................................   Verifying Checksum ... OK
OK
No initrd
## Transferring control to Linux (at address 80001000) ...
## Giving linux memsize in MB, 256

Starting kernel ...



OpenWrt kernel loader for MIPS based SoC
Copyright (C) 2011 Gabor Juhos <juhosg@openwrt.org>
Decompressing kernel... done!
Starting kernel at 80001000...

[    0.000000] Linux version 5.4.154 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16325-88151b8303)) #0 SMP Sun Oct 24 09:01:35 2021
[    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
[    0.000000] MIPS: machine is Ubiquiti EdgeRouter X
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] VPE topology {2,2} total 4
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[    0.000000] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x000000000fffffff]
[    0.000000]   HighMem  empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000000fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000000fffffff]
[    0.000000] percpu: Embedded 14 pages/cpu s26768 r8192 d22384 u57344
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 64960
[    0.000000] Kernel command line: console=ttyS0,57600 rootfstype=squashfs,jffs2
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[    0.000000] Writing ErrCtl register=00049340
[    0.000000] Readback ErrCtl register=00049340
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 250792K/262144K available (6089K kernel code, 210K rwdata, 748K rodata, 1260K init, 238K bss, 11352K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] NR_IRQS: 256
[    0.000000] random: get_random_bytes called from 0x806e5a3c with crng_init=0
[    0.000000] CPU Clock: 880MHz
[    0.000000] clocksource: GIC: mask: 0xffffffffffffffff max_cycles: 0xcaf478abb4, max_idle_ns: 440795247997 ns
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 4343773742 ns
[    0.000009] sched_clock: 32 bits at 440MHz, resolution 2ns, wraps every 4880645118ns
[    0.015502] Calibrating delay loop... 583.68 BogoMIPS (lpj=1167360)
[    0.055845] pid_max: default: 32768 minimum: 301
[    0.065197] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.079603] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.097734] rcu: Hierarchical SRCU implementation.
[    0.107843] smp: Bringing up secondary CPUs ...
[    2.194788] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    2.194800] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[    2.194813] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[    2.194914] CPU1 revision is: 0001992f (MIPS 1004Kc)
[    0.145017] Synchronize counters for CPU 1: done.
[    2.285843] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    2.285853] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[    2.285861] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[    2.285918] CPU2 revision is: 0001992f (MIPS 1004Kc)
[    0.239469] Synchronize counters for CPU 2: done.
[    2.376968] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    2.376978] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[    2.376987] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[    2.377048] CPU3 revision is: 0001992f (MIPS 1004Kc)
[    0.327069] Synchronize counters for CPU 3: done.
[    0.386680] smp: Brought up 1 node, 4 CPUs
[    0.399024] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.418312] futex hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.432146] pinctrl core: initialized pinctrl subsystem
[    0.444102] NET: Registered protocol family 16
[    0.475286] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[    0.496036] clocksource: Switched to clocksource GIC
[    0.507386] thermal_sys: Registered thermal governor 'step_wise'
[    0.507842] NET: Registered protocol family 2
[    0.528464] IP idents hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.543595] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.560338] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.575469] TCP bind hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.589641] TCP: Hash tables configured (established 2048 bind 2048)
[    0.602390] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.615281] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.629392] NET: Registered protocol family 1
[    0.637968] PCI: CLS 0 bytes, default 32
[    0.735983] 4 CPUs re-calibrate udelay(lpj = 1167360)
[    0.747494] workingset: timestamp_bits=14 max_order=16 bucket_order=2
[    0.765135] random: fast init done
[    0.773416] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.784910] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.806141] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.822666] mt7621_gpio 1e000600.gpio: registering 32 gpios
[    0.833992] mt7621_gpio 1e000600.gpio: registering 32 gpios
[    0.845314] mt7621_gpio 1e000600.gpio: registering 32 gpios
[    0.857176] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.873578] printk: console [ttyS0] disabled
[    0.882039] 1e000c00.uartlite: ttyS0 at MMIO 0x1e000c00 (irq = 19, base_baud = 3125000) is a 16550A
[    0.899958] printk: console [ttyS0] enabled
[    0.899958] printk: console [ttyS0] enabled
[    0.916512] printk: bootconsole [early0] disabled
[    0.916512] printk: bootconsole [early0] disabled
[    0.937833] mt7621-nand 1e003000.nand: Using programmed access timing: 31c07388
[    0.952680] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
[    0.965335] nand: Macronix MX30LF2G18AC
[    0.972974] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.988055] mt7621-nand 1e003000.nand: ECC strength adjusted to 4 bits
[    1.001087] mt7621-nand 1e003000.nand: Using programmed access timing: 21005134
[    1.015647] mt7621-nand 1e003000.nand: Using programmed access timing: 21005134
[    1.030208] Scanning device for bad blocks
[    1.604645] Bad eraseblock 446 at 0x0000037c0000
[    3.014983] Bad eraseblock 1551 at 0x00000c1e0000
[    3.286361] Bad eraseblock 1758 at 0x00000dbc0000
[    3.305267] Bad eraseblock 1766 at 0x00000dcc0000
[    3.671255] 6 fixed-partitions partitions found on MTD device mt7621-nand
[    3.684784] Creating 6 MTD partitions on "mt7621-nand":
[    3.695200] 0x000000000000-0x000000080000 : "u-boot"
[    3.706593] 0x000000080000-0x0000000e0000 : "u-boot-env"
[    3.718474] 0x0000000e0000-0x000000140000 : "factory"
[    3.729978] 0x000000140000-0x000000440000 : "kernel1"
[    3.741378] 0x000000440000-0x000000740000 : "kernel2"
[    3.752983] 0x000000740000-0x00000ff00000 : "ubi"
[    3.766349] libphy: Fixed MDIO Bus: probed
[    3.802483] libphy: mdio: probed
[    3.809195] mt7530 mdio-bus:1f: MT7530 adapts as multi-chip module
[    3.825773] mtk_soc_eth 1e100000.ethernet dsa: mediatek frame engine at 0xbe100000, irq 20
[    3.846779] NET: Registered protocol family 10
[    3.857197] Segment Routing with IPv6
[    3.864666] NET: Registered protocol family 17
[    3.873620] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    3.899664] 8021q: 802.1Q VLAN Support v1.8
[    3.909868] mt7530 mdio-bus:1f: MT7530 adapts as multi-chip module
[    3.931845] libphy: dsa slave smi: probed
[    3.940310] mt7530 mdio-bus:1f eth0 (uninitialized): PHY [dsa-0.0:00] driver [Generic PHY]
[    3.958261] mt7530 mdio-bus:1f eth1 (uninitialized): PHY [dsa-0.0:01] driver [Generic PHY]
[    3.976315] mt7530 mdio-bus:1f eth2 (uninitialized): PHY [dsa-0.0:02] driver [Generic PHY]
[    3.994207] mt7530 mdio-bus:1f eth3 (uninitialized): PHY [dsa-0.0:03] driver [Generic PHY]
[    4.012273] mt7530 mdio-bus:1f eth4 (uninitialized): PHY [dsa-0.0:04] driver [Generic PHY]
[    4.030272] mt7530 mdio-bus:1f: configuring for fixed/rgmii link mode
[    4.047924] DSA: tree 0 setup
[    4.055068] UBI: auto-attach mtd5
[    4.061721] ubi0: attaching mtd5
[    4.068498] mt7530 mdio-bus:1f: Link is Up - 1Gbps/Full - flow control off
[    6.587532] ubi0: scanning is finished
[    6.614055] ubi0: attached mtd5 (name "ubi", size 247 MiB)
[    6.625014] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    6.638702] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    6.652222] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    6.666085] ubi0: good PEBs: 1978, bad PEBs: 4, corrupted PEBs: 0
[    6.678217] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    6.692608] ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 23324735
[    6.710448] ubi0: available PEBs: 0, total reserved PEBs: 1978, PEBs reserved for bad PEB handling: 36
[    6.729009] ubi0: background thread "ubi_bgt0d" started, PID 467
[    6.731441] block ubiblock0_0: created from ubi0:0(rootfs)
[    6.751934] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    6.765816] hctosys: unable to open rtc device (rtc0)
[    6.782057] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    6.800700] Freeing unused kernel memory: 1260K
[    6.809742] This architecture does not have kernel memory protection.
[    6.822569] Run /sbin/init as init process
[    6.961655] SQUASHFS error: xz decompression failed, data probably corrupt
[    6.975369] SQUASHFS error: squashfs_read_data failed to read block 0x61422
[    7.011259] SQUASHFS error: xz decompression failed, data probably corrupt
[    7.024970] SQUASHFS error: squashfs_read_data failed to read block 0x61422
[    7.039002] Starting init: /sbin/init exists but couldn't execute it (error -5)
[    7.053610] Run /etc/init as init process
[    7.061766] Run /bin/init as init process
[    7.071906] Run /bin/sh as init process
[    7.233750] SQUASHFS error: xz decompression failed, data probably corrupt
[    7.247464] SQUASHFS error: squashfs_read_data failed to read block 0x61422
[    7.261506] Starting init: /bin/sh exists but couldn't execute it (error -5)
[    7.275591] Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[    7.303812] Rebooting in 1 seconds..

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

Источник

«errno 5 — ошибка ввода / вывода» при попытке установить

Сегодня я скачал Ubuntu для своего ноутбука. Он отлично работает с загрузочного USB, но когда я попытался установить его, я получил следующее сообщение об ошибке:

Я перепробовал все, чтобы установить его на свой ноутбук, но ничего не работает (также повторно загрузите ISO-образ).

8 ответов

На целевом жестком диске могут быть поврежденные сектора.

Проверять sda1 запустить том для плохих секторов в Linux fsck -c /dev/sda1 , Для езды C: в винде это должно быть chkdsk c: /f /r ,

по моему мнению chkdsk способ будет более подходящим, поскольку он будет перераспределять плохие блоки на жестком диске, в то время как Linux fsck просто помечает такие блоки как непригодные для использования в текущей файловой системе.

Цитата из man fsck.ext2

-c Эта опция вызывает e2fsck использовать badblocks(8) программа для сканирования устройства только для чтения с целью обнаружения любых поврежденных блоков. Если обнаружены какие-либо поврежденные блоки, они добавляются в индекс плохих блоков, чтобы предотвратить их размещение в файле или каталоге. Если эта опция указана дважды, то сканирование плохих блоков будет выполнено с использованием неразрушающего теста чтения-записи

У меня тоже была эта проблема при установке.

Целевой машиной стал совершенно новый ноутбук Asus K53e. Установочный образ был ubuntu-11.10-desktop-amd64.iso (64-разрядная версия). Я записал этот образ на компакт-диск. Errno 5. Записал его на загрузочную флешку. Errno 5 снова:(Я пытался 4 или 5 раз.

fsck сказал, что весь корневой раздел был в порядке (через 10 часов). memtest86 + сказал, что все 6 ГБ оперативной памяти тоже хорошо. Я попытался установить непосредственно при загрузке живого образа (Установить Ubuntu). Я также попробовал кнопку Try Ubuntu, затем запустил установку с живого рабочего стола. Опять Errno 5.

В итоге получается, что скачанный iso-файл был как-то устаревшим или неправильным. Ты можешь в это поверить!?

Вывод отличался от официального хеша Ubuntu (62fb5d750c30a27a26d01c5f3d8df459). Тогда я забыл свой разум. Я помню, что когда я загружал это изображение, мне показалось, что я был перенаправлен с ubuntu.com на зеркальный сайт, и я выбрал французский случайным образом, потому что мое ближайшее британское зеркало не работает. Должно быть, он немного устарел или что-то в этом роде. На самом деле, я сейчас помню, как видел записи, как это

на выходе dmesg (Я думаю) или где-то в /var/log при проверке после сбоя установки вывалил меня обратно на рабочий стол (Try Ubuntu).

В общем, убедитесь, что вы проверили хеш MD5 загруженного ISO-файла! (Я знаю. Я знаю. Я тоже редко проверяю!)

В любом случае, я снова скачал 64-битную Ubuntu 11.10 и на этот раз мне предложили в диалоговом окне Сохранить как вместо того, чтобы попросить выбрать зеркальный сайт. При загрузке контрольная сумма совпадает:) Установка в порядке:)

Ваш ISO либо поврежден, либо ваш носитель записи для установки был некорректным. Другими причинами для этого являются неисправность установочного носителя и т. Д., Но, по моему опыту, больше всего виновата запись для установки носителя.

Вы проверяли свой ISO после загрузки и перед записью на носитель?

Предполагая, что вы доверяете своему установочному носителю, запись является наиболее распространенной ошибкой в моем опыте, поэтому я записываю ее снова (если снова не удается, используя другой ящик или другой носитель). В любом случае первым шагом является проверка вашего ISO после обучения.

К вашему сведению: для неисправного установочного носителя вы увидите в журналах такие сообщения, как следующие, это результат того, что я описываю:

Вы можете проверить это, используя

который должен сообщать только сообщения о версии без ошибок.

Источник

ThinkPad T440p: problems with various Ubuntu flavours

I’ve got a few (serious) problems with Ubuntu and Thinkpad T440p, the biggest one being the inability to install any of the *buntu 14.04 (Trusty Tahr) flavours.

The main reason for testing the 14.04 Beta 1 and Beta 2, is flakyness of 13.10 on the same machine.

The Trusty Tahr live DVD starts to boot, but then hangs on «breathing logo».
If I switch to the virtual console in time, I can catch these messages:

(please note: I copied these by hand, because I have neither control over, nor interaction with OS — a very short while after Ctrl-Alt-F1 it starts to ignore the input from keyboard, so no dmesg output — sorry. I apologize for the typing mistakes as well)

[code]unsupported brightness interface — please contact ibm-acpi-devel (AT) lists.sourcefor ge.net[ /code]

After that, it spews loads of lines, presumably like these below (the ones I’m quoting here are among the last ones written, the rest scrolled off the screen too quickly):

[code][ 103.644587] SQUASHFS error: zlib decompression failed, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x1db34607
SQUASHFS error: zlib decompression failed, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x1d9b3558
SQUASHFS error: Unable to read fragment cache entry [1db980c3]
SQUASHFS error: Unable to read page, block 1db980c3, size 6623[/code]

Blocks of messages almost identical to the one above repeat quite a number of times, and finally, the followinng lines loop (endlessly?) very slowly:

[code][ 167.070261] INFO: rcu_sched detected stalls on CPUs/tasks: < 3>(detected by 1, t=15002 jiffies, g=2425, c=2424, q=0)
BUG: soft lockup — CPU#0 stuck for 22s! [ondemand:1990]
BUG: soft lockup — CPU#0 stuck for 22s! [ondemand:1990]
BUG: soft lockup — CPU#0 stuck for 22s! [ondemand:1990]
BUG: soft lockup — CPU#0 stuck for 22s! [ondemand:1990]
BUG: soft lockup — CPU#0 stuck for 23s! [ondemand:1990]
BUG: soft lockup — CPU#0 stuck for 22s! [ondemand: 1990][/ code]

This happened with the following 14.04 flavours: Ubuntu, Xubuntu, Kubuntu (the one I intend to use) and Ubuntu Gnome. I’ve tried to boot all of these from DVD, and one or two from an USB flash drive.

As a reference: I’ve had no troubles installing Kubuntu 13.10 from a DVD (and I did it more than once in last few days), so optical drive is not the culprit.

There are a few problems with 13.10 though (and I am giving the details in hope it can help resolving the installation issue stated above):

— WiFi — an Intel 7260 — keeps dropping out suddenly; This issue is frustratingly annoying, and I was hoping that Trusty will change things for the better.

— Brightness change using dual-function F-keys works rather awkwardly: the change is very slow if the button is kept pressed, and if one presses it repeatedly, 5-6 presses are needed for a change of 1 brightness level. This problem disappears if K13.10 is booted with acpi=off, but then I am unable to power the machine off. The only way to do it then is to force it by a «long press» of the power button.

— Bumblebee for Nvidia Optimus renders all file systems unusable/read-only and corrupts memory, finaly freezing the machine. I don’t need the rendering capabilities of Nvidia dicrete graphics, but I do need properly installed and usable CUDA toolkit.
— Sound is almost inaudible and does not respond to volume change neither through volume keys, nor through volume applet.

I should mention that preinstalled Win8 worked «as advertised», albeit for a very short time — I scraped it off of the HDD in favour of Kubuntu 13.10

My questions are:

1. Did anybody else here encounter such problems? — I found one or two similar posts on the net but none of suggested actions worked in my case.
2. Does any of this qualify for a bug-report? This is my 1st post ever, so I am not quite sure what/where/how.
3. Can anyone suggest a solution to any/all of these?

I could easily live with K13.10 if I could get rid of those quirks. After all. I installed the 13.10 on other computers I use regularly, and it works flawlessly.

If necessary, I can provide a more detailed hw-info and dmesg output from Kubuntu 13.10

I’d appreciate any help — Thanks!
Ino

Источник

error in repositories, reinstalled ubuntu and error on installation, says disk error but is new, I changed recently

Bug Description

I had problems with this machine since the begining, I installed W10 and the machine reestarted many times during the day, after that I installed Ubuntu and the PC worked well for a period of time, then some issues started, repositories, crashes, freezing screens etc. The last problem was the repositories I could not fix it and the printer and visualizing documents from the system could not be used, finally I decided to install again Ubuntu and I changed the Hard disk for the advice frome the software so, is a new one. I do not know if there is a problem on compatibility of my hardware components, BIOS or software.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSign ature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelMo dules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckR esult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 28 22:30:46 2020
InstallCmdLine: file=/cdrom/ preseed/ ubuntu. seed initrd= /casper/ initrd quiet splash — maybe-ubiquity
LiveMediaBuild: Ubuntu 20.04.1 LTS «Focal Fossa» — Release amd64 (20200731)
ProcEnviron:
LANGUAGE= es_MX.UTF- 8
PATH=(custom, no user)
XDG_RUNTIME_ DIR=
LANG=es_MX.UTF-8
LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

• Casper.txtEdit (1.5 KiB, text/plain; charset=»utf-8″)
• Dependencies.txtEdit (6.4 KiB, text/plain; charset=»utf-8″)
• ProcCpuinfoMinimal.txtEdit (1.3 KiB, text/plain; charset=»utf-8″)
• UbiquityDebug.txtEdit (10.7 KiB, text/plain; charset=»utf-8″)
• UbiquityDm.txtEdit (6.7 KiB, text/plain; charset=»utf-8″)
• UbiquityPartman.txtEdit (150.7 KiB, text/plain; charset=»utf-8″)
• UbiquitySyslog.txtEdit (199.1 KiB, text/plain; charset=»utf-8″)

Thank you for taking the time to report this issue and helping to make Ubuntu better.

This package failure looks like it was caused by bad ISO download, corrupted install media, or device failure. eg. look in the logs and you’ll see messages like these :-

Aug 29 03:27:57 ubuntu kernel: [ 330.817399] SQUASHFS error: zlib decompression failed, data probably corrupt
Aug 29 03:27:57 ubuntu kernel: [ 330.817401] SQUASHFS error: squashfs_read_data failed to read block 0x15a2cde2

Examining the information you have given us, this does not appear to be a useful bug report so I am incomplete/closing it, as it appears to be a bad ISO or faulty device (inc. bad write-to-device). If you believe I’m in error, please leave a comment explaining why and change the status back to ‘New’. I suggest you verify your ISO download, and use the ‘check disc for defects’ option to validate your media before install to ensure a good download & write.

From your description, I would verify you have a good & working correctly PSU (power supply), as components that are working correctly will still fail if not getting enough power.

I note you have «CasperMD5Check Result: pass» meaning your install media was checked & passed, yet still failed because of problems reading that already verified media. which can occur, if for example other components were using power at the time too, and insufficient power being supplied by PSU caused the issues.

Myself, I’d validate your hardware is all good, perform a cap-check, check SMART (hdd health), check RAM, and cap-check of motherboard, but also check your PSU/power supply, which maybe needs checking first (as other checks can give false results if PSU isn’t good).

Источник

squashfs corruption over time #236

Adi mentioned they are seeing corruption after leaving the bmc to run for about 54 hours

The text was updated successfully, but these errors were encountered:

From other reports the decompression fails causing the caches to be populated with error entries. The file system in flash is ok when upon reboot.

We can try dmesg or a log capture at the start of the corruption, or add instrumentation of the data being decompressed. Could be some error preventing the flash to be read or memory corruption maybe of the decompression workspace or cache pointing to data to be read.

On 21 Apr 2016 11:22 pm, «Milton D. Miller II» notifications@github.com
wrote:

From other reports the decompression fails causing the caches to be
populated with error entries. The file system in flash is ok when upon
reboot.

Where are the other reports? Can we collect them here please.

Have we seen it happen with development machines, or just those in the
datacentre?

We can try dmesg or a log capture at the start of the corruption, or add
instrumentation of the data being decompressed. Could be some error
preventing the flash to be read or memory corruption maybe of the
decompression workspace or cache pointing to data to be read.

The sigbus in the log I pasted suggests memory corruption beyond bad flash
data.

I received a report Monday. The claim was 12 systems were flashed Friday with PVT code and monitoring of the periodic (30s) ssh connect attempts was made and recorded.

Since we’ve had this kind of thing happen a few times I setup monitoring to keep an eye on the BMCs and it looks like 12 of them are down this morning, failing roughly in the order I reflashed them in (bottom of the rack, up).

All failed over time with age reported 2 — 12 hours (guessing this was time of last good report).

The system with the debug serial cable was proded with this result:

‘
SQUASHFS error: Unable to read metadata cache entry [16832a4]
SQUASHFS error: Unable to read inode 0x1648
barreleye login:
SQUASHFS error: Unable to read metadata cache entry [16832a4]
SQUASHFS error: Unable to read inode 0x1648
barreleye login:
SQUASHFS error: Unable to read metadata cache entry [16832a4]
SQUASHFS error: Unable to read inode 0x1648
barreleye login: rootSQUASHFS error: xz decompression failed, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x3137f4
SQUASHFS error: Unable to read data cache entry [3137f4]
SQUASHFS error: Unable to read page, block 3137f4, size da98
SQUASHFS error: Unable to read metadata cache entry [1684b1a]
‘

Note after root login the xz decompression report, which means the attempt to decompress a buffer failed. The rest are reporting cache access failures which could be attempts to read beyond the size of the file system or cached failures of a decompression failure.

Have we seen it happen with development machines, or just those in the datacentre?

I’ve only heard reports.

Something different about the usage we’ve been throwing at the BMCs is our monitoring system. It attempts to connect to port 22 on the BMC every 30 seconds, so it may be nobody is pushing this kind of usage at it.

instrumentation of the data being decompressed. Could be some error preventing the flash to be read or memory corruption maybe of the decompression workspace or cache pointing to data to be read.

The sigbus in the log I pasted suggests memory corruption beyond bad flash data.

That could just be due to a discard and attempted re-read of the program from the file system.
The discard would imply memory pressure

Источник