Oops, sorry, I meant ‘dmesg --follow’ (or ‘dmesg -w’ )
Normally the dmesg kernel log will be quiet after boot, and only give new messages when there’s hardware related changes, like pluging in or out a USB device, or the charger cable.
In my case the log was spamming several messages every second non-stop so it was very obvious
I’ve had a WD Blue SSD completely die in the past, but that could be coincidental. Then again I now have a WD Black nvme where the SMART error counter trickles upwards, so thanks for reminding me I need to change it xD
I’ve also had a Kingston SSD fail on writes, and a Samsung SSD where the error counter trickles upwards, so it might just be coincidental. I’ve also encountered a batch of very expensive Intel SSDs dying early due to a firmware bug, so… TLDR: WD Blue is probably fine :P
Regarding TimeShift, I’m assuming you’ve specified what it should back up, and where. By default it only backs up system files, basically everything outside your /home folder. And stores it on the root partition. That setup is great for recovering from bad system updates, but useless to protect against drive failure.
Assuming you have specified TimeShift to backup your home folder, to a separate physical drive, then twice per day sounds fine. Daily would probably also be fine. Just ask yourself how catastrophic would it really be to loose 1 day of changes?