Boot method: USBImage version: https://saimei.ftp.acc.umu.se/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-gnome.iso
Date: 24-may-2025
Machine: HP ZBook 15 G4

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [o]
Detect network card:    [o]
Configure network:      [o]
Detect media:           [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:    [o]
Detect hard drives:     [o]
Partition hard drives:  [o]
Install base system:    [e]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Relevant (I believe) messages from the log:

May 24 23:34:00 anna-install: Installing squashfs-modules
May 24 23:34:00 anna[10875]: DEBUG: resolver (kernel-image-6.12.27-amd64-di): package doesn't exist (ignored)
May 24 23:34:00 anna[10875]: DEBUG: retrieving squashfs-modules-6.12.27-amd64-di 6.12.27-1
May 24 23:34:02 kernel: [  391.136946] squashfs: version 4.0 (2009/01/31) Phillip Lougher
May 24 23:34:02 kernel: [  391.142328] loop: module loaded
May 24 23:34:02 kernel: [  391.144514] loop0: detected capacity change from 0 to 6585320
May 24 23:34:07 base-installer: error: The tar process copying the live system failed (only 6 out of 276795 files have been copied, last file was ).
May 24 23:34:07 main-menu[804]: (process:10822): tar: write error: No space left on device
May 24 23:34:07 main-menu[804]: (process:10822): tar: write error: Broken pipe
May 24 23:34:07 main-menu[804]: WARNING **: Configuring 'live-installer' failed with error code 1

The following three methods failed:

  -) Plain text installer (Gnome live image),
  -) Calamares installer (Gnome live image),
  -) Plain text installer (debian-testing-amd64-netinst.iso)

The log included is from the plain text installer (Gnome live image).

Cheers.

Find a screenshot and syslog from both the graphical and text installers from debian-testing-amd64-netinst.iso.

Both installers fail somewhere between 'Detect media' and 'Load installer modules' steps.

Hi!

Those log messages are not showing a failure due to a missing kernel
image (that's ignored with a warning). Instead, the failure looks like
you've configured the system with a root filesystem that's too small,
Could you please try again and double-check the filesystem setup
please?

[ re-added CC to the BTS and the merged bugs ]

The issues here suggest that you've been writing to a filesystem that's
already had an installation (or maybe other data?) written to it. If
recreating the rootfs (and hence blanking it) fixes that, then I think
we've found the problem.

The daily builds hit this issue from time to as kernel versions are
updated, I'm afraid.