SDM burn seems to fail

[timrowledge]

After the fun of the failing update problem I attempted a re-run of an SDM build & burn, reusing my scripts from last time.

The burn seems to fail; the output is - ` ./sdm-burn.sh Pi-Top2

• (( 1 == 1 ))
• sudo sdm --burn /dev/sda --host Pi-Top2 --expand-root /home/tim/Documents/SDM-files/2024-07-04-raspios-bookworm-arm64.img Start Burn

Burn /home/tim/Documents/SDM-files/2024-07-04-raspios-bookworm-arm64.img (6.1GB, 5.7GiB) to '/dev/sda'... Burn command line: /usr/local/bin/sdm --burn /dev/sda --host Pi-Top2 --expand-root /home/tim/Documents/SDM-files/2024-07-04-raspios-bookworm-arm64.img dd command: dd if=/home/tim/Documents/SDM-files/2024-07-04-raspios-bookworm-arm64.img of=/dev/sda status=progress bs=16M iflag=direct 6081740800 bytes (6.1 GB, 5.7 GiB) copied, 299 s, 20.3 MB/s 362+1 records in 362+1 records out 6081740800 bytes (6.1 GB, 5.7 GiB) copied, 299.435 s, 20.3 MB/s dd Copy completed Set new disk ID 453268eb on /dev/sda Disk identifier changed from 0x75d6d1b4 to 0x453268eb.

The partition table has been altered. Calling ioctl() to re-read partition table. Re-reading the partition table failed.: Device or resource busy The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8). Syncing disks.

Disk ID 453268eb set successfully with sfdisk ? Device /dev/sda is already mounted `

The symptom on the machine is that it simply sits there with a red led on the Pi. :-(