Ok I think the problem here is also that sda/sdb/sdc can be in any order…
If you reboot a few times, you should see them change.
The solution is probably a udev rule.
This goes further into hand-tuning the rule for that specific nuc/hardware combination…
I’m wondering if there is a manual workaround I can suggest.
- Flash a nuc flasher image on usb
- Edit the file
sda sdb both. This is to make the service fail to prevent flashing. So that we can select the right device to flash!
- Once device boots, manually check lsblk for which device is the ‘right’ one.
- Remount fs read-write,
mount -o remount,rw /
/etc/resin-init-flasher.conf and put in the right
- Start flasher service
systemctl start resin-init-flasher
The right solution would be to craft a udev rule.
And a more architectural solution for us would be to have some way to add more information via the dashboard/boot partition instead of the default priority order
INTERNAL_DEVICE_KERNEL = "nvme0n1 sda sdb mmcblk0 mmcblk1"
Perhaps a udev rule that injects via dashboard into config.json at the time of download.
We do have custom udev rules via config.json. I’m not sure if that works for flasher images.