Domotica - Home Automation Forum
https://www.domoticaforum.eu/
Looks like the install wasn't completed. You could try to run the update script from TheHogNL again, forcing a reinstall of version 4.18.8.mAiden wrote:Other error i got..
Inittab is fixed, thanks guys!
Code: Select all
INIT: Id "qtqt" respawning too fast: disabled for 5 minutes
Hi Toonz,Toonz wrote:Looks like the install wasn't completed. You could try to run the update script from TheHogNL again, forcing a reinstall of version 4.18.8.mAiden wrote:Other error i got..
Inittab is fixed, thanks guys!
Code: Select all
INIT: Id "qtqt" respawning too fast: disabled for 5 minutes
New resource file is available so should work...
Code: Select all
2018-07-25 08:38:42 (1.21 MB/s) - `update-rooted.sh' saved [19684/19684]
eneco-001-xxxxxx:~# sh update-rooted.sh -f 4.18.8
===================================================================================================================================================================
Welcome to the rooted Toon upgrade script. This script will try to upgrade your Toon using your original connection with Eneco. It will start the VPN if necessary.
Please be advised that running this script is at your own risk!
Version: 2.94 - ThehogNL - 19-7-2018
===================================================================================================================================================================
Only fixing files.
FIXING: Downloading resources.rcc TSC mod for this version 4.18.8.
FIXING: Now installing latest toonstore app. This fixes some files also.
Downloading http://files.domoticaforum.eu/uploads/Toon/apps//toonstore-1.1.4/toonstore_1.1.4-r0_qb2.ipk.
Package toonstore (1.1.5-r0) installed in root is up to date.
FIXING: Now installing latest busybox mod. This is necessary to enable console output again which is disabled in 4.10 by Eneco.
sh: 4: unknown operand
sh: 4: unknown operand
Custom busybox install not necessary for this firmware.
eneco-001-xxxxxx:~#
Code: Select all
eneco-001-xxxx:~# ./update-rooted.sh -f 4.18.8
-sh: ./update-rooted.sh: Permission denied
eneco-001-xxxx:~# chmod -x update-rooted.sh
eneco-001-xxxx:~# ./update-rooted.sh -f 4.18.8
-sh: ./update-rooted.sh: Permission denied
eneco-001-xxxxx:~#
.
Empty inittab can happen when an upgrade was unsuccessful and you did not check it before rebootingTheHogNL wrote:First read what the options are doing: https://github.com/IgorYbema/update-rooted
You are trying -f with a version number. That is invalid. -f is for fixing after an install and doesn't need a version number. You probably mean -v 4.18.8 (force version 4.18.
And the permissions denied is because you are now running it as "./update-script.sh" instead of "sh update-script.sh" (and you did make the file executable).
And an empty /etc/inittab .. how did you manage to do that?? It looks you are doing stuff on linux without understanding what you are doing
Good to hear you're up and running againmAiden wrote:I have fixed already, Toon start up normally. Thank you for the support.
.Update doesn't do anything with inittabmAiden wrote: Inittab goes empty indeed due to a failed update.
maybe mAiden is not very familiar with the vi editor ?Toonz wrote:Question remains why the inittab file can get empty in some cases....
Maybe true but he isn't the first one with this issue after updating. already seen 3-4 persons before who had exactly the same issue with inittab.aabre wrote:maybe mAiden is not very familiar with the vi editor ?Toonz wrote:Question remains why the inittab file can get empty in some cases....
It is possible that after (manually) editing the inittab file (to disable openvpn) you forget to 'sync' to the disk and reboot to soon. This will result in a corrupted or empty file.TerrorSource wrote:Maybe true but he isn't the first one with this issue after updating. already seen 3-4 persons before who had exactly the same issue with inittab.aabre wrote:maybe mAiden is not very familiar with the vi editor ?Toonz wrote:Question remains why the inittab file can get empty in some cases....
I do not like vi, indeed. Use much more often and prefer nano.aabre wrote:maybe mAiden is not very familiar with the vi editor ?Toonz wrote:Question remains why the inittab file can get empty in some cases....
Code: Select all
HCBv2 startables changed, writing /etc/inittab.
>> Done, scheduling reboot in 2 secs...
>> 2018-07-23 17:35:37 +0200 (pid 1453) executed
Code: Select all
printline "startables changed, writing $INITTAB_FILE."
echo "$INITTAB_CONTENT_NEW" > $INITTAB_FILE.new
# file was created ok? (non-zero size)
if [ -s $INITTAB_FILE.new ]
then
# force-rename removes old file, still more atomic than direct write
mv -f $INITTAB_FILE.new $INITTAB_FILE
# so repeated calls to it_writeifchanged() work:
INITTAB_CONTENT_ONDISK="$INITTAB_CONTENT_NEW"
else
printline "ERROR: Writing $INITTAB_FILE failed! Disk full/read-only?"
fi