Announcing MinimServer 2 for ASUSTOR and ReadyNASLinux

[dionw]

Hi Simon, I've attempted an install of `MinimServer-2.0.16-readynas-x86.bin` on a ReadyNAS Pro Business Edition running `RAIDiator 4.2.31` firmware. Install proceeded as expected, however on server start-up an error occurred, with log entries as follows:
Wed Oct 28 11:26:08 EST 2020 The MinimServer 2 add-on has been successfully installed.
Wed Oct 28 11:26:05 EST 2020 ERROR: MinimServer startup error: Error: dl failure on line 604

As I was unable to access the MinimServer status page on a web browser at n.n.n.n:9790 it looks like the start-up error is terminal.

I then followed the troubleshooting advice provided at: https://minimserver.com/install-readynas...20problems
Tried "Startup problems" suggestions 1. & 2. to no avail. In both instances the same "dl failure on line 604" error was logged. So I did 3. by installing MinimServer 2 on a Mac. MinimServer 2 on the Mac started up AOK, with the MinimWatch menu bar icon showing 'red' due to no media directory having been set. And localhost:9790 in a browser loaded the MinimServer status page AOK as well.

I then accessed the `minimserver-out.log` file on the ReadyNAS. Contents of this file were as follows:
"xxxx-nas:/# cat /c/backup/minimserver-out.log
Error: dl failure on line 604
Error: failed /etc/frontview/addons/bin/MINIMSERVER/lib/minimjre-readynas(linux-x86)-14.0.1.dir/jre/lib/client/libjvm.so, because /etc/frontview/addons/bin/MINIMSERVER/lib/minimjre-readynas(linux-x86)-14.0.1.dir/jre/lib/client/libjvm.so: ELF file OS ABI invalid"

Googling "ELF file OS ABI invalid" gives responses indicating this is likely due to the linux version system libraries on my box being too old.

I know some linux, but only enough to be dangerous. Insofar as I'm aware RAIDiator 4.2.31 is the most up to date firmware available for this device, short of an unsupported upgrade path that can be used to install ReadyNAS OS 6.x.x.
https://blah.cloud/just-for-fun/upgradin...-to-6-2-x/

This I'm loathe to attempt unless as a very last resort given this box holds all my treasure in a n/w accessible mode. It is backed up independently of the NAS RAID array.

Is there a chance you may have a solution to bypass this issue short of requiring such an update?