I will have to set up a cable and debugging client, which I cant do immediately, but thanks for the suggestion.
However I have retried the process 3 more times and it fails the same way. Interestingly after doing the image the partitions which were there disappear after an SSD/NVMe HAT boot attempt (just the disk node is shown in lsblk). This means the next attempt at imaging fails. At this point dmsg reveals problems
[ 70.639975] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[ 70.639985] nvme nvme0: Does your device have a faulty power saving mode enabled?
[ 70.639989] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
[ 70.723978] nvme 0001:01:00.0: enabling device (0000 -> 0002)
[ 70.723993] nvme nvme0: Disabling device after reset failure: -19
[ 143.481239] Buffer I/O error on dev nvme0n1p1, logical block 0, async page read
[ 143.481425] EXT4-fs (nvme0n1p1): unable to read superblock
[ 186.657771] Buffer I/O error on dev nvme0n1p1, logical block 0, async page read
[ 186.661438] nvme nvme0: Identify namespace failed (-5)
Which I think translates as 'The NVMe controller which was there, has completely disappeared from the PCIe bus'
Is this faulty hardware (it is brand new) ?
Are there any NVMe incompatibility issues with Trixie/Pi 5
Any suggestions ?
However I have retried the process 3 more times and it fails the same way. Interestingly after doing the image the partitions which were there disappear after an SSD/NVMe HAT boot attempt (just the disk node is shown in lsblk). This means the next attempt at imaging fails. At this point dmsg reveals problems
[ 70.639975] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[ 70.639985] nvme nvme0: Does your device have a faulty power saving mode enabled?
[ 70.639989] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
[ 70.723978] nvme 0001:01:00.0: enabling device (0000 -> 0002)
[ 70.723993] nvme nvme0: Disabling device after reset failure: -19
[ 143.481239] Buffer I/O error on dev nvme0n1p1, logical block 0, async page read
[ 143.481425] EXT4-fs (nvme0n1p1): unable to read superblock
[ 186.657771] Buffer I/O error on dev nvme0n1p1, logical block 0, async page read
[ 186.661438] nvme nvme0: Identify namespace failed (-5)
Which I think translates as 'The NVMe controller which was there, has completely disappeared from the PCIe bus'
Is this faulty hardware (it is brand new) ?
Are there any NVMe incompatibility issues with Trixie/Pi 5
Any suggestions ?
Statistics: Posted by marthr — Thu Jan 01, 2026 3:36 pm