Allonis Master Image for Raspberry Pi4

The myServer 6 Master Image for Raspberry Pi 4 includes:

• myServer 6 (including 30 day trial)
• TeamViewer for remote management of the server
• Installation utilities for multiple optional system services - mostly to support AES67,  MediaMatrix, and many other advanced functions.
• Raspberry Pi OS w/Desktop pre-configured for use as an automation server
• Docker software to install optional packages
• Firmware update files to boot from USB or NVME M.2 drive

Notes:

• Due to support issues, Allonis does not support installing myServer 6 to a non Allonis Master Build.  Sure it's possible, but there are a lot of steps...Allonis can be contracted to assist if this is really needed.
• It is highly recommended to purchase myServer 6 controllers direct from Allonis.  A pre loaded USB stick is also available (must have Pi4 4/8gig on latest firmware set to boot from USB).
• One of the possible reasons to install a Master Image on a new USB drive (recommended is 400mhz 128 gig) is that the boot sector of the USB has been corrupted due to power cycling.  Power cycling is NOT recommended as it is very possible that that will damage the USB drive, which prevents system boot.  See notes at the bottom of this article for specific corruption assistance after the Master Image has been created.  Power cycle related failures are not covered under Warranty.  It is highly recommended to have myServer controllers connected to a UPS and monitored by myServer (see Allonis for details).

Required:

• Windows PC connected to the Internet.  MacOS can be used to burn the image (using Etcher) as well.
• USB 3.0 flash drive (ideally 400mhz) 16gb or larger (Samsung 128gb 400mhz is recommended) or SDMicro read / write hardware (or an SD reader and use the SDMicro adapter that a lot of SDMicro sticks come with).
• If SDMicro as a boot drive (USB 3.0 recommended): SDMicro 32gig / Class 10 memory stick
• Best is NVME M.2 drive as it is fastest read / write and can be signficant capacity
• M.2 to USB drive adapter (if you are using the M.2)
• 
• "Etcher" software to burn the Master Image to the SDMicro / USB / NVME stick (NVME requires usb adapter)

Select the USB Flash drive you want to use for your Raspberry Pi (NOT the Boot Drive! - which is typically hidden from view)

Click on “Flash!” to start writing the image:

When Balena Etcher is finished writing the image you will get this confirmation:

• Raspberry Pi4 4 gig minimum (4 is recommended, 8 gig is "overkill").  A Pi5 can also be used for higher performance (but overkill for most applications).
• Optional: "Putty" for Mac or "Putty" for Windows software to remotely connect to the Pi
• Optional (but makes this all way easier): HDMI Micro to HDMI video adapter cable connected to an HDMI monitor
• Optional (makes install way easier): wireless keyboard / mouse

 Please remember to ensure you’re using an appropriate power supply with your Raspberry Pi. Mobile chargers may not be suitable, since some are designed to only provide the full power with that manufacturer’s handsets. USB ports on your computer also will not supply enough power and must not be used.

Instructions:

Download myServer 6  (Raspberry Pi OS w/ Desktop) Master Image HERE 

PI5-4-Master arm64 for either a Pi4 or Pi5 (4 or 8 gig).

Once download has finished, you’ll have a zip file.  Unzip it.  Put the file on same PC that Etcher is running.

Click HERE to learn how to create a bootable image device.

Once you have the boot image to an USB, follow instructions in same document to update the firmware so you can also boot from an USB 3.0 drive.  Highly recommended for speed and reliability.  Old Pi4's original firmware cannot boot from USB until updated with latest firmware.

Once you have a bootable SDMicro / USB drive, click HERE on how to get it running.

The system will reboot several times (If you have a monitor connected, you will see the "Allonis" logo three times) as it reconfigures its settings for your network.  Be patient until it finally reboots and stays running.  This will take about 10 minutes total.

 

All Allonis software resides in the /home/allonis/applications folders  

Debian OS Username / password is allonis / allonis

 How to determine myServer's IP address:  If you have a monitor / keyboard mouse connected, click on the network icon on the OS desktop and you should see the network IP address (you can also static address the controller there too).  If you don't have a monitor, then look at your Router to see what address has been assigned to the device that has "myServer-some random number" as a computer name.  If the controller has been renamed (like to the bar's name), then look for a device with that name.  You can also go to http://barname/dashboard if it has already been renamed.  You can also install network "ping" tool like "Advanced IP Sniffer" on a Windows PC on the network.

If you are viewing the Pi's Desktop on a local monitor, open browser to myServer's dashboard (http://127.0.0.1/dashboard).

Once system reboots, connect again and add all project relevant software (install only what you will use) using the Software Updater in Dashboard.  System will reboot after it downloads all files.

Update the OS image by ensuring the Pi is on the Internet and then clicking on the desktop's menu / Accessories / Get Updates.  A command window will open and a list of new files will be generated.  The window will then close.  Next, perform a Get Upgrades.  This will have prompts that need to be read and selected.  When the upgrade is complete, reboot Pi.  The upgrade will take several minutes depending on your network speed.  HAVE Patience!!!

Once booted, if you are using a monitor and keyboard / mouse, you can change the computer name in the Dashboard.  Click the Computer name.  A command popup should appear.  Replace "myServer" with your new computer name.  Run the command by hitting the "Play" button.  System will restart a few times.

Once the Pi reboots, myServer 6 should be running as a service.  You can then configure the system for your facility HERE.

Go to myServer's webpage:  http://myServerIPAddress/dashboard  first thing is update myServer from Utilities / Software updater.  You can also use http://computername/dashboard.

 

If Pi does not boot, check the PWR LED indicator light near the USB_C power connector. If it's blinking, then the voltage being supplied to the Raspberry Pi is too low to turn it on.

Read More: https://www.slashgear.com/1636165/raspberry-pi-low-voltage-causes-fixes/

You may need to replace the power supply.

 

 If you are doing the Master Image installation as a result of an older myServer boot issue or to upgrade to 64 bit operating system, Note the current IP address.  Gracefully shut down the system and remove all USBs.  Insert the NEW USB into the bottom Blue USB3.0 connection.  Power up / Boot the new image system (remember - it will initially boot multiple times - have patience - can take 10 minutes). After the system is stable, insert the OLD USB into one of the remaining USB slots.  Let Allonis know and we can remote into the NEW image, and attempt to restore the OLD system onto the NEW USB.  If this is successful, then you will save many hours of programming and reconfiguration.  Provide the TeamViewer ID of the NEW system to Allonis.  You can see this by going to:  http://myserverlocalipaddress/dashboard.  If the myServer computer was not changed, and if the network is using DHCP addressing, the address should be same as the Old USB.  Otherwise, you may have to look in the router for the DHCP new IP address.

The Teamviewer ID will be displayed top middle of that webpage.

Note that depending on system vintage, the new software may require changes to the base files (like the user interface) to ensure all is compatible.

Once the system is migrated from Old to New usb, gracefully shut down the system, and then remove the OLD USB and repower the system so it will boot from the NEW USB.

 

 

Advanced: If you want to try mounting the "Old" USB on the "New" OS:

Assumptions:  New USB (boot) is in the lower Blue USB3.0.  Old USB (with the old files) in the lower Black USB 2.0 Pi4 connections.

sudo mkdir /mnt/olddrive
sudo mount -t auto /dev/sdb2 /mnt/olddrive
ls -al /mnt/olddrive

myServer files will be in

ls -al /dev/sd*

sda is the boot drive

sdb is the "Old" USB that the data needs to be extracted from

Now we need to create a directory to mount the old USB

In File Manager, you will see /mnt directory

sudo mkdir /mnt/olddrive

Mount the old usb in the sdb2 data partition (sdb1 is the boot partition):

sudo mount -t auto /dev/sdb2 /mnt/olddrive

when you run the "sudo mount -t auto /dev/sdb2 /mnt/olddrive" command you might see:
"mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload."

If you see that try running this:
systemctl daemon-reload

Then try reloading the drive again:

sudo mount -t auto /dev/sdb2 /mnt/olddrive

If that was successful you might see:    mount: /mnt/olddrive: /dev/sdb2 already mounted on /mnt/olddrive.
dmesg(1) may have more information after failed mount system call.

To verify that the USBOld is mounted you can run this command:

ls -al /mnt/olddrive/home/allonis/applications/myServer

You should now be able to use File Manager to copy files from the Old USB to the New USB.

 

If the old USB still boots, you can boot on a new USB.  Then insert Old USB into second USB connection and run

sudo fsck -a /dev/sdb

This will analyze the old USB file structure and report / fix found corruptions.

 

Advanced:

myServer 6 installs to: /home/allonis/applications/Allonis/myServer

Notes:

If the "activate.video" macro has server variables using {{vout*} then it is old and cannot be updated to a later version of myServer 6 software suite (all macros must be updated to latest syntax first).

 

On some myServer 6 devices, you may run into an issue where the myServer Event Viewer (launched from Raspberry PI Desktop menu) won't load.  This can be due to Chrome permissions need to be reset:

 sudo rm -rf ~/.config/chromium/Singleton*

 sudo rm -rf ~/Documents/Singleton*

Later versions of myServer automatically run these commands when the computer name is changed using SetHostName command in myServer command builder.

 

Troubleshooting

Long flashes	Short flashes	Status
0	3	Generic failure to boot
0	4	start*.elf not found
0	7	Kernel image not found
0	8	SDRAM failure
0	9	Insufficient SDRAM
0	10	In HALT state
1	2	SD card overcurrent detected
2	1	Partition not FAT
2	2	Failed to read from partition
2	3	Extended partition not FAT
2	4	File signature/hash mismatch - Pi 4 and Pi 5
3	1	SPI EEPROM error - Pi 4 and Pi 5
3	2	SPI EEPROM is write protected - Pi 4 and Pi 5
3	3	I2C error - Pi 4 and Pi 5
3	4	Secure-boot configuration is not valid
4	3	RP1 not found
4	4	Unsupported board type
4	5	Fatal firmware error
4	6	Power failure type A
4	7	Power failure type B