Yup.

debug.log in the bitcoin directory tells you a lot.  every restart of bitcoind will reset the log to a 10MB file size limit.  It grows as the bitcoind runs.  until the next restart of bitcoind.
this is in the nvme/bitcoin directory.  If you open a terminator window change to the /media/nvme/Bitcoin directory. you can follow the log live with the command "tail -f debug.log."  You are looking at constant data produced.  If the log is frozen you need to check the system monitor and make sure your bitcoind program is running.

There is also a log in Ckpool directory  on microsd that you can do the same to.  It shows the miner operation and data result updates.  Not as important.  It can show if the miner is frozen or not getting blockchain data.

I leave 2 terminator windows open monitoring these files realtime. 

debug.log shows when you startup the bitcoind and if you can watch the nvme activity( with an activity LED on the nvme drive) you may notice the bitcoind write the chainstate, also in the system monitor file read/write activity.  Takes several minutes.  the debug.log proves the chainstate is written complete when it reports the transaction data recorded success/fail during this event.