Thanks for the inputs which though seems to be sliding off topic. Could we please stay on the eMMC and the questions posted and not veer off to uboot and usb?
Whilst the TO data sheet does not specify the brand/type of the eMMC I came across some hint that it might be a SK hynix eMMC, is that correct?
After some search in the public domain it seems that producers of eMMC NAND chips are shy of providing such information. Related data sheets state all kinds of information but nothing related to live span expectancy which seems dependent on the wear levelling algorithm/method deployed in the controller
S.M.A.R.T . is apparently not available for eMMC.
mmc-utils is available in the TOS repo though the version (2016-06-28) seems to be lagging behind the upstream version (2018-03-27) [OpenWrt Wiki] package: mmc-utils.
getting info about the eMMC with mmc extcsd read /dev/mmcblk0p1 though fails with
ioctl: Operation not permitted
Could not read EXT_CSD from /dev/mmcblk0p1
Same happens with mmc status get /dev/mmcblk0p1
ioctl: Operation not permitted
Could not read response to SEND_STATUS from /dev/mmcblk0p1
Whilst offering some eMMC control/tuning it does not provide a health status. Micron though has patched mmc-utils to implement the HEALTH STATUS command
It would probably useful to have such for the TO, ideally integrated with Foris perhaps.
Aside from LXC I would reckon NextCloud and NAS stressing the eMMC unduly, notwithstanding Writing to mmcblk0p1 concerns - #2 by paja - SW help - Turris forum
But what about Pakon and other apps like the DNS resolvers?