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.

Hi,

Am 25. Mai 2025 02:59:31 MESZ schrieb Sistemas Jaguar <sjaguar@proton.me>:


Holger

Exactly.

What is causing the 'disk full' condition?
Was installing Debian Trixie to a 128GB partition.

Please take a look at bug 1106496 where I attached the syslog.

Juan

ps I apologize for the duplicate, I wasn't sure how to add attachements to a bug report.

Hi,

Sistemas Jaguar <sjaguar@proton.me> wrote (Sun, 25 May 2025 17:00:01 +0000):

The installation logs show, that there is more than one harddisc existing:

	scsi 4:0:0:0: Direct-Access     NGFF 224 2 64GB SSD       1.00 PQ: 0 ANSI: 6
	sd 4:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)

	scsi 5:0:0:0: Direct-Access     KBG40ZNS 128G NVMe KIOXIA 1.00 PQ: 0 ANSI: 6
	sd 5:0:0:0: [sdb] 250069680 512-byte logical blocks: (128 GB/119 GiB)

And you installed to the 128GB nvme disc:

	kernel: [  307.385114]  nvme0n1: p1 p2 p3 p4

	kernel: [  387.326533] Adding 62499836k swap on /dev/nvme0n1p3.  Priority:-2 extents:1 across:62499836k SS
	kernel: [  387.906598] EXT4-fs (nvme0n1p4): mounted filesystem 3537befb-4fd0-473c-87af-724b5043ffff r/w with ordered data mode. Quota mode: none.

But that 128GB were devided into 4 partitions.
I cannot see from the logs how big the p4 partition for the root filesystem
was...

Maybe you should look more intensively in the partitioning step, what
size to choose...


Holger

Hello.

nvme0n1    is 1TB
nvme0n1p1  EFI partition (existing)
nvme0n1p2  Debian 12 installed (existing)
nvme0n1p3  Linux swap (existing)
nvme0n1p4  is where Debian 13 is being installed (128GB)

The installer went through after nvme0n1p4 was created by itself, so perhaps the issue is related to selecting an existing partition and using it as a root partition?

Juan

What do you mean ?

Was the partition empty or did you re-format it before installing ?

I think you understand things wrong:

According to your logs, the whole disk ("nvme0n1") has 128GB.
Those 128GB are divided into several parts.

Thus, nvme0n1p4 (the partition for the new Debian 13) does NOT have 128GB!
I think it's much smaller...


Holger

Just gave this another try to better document/understand the issue, this time using debian-testing-amd64-netinst.iso 2025-05-26.

Was unable to reproduce the issue, Trixie installed without a glitch in two systems with a similar setup.

So, thanks a bunch to you all.

Juan

Lets not jump to conclusions here, I am confident on the size of my internal drive and the partition being used.

Having triple checked the syslog, I can confirm that there is no single event in the whole log informing the size of nvme0n1.

The only events refering to the size of a drive are:

May 24 17:27:20 kernel: [    8.297330] scsi 5:0:0:0: Direct-Access     KBG40ZNS 128G NVMe KIOXIA 1.00 PQ: 0 ANSI: 6
May 24 17:27:20 kernel: [    8.302225] sd 5:0:0:0: [sdb] 250069680 512-byte logical blocks: (128 GB/119 GiB)
May 24 17:27:20 kernel: [    8.302840] sd 5:0:0:0: [sdb] Write Protect is off
May 24 17:27:20 kernel: [    8.302844] sd 5:0:0:0: [sdb] Mode Sense: 37 00 00 08
May 24 17:27:20 kernel: [    8.303435] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

The above is referring to 'sdb', not for 'nvme0'.

'sdb': external USB drive that was left plugged-in during the install for no particular reason.
'sda': external USB drive with the Trixie installer.

So it looks like the installer mistook 'sdb' as the install media:

May 24 17:29:09 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
May 24 17:29:09 cdrom-detect: Detected CD 'Auto-generated Debian GNU/Linux Live testing gnome 2025-05-19T02:19:02Z'
May 24 17:29:10 cdrom-detect: Detected CD with 'trixie' (trixie) distribution

Could this be the cause?

Juan