ZyXEL NSA325v2 how to install new Samba (Entware-ng) and where to find it

124»

All Replies

  • spin35
    spin35 Posts: 8 image  Freshman Member
    First Comment

    It looks like we have both "snatched defeat from the jaws of victory" as I too have lost the SMB2 and I'm also unable to login to the NAS through its web-interface. I appear to be able to SSH, but the nano editor that I installed from the random package is not there.

    I think that the system is failing to boot properly. I think the Zycel replacement is in the boot-up path bacause it is stored in /init.d and something is going wrong in the boot-up.

    I too have installed the Tweaks - perhaps that is the culprit.

    Perhaps Mijzelf may be able to throw some light on the problem?

  • Mijzelf
    Mijzelf Posts: 2,980 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary

    When booting, at some point the script /etc/init.d/zypkg.sh is called with argument 'startup'. (That is not the real name, I can't remember it at the moment, and I don't have a ZyXEL at hand, but you'll recognize it.)

    This script starts all installed packages by calling their startscript with argument 'startup'. This happens sequentially, and if one script is blocking, it will block the boot process. The Entware-ng startscript creates the /opt symlink, and the executes all executables in /opt/etc/init.d/ with argument 'start'. These scripts are blocking too.

    The sequence in which packages are started is a bit funny. Inside the ZYPKG_INFO.tgz file (or PKG_INFO.tgz) as it was downloaded from the vendor repository, there is a file ZYPKG_DEPS (PKG_DEPS?) which defines a sequence.

    /etc/init.d/zypkg.sh first start all installed packages which are mentioned in ZYPKG_DEPS in the given sequence. Then it will start all installed packaged which aren't started yet in alphabetical sequence. And finally it will call all startscripts in /usr/local/zy-pkgs/etc/init.d/ which aren't called yet in alphabetical sequence.

    (I have written some documentation here)

    If there is a blocking script, it might be visible in top. (The backend of Process Monitor uses '/bin/top -bn1').

    AFAIK Tweaks can not be the culprit, as in, I have never got feedback like this, in the 10~15 years the package exists.

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）