Cubietruck: remaining errors after filesystem-repair

[Wittenborg]

Hi!

 

I had serveral errors with my Cubietruck running Ubuntu 16.04 Vanilla Kernel. The system is installed on a hard-disc. There were some filesystem-error which fsck could repair. But I still have some errors.
 

root@cubianx:~# systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
● apparmor.service             loaded failed failed LSB: AppArmor initialization
● systemd-modules-load.service loaded failed failed Load Kernel Modules

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.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@cubianx:~#

 

root@cubianx:~# /lib/systemd/systemd-modules-load
Failed to find module 'gpio_sunxi'
Failed to find module 'sunxi-ir'
Failed to find module 'spi_sun7i'
Failed to find module 'ap6210'
root@cubianx:~#

 

I don't know what these errors mean and how to repair them.

 

[zador.blood.stained]

Did you switch kernel branch from legacy/default to mainline? These module names match default/legacy configuration, so you should remove them from /etc/modules

[Wittenborg]

Yes, I think i switched a time ago. So these modules are now integrated?

 

What about apparmor? Can I remove this?

[Wittenborg]

12 hours ago, Wittenborg said:

What about apparmor? Can I remove this?

No, I can't. When I try to remove this, mysql-server will also be removed.

 

I tried apt-get install --reinstall apparmor but I still got this error. Anybody knows how to repair apparmor? Maybe this is the source of the crashes up to 3 times a day.

[zador.blood.stained]

You can just disable apparmor service. Most likely it's missing some required kernel options to start properly, but it may as well be ignored.

[Wittenborg]

So these crashes didn't stop. Because I wasn't able to connect via SSH when the CT crashed and I didn't find something usefull in the syslog, I connected the CT to a monitor. The next crash happend 4,5 hours later, with this matrix-like screen:

 

 

Can anyone find the source of the problem?

 

On this device there is a nextcloud running on nginx and mysql and also a tvheadend server. The SAT-IP-tuner is connected via LAN.

tvheadend is HTS Tvheadend 4.1-2533~g80c52b2 compiled with:

 

AUTOBUILD_CONFIGURE_EXTRA=--disable-bintray_cache\ --disable-hdhomerun_static\ --disable-ffmpeg_static\ --disable-dvbscan ./Autobuild.sh