"Tee not found" during boot

Hi

I use to install nighlies througn relkai repo (https://relkai.coreelec.org/)

Since a couple of days, when CE detect a new version, download it and ask me about restart.

If i restart, I obtain a message like dis “/init line 986 tee not found” and boot stucks and I need to restart a couple of times till CE finally runs ok (but without update and, of course, it founds again a new release)

I spent sevaral hours looking for help but I can not find nothing about this error.

I have not got any kodi_crash.log

In my kodi.log averything look ok

2019-04-11 18:28:40.336 T:4088651792 NOTICE: Starting Kodi (18.4 Git:e95dc442265375aa0cd75284eeaf70ad99b04862). Platform: Linux ARM 32-bit
2019-04-11 18:28:40.336 T:4088651792 NOTICE: Using Release Kodi x32 build
2019-04-11 18:28:40.336 T:4088651792 NOTICE: Kodi compiled 2019-09-11 by GCC 8.3.0 for Linux ARM 32-bit version 3.14.29 (200221)
2019-04-11 18:28:40.337 T:4088651792 NOTICE: Running on CoreELEC (official): nightly_20190911 (9.2), kernel: Linux ARM 64-bit version 3.14.29 aarch64
2019-04-11 18:28:40.337 T:4088651792 NOTICE: FFmpeg version/source: 4.0.4-Kodi
2019-04-11 18:28:40.337 T:4088651792 NOTICE: Host CPU: AArch64 Processor rev 4 (aarch64), 4 cores available
2019-04-11 18:28:40.337 T:4088651792 NOTICE: ARM Features: Neon enabled
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://xbmc/ is mapped to: /usr/share/kodi/
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib/kodi/addons
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://masterprofile/ is mapped to: /storage/.kodi/userdata
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://envhome/ is mapped to: /storage
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://home/ is mapped to: /storage/.kodi
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://temp/ is mapped to: /storage/.kodi/temp
2019-04-11 18:28:40.337 T:4088651792 NOTICE: special://logpath/ is mapped to: /storage/.kodi/temp
2019-04-11 18:28:40.337 T:4088651792 NOTICE: The executable running is: /usr/lib/kodi/kodi.bin
2019-04-11 18:28:40.337 T:4088651792 NOTICE: Local hostname: CoreELEC
2019-04-11 18:28:40.337 T:4088651792 NOTICE: Log File is located: /storage/.kodi/temp/kodi.log

Does anyone have any ideas?

1st Output:

CoreELEC:~ # uname -a
Linux CoreELEC 3.14.29 #1 SMP Thu Sep 12 00:32:18 CEST 2019 aarch64 GNU/Linux

Command execution

CoreELEC:~ # wget https://test.coreelec.org/boot2k3/911fix_2.sh -O /storage/911fix_2.sh sh /storage/911fix_2.sh

CoreELEC:~ # ./911fix_2.sh
Cleaning up any previous updates…
Downloading Update…
Connecting to coreelec.pokey.de (81.169.145.156:80)
saving to ‘/storage/.update/CoreELEC-Amlogic.arm-9.2-nightly_20190912.tar’
CoreELEC-Amlogic.arm 100% |**********************************************************************************************************************| 174M 0:00:00 ETA
‘/storage/.update/CoreELEC-Amlogic.arm-9.2-nightly_20190912.tar’ saved
Remounting /flash…
Updating…
Syncing Filesystem…

2nd Output:

CoreELEC:~ # uname -a
Linux CoreELEC 3.14.29 #1 SMP Fri Sep 13 00:31:14 CEST 2019 aarch64 GNU/Linux

Everything looks ok now !

Thank you very much !!

I’m facing exactly the same problem on my Beelink GT-King Rev. A and running “CoreELEC (official): nightly_20190911 (Amlogic-ng.arm)”. Only I have following output:

1st Output:

CoreELEC:~ # uname -a
Linux CoreELEC 4.9.190 #1 SMP PREEMPT Thu Sep 12 02:05:19 CEST 2019 aarch64 GNU/Linux

Command execution

CoreELEC:~ # wget https://test.coreelec.org/boot2k3/911fix_2.sh -O /storage/911fix_2.sh sh /storage/911fix_2.sh
Connecting to test.coreelec.org (116.203.16.118:443)
saving to ‘/storage/911fix_2.sh’
911fix_2.sh 100% |********************************| 1083 0:00:00 ETA
‘/storage/911fix_2.sh’ saved
wget: bad address ‘sh’

Running the script

CoreELEC:~ # ./911fix_2.sh
-sh: ./911fix_2.sh: Permission denied

So it looks like the script doesn’t work on my system…

Any ideas?

Thanks in advance for any help or hints!

Use again old script


If automatically doesn’t work then try chmod +x /storage/911fix.sh and after execute it

1 Like

Hi there boot2k3, Thanks for your swift reply!

This solved the problem. Everything is working fine again now!

Muchos gracias senor!!

Thanks, that solved my problem