[SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

PeterP_swe · 2023-10-15 13:11:48

Hi,

I'm trying to install Arch on a new computer and I can't get the install to boot.

I put the new 10.14 ISO on a USB stick and after selecting "Arch Linux install medium (x86_64, UEFI)" from the GRUB menu I get:

Initramfs unpacking failed: XY-compressed data is corrupt
Failed to execute /init (error -2)

Things I've tried so far:

Verified that the USB stick works fine on my old computer and I get into the install prompt without errors.
Tried a few different USB slots and a different brand USB stick.
Ran memtest for a couple hours to make sure the RAM is fine.
Stripped the computer down to just a motherboard, cpu, 1 ram stick, a wired keyboard and an old reliable HDMI monitor.
Did a CMOS reset of the motherboard and went through the BIOS settings in search for something that might cause problems. I think that Secure Boot, Fast Boot, TPM and ASUS "boosts" should all be disabled now.
Tried an older arch ISO and the NetBoot ISO but got a similar errors there.
Tried a USB stick with Ubuntu but that one also crashes on boot.

The hardware:

ASUS Prime Z790-P WIFI D4
Intel i9-13900k
Corsair Vengeance LPX Black 16GB / 3200MHz / DDR4 / CL16

I did have Win11 running on this hardware a month ago, so I think it should be fine. I'm guessing it's either a configuration or compatibility thing I've missed.

I'm running out of ideas for how to troubleshoot this. Any ideas?

Last edited by PeterP_swe (2023-10-24 14:38:10)

c00ter · 2023-10-15 21:14:35

I did not see where you verified the signature. This step from the official Installation Guide: https://wiki.archlinux.org/title/Instal … _signature

PeterP_swe · 2023-10-16 07:09:58

You're right, I hadn't verified the signature.

I just ran a check on the ISO and it looks genuine:

[peterp@peterp-9900k-arch Downloads]$ pacman-key -v archlinux-2023.10.14-x86_64.iso.sig
==> Checking archlinux-2023.10.14-x86_64.iso.sig... (detached)
gpg: Signature made Sat 14 Oct 2023 09:02:37 AM CEST
gpg:                using EDDSA key 3E80CA1A8B89F69CBA57D98A76A5EF9054449A5C
gpg:                issuer "pierre@archlinux.org"
gpg: Note: trustdb not writable
gpg: Good signature from "Pierre Schmitz <pierre@archlinux.org>" [full]
gpg:                 aka "Pierre Schmitz <pierre@archlinux.de>" [unknown]

PeterP_swe · 2023-10-21 10:26:46

Is it reasonable to assume that I have a broken or incompatible motherboard?

If I'm going to get a new one, is there something special about compatibility I should keep in mind?

seth · 2023-10-21 14:40:59

Tried a USB stick with Ubuntu but that one also crashes on boot.

How do you write those usb keys?
See whether this gets you more output: https://wiki.archlinux.org/title/Genera … l_messages

Generally this is an IO issue, either the device or the bus are failing or the image was corrupted when written.

PeterP_swe · 2023-10-22 13:20:24

seth wrote:

How do you write those usb keys?

I used Gnome FILES to format the USB stick as etx4 and erase all data. Then I ran:

[peterp@peterp-9900k-arch Downloads]$ sudo dd bs=4M if=archlinux-2023.10.14-x86_64.iso of=/dev/disk/by-id/usb-SMI_USB_DISK_22031270050084-0\:0 conv=fsync oflag=direct status=progress

Then I unmounted the USB stick before unplugging and moving it to the new computer.

seth wrote:

See whether this gets you more output:

I added "debug" as a kernel parameter and got:

[ 0.787783 ]     archisodevice=UUID=2023-10-14-06-59-02-00
[ 0.788023 ] Failed to execute /init (error -2)
[ 0.788126 ] Run /sbin/init as init process
[ 0.788219 ]   with arguments:
[ 0.788314 ]     /sbin/init
[ 0.788403 ]   with environment:
[ 0.788489 ]     HOME=/
[ 0.788581 ]     TERM=1inux
[ 0.788671 ]     BOOT_IMAGE=/arch/boot/x86_64/umlinuz-linux
[ 0.788759 ]     archisobasedir-arch
[ 0.788844 ]     archisodevice=UUID=2023-10-14-06-59-02-00 
[ 0.788951 ] Run /etc/init as init process
[ 0.789035 ]   with arguments:
[ 0.789120 ]     /etc/init
[ 0.789199 ]   with environment:
[ 0.789275 ]     HOME=/
[ 0.789351 ]     TERM=1inux
[ 0.789433 ]     BOOT_IMAGE=/arch/boot/x86_64/umlinuz-linux 
[ 0.789517 ]     archisobasedir=arch
[ 0.789590 ]     archisodevice=UUID=2023-10-14-06-59-02-00
[ 0.789667 ] Run/bin/init as init process 
[ 0.789738 ]   with arguments:
[ 0.789808 ]     /bin/init
[ 0.789876 ]   with environment:
[ 0.789955 ]     HOME=/
[ 0.790017 ]     TERM=1inux
[ 0.790076 ]     BOOT_IMAGE=/arch/boot/x86_64/umlinuz-linux 
[ 0.790135 ]     archisobasedir=arch
[ 0.790198 ]     archisodevice=UUID=2023-10-14-06-59-02-00
[ 0.790271 ] Run /bin/sh as init process
[ 0.790332 ]   with arguments:
[ 0.790390 ]     /bin/sh
[ 0.790447 ]   with environment:
[ 0.790505 ]     HOME=/
[ 0.790563 ]     TERM=1inux
[ 0.790621 ]     BOOT_IMAGE=/arch/boot/x86_64/umlinuz-linux
[ 0.790687 ]     archisobasedir=arch
[ 0.790244 ]     archisodevice=UUID=2023-10-14-06-59-02-00
[ 0.790811 ] Kernel panic- not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/a
dmin-guide/init.rst for guidance,
[ 0.790929 ] CPU: 15 PID: 1 Comm: swapper/0 Not tainted 6.5.7-arch1-1 #1 0f5c742c3372ed589b7098a21a0ff406fc2e7c9c
[ 0.790997 ] Hardware name: ASUS System Product Name/PRIME 2790-P WIFI D4, BIOS 1402 09/11/2023
[ 0.791077 ] Call Trace:
[ 0.791145 ]  <TASK>
[ 0.791210 ]  dump_stack_lul+0x47/0x60
[ 0.791282 ]  panic+0x180/0x330
[ 0.791352 ]  ? pfx_kernel_init+0x10/0x10
[ 0.791420 ]  kernel_init+0x17d/0x1c0

It looks like I've missed some lines at the start of the log but it flashes past too quick for me to pause.

It says "Try passing init= option to kernel." so I did that and then I got:

[ 0.114888 ] Non-volatile memory driver v1.3
[ 0.411889 ] Linux agpgart interface v0.103
[ 0.432833 ] AMD-V1: AMD 10MMUZ functionality not available on this system -
This is not a bug.
[ 0.433212 ] ACPI: bus type drn_connector registered
[ 0.433918 ] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer
 .0 on minor 0
[ 0.434897 ] Console: switching to colour frame buffer device 128x18
[ 0.136175 ] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrnfb frame buffer device
[ 0.438424 ] ahci 0000:00:17.0: version 3.0
[ 0.138617 ] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf0 impl SATA mode
[ 0.438623 ] ahci 0000:00:17.0: flags: 64bit ncq sntf led clo only pio slum part ens deso sadn sds
[ 0.470172 ] scsi host0: ahci
[ 0.470313 ] scsi host1: ahci
[ 0.470482 ] scsi host2: ahci
[ 0.470768 ] scsi host3: ahci
[ 0.470949 ] scsi host4: ahci
[ 0.471207 ] scsi host5: ahci
[ 0.471551 ] scsi host6: ahci
[ 0.471817 ] scsi host?: ahci
[ 0.471927 ] atal: DUMMY
[ 0.472009 ] ata2: DUMMY
[ 0.472091 ] ata3: DUMMY
[ 0.472175 ] ata4: DUMMY
[ 0.172264 ] ata5: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02300 irq 127
[ 0.472357 ] ata6: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02380 irq 127
[ 0.172449 ] ata7: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02400 irq 127
[ 0.472541 ] ata8: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02480 irq 127
[ 0.172675 ] usbcore: registered neu interface driver usbserial_generic
[ 0.472763 ] usbserial: USB Serial support registered for generic
[ 0.172893 ] rtc_cnos rtc_cnos: BTC can wake from S4
[ 0.474135 ] rtc_cnos rtc_cnos: registered as rtco
[ 0.474822 ] rtc_cnos rtc_cnos: setting system clock to 2023-10-22T12:53:15 UTC (1697979195) 0.4749301 rtc cnos rtc_cnos: alarms up to one month, y3k, 111 bytes nuran
[ 0.476503 ] Intel pstate: Intel P-state driver initializing 0.478976) intel pstate: HUP enabled
[ 0.480305 ] ledtrig-cpu: registered to indicate activity on CPUS 0.4805301 hid: rau HID events driver (C) Jiri Kosina
[ 0.480651 ] intel pnc_core INT33A1:00: initialized
[ 0.480794 ] drop monitor: Initializing network drop monitor service 0.1862101 Initializing XFRM netlink socket
[ 0.486330 ] MET: Registered PF_INET6 protocol family 0.7861661 ataB: SATA link down (SStatus 4 SControl 300)
[ 0.787212 ] ata5: SATA link down (SStatus 4 SControl 300)
[ 0.787329 ] ata6: SATA link down (SStatus 4 SControl 300) 0.7874403 ata7: SATA link down (SStatus 4 SControl 300)
[ 2.955492 ] Freeing initrd memory: 80708K

seth wrote:

Generally this is an IO issue, either the device or the bus are failing or the image was corrupted when written

If I know that the motherboard is faulty or incompatible then I don't have a problem with getting a new one. I'm just worried that it's something I'm doing and that I'll have the same kind of problems with a new MB.

seth · 2023-10-22 13:28:45

Passing an empty init string won't help.

It looks like I've missed some lines at the start of the log but it flashes past too quick for me to pause.

Yes, unfortunately the crucial one.
You could record that on video - use a tripod. If you don't have a tripod, makeshift one out of two books or so.

Basic ascii art: -\_

frostschutz · 2023-10-22 13:39:13

PeterP_swe wrote:

I used Gnome FILES to format the USB stick as etx4 and erase all data. Then I ran:
[peterp@peterp-9900k-arch Downloads]$ sudo dd bs=4M if=archlinux-2023.10.14-x86_64.iso of=/dev/disk/by-id/usb-SMI_USB_DISK_22031270050084-0\:0 conv=fsync oflag=direct status=progress
Then I unmounted the USB stick before unplugging and moving it to the new computer.

Not sure if I understand you correctly, but "formatting USB stick as ext4" and then unmounting it after running dd, doing this would result in a corrupted USB.

Writing the iso would corrupt the mounted ext4 filesystem; and vice versa, umounting a mounted ext4 would write data back to the stick, thus corrupting the iso.

dd does not need a ext4 filesystem, and if you write iso image to device directly, the target device must not be mounted or otherwise in use at all.

If you want to get rid of old data before dd, you can use wipefs -a, don't format/mount as ext4.

You can validate your stick:

cmp archlinux.iso /dev/usbstick

should say nothing or EOF on archlinux.iso. If it reports any difference then the data was not written correctly, or altered after writing it.

If cmp does not find any difference and it still doesn't work, the iso file itself might be bad.

PeterP_swe · 2023-10-22 14:44:02

seth wrote:

Passing an empty init string won't help.
It looks like I've missed some lines at the start of the log but it flashes past too quick for me to pause.
Yes, unfortunately the crucial one.
You could record that on video - use a tripod. If you don't have a tripod, makeshift one out of two books or so.
Basic ascii art: -\_

I found another kernel parameter (boot_delay=N) that helps a bit, but I still need to figure out a way to record video. I'll try to figure it out something tomorrow.

seth · 2023-10-22 14:45:16

Please address frostschutz' question regarding the umount - when and why was the key mounted tbw?

PeterP_swe · 2023-10-22 14:55:08

frostschutz wrote:

PeterP_swe wrote:
I used Gnome FILES to format the USB stick as etx4 and erase all data. Then I ran:
[peterp@peterp-9900k-arch Downloads]$ sudo dd bs=4M if=archlinux-2023.10.14-x86_64.iso of=/dev/disk/by-id/usb-SMI_USB_DISK_22031270050084-0\:0 conv=fsync oflag=direct status=progress
Then I unmounted the USB stick before unplugging and moving it to the new computer.
Not sure if I understand you correctly, but "formatting USB stick as ext4" and then unmounting it after running dd, doing this would result in a corrupted USB.
Writing the iso would corrupt the mounted ext4 filesystem; and vice versa, umounting a mounted ext4 would write data back to the stick, thus corrupting the iso.
dd does not need a ext4 filesystem, and if you write iso image to device directly, the target device must not be mounted or otherwise in use at all.
If you want to get rid of old data before dd, you can use wipefs -a, don't format/mount as ext4.
You can validate your stick:
cmp archlinux.iso /dev/usbstick
should say nothing or EOF on archlinux.iso. If it reports any difference then the data was not written correctly, or altered after writing it.
If cmp does not find any difference and it still doesn't work, the iso file itself might be bad.

Formatting the stick was to clear out old data. I think wipefs only clears the partition table, not the actual data on the disk, but I can be wrong there. And that step is probably not necessary.

After writing the iso with dd I opened the gnome file browser and it probably auto mounted the USB stick then, so I clicked the "eject" button (unmount) before unplugging the stick from the computer.

I ran cmp to check the USB stick:

$ sudo cmp archlinux-2023.10.14-x86_64.iso /dev/sda
cmp: EOF on archlinux-2023.10.14-x86_64.iso after byte 847589376, in line 3275786

Last edited by PeterP_swe (2023-10-22 14:58:57)

PeterP_swe · 2023-10-23 15:21:44

Here's the log when using kernel parameters "debug boot_delay=50":

[ 201.969835] Monitor-Mwait will be used to enter C-3 state
[ 202.023167] ACPI: \_SB_.PR00: Found 3 idle states
[ 202.076501] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:0
0/input/inputo
[ 202.129834] ACPI: button: Sleep Button [SLPB]
[ 202.183167] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS: 00/PNPOCOC:0
0/input/input1 
[ 202.236500] ACPI: button: Power Button [PWRB]
[ 202.289834] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN: 00/input/inp
utz
[ 202.346502] ACPI: button: Power Button [PWRF]
[ 202.399833] thermal LNXTHERM:00: registered as thermal_zone0
[ 202.453167] ACPI: thermal: Thermal Zone [T200] (28 C)
[ 202.506500] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 202.559834] 00:01: ttyS0 at I/0 0x3f8 (irq = 4, base_baud = 115200) is a 1655
0A
[ 202.613167] hpet_acpi_add: no address or irqs in _CRS
[ 202.666500] Non-volatile memory driver v1.3
[ 202.719834] Linux agpgart interface u0.103
[ 202.779834] AMD-Vi: AMD IOMMUv2 functionality not available on this system -
This is not a bug
[ 202.833167] ACPI: bus type drm_connector registered 
[ 202.886500] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer
.0 on minor 0
[ 202.939834] Console: switching to colour frame buffer device 128x48
[ 203.049833] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[ 203.103167] ahci 0000:00:17.0: version 3.0
[ 203.119833] Freeing initrd memory: 80708K 
[ 203.156500] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf0 impl SATA mode
[ 203.209833] ahci 0000:00:17.0: flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds
[ 203.293167] scsi host0: ahci
[ 203.346500] scsi host1: ahci
[ 203.399833] scsi host2: ahci
[ 203.453167] scsi host3: ahci
[ 203.506500] scsi host4: ahci
[ 203.559833] scsi host5: ahci
[ 203.613167] scsi host6: ahci
[ 203.666500] scsi host?: ahci
[ 203.719833] ata1: DUMMY
[ 203.773167] ata2: DUMMY
[ 203.826500] ata3: DUMMY
[ 203.879833] ata4: DUMMY
[ 203.933166] ata5: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02300 irq 127
[ 203.986500] ata6: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02380 irq 127
[ 204.039833] ata7: SATA max UDMA/133 abar m204800x85f02000 port 0x85f02400 irq 127
[ 204.146502] usbcore: registered new interface driver usbserial_generic
[ 204.199833] usbserial: USB Serial support registered for generic
[ 204.253167] rtc_cmos rtc_cmos: RTC can wake from S4
[ 204.306500] rtc_cmos rtc_cmos: registered as rtc0
[ 204.359833] rtc_cmos rtc_cmos: setting system clock to 2023-10-23T13:32:22 UTC (1698067942)
[ 204.413167] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram
[ 204.459833] ata8: SATA link down (SStatus 4 SControl 300)
[ 204.466500] intel_pstate: Intel P-state driver initializing
[ 204.513166] ata6: SATA link down (SStatus 4 SControla300)
[ 204.519833] intel_pstate: HUP enabled
[ 204.566500] ata7: SATA link down (SStatus 4 SControl 300)
[ 204.573167] ledtrig-cpu: registered to indicate activity on CPUs
[ 204.619833] ata5: SATA link down (SStatus 4 SControl 300)
[ 204.626500] hid: raw HID events driver (C) Jiri Kosina
[ 204.679833] intel_pmc_core INT33A1:00: initialized
[ 204.733167] drop monitor: Initializing network drop monitor service
[ 204.789833] Initializing XFRM netlink socket
[ 204.843167] NET: Registered PF_INET6 protocol family
[ 204.899902] Segment Routing with IPv6
[ 204.953167] RPL Segment Routing with IPv6
[ 205.006500] In-situ OAM (IOAM) with IPv6
[ 205.059833] NET: Registered PF_PACKET protocol family
[ 205.116500] microcode: Microcode Update Driver: v2.2.
[ 205.169833] IPI shorthand broadcast: enabled 
[ 205.223167] sched_clock: Marking stable (195616647501, 9553185711)-> (223692960591, -18523127379)
[ 205.276500] registered taskstats version 1
[ 205.329833] Loading compiled-in X.509 certificates
[ 205.383167] Loaded X.509 cert 'Build time autogenerated kernel key: 31c4ce631efedf5ae9428b0eec9291d28851bf25'
[ 205.439833] zsuap: loaded using pool zstd/zsmalloc
[ 205.493167] Key type .fscrypt registered
[ 205.546500] Key type fscrypt-provisioning registered
[ 205.599833] integrity: Loading X.509 certificate: UEFI:db
[ 205.653166] integrity: Loaded X.509 cert 'ASUSTeK MotherBoard SW Key Certificate: da83b990422ebc8c441f8d8b039a65a2*
[ 205.706500] integrity: Loading X.509 certificate: UEFI :db
[ 205.759833] integrity: Loaded X.509 cert ASUSTeK Notebook SW Key Certificate: b8e581e4df77a5bb4282d5ccfc00c071'
[ 205.813166] integrity: Loading X.509 certificate: UEFI:db
[ 205.866500] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[ 205.919833] integrity: Loading X.509 certificate: UEFI:db
[ 205.973166] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[ 206.026500] integrity: Loading X.509 certificate: UEFI:db
[ 206.079833] integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a
63'
[ 206.133166] PM: Magic number: 11:609:534
[ 206.186500] tty ttyS14: hash matches [ 206.2398331 port seria 18250:0.13: hash matches
[ 206.293166] RAS: Correctable Errors collector initialized. Ε 206.346500] clk: Disabling unused clocks
[ 206.399833] Freeing unused decrypted memory: 2036K
[ 206.453166] Freeing unused kernel image (initmem) memory: 3384K 206.5065001 Write protecting the kernel read-only data: 30720k
[ 206.559833] Freeing unused kernel image (rodata/data gap) memory: 1380K
:: running hook [memdisk]
:: running hook [archiso]
:: running hook [archiso_loop_mnt]
:: running hook [archiso pxe common]
:: running hook [archiso_pxe_nbd]
:: running hook [archiso pxe http]
:: running hook [archiso_pxe_nfs]
Mounting "UUID-2023-10-14-06-59-02-00 to /run/archiso/bootmnt
Waiting 30 seconds for device /dev/disk/by-uuid/2023-10-14-06-59-02-00...
[ 207.283565] usb 2-6: new SuperSpeed USB device number 2 using xhci_hcd
[ 207.303511] usb 2-6: New USB device found, idVendor-090c, idProduct 2000, bcdDevice-11.00
[ 207.303564] usb 2-6: New USB device strings: Mfr:1, Product-2, Serial Number 3 207.3835981 usb 2-6: Product: USB DISK
[ 207.303620] usb 2-6: Manufacturer: SHI
[ 207.303615] usb 2-6: SerialNumber: 2203124t10N
[ 207.316344] usb-storage 2-6:1.0: USB Mass Storage device detected
[ 207.316487] usb-storage 2-6:1.0: Quirks match for vid 098c pid 2000: 800000
[ 207.316515] scsi host8: usb-storage 2-6:1.0 
[ 207.316548] usbcore: registered new interface driver usb-storage
[ 207.318254] usbcore: registered neu interface driver was
[ 207.423414] usb 1-11: neu high-speed USB device number 3 using xhci_hcd
[ 207.566024] usb 1-11: Neu USB device found, idVendor-05e3, idProduct-0608, bodDevice-60.90
[ 207.566088] usb 1-11: Neu USB device strings: Mfr-0, Product-1, SerialNumber-0
[ 207.566125] usb 1-11: Product: USB2.0 Hub
[ 207.568745] hub 1-11:1.0: USB hub found
[ 207.569199] hub 1-11:1.0: 4 parts detected
[ 207.693380] usb 1-13: new high-speed USB device number 4 using xhci_hcd
[ 207.835732] usb 1-13: New USB device found, idVendor-05e3, idProduct-0608, bodDevice-60.90
[ 207.835796] usb 1-13: New USB device strings: Mfr 8, Product-1, SerialNumber- 
[ 207.835832] usb 1-13: Product: USB2.0 Hub
[ 207.840485] hub 1-13:1.0: USB hub found
[ 207.842518] hub 1-13:1.0: 4 ports detected
[ 207.906715] usb 1-11.3: nou full-speed USB device number 5 using xhci_hcd
[ 207.999481] usb 1-11.3: New USB device found, idVendor-1838, idProduct-1361, bcdDevice= 0.fc 
[ 208.000681] usb 1-11.3: New USB device strings: Mfr-1, Product-2, SerialNumber-0
[ 208.001633] usb 1-11.3: Product: SteelSeries Sensei
[ 208.002567] usb 1-11.3: Manufacturer: La-VIEW Technology
[ 208.010657] input: La-VIEW Technology SteelSeries Sensel as devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.3/1-11.3:1.0/0003:1038:1361.0002/input/input4
[ 208.011801] hia-generic 0003:1038:1361.0082: input,hidraul: USB HID v1.00 House [La-VIEW Technology SteelSeries Senseil on usb-0000:00:14.0-11.3/inpute /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.3/1-11.3:1.1/0003:1038:1361.0003/input/input5
[ 208.013939] input: La-VIEW Technology SteelSeries Sensei Keyboard as 208.0702261 hid-generic 8003:1038:1361.0003: input,hiddev97,hidrau2: USB HID v1.00 Keyboard [La-VIEW Technology SteelSeries Senseil on usb-0000:00:14.0-11.3/input1
[ 208.120032] usb 1-14: new full-speed USB device number 6 using xhci_hcd
[ 208.262907] usb 1-14: New USB device found, idVendor-8087, idProduct-0026, bcdDevice 0.02 208.264565] usb 1-14: New USB device strings: Mfr-0, Product-0, SerialNumber=0
[ 208.333354] usb 1-11.4: new low-speed USB device number 7 using xhci_hcd
[ 208.423237] scsi 8:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 6
[ 208.126185] sd 8:0:0:0: [sda] 30310100 512-byte logical blocks: (15.5 GB/14.5 GIB)
[ 208:128369] sd 8:0:0:0: [sda] Write Protect is off
[ 208.129379] sd 8:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 208.431315] sd 8:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 208.437459]  sda: sdal sda2
[ 208.138787] sd 8:0:0:0: [sda] Attached SCSI removable disk
[ 208.449125] usb 1-11.4: New USB device found, idVendor-045e, idProduct-00db, bcdDevices 1.73
[ 208.150281] usb 1-11.4: New USB device strings: Mfr-1, Product-2, SerialNumber-0
[ 208.451301] usb 1-11.4: Product: Naturaly Ergononic Keyboard 4000
[ 208.452296] usb 1-11.4: Manufacturer: Microsoft
[ 208.492774] input: Microsoft Naturaly Ergonomic Keyboard 4000 as /devices/pc10000:00/0000:00:14.0/usb1/1-11/1-11.1/1-11.4:1.0/0003:015E:00DB.0001/input/input6
[ 208.550186] microsoft 0003:045E:00DB.0004: input,hidraw3: USB HID v1.11 Keyboard [Microsoft Natural Ergononic Keyboard 4000] on usb-0000:00:14.0-11.1/Inputo
[ 208.551635] input: Microsoft Naturaly Ergononic Keyboard 4000 as /devices/pc10000:00/0000:00:14.0/usb1/1-11/1-11.1/1-11.1:1.1/0003:045E:00DB.0005/input/Input?
[ 208.607169] microsoft 0003:045E:00DB.0005: input, hidraw4: USB HID v1.11 Device [Microsoft Naturaly Ergononic Keyboard 4000] on usb-0000:00:11.0-11.4/inputi
[ 208.760634] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 208.762305] ISO 9660 Extensions: RRIP_1991A
:: Device UUID-2023-10-14-06-59-02-00' mounted successfully.
:: Mounting /run/archiso/copytoram (tmpfs) filesysten, size-75%
:: Mounting /run/archiso/cowspace (tmpfs) filesystem, size=256M...
:: Copying rootfs image to RAM...
685MIB 0:00:06 I 103MIB/s] [======================>] 100%
done. 
[ 215.403792] loop: module loaded
[ 215.404458] loop0: detected capacity change from 0 to 1403944
:: Mounting '/dev/loop0' to '/run/archiso/airootfs'
[ 215.419849] squashfs: version 4.0 (2009/01/31) Phillip Lougher
:: Device '/dev/loop0' mounted successfully.
[ 215.139059] overlayfs: "xino" feature enabled using 2 upper inode bits.
:: running late hook [archiso_pxe_common]
:: running cleanup hook [udev]
[ 215.697141] SQUASHFS error: xz decompression failed, data probably corrupt
[ 215.697538] SQUASHFS error: Failed to read block 0x1346e113: -5
[ 215.697933] SQUASHFS error: Unable to read fragment cache entry [1346e113]
[ 215.698341] SQUASHFS error: Unable to read fragment cache entry [1346e113]
[ 215.698728] SQUASHFS error: Unable to read page, block 1346e113, size 5331c
/sbin/init: error while loading shared libraries: /usr/lib/libcap.so.2: cannot read file data: Input/output error
[ 215.699884] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 215.700272] CPU: 9 PID: 1 Comm: init Not tainted 6.5.7-arch1-1 #1 0f5c742c3372ed589b7098a21a0ff406fc2e7c9c
[ 215.700668] Hardware name: ASUS System Product Name/PRIME 2790-P WIFI D4, BIOS 1402 09/11/2023
[ 215.701062] Call Trace:
[ 215.701458]  <TASK>
[ 215.701846]  dump_stack_lvl+0x47/0x60
[ 215.702236]  panic+0x180/0x330.
[ 215.782620]  do_exit+0x9a7/0xb20
[ 215.703005]  ? vfs_writev+0x10b/0x1b0
[ 215.703414]  do_group_exit+0x31/0x80
[ 215.703831]  __x64_sys_exit_group+0x18/0x20
[ 215.704249]  do_syscall_64+0x50/0x90 
[ 215.704666]  ? exit_to_user_node_prepare+0x132/0x1f0
[ 215.705086]  ? syscall_exit_to_user_node+0x2b/0x40
[ 215.705502]  ? do_syscall_64+0x6c/0x90
[ 215.705917]  ? exc_page_fault+0x7f/0x180
[ 215.706335]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 215.706749] RIP: 0033:0x7fbf8c4556c5
[ 215.707164] Code: ba 01 00 00 00 b8 ca 00 00 00 of 05 c3 of 1f 84 00 00 6 f3 of 1e fa ba c7 00 00 00 eb 06 of 1f 44 00 00 f4 89 do of 05 <48> 3d 00 fe ff ff 76 f3 f7 d8 89 05 bb 2b 01 00 eb e9 66 of 1f 84
[ 215.707597] RSP: 002b:00007ffe2a9b2cd8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7
[ 215.708038] RAX: ffffffffffffffda RBX: 00007fbf8c45e2a8 RCX: 00007fbf8c4556c5
[ 215.708478] RDX: 00000000000000e7 RSI: 00007ffe2a9b23a0 RDI: 000000000000007f
[ 215.708913] RBP: 00007fbf8bbc7f26 R08: 00007ffe2a9b2ce8 809: 0000000000000000
[ 215.709342] R10: ffffffffffffffff B11: 0000000000000202 R12: 0000000000000005
[ 215.709769] R13: 0000000000000004 R14: 00007fbf8ba11000 R15: 0000000000000000
[ 215.710194]  </TASK>
[ 215.210718] Kernel Offset: 0x2ce00000 from Oxffffffff81000000 (relocation range: Oxffffffff80000000-0xffffffffbfffffff)
[ 215.711156] ---[ end Kernel panic - not syncing: Attempted to kill initt exitcode 0x00007f00 ]---

May contain some errors since OCR from video isn't great, but I've cleaned up what I found.

seth · 2023-10-24 07:43:37

:: Copying rootfs image to RAM...
685MIB 0:00:06 I 103MIB/s] [======================>] 100%
done.

[ 215.697538] SQUASHFS error: Failed to read block 0x1346e113: -5
…
/sbin/init: error while loading shared libraries: /usr/lib/libcap.so.2: cannot read file data: Input/output error

The device seems to be read fine and we've pre-established that the iso is written properly as well.
Also the error seems to have moved /bin/init decompressing, but /usr/lib/libcap.so.2 failing.

Leaves xz itself and there're actually multiple reports for it while succeeding w/ eg. zstd, but they seem all™ ARM/MIPS related
Another issue could be the RAM, try to lower the speed/timings in your UEFI/BIOS to the most conservative values and see whether that succeeds.

PeterP_swe · 2023-10-24 10:04:02

seth wrote:

Also the error seems to have moved /bin/init decompressing, but /usr/lib/libcap.so.2 failing.

I suspect that boot_delay=N adds a bit of non-determinism to the boot sequence.

seth wrote:

Leaves xz itself and there're actually multiple reports for it while succeeding w/ eg. zstd, but they seem all™ ARM/MIPS related

Not sure if that could be because of different architectures or buildtools. But it made me realize that I hadn't tried experimenting with CPU settings.

I tried disabling the E cores and then hyperthreading but it didn't make any difference.

seth wrote:

Another issue could be the RAM, try to lower the speed/timings in your UEFI/BIOS to the most conservative values and see whether that succeeds.

Unfortunately that was the first thing I tried. I've tried hours or memtest and remove all but 1 RAM stick. XMP is disabled and everything with the RAM and motherboard is set to the most conservative values.

Last edited by PeterP_swe (2023-10-24 10:12:24)

frostschutz · 2023-10-24 10:33:22

Did you verify the checksum of the iso as well? cmp only shows the number of newline characters and that matches, but a checksum would make sure.

In addition to memtest86+ you can also try memtest=17 kernel parameter, and 'memtester 8G' from a running Linux (as root).

Otherwise that leaves... bad ram... bad cpu... bad usb? Really no idea. It would be better if the iso was corrupt somehow, since that's the easiest to solve. Everything else points at hardware and that's where things get icky.

It could simply be an obscure bug / incompatibility / whatnot and in that case you could try another livecd; arch can be installed from any linux. https://wiki.archlinux.org/title/Instal … ting_Linux

But this would only help if this somehow is a specific issue with this particular ISO on your system... won't help if there is an issue in general.

Last edited by frostschutz (2023-10-24 10:33:47)

seth · 2023-10-24 13:01:15

Does it work if you boot w/ "nosmp acpi=off iommu=soft"?

PeterP_swe · 2023-10-24 14:22:44

seth wrote:

Does it work if you boot w/ "nosmp acpi=off iommu=soft"?

It does!

It works with only "nosmp" or "acpi=off" as well.

With only "iommu=soft" it still crashes.

seth · 2023-10-24 14:28:14

\o/

Does "maxcpus=1" also work?
Though you should™ be able to install the system this way and then skip the paramter later on, since you're longer relying on an xz compressed squashfs and the initramfs is zstd compresed

PeterP_swe · 2023-10-24 14:36:20

seth wrote:

\o/
Does "maxcpus=1" also work?
Though you should™ be able to install the system this way and then skip the paramter later on, since you're longer relying on an xz compressed squashfs and the initramfs is zstd compresed

Yes, that also works.

Now I have some reading up to do, then I'm going to install and configure the system.

Thank you!!

seth · 2023-10-24 14:37:22

So it's the multi-threaded xz decompression ("likely")

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2023-10-15 13:11:48

[SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#2 2023-10-15 21:14:35

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#3 2023-10-16 07:09:58

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#4 2023-10-21 10:26:46

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#5 2023-10-21 14:40:59

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#6 2023-10-22 13:20:24

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#7 2023-10-22 13:28:45

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#8 2023-10-22 13:39:13

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#9 2023-10-22 14:44:02

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#10 2023-10-22 14:45:16

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#11 2023-10-22 14:55:08

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#12 2023-10-23 15:21:44

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#13 2023-10-24 07:43:37

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#14 2023-10-24 10:04:02

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#15 2023-10-24 10:33:22

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#16 2023-10-24 13:01:15

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#17 2023-10-24 14:22:44

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#18 2023-10-24 14:28:14

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#19 2023-10-24 14:36:20

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

#20 2023-10-24 14:37:22

Re: [SOLVED] (10.14 iso) Initramfs unpacking failed: XY-compressed data...

Board footer