>>103438None of the false coloring experts in this thread mentioned dmesg, /sys, or /dev.
I can tell that the original output in the first screenshot is NOT dmesg because the timestamps do not conform to dmesg format, there are no kernel-to-userspace bus-messaging parameterization, and the messages' output are not preceded or followed by bus- and device-initialization identifiers except for generic filesystem notes.
Look at your device messages (dmesg) and filesystem journal and try to match timestamps (journald).
That was a simple BusyBox boitup sequence.
SMART is not applicable to SSDs or NVMes. This is because SMART and it's older predecessor, hdparm, are spinning-platter hard-drive daughterboard reporting mechanisms.