This is not a “Jetson” issue. All Linux which uses a filesystem which is not synchronous (and all Windows and Mac which don’t use a synchronous filesystem) have damage to the filesystem by cutting power like that. They must be shut down properly. On your desktop PC, what would happen if you always turn it off by yanking the power cable in the middle of operation? Proper shutdown is not optional.
If you want more information, see:
https://forums.developer.nvidia.com/t/tuning-linux-on-jetson-nano-for-better-data-reliability-in-power-failure-scenario/252664/5
What you’ve described is either (A) damaging the filesystem beyond what journals can protect against, or (B) losing something the journal had to delete which just happens to be required to boot.
EDIT: fsck, when it works, loses content to do so. fsck is just a manual and more extreme version of a journal. The journal tends to keep basic structure working, but it doesn’t stop data loss.