Allied Telesis firmware build (need help)

[KennethMcNutt]

I have very limited knowledge of Linux ... Let's just say if I can't find a step-by-step.. Well, I'm not able..
Sometimes even with one I still can't do it..

Like now..
My switch is down and Allied wants a service contract to send me a copy of the OE firmware that it came with..

But I have an open source builder for most all their stuff !!!! I just can't figure out why its not working..
It is set up to basically to be a one-command build.
But I get error after error as I go about fixing its issue..
I have added links to the network pkg for the x510.. below and the builder and my old firmware (that gives me "bad release header") and won't install

Allied Telesis firmware builder - Google Drive

drive.google.com

If someone could help me with it I would be grateful,
Thanks in advance, Ken
(the how-to I got with it.. )
This is a basic build howto.
-----------------------------

The enclosed tarball contains:
- chroot, this provides the toolchain
- buildsys, a tool for building a set of packages
- the cached download directory (dl) that buildsys usually generates
(with all the GPL code and some BSD code too).
- The wrapper scripts necessary for building.
- this README.txt

To build the main release
-------------------------

1] build requirements
1.1] to get a complete replica of an official release you will need
to scp or tftp "/pkg/network*.pkg" from your switch and place it into
the dl directory (this is our proprietary package (squashfs image)
containing the switch driver, protocols etc...).
To get access to this file you will need to create a shell script
on the device and activate it:
awplus#edit copy.sh
#insert the following text
cp /pkg/*.pkg /flash/

#Activate the script. This will copy the package to the flash directory
# (Ensure you have ample space left on your device)
awplus#activate copy.sh

Use your preferred method to copy the file off the switch.

1.2] Chroot

The build is done in a gentoo chroot. The chroot is provided as a
.deb package located at chroot/awplus-chroot6_20150223-1atl2_all.deb

On debian based systems, this can just be installed. If your Linux
system is not debian based, you can still install the chroot
manually using the following steps:

# Create a temporary working directory
$ mkdir tmpchroot
$ cd tmpchroot

# Extract the debian package into the temporary directory
$ ar x path/awplus-chroot6_20150223-1atl2_all.deb
# ls will show a control.tar.* and data.tar.gz

# Install the chroot. This will extract the data to /chroot/20170112d
$ sudo tar -C / -xSpf tmpchroot/data.tar.*

# Run the post-install script.
$ tar -zxf control.tar.gz ./postinst
$ sudo bash postinst

# Remove the temporary working directory
$ cd ..
$ rm -rf tmpchroot

Be careful not to manually delete the installed chroot as it mounts
your home directory inside when doing builds, so there is a danger
that you will accidentally erase your home directory. Make sure any
mounted directories are unmounted first.

1.3] Userchroot

# Build userchroot which allows using a chroot without being the root user:
$ cd scripts
$ gcc -o userchroot userchroot.c

# The chroot.py scripts expect userchroot to live in /usr/bin
$ sudo cp userchroot /usr/bin/

# Give userchroot suid privileges to allow it to work
$ sudo chmod u+s /usr/bin/userchroot

NOTE:
Toolchain patches and build options are in the chroot tarball, under
/chroot/20170112d/usr/local/portage
sys-libs/uclibc
sys-devel/binutils
sys-devel/gcc
sys-devel/gdb
sys-devel/insight
sys-kernel/linux-headers

NOTE: 20170112d is the date of the portage release file that the
chroot was created from.

1.4 Build scripts.
The scripts in the scripts directory are used to kick off the
build process. They need to be somewhere in your path.
Alternatively you can add the scripts directory to your path.

1.5 tftpboot directory
The build process attempts to mount the directory /tftpboot inside
the chroot to copy the release output to. If this directory doesn't
exist, you will need to create it.
$ sudo mkdir /tftpboot
$ sudo chmod a+rwx /tftpboot

2]

cd into the buildsys directory
buildsys x510 -- network=import

This should give you a file called "x510-5.4.8-$(whoami).rel"
which is a fully fledged release.

For other platforms, replace x510 with the name of the platform.
The names required to build various platforms can be derived from
the names of the .lua files in the root of the buildsys directory.

Have fun!

 

[KennethMcNutt]

Well, I seem to be getting further..
I was getting NOWHERE with Ubuntu or Mint..
I was just getting denied and unfound files left and right...
So I went RedHat ??? (Centos)
That actually worked it starts the build!!!
Now it seems i have a few more bugs to fix ..
I sure could use some help for someone who at LEAST knows a little more than I do...
Here is where I am at now..
host,protobuf-c: is referring to a url that is either linked wrong or outdated
something again I will have to learn quickly..
Here you can see my progress and my ignorance lol

[admin@localhost ~]$ mkdir tmpchroot
[admin@localhost ~]$ cd tmpchroot
[admin@localhost tmpchroot]$ ar x path/awplus-chroot6_20150223-1atl2_all.deb
ar: path/awplus-chroot6_20150223-1atl2_all.deb: No such file or directory
[admin@localhost tmpchroot]$ ar x path/awplus-chroot6_20150223-1atl2_all.deb
ar: path/awplus-chroot6_20150223-1atl2_all.deb: No such file or directory
[admin@localhost tmpchroot]$ ar
Usage: ar [emulation options] [-]{dmpqrstx}[abcDfilMNoPsSTuvV] [--plugin <name>] [member-name] [count] archive-file file...
ar -M [<mri-script]
commands:
d - delete file(s) from the archive
m[ab] - move file(s) in the archive
p - print file(s) found in the archive
q[f] - quick append file(s) to the archive
r[ab][f] - replace existing or insert new file(s) into the archive
s - act as ranlib
t - display contents of archive
x[o] - extract file(s) from the archive
command specific modifiers:
[a] - put file(s) after [member-name]
- put file(s) before [member-name] (same as )
[D] - use zero for timestamps and uids/gids
- use actual timestamps and uids/gids (default)
[N] - use instance [count] of name
[f] - truncate inserted file names
[P] - use full path names when matching
[o] - preserve original dates
- only replace files that are newer than current archive contents
generic modifiers:
[c] - do not warn if the library had to be created
- create an archive index (cf. ranlib)
- do not build a symbol table
[T] - make a thin archive
[v] - be verbose
[V] - display the version number
@<file> - read options from <file>
--target=BFDNAME - specify the target object format as BFDNAME
optional:
--plugin <p> - load the specified plugin
emulation options:
No emulation specific options
ar: supported targets: elf64-x86-64 elf32-i386 elf32-iamcu elf32-x86-64 a.out-i386-linux pei-i386 pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big elf32-little elf32-big plugin srec symbolsrec verilog tekhex binary ihex
[admin@localhost tmpchroot]$ ar x /home/admin/awplus-chroot6_20150223-1atl2_all.deb
ar: /home/admin/awplus-chroot6_20150223-1atl2_all.deb: No such file or directory
[admin@localhost tmpchroot]$ ar x /home/admin/chroot/awplus-chroot6_20150223-1atl2_all.deb
[admin@localhost tmpchroot]$ ls
control.tar.gz data.tar.xz debian-binary
[admin@localhost tmpchroot]$ sudo tar -C / -xSpf tmpchroot/data.tar.*

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

[sudo] password for admin:
tar: tmpchroot/data.tar.*: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[admin@localhost tmpchroot]$ cd ..
[admin@localhost ~]$ sudo tar -C / -xSpf tmpchroot/data.tar.*

edit visible password removed


[admin@localhost ~]$
[admin@localhost ~]$
[admin@localhost ~]$ tar -zxf control.tar.gz ./postinst
tar (child): control.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
[admin@localhost ~]$ tar -zxf control.tar.gz ./postinst
tar (child): control.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
[admin@localhost ~]$ ks
bash: ks: command not found...
[admin@localhost ~]$ ls
btools cmsg Downloads linux perl5 README.txt tmpchroot
buildsys Desktop drivers Music Pictures scripts Videos
chroot Documents easyipc openatlibs Public Templates
[admin@localhost ~]$ cd chroot
[admin@localhost chroot]$ tar -zxf control.tar.gz ./postinst
tar (child): control.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
[admin@localhost chroot]$ ls
awplus-chroot6_20150223-1atl2_all.deb
[admin@localhost chroot]$ cd ..
[admin@localhost ~]$ ls
btools cmsg Downloads linux perl5 README.txt tmpchroot
buildsys Desktop drivers Music Pictures scripts Videos
chroot Documents easyipc openatlibs Public Templates
[admin@localhost ~]$ cd tmpchroot
[admin@localhost tmpchroot]$ tar -zxf control.tar.gz ./postinst
[admin@localhost tmpchroot]$ sudo bash postinst
[sudo] password for admin:
[admin@localhost tmpchroot]$ cd ,,
bash: cd: ,,: No such file or directory
[admin@localhost tmpchroot]$ cd ..
[admin@localhost ~]$ rm -rf tmpchroot
[admin@localhost ~]$ cd scripts
[admin@localhost scripts]$ gcc -o userchroot userchroot.c
[admin@localhost scripts]$ sudo cp userchroot /usr/bin/
[admin@localhost scripts]$ sudo chmod u+s /usr/bin/userchroot
[admin@localhost scripts]$ env
XDG_VTNR=1
SSH_AGENT_PID=2869
XDG_SESSION_ID=1
HOSTNAME=localhost.localdomain
DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-2jWUjmkB3F,guid=05e7f3e7618c3d89f1fe08f36332ed38
IMSETTINGS_INTEGRATE_DESKTOP=yes
TERM=xterm-256color
SHELL=/bin/bash
XDG_MENU_PREFIX=gnome-
VTE_VERSION=5204
HISTSIZE=1000
PERL5LIB=/home/admin/perl5/lib/perl5:
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/987ce77a_9016_487d_aae3_11c0e0eb57c2
QTDIR=/usr/lib64/qt-3.3
QTINC=/usr/lib64/qt-3.3/include
PERL_MB_OPT=--install_base /home/admin/perl5
IMSETTINGS_MODULE=none
QT_GRAPHICSSYSTEM_CHECKED=1
USER=admin
LS_COLORS=rs=0:di=38;5;27:ln=38;5;51:mh=44;38;5;15i=40;38;5;11:so=38;5;13:do=38;5;5:bd=48;5;232;38;5;11:cd=48;5;232;38;5;3r=48;5;232;38;5;9:mi=05;48;5;232;38;5;15:su=48;5;196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;196;38;5;226:tw=48;5;10;38;5;16w=48;5;10;38;5;21:st=48;5;21;38;5;15:ex=38;5;34:*.tar=38;5;9:*.tgz=38;5;9:*.arc=38;5;9:*.arj=38;5;9:*.taz=38;5;9:*.lha=38;5;9:*.lz4=38;5;9:*.lzh=38;5;9:*.lzma=38;5;9:*.tlz=38;5;9:*.txz=38;5;9:*.tzo=38;5;9:*.t7z=38;5;9:*.zip=38;5;9:*.z=38;5;9:*.Z=38;5;9:*.dz=38;5;9:*.gz=38;5;9:*.lrz=38;5;9:*.lz=38;5;9:*.lzo=38;5;9:*.xz=38;5;9:*.bz2=38;5;9:*.bz=38;5;9:*.tbz=38;5;9:*.tbz2=38;5;9:*.tz=38;5;9:*.deb=38;5;9:*.rpm=38;5;9:*.jar=38;5;9:*.war=38;5;9:*.ear=38;5;9:*.sar=38;5;9:*.rar=38;5;9:*.alz=38;5;9:*.ace=38;5;9:*.zoo=38;5;9:*.cpio=38;5;9:*.7z=38;5;9:*.rz=38;5;9:*.cab=38;5;9:*.jpg=38;5;13:*.jpeg=38;5;13:*.gif=38;5;13:*.bmp=38;5;13:*.pbm=38;5;13:*.pgm=38;5;13:*.ppm=38;5;13:*.tga=38;5;13:*.xbm=38;5;13:*.xpm=38;5;13:*.tif=38;5;13:*.tiff=38;5;13:*.png=38;5;13:*.svg=38;5;13:*.svgz=38;5;13:*.mng=38;5;13:*.pcx=38;5;13:*.mov=38;5;13:*.mpg=38;5;13:*.mpeg=38;5;13:*.m2v=38;5;13:*.mkv=38;5;13:*.webm=38;5;13:*.ogm=38;5;13:*.mp4=38;5;13:*.m4v=38;5;13:*.mp4v=38;5;13:*.vob=38;5;13:*.qt=38;5;13:*.nuv=38;5;13:*.wmv=38;5;13:*.asf=38;5;13:*.rm=38;5;13:*.rmvb=38;5;13:*.flc=38;5;13:*.avi=38;5;13:*.fli=38;5;13:*.flv=38;5;13:*.gl=38;5;13:*.dl=38;5;13:*.xcf=38;5;13:*.xwd=38;5;13:*.yuv=38;5;13:*.cgm=38;5;13:*.emf=38;5;13:*.axv=38;5;13:*.anx=38;5;13:*.ogv=38;5;13:*.ogx=38;5;13:*.aac=38;5;45:*.au=38;5;45:*.flac=38;5;45:*.mid=38;5;45:*.midi=38;5;45:*.mka=38;5;45:*.mp3=38;5;45:*.mpc=38;5;45:*.ogg=38;5;45:*.ra=38;5;45:*.wav=38;5;45:*.axa=38;5;45:*.oga=38;5;45:*.spx=38;5;45:*.xspf=38;5;45:
GNOME_TERMINAL_SERVICE=:1.116
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SESSION_MANAGER=local/unix/tmp/.ICE-unix/2740,unix/unix:/tmp/.ICE-unix/2740
USERNAME=admin
GNOME_SHELL_SESSION_MODE=classic
PATH=/usr/lib64/qt-3.3/bin:/home/admin/perl5/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/admin/.local/bin:/home/admin/bin
MAIL=/var/spool/mail/admin
DESKTOP_SESSION=gnome-classic
QT_IM_MODULE=ibus
XDG_SESSION_TYPE=x11
PWD=/home/admin/scripts
XMODIFIERS=@im=ibus
LANG=en_US.UTF-8
GDM_LANG=en_US.UTF-8
KDEDIRS=/usr
GDMSESSION=gnome-classic
HISTCONTROL=ignoredups
DBUS_STARTER_BUS_TYPE=session
HOME=/home/admin
XDG_SEAT=seat0
SHLVL=2
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
PERL_LOCAL_LIB_ROOT=:/home/admin/perl5
XDG_SESSION_DESKTOP=gnome-classic
LOGNAME=admin
QTLIB=/usr/lib64/qt-3.3/lib
XDG_DATA_DIRS=/home/admin/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-2jWUjmkB3F,guid=05e7f3e7618c3d89f1fe08f36332ed38
LESSOPEN=||/usr/bin/lesspipe.sh %s
WINDOWPATH=1
XDG_RUNTIME_DIR=/run/user/1000
DISPLAY=:0
QT_PLUGIN_PATH=/usr/lib64/kde4/plugins:/usr/lib/kde4/plugins
XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME
PERL_MM_OPT=INSTALL_BASE=/home/admin/perl5
COLORTERM=truecolor
XAUTHORITY=/run/gdm/auth-for-admin-dIzsF6/database
_=/usr/bin/env
OLDPWD=/home/admin
[admin@localhost scripts]$ cd ..
[admin@localhost ~]$ cd /home/admin/bin
[admin@localhost bin]$ cd ..
[admin@localhost ~]$ cd chroot
[admin@localhost chroot]$ sudo mkdir /tftpboot
[sudo] password for admin:
[admin@localhost chroot]$ sudo chmod a+rwx /tftpboot
[admin@localhost chroot]$ cd ..
[admin@localhost ~]$ sudo mkdir /tftpboot
mkdir: cannot create directory ‘/tftpboot’: File exists
[admin@localhost ~]$ cd buildsys
[admin@localhost buildsys]$ buildsys x510 -- network=import
Failed to import static analysis
Something funny happened creating dl symlink, oh well
Traceback (most recent call last):
File "/home/admin/bin/buildsys", line 343, in <module>
if bs.build().wait() != 0:
File "/home/admin/bin/buildsys.py", line 114, in build
prog_env=self.bs_env, stdout=stdout, stderr=stderr).wait()
File "/home/admin/bin/chroot.py", line 73, in run
Chroot.check(chroot_path)
File "/home/admin/bin/chroot.py", line 26, in check
raise IOError, "Chroot.check: directory {0} does not exist".format(directory)
IOError: Chroot.check: directory /chroot/20170112d does not exist
[admin@localhost buildsys]$ buildsys x510 -- network=import
Failed to import static analysis

 

[KennethMcNutt]

Something funny happened creating dl symlink, oh well
['sudo', 'mount', '-t', 'proc', 'none', '/chroot/20170112d/proc']
[sudo] password for admin:
['sudo', 'mount', '-t', 'sysfs', 'none', '/chroot/20170112d/sys']
['sudo', 'mount', '-o', 'bind', '/dev', '/chroot/20170112d/dev']
['sudo', 'mount', '-t', 'devpts', 'none', '/chroot/20170112d/dev/pts']
['sudo', 'mount', '-o', 'rbind', '/home', '/chroot/20170112d/home']
['sudo', 'mount', '-o', 'bind', '/tftpboot', '/chroot/20170112d/tftpboot']
g++ -Wall -Werror -ggdb2 -Iinclude -D_GNU_SOURCE -c -o command.o command.cpp
g++ -Wall -Werror -ggdb2 -Iinclude -D_GNU_SOURCE -c -o interface.o interface.cpp
g++ -Wall -Werror -ggdb2 -Iinclude -D_GNU_SOURCE -c -o main.o main.cpp
g++ -Wall -Werror -ggdb2 -Iinclude -D_GNU_SOURCE -c -o run.o run.cpp
g++ -Wall -Werror -ggdb2 -Iinclude -D_GNU_SOURCE -c -o world.o world.cpp
g++ -o luabuild command.o interface.o main.o run.o world.o -llua -lm -lrt
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o include/buildsys.h.gch include/buildsys.h
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o extraction.o extraction.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o fetch.o fetch.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o graph.o graph.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o hash.o hash.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o main.o main.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o namespace.o namespace.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o packagecmd.o packagecmd.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o package.o package.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o run.o run.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o world.o world.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o dir/builddir.o dir/builddir.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o interface/builddir.o interface/builddir.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o interface/fetchunit.o interface/fetchunit.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -c -o interface/toplevel.o interface/toplevel.cpp
g++ -std=c++11 -Wall -Werror -ggdb2 -pthread -Iinclude -D_GNU_SOURCE -llua -lm -lrt -pthread -lssl -lcrypto -o buildsys extraction.o fetch.o graph.o hash.o main.o namespace.o packagecmd.o package.o run.o world.o dir/builddir.o interface/builddir.o interface/fetchunit.o interface/toplevel.o -llua -lm -lrt -pthread -lssl -lcrypto
BuildSys: Buildsys (C++ version)
BuildSys: Built: 13:24:09 Sep 27 2022
host,host.lua: Processing (host.lua)
host,protobuf: Processing (./package/protobuf/protobuf.lua)
host,host/env: Processing (./package/host/env/env.lua)
host,protobuf-c: Processing (./package/protobuf-c/protobuf-c.lua)
host,cmsg: Processing (./package/cmsg/cmsg.lua)
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
host,awp-build-tools: Processing (./package/awp-build-tools/awp-build-tools.lua)
host,makedevs: Processing (./package/makedevs/makedevs.lua)
host,intltool: Processing (./package/intltool/intltool.lua)
host,grpc-gateway: Processing (./package/grpc-gateway/grpc-gateway.lua)
host,qemu-img: Processing (./package/qemu-img/qemu-img.lua)
host,python/host: Processing (./package/python/host/host.lua)
host,intltool: Build Thread
host,intltool: Building (0 others running)
host,host/env: Build Thread
host,host/env: Building (1 others running)
host,host/env: Hash: fdaa0224892bec7dfff4997cb2ccb64701a9d86629c74643e1dfb84506e42f9a
host,intltool: --2022-09-27 13:24:16-- https://launchpad.net/intltool/trunk/0.51.0/+download/intltool-0.51.0.tar.gz
host,intltool: Resolving launchpad.net... failed: Connection refused.
host,intltool: wget: unable to resolve host address ‘launchpad.net’
Path: dl
Arg[0] = 'wget'
Arg[1] = 'https://launchpad.net/intltool/trunk/0.51.0/+download/intltool-0.51.0.tar.gz'
Arg[2] = '-Ointltool-0.51.0.tar.gz'
host,host/env: Extracting ...
host,host/env: Extracting sources and patching
terminate called after throwing an instance of 'buildsys::CustomException'
[admin@localhost buildsys]$ buildsys x510 -- network=import
Failed to import static analysis
Something funny happened creating dl symlink, oh well
make: `luabuild' is up to date.
make: `buildsys' is up to date.
BuildSys: Buildsys (C++ version)
BuildSys: Built: 13:24:09 Sep 27 2022
host,host.lua: Processing (host.lua)
host,protobuf: Processing (./package/protobuf/protobuf.lua)
host,host/env: Processing (./package/host/env/env.lua)
host,protobuf-c: Processing (./package/protobuf-c/protobuf-c.lua)
host,cmsg: Processing (./package/cmsg/cmsg.lua)
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
host,awp-build-tools: Processing (./package/awp-build-tools/awp-build-tools.lua)
host,makedevs: Processing (./package/makedevs/makedevs.lua)
host,intltool: Processing (./package/intltool/intltool.lua)
host,grpc-gateway: Processing (./package/grpc-gateway/grpc-gateway.lua)
host,qemu-img: Processing (./package/qemu-img/qemu-img.lua)
host,python/host: Processing (./package/python/host/host.lua)
host,intltool: Build Thread
host,intltool: Building (0 others running)
host,host/env: Build Thread
host,host/env: Building (1 others running)
host,intltool: Hash: 787e89c0757e29aeb12192f02b8a99b4ddc8efe46dd8fb502e2a43de8b65e73c
host,host/env: Hash: fdaa0224892bec7dfff4997cb2ccb64701a9d86629c74643e1dfb84506e42f9a
host,intltool: Extracting ...
host,intltool: Extracting sources and patching
host,host/env: Extracting ...
host,host/env: Extracting sources and patching
host,host/env: Building ...
host,host/env: Generating staging directory ...
host,intltool: tar: This does not look like a tar archive
host,intltool:
host,intltool: gzip: stdin: unexpected end of file
host,intltool: tar: Child returned status 1
host,intltool: tar: Error is not recoverable: exiting now
Path: /home/admin/buildsys/output/host/intltool/work
Arg[0] = 'tar'
Arg[1] = 'xf'
Arg[2] = '/home/admin/buildsys/dl/intltool-0.51.0.tar.gz'
terminate called after throwing an instance of 'buildsys::CustomException'
[admin@localhost buildsys]$ buildsys x510 -- network=import
Failed to import static analysis
Something funny happened creating dl symlink, oh well
make: `luabuild' is up to date.
make: `buildsys' is up to date.
BuildSys: Buildsys (C++ version)
BuildSys: Built: 13:24:09 Sep 27 2022
host,host.lua: Processing (host.lua)
host,protobuf: Processing (./package/protobuf/protobuf.lua)
host,host/env: Processing (./package/host/env/env.lua)
host,protobuf-c: Processing (./package/protobuf-c/protobuf-c.lua)
host,cmsg: Processing (./package/cmsg/cmsg.lua)
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
host,awp-build-tools: Processing (./package/awp-build-tools/awp-build-tools.lua)
host,makedevs: Processing (./package/makedevs/makedevs.lua)
host,intltool: Processing (./package/intltool/intltool.lua)
host,grpc-gateway: Processing (./package/grpc-gateway/grpc-gateway.lua)
host,qemu-img: Processing (./package/qemu-img/qemu-img.lua)
host,python/host: Processing (./package/python/host/host.lua)
host,intltool: Build Thread
host,intltool: Building (0 others running)
host,host/env: Build Thread
host,host/env: Building (1 others running)
host,host/env: Hash: fdaa0224892bec7dfff4997cb2ccb64701a9d86629c74643e1dfb84506e42f9a
host,intltool: --2022-09-27 13:40:30-- https://launchpad.net/intltool/trunk/0.51.0/+download/intltool-0.51.0.tar.gz
host,intltool: Resolving launchpad.net... failed: Connection refused.
host,intltool: wget: unable to resolve host address ‘launchpad.net’
Path: dl
Arg[0] = 'wget'
Arg[1] = 'https://launchpad.net/intltool/trunk/0.51.0/+download/intltool-0.51.0.tar.gz'
Arg[2] = '-Ointltool-0.51.0.tar.gz'
terminate called after throwing an instance of 'buildsys::CustomException'
[admin@localhost buildsys]$ buildsys x510 -- network=import
Failed to import static analysis
Something funny happened creating dl symlink, oh well
make: `luabuild' is up to date.
make: `buildsys' is up to date.
BuildSys: Buildsys (C++ version)
BuildSys: Built: 13:24:09 Sep 27 2022
host,host.lua: Processing (host.lua)
host,protobuf: Processing (./package/protobuf/protobuf.lua)
host,host/env: Processing (./package/host/env/env.lua)
host,protobuf-c: Processing (./package/protobuf-c/protobuf-c.lua)
host,cmsg: Processing (./package/cmsg/cmsg.lua)
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
host,awp-build-tools: Processing (./package/awp-build-tools/awp-build-tools.lua)
host,makedevs: Processing (./package/makedevs/makedevs.lua)
host,intltool: Processing (./package/intltool/intltool.lua)
host,grpc-gateway: Processing (./package/grpc-gateway/grpc-gateway.lua)
host,qemu-img: Processing (./package/qemu-img/qemu-img.lua)
host,python/host: Processing (./package/python/host/host.lua)
host,intltool: Build Thread
host,intltool: Building (0 others running)
host,host/env: Build Thread
host,host/env: Building (1 others running)
host,intltool: Hash: 787e89c0757e29aeb12192f02b8a99b4ddc8efe46dd8fb502e2a43de8b65e73c
host,host/env: Hash: fdaa0224892bec7dfff4997cb2ccb64701a9d86629c74643e1dfb84506e42f9a
host,intltool: Extracting ...
host,intltool: Extracting sources and patching
host,host/env: Building ...
host,host/env: Generating staging directory ...
host,intltool: tar: This does not look like a tar archive
host,intltool:
host,intltool: gzip: stdin: unexpected end of file
host,intltool: tar: Child returned status 1
Path: /home/admin/buildsys/output/host/intltool/work
Arg[0] = 'tar'
Arg[1] = 'xf'
Arg[2] = '/home/admin/buildsys/dl/intltool-0.51.0.tar.gz'
host,intltool: tar: Error is not recoverable: exiting now
terminate called after throwing an instance of 'buildsys::CustomException'
[admin@localhost buildsys]$ git
usage: git [--version] [--help] [-c name=value]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
<command> [<args>]

The most commonly used git commands are:
add Add file contents to the index
bisect Find by binary search the change that introduced a bug
branch List, create, or delete branches
checkout Checkout a branch or paths to the working tree
clone Clone a repository into a new directory
commit Record changes to the repository
diff Show changes between commits, commit and working tree, etc
fetch Download objects and refs from another repository
grep Print lines matching a pattern
init Create an empty Git repository or reinitialize an existing one
log Show commit logs
merge Join two or more development histories together
mv Move or rename a file, a directory, or a symlink
pull Fetch from and merge with another repository or a local branch
push Update remote refs along with associated objects
rebase Forward-port local commits to the updated upstream head
reset Reset current HEAD to the specified state
rm Remove files from the working tree and from the index
show Show various types of objects
status Show the working tree status
tag Create, list, delete or verify a tag object signed with GPG

'git help -a' and 'git help -g' lists available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
[admin@localhost buildsys]$ git
usage: git [--version] [--help] [-c name=value]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
<command> [<args>]

The most commonly used git commands are:
add Add file contents to the index
bisect Find by binary search the change that introduced a bug
branch List, create, or delete branches
checkout Checkout a branch or paths to the working tree
clone Clone a repository into a new directory
commit Record changes to the repository
diff Show changes between commits, commit and working tree, etc
fetch Download objects and refs from another repository
grep Print lines matching a pattern
init Create an empty Git repository or reinitialize an existing one
log Show commit logs
merge Join two or more development histories together
mv Move or rename a file, a directory, or a symlink
pull Fetch from and merge with another repository or a local branch
push Update remote refs along with associated objects
rebase Forward-port local commits to the updated upstream head
reset Reset current HEAD to the specified state
rm Remove files from the working tree and from the index
show Show various types of objects
status Show the working tree status
tag Create, list, delete or verify a tag object signed with GPG

'git help -a' and 'git help -g' lists available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
[admin@localhost buildsys]$ update
bash: update: command not found...
[admin@localhost buildsys]$ git --version
git version 1.8.3.1
[admin@localhost buildsys]$ yum remove git-*
Loaded plugins: fastestmirror, langpacks
You need to be root to perform this command.
[admin@localhost buildsys]$ sudo yum remove git-*
[sudo] password for admin:
Loaded plugins: fastestmirror, langpacks
Resolving Dependencies
--> Running transaction check
---> Package git.x86_64 0:1.8.3.1-23.el7_8 will be erased
--> Processing Dependency: git = 1.8.3.1-23.el7_8 for package: perl-Git-1.8.3.1-23.el7_8.noarch
--> Processing Dependency: git for package: gettext-devel-0.19.8.1-3.el7.x86_64
--> Running transaction check
---> Package gettext-devel.x86_64 0:0.19.8.1-3.el7 will be erased
--> Processing Dependency: gettext-devel for package: intltool-0.50.2-7.el7.noarch
---> Package perl-Git.noarch 0:1.8.3.1-23.el7_8 will be erased
--> Running transaction check
---> Package intltool.noarch 0:0.50.2-7.el7 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

==========================================================================================================
Package Arch Version Repository Size
==========================================================================================================
Removing:
git x86_64 1.8.3.1-23.el7_8 @anaconda 22 M
Removing for dependencies:
gettext-devel x86_64 0.19.8.1-3.el7 @anaconda 1.4 M
intltool noarch 0.50.2-7.el7 @anaconda 166 k
perl-Git noarch 1.8.3.1-23.el7_8 @anaconda 57 k

Transaction Summary
==========================================================================================================
Remove 1 Package (+3 Dependent packages)

Installed size: 24 M
Is this ok [y/N]: yum install https://repo.ius.io/ius-release-el7.rpm https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Is this ok [y/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Erasing : intltool-0.50.2-7.el7.noarch 1/4
Erasing : gettext-devel-0.19.8.1-3.el7.x86_64 2/4
Erasing : perl-Git-1.8.3.1-23.el7_8.noarch 3/4
Erasing : git-1.8.3.1-23.el7_8.x86_64 4/4
Verifying : git-1.8.3.1-23.el7_8.x86_64 1/4
Verifying : intltool-0.50.2-7.el7.noarch 2/4
Verifying : perl-Git-1.8.3.1-23.el7_8.noarch 3/4
Verifying : gettext-devel-0.19.8.1-3.el7.x86_64 4/4

Removed:
git.x86_64 0:1.8.3.1-23.el7_8

Dependency Removed:
gettext-devel.x86_64 0:0.19.8.1-3.el7 intltool.noarch 0:0.50.2-7.el7 perl-Git.noarch 0:1.8.3.1-23.el7_8

 

[KennethMcNutt]

Complete!
[admin@localhost buildsys]$ buildsys x510 -- network=import
Failed to import static analysis
Something funny happened creating dl symlink, oh well
make: `luabuild' is up to date.
make: `buildsys' is up to date.
BuildSys: Buildsys (C++ version)
BuildSys: Built: 13:24:09 Sep 27 2022
host,host.lua: Processing (host.lua)
host,protobuf: Processing (./package/protobuf/protobuf.lua)
host,host/env: Processing (./package/host/env/env.lua)
host,protobuf-c: Processing (./package/protobuf-c/protobuf-c.lua)
host,cmsg: Processing (./package/cmsg/cmsg.lua)
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
host,awp-build-tools: Processing (./package/awp-build-tools/awp-build-tools.lua)
host,makedevs: Processing (./package/makedevs/makedevs.lua)
host,intltool: Processing (./package/intltool/intltool.lua)
host,grpc-gateway: Processing (./package/grpc-gateway/grpc-gateway.lua)
host,qemu-img: Processing (./package/qemu-img/qemu-img.lua)
host,python/host: Processing (./package/python/host/host.lua)
host,intltool: Build Thread
host,intltool: Building (0 others running)
host,host/env: Build Thread
host,host/env: Building (1 others running)
host,host/env: Hash: fdaa0224892bec7dfff4997cb2ccb64701a9d86629c74643e1dfb84506e42f9a
host,intltool: Hash: 787e89c0757e29aeb12192f02b8a99b4ddc8efe46dd8fb502e2a43de8b65e73c
host,intltool: Extracting ...
host,intltool: Extracting sources and patching
host,host/env: Building ...
host,host/env: Generating staging directory ...
host,intltool: tar: This does not look like a tar archive
host,intltool:
host,intltool: gzip: stdin: unexpected end of file
Path: /home/admin/buildsys/output/host/intltool/work
Arg[0] = 'tar'
Arg[1] = 'xf'
Arg[2] = '/home/admin/buildsys/dl/intltool-0.51.0.tar.gz'
terminate called after throwing an instance of 'buildsys::CustomException'
[admin@localhost buildsys]$

 

[KGIII]

Complete!

Congratulations. The error in the first post made me wonder if it just needed a different distro, as it was a release error. I didn't want to speculate and know nothing about the application.

I will point out that any admin/mod can retrieve your edited post. I'm 100% positive that this will never be a concern, but we can see your edited content. For security reasons, edits are retained. But, I can look at your edit and see your password.

It will make your thread different, but I can completely remove that post for you, putting it in a state where it can't be retrieved by anyone. Or not... It's up to you. If you don't share passwords, you are even less at risk. I'm positive nobody who can see that will act on it, but I think you should know about this.

 

[KGIII]

Oh, wait... I misread and thought you had completed it properly. And, my only speculation was that it may need a different distro (or to edit the scripts and change the release information).

With further looking, it looks like it's looking for a .tar file. You could check that directory and see if there's a .tar file there. It may also be a bug/error and you can try to contact the authors of the software. They're receptive and helpful - in my experiences.

 

[KennethMcNutt]

Congratulations. The error in the first post made me wonder if it just needed a different distro, as it was a release error. I didn't want to speculate and know nothing about the application.

I will point out that any admin/mod can retrieve your edited post. I'm 100% positive that this will never be a concern, but we can see your edited content. For security reasons, edits are retained. But, I can look at your edit and see your password.

It will make your thread different, but I can completely remove that post for you, putting it in a state where it can't be retrieved by anyone. Or not... It's up to you. If you don't share passwords, you are even less at risk. I'm positive nobody who can see that will act on it, but I think you should know about this.

I'm ok with it I only use that password in things I don't plan on keeping it is a goto password for VM OS's I use.. and please speculate!! I really need the help.. The only CL I ever learned well was Dos.. Linux CL is overwhelming.. LOL

 

[KennethMcNutt]

Oh, wait... I misread and thought you had completed it properly. And, my only speculation was that it may need a different distro (or to edit the scripts and change the release information).

With further looking, it looks like it's looking for a .tar file. You could check that directory and see if there's a .tar file there. It may also be a bug/error and you can try to contact the authors of the software. They're receptive and helpful - in my experiences.

I saw that also I think it is referring to the network pkg (tar) I pulled it from the Backup firmware .rel not from the switch itself hope that is fixable.. I really need this to work.. it's a 52 port POE switch I can't afford a new one... or the 1000 dollor service contract from allied telesis just to get some firmware!! The sad part is I broke it with a NAND flash to erase all command. My finger was milliseconds behind my brain.. and somehow my backup gives me A "Release header corrupt" which seems to be for the vmlinux.bin in the squashfs.. it is the part of the fs I can't open correctly.. I can "dump it" but My knowlage of it leaves me unable to rebuild it as of yet... The Vmlinux.bin seems to be the part of the firmware that sets up the flash rebuild process.. rewriting the partitions and rewrites the os files..)

 

[KennethMcNutt]

https://www.linux.org/threads/allie... and helpful - in my experiences.,-I saw that I don't remember where I got it.. I believe it was out of an archive that came from Allied themselves. in their attempt to satisfy open source. I looked back for it and find NO reference of it anywhere?? But If I can get this to work it will be helpful to many, Cuz allied sure is NOT!!!

 

[KennethMcNutt]

To whomever reads this:
I will do my best to log what works and what does not. as I attempt to learn it myself..
The builder creates one of the last firmwares (before) Allied moved the licensing from the hardware to the cloud and forced a subscription to have any use of their switches..
It builds firmware for almost all Allied Telesis Enterprise switches to date.
AT-SBx81CFC960 (SwitchBlade x8100 series), SwitchBlade x908 GEN2
CenterCOM x950 / x930 / x550 / x530 / x530L / x510 / x510DP / x320 / x310 / x230 / x230L / x220 series
CentreCOM Secure HUB SH310 / SH230 / XS900MX / GS980MX / GS980EM / GS980M / FS980M series
CentreCOM IE340 / IE340L / IE200 / IE210L series
AT-AR4050S, AT-AR3050S, AT-AR2050V, AT-AR2010V, AT-AR1050V
If I am successful I will create a working single-line command build in Virtual Machine to save others from this hassle..
If I fail.. at least you'll have the builder to try yourself.
Believe it or not, there are NO publicly available copies of these firmwares anywhere..
The only proprietary part of the firmware is in the network pkg which you will need from your switch..
I hope this post finds its way to extend the life of these +15,000 dollar switches in the public sector as they reach their EOL on the enterprise market.

 

[KennethMcNutt]

Well, I've been down a few more dead-end roads.. I am sure Is is me and my inability to grasp the linux CL .. Jeez what were these PPL think'n when they came up with this file system.. I mean even trying to come to grips with the fact that usr/"user"/desktop isn't the path to the Desktop??? it's local /share/ or something I am lost!! LOL
DOS was a lot more straightforward!!!

I did have a great moment!!! I found a copy of my f/w on a one-drive backup that it pulled from my desktop, I hated that about one drive that's why I started killing on all my windows machines!!! But I guess I should thank Bill !!
So it ran and it gave me an error I never saw before. Ive seen MANY.!.!. LOL

It stopped and said: Your machine has no personality therefore it can not boot.. I was like what the???

So come to find out it has a dual personality??? I and I starting not to like either one of them!!

All jokes aside I'm screwed now... Allied is gonna be the only one to can fix that right??

So I thought .....so I thought... I don't give up easily... I went in search of a personality fixer ... and like everything else about Allied, I get only glimpses of things... But just enough to remind me about what this F/W build had said in the how-to..

"Full-fledged," it said...and that got me think'n
I'm think'n to myself no way...
But ,

let me see..

I looked
and I FOUND this...

"full fledged," it said..

/* Taken verbatim from Linux 2.6 (include/linux/personality.h). */

#ifndef _SYS_PERSONALITY_H
#define _SYS_PERSONALITY_H 1

#include <features.h>

/* Flags for bug emulation.
These occupy the top three bytes. */
enum
{
ADDR_NO_RANDOMIZE = 0x0040000,
MMAP_PAGE_ZERO = 0x0100000,
ADDR_COMPAT_LAYOUT = 0x0200000,
READ_IMPLIES_EXEC = 0x0400000,
ADDR_LIMIT_32BIT = 0x0800000,
SHORT_INODE = 0x1000000,
WHOLE_SECONDS = 0x2000000,
STICKY_TIMEOUTS = 0x4000000,
ADDR_LIMIT_3GB = 0x8000000
};

/* Personality types.

These go in the low byte. Avoid using the top bit, it will
conflict with error returns. */
enum
{
PER_LINUX = 0x0000,
PER_LINUX_32BIT = 0x0000 | ADDR_LIMIT_32BIT,
PER_SVR4 = 0x0001 | STICKY_TIMEOUTS | MMAP_PAGE_ZERO,
PER_SVR3 = 0x0002 | STICKY_TIMEOUTS | SHORT_INODE,
PER_SCOSVR3 = 0x0003 | STICKY_TIMEOUTS | WHOLE_SECONDS | SHORT_INODE,
PER_OSR5 = 0x0003 | STICKY_TIMEOUTS | WHOLE_SECONDS,
PER_WYSEV386 = 0x0004 | STICKY_TIMEOUTS | SHORT_INODE,
PER_ISCR4 = 0x0005 | STICKY_TIMEOUTS,
PER_BSD = 0x0006,
PER_SUNOS = 0x0006 | STICKY_TIMEOUTS,
PER_XENIX = 0x0007 | STICKY_TIMEOUTS | SHORT_INODE,
PER_LINUX32 = 0x0008,
PER_LINUX32_3GB = 0x0008 | ADDR_LIMIT_3GB,
PER_IRIX32 = 0x0009 | STICKY_TIMEOUTS, /* IRIX5 32-bit */
PER_IRIXN32 = 0x000a | STICKY_TIMEOUTS, /* IRIX6 new 32-bit */
PER_IRIX64 = 0x000b | STICKY_TIMEOUTS, /* IRIX6 64-bit */
PER_RISCOS = 0x000c,
PER_SOLARIS = 0x000d | STICKY_TIMEOUTS,
PER_UW7 = 0x000e | STICKY_TIMEOUTS | MMAP_PAGE_ZERO,
PER_OSF4 = 0x000f,
PER_HPUX = 0x0010,
PER_MASK = 0x00ff,
};

__BEGIN_DECLS

/* Set different ABIs (personalities). */
extern int personality (unsigned long int __persona) __THROW;

__END_DECLS

#endif /* sys/personality.h */

and it wasn't hyped!!

So I am back to try'n again!!!! I really could use some help.. I think all My Issues are somehow in the path and most likely the directory I run it from The how-to I for someone more fluent in linux's needs.. Hell I can even set up the path .. I have to brute-force my root hammer and use /bin to get where I have ...

 

[KennethMcNutt]

Well I tried and I tried, But it was just beyond me.. I basically read every script and command the build had in it.. Yet I just couldn't get it to finish vast parts of it...
So I just did it by hand..
I took what I could get and Frankenstein'd it ..
I have no clue how I managed it

But here SHE LIVES AGAIN!!!!

▒RAsf▒▒▒▒"▒6▒▒dg▒A▒▒CK▒▒. C׆▒▒▒rRy▒▒▒▒=▒ϸ▒
do▒▒▒▒G▒
Epi3: Failed to get MAC address out of EPI3 information.
Epi3: This device may not have any valid personalities.

Reading filesystem...
Error: There is no primary release file set
Error: There is no backup release file set
Error: Boot failed. Please recover the system using the Boot Menu
Restarting..
Bootloader 2.0.25 loaded
Press <Ctrl+B> for the Boot Menu
Epi3: Failed to get MAC address out of EPI3 information.
Epi3: This device may not have any valid personalities.

Reading filesystem...
Error: There is no primary release file set
Error: There is no backup release file set
Error: Boot failed. Please recover the system using the Boot Menu
Restarting..
Bootloader 2.0.25 loaded
Press <Ctrl+B> for the Boot Menu


Bootup Stage 1 Diagnostics Menu:

0. Restart
1. Full RAM test
2. Quick RAM test
3. Battery backed RAM (NVS) test
4. Bootloader ROM checksum test
----------------------------------
7. Bootup stage 2 diagnostics menu
----------------------------------
8. Quit to U-Boot shell
9. Quit and continue booting

Enter selection ==> 8

Epi3: Failed to get MAC address out of EPI3 information.
Epi3: This device may not have any valid personalities.

x510epi3mk -?
Unknown command 'EPIpi3mk' - try 'help'
x510>
x510> help
? - alias for 'help'
awbootf - Start the AlliedWare+ bootup sequence from flash
awbootm - Start the AlliedWare+ bootup sequence from a location in memory
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootmenu- <INTERNAL COMMAND **DO NOT USE**>
bootp - boot image via network using BOOTP/TFTP protocol
bootupda- <INTERNAL COMMAND **DO NOT USE**>
bootvx - Boot vxWorks from an ELF image
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
delay - delay for N (decimal) microseconds/milliseconds/seconds (not calibrate d)
echo - echo args to console
editenv - edit environment variable
epi3mk - Make an EPI3 block
epi3psumk- epi3psumk - Make an EPI3 block in a PSU

epi3show- Show current EPI3 information
erase - erase FLASH memory
exit - exit script
exttftp - Load via external TFTP
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
flinfo - print FLASH memory information
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
iminfo - print header information for application image
imls - list all images found in flash
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
mat - <Manufacturing Automation Tool entry **DO NOT USE**>
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtest - simple RAM read/write test
mw - memory write (fill)
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
pci - list and access PCI Configuration Space
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reloc - print U-Boot relocation information
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
tftpboot6- boot image via network using TFTP protocol
true - do nothing, successfully
usb - USB sub-system
usbboot - boot from USB device
version - print monitor version
x510> epi3mk -?
Error: No previous personality to get value from
x510> help epi3mk
epi3mk - Make an EPI3 block

Usage:
epi3mk [Serial] [Mfg] [Year] [Month] [BoardID] [PCBRev] [MAC] [844Bom] [OEM] [HW ModLevel]

Standard command usage:

epi3mk 123456789 A 06 06 270 X2 001122334455 A U 1

The 'Serial' parameter is required but ignored. The only case where this paramet er is observed is when the
personality area is blank (factory first program).

If a parameter is specified as a dash '-' character, then the value is copied fr om the last valid personality.
There is no need to insert the '-' character in place of values after any of tho se you wish to modify.
For example, the command:

epi3mk - - - - 270

Will make a new personality, with all attributes unchanged apart from the specif ied BoardID.
x510> epi3mk A04746G155000004M A 15 12 370 X2 001AEB9332CC A U 1
. done
Un-Protected 1 sectors
Copy to Flash... done
. done
Protected 1 sectors
Successfully wrote EPI3 information to flash in position: 0
x510> EXIT
Unknown command 'EXIT' - try 'help'
x510> HELP
Unknown command 'HELP' - try 'help'
x510> help
? - alias for 'help'
awbootf - Start the AlliedWare+ bootup sequence from flash
awbootm - Start the AlliedWare+ bootup sequence from a location in memory
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootmenu- <INTERNAL COMMAND **DO NOT USE**>
bootp - boot image via network using BOOTP/TFTP protocol
bootupda- <INTERNAL COMMAND **DO NOT USE**>
bootvx - Boot vxWorks from an ELF image
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
delay - delay for N (decimal) microseconds/milliseconds/seconds (not calibrated)
echo - echo args to console
editenv - edit environment variable
epi3mk - Make an EPI3 block
epi3psumk- epi3psumk - Make an EPI3 block in a PSU

epi3show- Show current EPI3 information
erase - erase FLASH memory
exit - exit script
exttftp - Load via external TFTP
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
flinfo - print FLASH memory information
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
iminfo - print header information for application image
imls - list all images found in flash
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
mat - <Manufacturing Automation Tool entry **DO NOT USE**>
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtest - simple RAM read/write test
mw - memory write (fill)
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
pci - list and access PCI Configuration Space
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reloc - print U-Boot relocation information
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
tftpboot6- boot image via network using TFTP protocol
true - do nothing, successfully
usb - USB sub-system
usbboot - boot from USB device
version - print monitor version exit exit not allowed from main input shell.
x510> reboot
Unknown command 'reboot' - try 'help'
x510> awboot
Unknown command 'awboot' - try 'help'
x510> awbootf

Reading filesystem...
Scanning JFFS2 FS: done.
find_inode failed for name=.release
load: Failed to find inode
Error: There is no primary release file set
Scanning JFFS2 FS: done.
find_inode failed for name=.backup
load: Failed to find inode
Error: There is no backup release file set
Error: Boot failed. Please recover the system using the Boot Menu
Restarting..
Bootloader 2.0.25 loaded
Press <Ctrl+B> for the Boot Menu

Reading filesystem...
Error: There is no primary release file set
Error: There is no backup release file set
Error: Boot failed. Please recover the system using the Boot Menu
Restarting..
Bootloader 2.0.25 loaded
Press <Ctrl+B> for the Boot Menu

Boot Menu:

------------------------------------------------------
B. Boot backup software
------------------------------------------------------
0. Restart
1. Perform one-off boot from alternate source
2. Change the default boot source (for advanced users)
3. Update Bootloader
4. Adjust the console baud rate
5. Special boot options
6. System information
7. Restore Bootloader factory settings
------------------------------------------------------
9. Quit and continue booting

Enter selection ==> 1

Select device:

0. Return to previous menu
------------------------------------------------------
1. Flash (flash
3. TFTP (tftp://)
4. YMODEM (ymodem
6. USB (usb

Enter selection ==> 6

Reading filesystem...

Listing of usable files (root directory only)

1. usb:x510-5.4.5-2.1.rel

Enter selection (1-1, 0 to cancel) and press enter ==> 1

Reading usb:x510-5.4.5-2.1.rel...

Verifying release... OK
Booting...
Starting base/first... [ OK ]
Mounting virtual filesystems... [ OK ]

______________ ____
/\ \ / /______\
/ \ \_ __/ /| ______ |
/ \ | | / | ______ |
/ \ \ / / \ ____ /
/______/\____\ \/ /____________/

Allied Telesis Inc.
AlliedWare Plus (TM) v5.4.5
Current release filename: x510-5.4.5-2.1.rel
Built: Thu Nov 12 03:15:22 UTC 2015
Mounting static filesystems... [ OK ]
Checking flash filesystem... [FAILED]
Initialising flash filesystem...

^[^[
[ OK ]
Mounting flash filesystem... [ OK ]
Checking NVS filesystem... [ OK ]
Mounting NVS filesystem... [ OK ]
Starting base/dbus... [ OK ]
Starting base/syslog... [ OK ]
Starting base/loopback... [ OK ]
Starting base/poe_done... [ OK ]
Starting base/sysctl... [ OK ]
Starting base/portmapper... [ OK ]
Received event syslog.done
Starting base/reboot-stability... [ OK ]
Checking system reboot stability... [ OK ]
Starting base/cron... [ OK ]
Starting base/apteryx... [ OK ]
Starting base/appmond... [ OK ]
Starting base/clockcheck... [ OK ]
Starting hardware/openhpi... [ OK ]
Starting hardware/timeout... [ OK ]
Starting base/inet... [ OK ]
Starting base/modules... [ OK ]
Received event modules.done
Received event apteryx.done
Starting network/kermond... [ OK ]
Starting hardware/plugman... [ OK ]
Starting base/apteryx-sync... [ OK ]
Received event apteryx-sync.done
Received event board.inserted
Starting hardware/hardware-done... [ OK ]
Received event hardware.done
Starting network/poefw... [ OK ]
Starting base/external-media... [ OK ]
Received event poefw.done
Starting network/startup... [ OK ]
Starting network/stackd... [ OK ]
Starting network/election.timeout... [ OK ]
Received event network.enabled

Initializing HA processes:
10:46:09 awplus HPI: SENSOR PSU slot 2 - PSU Power Output: now OK
atmfd, auth, cntrd, epsr, hostd, hsl, imiproxyd
irdpd, lacp, lldpd, loopprot, mstp, nsm, ospf6d
ospfd, pdmd, pim6d, pimd10:46:11 awplus VCS[631]: stack member has booted as one off boot, SW version auto synchronization cannot be supported.
, ripd, ripngd, rmon
sflowd, udldd, vrrpd, almond, bgpd, imi

Received event network.initialized

10:46:47 awplus-1 VCS[631]: No neighboring members found, unit may be in a standalone configuration
Received event vcs.elected-master
Assigning Active Workload to HA processes:
10:46:47 awplus-1 VCS[631]: Startup speed can be improved by adding 'no stack 1 enable' to configuration
10:46:47 awplus-1 VCS[631]: Member 1 (001a.eb93.32cc) has become the Active Master
authd, epsrd, hsl, irdpd, lacpd, lldpd, loopprotd
mstpd, nsm, rmond, sflowd, vrrpd, imi, imiproxyd

Received event network.activated

Loading default configuration
Warning: flash:/default.cfg does not exist, loading factory defaults.
....

done!
Received event network.configured


awplus login: manager
Password:

AlliedWare Plus (TM) 5.4.5 11/12/15 03:15:22

The system has been booted using the one off boot/recovery mechanism.
Bootup has successfully completed.

Use the "copy current-software" and "boot system" commands to save this
release file for future use.

awplus>
I put everything I found on my GDrive hope it helps someone !!!