Just migrated from M.2 HAT+ to PIMORONI NVMe Base DUO using
- OS NVMe in slot A
- new date NVMe in slot B
All working fine and fast.
Final test is always running the 'image-backup' script and it was failing now with
"Unsupported partition table type: "
Failure is raised due to the naming of the devices - slot A numbered '1' and slot B '0':This behaviour is causing the image-backup script to fail at line 230testing against nvme0n1p explicitly.
Switching the NVme slots - OS in B, data in A - fixed the issue, root partition is named 'nvme0n1p2' in this case and all is working excellent as usual.
Root cause is new hardware with new features and a bit unexpected behaviour in partition naming. Btw.: initial image backup of 64bit desktop installation to 2nd NVMe disc took 45 seconds !
- OS NVMe in slot A
- new date NVMe in slot B
All working fine and fast.
Final test is always running the 'image-backup' script and it was failing now with
"Unsupported partition table type: "
Failure is raised due to the naming of the devices - slot A numbered '1' and slot B '0':
Code:
pi@PI20241102:~ $ lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSnvme1n1 259:0 0 238,5G 0 disk nvme1n1p1 259:1 0 512M 0 part /boot/firmwarenvme1n1p2 259:2 0 238G 0 part /nvme0n1 259:3 0 931,5G 0 disk nvme0n1p1 259:4 0 931,5G 0 part Code:
if [[ "${ROOT_DEV}" = "/dev/mmcblk0p" || "${ROOT_DEV}" = "/dev/nvme0n1p" ]]; then ROOT_DEV="${ROOT_DEV:0:(${#ROOT_DEV} - 1)}"Switching the NVme slots - OS in B, data in A - fixed the issue, root partition is named 'nvme0n1p2' in this case and all is working excellent as usual.
Root cause is new hardware with new features and a bit unexpected behaviour in partition naming. Btw.: initial image backup of 64bit desktop installation to 2nd NVMe disc took 45 seconds !
Statistics: Posted by hgraus — Fri Nov 15, 2024 2:39 pm