I have a problem whereby a remote BeagleBone device is taking hours to boot up. When it does, I don't see any problems in the kernel boot logs such as journalctl -b or journalctl -b -1
Without having physical access to the device over the serial interface, we can't see what is happening in the bootloader. Why is it that the U-Boot bootloader logs are not saved to somewhere on the flash memory or even RAM, or somewhere readable from when the kernel takes over? This would be extremely useful.
I understand that the file system is not mounted at that point, but surely there could be a solution? Or am I missing something that makes this procedure very difficult?