Entware after reboot

[NeoDragon]

I have kind of the same problems. Transmission and minidlna won't start automaticly after reboot.
Fresh install of entware , no optware installed previously.
jffs scripts have been chmod and haven't changed anything to them beside adding swapon/swapoff.
If i start services-start manually after boot via putty, everything starts properly.
Any clue?

 

[daniebast]

Hi, i have the same problem, i update my rt-n66 from 376.47 Merlin fw to 378.51 and with the latest firmware after every reboot can't found entware folder, i tried to format usb, downgrade and upgrade Merlin firmware but not work. Now i restore the 376.47 version and all work fine.

 

[joegreat]

I have kind of the same problems. Transmission and minidlna won't start automaticly after reboot.

Hi, i have the same problem, i update my rt-n66 from 376.47 Merlin fw to 378.51 and with the latest firmware after every reboot can't found entware folder, i tried to format usb, downgrade and upgrade Merlin firmware but not work. Now i restore the 376.47 version and all work fine.

Hi,

After updating to .51 version I found out that the USB-Mount does not happen always at the same time.
Did you put the Entware start into the post-mount script? This will ensure that your Entware startup will happen after the USB drive is avaliable...

Here my post-mount script with the Entware start (in red) - do not forget to change the if command with the right mount-point of your USB drive(!):

#!/bin/sh
/usr/bin/logger -t START_$(basename $0) "started [$@]"
SCRLOG=/tmp/$(basename $0).log
touch $SCRLOG
echo "START_$(basename $0) started [$@]" >> $SCRLOG
#
if [ $1 = "/tmp/mnt/sdcard" ] # change the mount-point to your USB-drive!
then
mkdir /tmp/opt >> $SCRLOG
/bin/mount -o bind /tmp/mnt/sdcard/Optware /opt >> $SCRLOG
/opt/etc/init.d/rc.unslung start >> $SCRLOG
wait
fi
#
if [ "$?" -ne 0 ]
then
echo "Error in postmount execution! Script: $0" >> $SCRLOG
else
echo "Postmount execution OK. Script: $0" >> $SCRLOG
fi
/usr/bin/logger -t STOP_$(basename $0) "return code $?"
exit $?

By the way the commands in blue will create a nice post-mount.log file in the /tmp folder for analyzing afterwards what happened during boot time!

With kind regards
Joe

 

[daniebast]

Hi,

After updating to .51 version I found out that the USB-Mount does not happen always at the same time.
Did you put the Entware start into the post-mount script? This will ensure that your Entware startup will happen after the USB drive is avaliable...

Here my post-mount script with the Entware start (in red) - do not forget to change the if command with the right mount-point of your USB drive(!):


By the way the commands in blue will create a nice post-mount.log file in the /tmp folder for analyzing afterwards what happened during boot time!

With kind regards
Joe

Hi joegreat, thank you for your reply. No, i don't put the start command into the post mont script. Tomorrow i will try to reinstall latest firmware and write the command into the script.

Thanks a lot for your advice
Dani

 

[top4ek]

Have problems with entware too on n66u.
Install entware with script, opkg install mc and run wan-start script(its updates ip addres via yandex api). Everything works as usual...until reboot. So after reboot i see that jffs and /dev/sda (internal sd card) filesystem persist, but no opkg or mc commands are known. After reinstalling entware i see backup of old entware installation named "entware-old_2015-04-21_21-25".

Using 3.0.0.4.378.51_0

 

[Ken]

I had the problem as well on my ASUSWRT-MERLIN version 378.53@RT87U, no opkg command after reboot.
After some searching, I found out the problem was caused by the symbolic link in /tmp/opt. The original symbolic link was "opt -> /tmp/mnt/1.41.12-3255/asusware.arm/", and should be "opt -> /tmp/mnt/1.41.12-3255/entware.arm/"
And then I found out the problem is that the command "ln -sf $1/entware.arm /tmp/opt" in the path "/jffs/scripts/post-mount" isnt working.
I dont know why, but when I changed the command to "ln -nsf $1/entware.arm /tmp/opt" things come to work now.

 

[mreckhof]

I had the problem as well on my ASUSWRT-MERLIN version 378.53@RT87U, no opkg command after reboot.
After some searching, I found out the problem was caused by the symbolic link in /tmp/opt. The original symbolic link was "opt -> /tmp/mnt/1.41.12-3255/asusware.arm/", and should be "opt -> /tmp/mnt/1.41.12-3255/entware.arm/"
And then I found out the problem is that the command "ln -sf $1/entware.arm /tmp/opt" in the path "/jffs/scripts/post-mount" isnt working.
I dont know why, but when I changed the command to "ln -nsf $1/entware.arm /tmp/opt" things come to work now.

That fixed my problem. Manually linked it and all was good.