Hey Julien! On Thu, Jan 23, 2020 at 09:18:54AM +0100, Julien Cristau wrote: >Package: installation-reports >Severity: normal > >Boot method: CD >Image version: >https://get.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.2.0+nonfree/amd64/iso-cd/firmware-10.2.0-amd64-netinst.iso >Date: January 22, 2020
... >Comments/Problems: > >I couldn't get guided partitioning to work. It would fail every time >complaining that the drive was probably too small or something like >that (I didn't save the exact message). This is a brand new machine, >sda is hw raid1 on 2x128G M.2 SATA modules. (Same thing happened on >another identical system so this is apparently reproducible.) Hmmm, odd. Something is picking up on those M2 modules multiple times, it seems. You sure they're SATA? $ grep /dev/nvme partman.log /lib/partman/init.d/30parted: IN: OPEN =dev=nvme0n1 /dev/nvme0n1 /lib/partman/init.d/30parted: IN: OPEN =dev=nvme1n1 /dev/nvme1n1 /lib/partman/init.d/30parted: IN: OPEN =dev=nvme2n1 /dev/nvme2n1 /lib/partman/init.d/30parted: IN: OPEN =dev=nvme3n1 /dev/nvme3n1 /lib/partman/init.d/30parted: IN: OPEN =dev=nvme4n1 /dev/nvme4n1 /lib/partman/init.d/30parted: IN: OPEN =dev=nvme5n1 /dev/nvme5n1 Path: /dev/nvme0n1 Path: /dev/nvme1n1 Path: /dev/nvme2n1 Path: /dev/nvme3n1 Path: /dev/nvme4n1 Path: /dev/nvme5n1 I don't know if that's the cause of the problem, but it looks suspect to me. -- Steve McIntyre, Cambridge, UK. st...@einval.com "Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters." -- Ignatios Souvatzis