After rebooting the router and several more attempts with different permutations, I was able to get a postboot.log file created. It contained the message:
Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
The Starlink router has the Google (8.8.8.8) DNS server coded into firmware, and this can not be changed.
From another Starlink connected computer, a traceroute to 8.8.8.8 takes over 16 seconds:
prompt$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 starlinkrouter (192.168.1.1) 4.752 ms 2.759 ms 1.792 ms
2 100.64.0.1 (100.64.0.1) 53.591 ms 87.076 ms 74.828 ms
3 172.16.249.0 (172.16.249.0) 68.357 ms 47.719 ms 58.042 ms
4 149.19.108.45 (149.19.108.45) 56.927 ms 47.613 ms 49.801 ms
5 undefined.hostname.localhost (206.224.64.63) 64.224 ms 49.324 ms 58.335 ms
6 * * *
7 dns.google (8.8.8.8) 52.999 ms 54.107 ms 56.544 ms
A similar traceroute to the Cloudflare DNS server (1.1.1.1) takes just over a second.
So what seems to be happening is that the Shake software is timing out when it tries to resolve a hostname address.
I’m able to see the postboot.log file on the Linux ext4 partition, after the fact, by installing the ext4fuse software on my Macintosh -but this does not allow writes to the filesystem, so I can not change the DNS server that the Shake software is using. Since this was to be a headless installation, I do not have access to an HDMI monitor and keyboard.
The solution (other than changing routers) seems to be to install the Shake software using a landline connection, change the DNS Server, and then install it at the Starlink location.
I’ve had help from Jeff Geerling on this; thank you! He’s made a good video about this initial Raspberry Shake experiences:
He also has a number of videos documenting his experiences with both Starlink and with Raspberry Pis (and other topics too). Check out his Youtube channel at:
https://www.youtube.com/c/JeffGeerling/videos