> 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:
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
