Willy Moto

You are right. I looked at a different RK3318 TV box with the build in your tree. The same service is loaded and in active status. root@boss-box:/etc# systemctl status smartmontools.service ● smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon Loaded: loaded (/lib/systemd/system/smartmontools.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-08-17 23:19:09 HKT; 1 day 17h ago Docs: man:smartd(8) man:smartd.conf(5) Main PID: 669 (smartd) Status: "Next check of 0 devices will start at 16:49:09" Tasks: 1 (limit: 999) Memory: 3.2M CGroup: /system.slice/smartmontools.service └─669 /usr/sbin/smartd -n Guess it's time to debug what's happening with the trunk build & my EMMC configuration.

My configuration /etc/smartd.conf seems to be the same as yours: DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner So my suspicion is this: Is EMMC considered to be a removable device ( -d removable ) or not? For USB storage or MicroSD card, the answer is obviously yes.

. Thanks for the clarification. I can see that the file size of sid-current-cli image close to double the size of your build. That probably explains it.

I found out the degraded service: It is smartmontools.service root@rk3318-h96max:/dev# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● smartmontools.service loaded "failed failed" Self Monitoring and Reporting Tech LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. Further investigation suggested that it appears the EMMC (where I installed Armbian) cannot be scanned by smartmontools. root@rk3318-h96max:/dev# systemctl status smartmontools.service × smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon Loaded: loaded (/lib/systemd/system/smartmontools.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2022-08-18 09:00:19 HKT; 22min ago Docs: man:smartd(8) man:smartd.conf(5) Process: 2333 ExecStart=/usr/sbin/smartd -n $smartd_opts (code=exited, status=17) Main PID: 2333 (code=exited, status=17) Status: "No devices to monitor" CPU: 194ms Aug 18 09:00:19 rk3318-h96max smartd[2333]: smartd 7.3 2022-02-28 r5338 [aarch64-linux-5.15.60-rockchip64] (local build) Aug 18 09:00:19 rk3318-h96max smartd[2333]: Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org Aug 18 09:00:19 rk3318-h96max smartd[2333]: Opened configuration file /etc/smartd.conf Aug 18 09:00:19 rk3318-h96max smartd[2333]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf Aug 18 09:00:19 rk3318-h96max smartd[2333]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices Aug 18 09:00:19 rk3318-h96max smartd[2333]: In the system's table of devices NO devices found to scan Aug 18 09:00:19 rk3318-h96max smartd[2333]: "Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting... " Aug 18 09:00:19 rk3318-h96max systemd[1]: smartmontools.service: Main process exited, code=exited, status=17/n/a Aug 18 09:00:19 rk3318-h96max systemd[1]: smartmontools.service: Failed with result 'exit-code'. Aug 18 09:00:19 rk3318-h96max systemd[1]: Failed to start Self Monitoring and Reporting Technology (SMART) Daemon. I did some google search, and this discussion suggested that Smartmontools does not support EMMC. Suppose I should just disable this service, if it's no use to EMMC where I installed Armbian.

@jock I was able to test the Nightly build from trunk on Armbian Github ( https://github.com/armbian/community ) as you revised in the first post yesterday. I noticed that in both cases of jammy-current-cli & sid-current-cli build, they are consistently slower than the stables build in your tree ( https://users.armbian.com/jock/rk3318/ ). You can notice it immediately when (1) trying to apt install stuff (slower at 'Building dependency tree' ), or when (2) navigating inside armbian-config when loading softy modules, or reconfiguring SSH daemon. In particular, the htop screen looks a little different and it shows something related to Systemd: degraded ( not shown in your build ) Is this slow behavior normal? Or maybe you did some magic with the build in your tree so that it's running noticeably faster?

Confirmed the Armbian system is still up & running after 3 days. Suffice to say it's working OK now after CPU voltage adjustment. @jock Thanks again.

@jock Thanks very much. You are the man. 👍👍👍 I tried the latest build with Kernel 5.18.10-rockchip64, and now the TV box is able to boot & run @ 1.3 Ghz CPU speed without freezing & hang-up. I did a complete EMMC erase and reinstallation though, just to prevent any mix of existing & newer configuration. I will observe for a few more days, but feel fairly confident that it should work this time.

@JMCC I think I have another one of these X88 Pro 10 TV box lying around (actually I managed to acquire quite a few RK3318/RK3328 TV boxes at a bargain sale store). It's of the model 4GB RAM + 128 EMMC storage. Do you still want it? UPDATE: It looks @Aapo Tahkola already posted a new firmware for X88 Pro 10 TV box. Would that help you?