From 3e8ec7ad2cda240dcbf76774ac240a1054ea80f4 Mon Sep 17 00:00:00 2001 From: jeremyhann <38609717+jeremyhann@users.noreply.github.com> Date: Fri, 11 Oct 2024 03:24:54 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20main=20@=20e?= =?UTF-8?q?51e22025b797605d20f68377db920875148f056=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...37PVE-makes-your-service-Migratable!.html" | 6 +- docs/All-in-one-routing-system-OpenWRT.html | 6 +- .../Basic-functions-of-dedicated-systems.html | 6 +- ...4K-Arcade-with-ZimaBoard-and-Batocera.html | 6 +- docs/DownloadLLMmodels.html | 6 +- docs/ForgotPassword.html | 6 +- docs/GetNetworkID.html | 6 +- docs/Hardware-Interface-Introduction.html | 6 +- docs/How-to-set-up-a-NAS-with-ZimaBlade.html | 6 +- docs/MineCraft-Friendship-Service.html | 6 +- docs/Openwrt-eMMc-boot.html | 6 +- docs/Self-Deploying-Applications.html | 6 +- ...Big-applications-OMV-First-Experience.html | 6 +- ...all-body-Big-applications-OMV-install.html | 6 +- docs/Speedlimit.html | 6 +- ...er-is-best-suited-for-Personal-Server.html | 6 +- ...rd-party-system-installation-tutorial.html | 6 +- ...perience-At-$129-Five-drive-Disks-Nas.html | 6 +- ...First-Experience-at-$129-Installation.html | 6 +- docs/UseSambaviacomputer.html | 6 +- .../VR-Audio-And-Video-Experience-Oculus.html | 6 +- ...oard-DIY-Fan-Guide-and-Specifications.html | 6 +- docs/index.html | 6 +- faq/How-to-check-IP-address.html | 6 +- faq/Restore-factory-settings.html | 6 +- faq/Upgrade-Motherboard-BIOS-Version.html | 6 +- faq/index.html | 6 +- index.html | 6 +- index_old.html | 4 +- knowledge/index.html | 6 +- search.xml | 240 ++++++++--------- sitemap.txt | 110 ++++---- sitemap.xml | 242 +++++++++--------- zimablade/index.html | 6 +- .../All-in-one-routing-system-OpenWRT.html | 6 +- .../Basic-functions-of-dedicated-systems.html | 6 +- ...4K-Arcade-with-ZimaBoard-and-Batocera.html | 6 +- .../Hardware-Interface-Introduction.html | 6 +- zimaboard/How-to-check-IP-address.html | 6 +- .../How-to-set-up-a-NAS-with-ZimaBlade.html | 6 +- zimaboard/MineCraft-Friendship-Service.html | 6 +- zimaboard/Openwrt-eMMc-boot.html | 6 +- zimaboard/Power-on-Zimablade.html | 6 +- zimaboard/Restore-factory-settings.html | 6 +- zimaboard/Self-Deploying-Applications.html | 6 +- ...Big-applications-OMV-First-Experience.html | 6 +- ...all-body-Big-applications-OMV-install.html | 6 +- zimaboard/Syncthing.html | 6 +- ...rd-party-system-installation-tutorial.html | 6 +- ...First-Experience-at-$129-Installation.html | 6 +- .../Upgrade-Motherboard-BIOS-Version.html | 6 +- .../VR-Audio-And-Video-Experience-Oculus.html | 6 +- zimaboard/index.html | 6 +- zimacube/About-ZimaOS.html | 6 +- zimacube/Advanced-Using.html | 6 +- zimacube/Auto-Power-On.html | 6 +- zimacube/BIOS-Configuration.html | 6 +- .../Connecting-ZimaCube-via-Thunderbolt.html | 6 +- .../Creating-RAID-Troubleshooting-Guide.html | 6 +- zimacube/Detailed-Plex-Operation-Guide.html | 6 +- ...maCube\357\274\214migrate-all-files!.html" | 6 +- zimacube/GPU-Expansion.html | 11 +- zimacube/HDD-Interface-Usage-Guide.html | 6 +- zimacube/Hardware-Brief.html | 6 +- zimacube/Hardware-Details.html | 6 +- zimacube/How-to-Install-ZimaOS.html | 6 +- ...How-to-Install-and-Remove-the-7th-Bay.html | 6 +- zimacube/How-to-Open-SSH-in-ZimaOS.html | 6 +- ...derstand-Docker-App's-paths-On-ZimaOS.html | 6 +- zimacube/Install-TrueNAS.html | 6 +- zimacube/Install-UnRAID.html | 6 +- .../Instructions-for-use-of-the-7th-Bay.html | 6 +- zimacube/PC-Direct.html | 6 +- zimacube/Plex-and-GPU-Transcoding.html | 6 +- zimacube/Quick-Start.html | 6 +- zimacube/RAID-SSD-Expansion.html | 6 +- zimacube/Release-Note.html | 6 +- zimacube/Resets-CMOS.html | 6 +- zimacube/Tutorials.html | 6 +- zimacube/User-Guide.html | 6 +- ...oard-DIY-Fan-Guide-and-Specifications.html | 6 +- zimacube/ZimaOS-application-content.html | 6 +- zimacube/index.html | 6 +- zimaos/7th-Bay-LED.html | 6 +- zimaos/A-list-of-Contributions.html | 6 +- zimaos/Achieve-Fastest-Transfer-Speed.html | 6 +- zimaos/Build-Apps.html | 6 +- zimaos/Build-Multiple-Clones-using-rsync.html | 6 +- zimaos/Connect-with-Cloud-Drives.html | 6 +- zimaos/Data-Migration.html | 6 +- zimaos/Detailed-Plex-Operation-Guide.html | 6 +- zimaos/Features.html | 6 +- zimaos/Get-Network-ID.html | 6 +- zimaos/Get-Started.html | 6 +- zimaos/How-to-Contribute.html | 6 +- ...lly-Download-the-Large-Language-Model.html | 6 +- zimaos/How-to-Open-SSH-in-ZimaOS.html | 6 +- ...ow-to-download-and-install-ZimaClient.html | 6 +- ...derstand-Docker-App's-paths-On-ZimaOS.html | 6 +- zimaos/How-to-use-OpenAPI.html | 6 +- zimaos/Install-offline.html | 6 +- zimaos/Link-Synology-and-SMB-Shares.html | 6 +- zimaos/Media-Server-Setup-with-Jellyfin.html | 6 +- zimaos/More-RAID-Options.html | 6 +- zimaos/NVR-Camera-Server.html | 8 +- zimaos/Networking.html | 6 +- zimaos/OpenAPI-Live-Preview.html | 6 +- zimaos/Recover-Your-Password.html | 6 +- zimaos/Romote-Access.html | 6 +- zimaos/Setup-Python.html | 6 +- zimaos/Sync-Photos-via-Configurable-CLI.html | 6 +- zimaos/Sync-Photos-with-Immich.html | 6 +- zimaos/Thunderbolt-PC-Direct.html | 6 +- zimaos/User-Guide.html | 6 +- zimaos/Using-Samba-as-a-Member.html | 6 +- zimaos/ZFS-Setup.html | 6 +- zimaos/index.html | 6 +- ...grate-files-from-Synology-to-ZimaCube.html | 6 +- zimaos/set-your-SSH.html | 6 +- zimaos/share-via-link.html | 6 +- zimaos/v-1.2.2.html | 6 +- zimaos/v-1.2.3.html | 6 +- zimaos/v-1.2.4.html | 6 +- 123 files changed, 658 insertions(+), 659 deletions(-) diff --git "a/docs/2-ZimaBlades\357\274\2141-Cluster\357\274\237PVE-makes-your-service-Migratable!.html" "b/docs/2-ZimaBlades\357\274\2141-Cluster\357\274\237PVE-makes-your-service-Migratable!.html" index d6b88a2085..2cb2507e5c 100644 --- "a/docs/2-ZimaBlades\357\274\2141-Cluster\357\274\237PVE-makes-your-service-Migratable!.html" +++ "b/docs/2-ZimaBlades\357\274\2141-Cluster\357\274\237PVE-makes-your-service-Migratable!.html" @@ -62,8 +62,8 @@ - - + + @@ -298,7 +298,7 @@
Loading...
ZimaBlade is a compact yet powerful server computer. PVE (Proxmox Virtual Environment) is a server virtualization management solution. You can use ZimaBlade with PVE to manage virtual machines, containers, and highly available clusters.
Today, we’ll set up our PVE Cluster using 2 ZimaBlade units to achieve service migration.
Here’s what you need:
2 ZimaBlade Kits: ZimaBlade Single Board Server
2 Hard Drives (SATA)
Additionally:
1 USB Drive for creating the PVE installation media
1 USB Hub so you can connect both your keyboard and USB drive to the ZimaBlade
2 RJ45 cables with LAN connections for networking
1 Keyboard and Monitor for initial setup
Here are the simple steps to install PVE on ZimaBlade:
Using Rufus
, write the PVE ISO file to a USB drive. You might need these resources:
Get Rufus: Rufus Download
Get PVE ISO: Proxmox Download
Write PVE to the USB drive to create the PVE installation media:
Insert the USB drive into a Windows host and launch the Rufus program on that host.
In Rufus, under “Device”, select the USB drive you just inserted.
Under “Boot selection”, click the SELECT button to choose the PVE ISO file from your disk.
Install memory, connect the Ethernet, and video cables to ZimaBlade. For a detailed step-by-step guide on installing memory and other components on ZimaBlade, refer to this comprehensive tutorial: Set up a NAS with ZimaBlade.
Now, let’s install PVE:
Safely remove the USB drive from the Windows machine and plug it, along with the keyboard, into the USB Hub.
Connect the USB Hub to ZimaBlade.
Power on the monitor.
Connect the power supply to ZimaBlade, then quickly and repeatedly press the DEL key on the keyboard to enter the ZimaBlade BIOS.
Use the arrow keys on the keyboard to navigate through the BIOS, and find the “Save & Exit” menu.
Under “Boot Override”, locate your USB drive and press Enter.
You will now enter the PVE installation UI.
When installing PVE on the 2 ZimaBlade units, keep these points in mind:
Install PVE on external storage (not on the internal eMMC).
Ensure they have consistent locale settings. Here’s an example:
Use different hostnames for each ZimaBlade.
Manually assign different IP addresses to each ZimaBlade (depending on your LAN configuration). Here’s an example:
Follow the prompts and wait for the installation to complete.
Choose any one of your ZimaBlade units and access the PVE WebUI at https://PVE1IP:8006
:
Click on “Cluster”, then “Create Cluster”. Give your cluster a name, then click “Create”:
After you see “TASK OK”, close the window, click on “Join Information”, and then click “Copy Information”:
Next, access the PVE WebUI on the second ZimaBlade at https://PVE2IP:8006
:
Click on “Cluster”, then “Join Cluster”, paste the join information you copied earlier, enter the root password of the other ZimaBlade, and click “Join **Cluster”:
Now, this machine is part of the Cluster. If you have more machines, the steps are the same. Once multiple nodes are joined to the Cluster, logging into the PVE WebUI on any ZimaBlade will show the presence of other nodes.
Now, you can install virtual machines and services on any node!
To migrate a service running on one node to another node in the Cluster:
Choose one node to install the system. Here, I will use Debian as an example.
Once installed, click the “Start” button on the right to start the virtual machine.
From another Windows machine on the same LAN, ping this virtual machine.
Service migration is just the beginning. With Ceph, you can automatically migrate services to other nodes in the Cluster when one node fails! In future articles, we will show you the complete setup process for ZimaBlade + Cluster + Ceph + HA.
If you encounter any issues during use, feel free to let us know at any time. You can also join our community and Discord to discuss more about PVE and ZimaBlade. We look forward to your feedback!
]]>Loading...
ZimaBlade is a compact yet powerful server computer. PVE (Proxmox Virtual Environment) is a server virtualization management solution. You can use ZimaBlade with PVE to manage virtual machines, containers, and highly available clusters.
Today, we’ll set up our PVE Cluster using 2 ZimaBlade units to achieve service migration.
Here’s what you need:
2 ZimaBlade Kits: ZimaBlade Single Board Server
2 Hard Drives (SATA)
Additionally:
1 USB Drive for creating the PVE installation media
1 USB Hub so you can connect both your keyboard and USB drive to the ZimaBlade
2 RJ45 cables with LAN connections for networking
1 Keyboard and Monitor for initial setup
Here are the simple steps to install PVE on ZimaBlade:
Using Rufus
, write the PVE ISO file to a USB drive. You might need these resources:
Get Rufus: Rufus Download
Get PVE ISO: Proxmox Download
Write PVE to the USB drive to create the PVE installation media:
Insert the USB drive into a Windows host and launch the Rufus program on that host.
In Rufus, under “Device”, select the USB drive you just inserted.
Under “Boot selection”, click the SELECT button to choose the PVE ISO file from your disk.
Install memory, connect the Ethernet, and video cables to ZimaBlade. For a detailed step-by-step guide on installing memory and other components on ZimaBlade, refer to this comprehensive tutorial: Set up a NAS with ZimaBlade.
Now, let’s install PVE:
Safely remove the USB drive from the Windows machine and plug it, along with the keyboard, into the USB Hub.
Connect the USB Hub to ZimaBlade.
Power on the monitor.
Connect the power supply to ZimaBlade, then quickly and repeatedly press the DEL key on the keyboard to enter the ZimaBlade BIOS.
Use the arrow keys on the keyboard to navigate through the BIOS, and find the “Save & Exit” menu.
Under “Boot Override”, locate your USB drive and press Enter.
You will now enter the PVE installation UI.
When installing PVE on the 2 ZimaBlade units, keep these points in mind:
Install PVE on external storage (not on the internal eMMC).
Ensure they have consistent locale settings. Here’s an example:
Use different hostnames for each ZimaBlade.
Manually assign different IP addresses to each ZimaBlade (depending on your LAN configuration). Here’s an example:
Follow the prompts and wait for the installation to complete.
Choose any one of your ZimaBlade units and access the PVE WebUI at https://PVE1IP:8006
:
Click on “Cluster”, then “Create Cluster”. Give your cluster a name, then click “Create”:
After you see “TASK OK”, close the window, click on “Join Information”, and then click “Copy Information”:
Next, access the PVE WebUI on the second ZimaBlade at https://PVE2IP:8006
:
Click on “Cluster”, then “Join Cluster”, paste the join information you copied earlier, enter the root password of the other ZimaBlade, and click “Join **Cluster”:
Now, this machine is part of the Cluster. If you have more machines, the steps are the same. Once multiple nodes are joined to the Cluster, logging into the PVE WebUI on any ZimaBlade will show the presence of other nodes.
Now, you can install virtual machines and services on any node!
To migrate a service running on one node to another node in the Cluster:
Choose one node to install the system. Here, I will use Debian as an example.
Once installed, click the “Start” button on the right to start the virtual machine.
From another Windows machine on the same LAN, ping this virtual machine.
Service migration is just the beginning. With Ceph, you can automatically migrate services to other nodes in the Cluster when one node fails! In future articles, we will show you the complete setup process for ZimaBlade + Cluster + Ceph + HA.
If you encounter any issues during use, feel free to let us know at any time. You can also join our community and Discord to discuss more about PVE and ZimaBlade. We look forward to your feedback!
]]> rm -fr /var/lib/casaos/db/user.db
4. Restart your device
5. Re-enter ZimaOS for initialization
Assist currently uses the “TheBloke/Llama-2-13b-Chat-GPTQ” by default for ZimaOS.
It can be downloaded manually and copied to the “/DATA/Assist/model/models–TheBloke–Llama-2-13b-Chat-GPTQ” folder on the Zima device at https://huggingface.co/TheBloke/Llama-2-13B-chat-GPTQ
Assist currently uses the “TheBloke/Llama-2-13b-Chat-GPTQ” by default for ZimaOS.
It can be downloaded manually and copied to the “/DATA/Assist/model/models–TheBloke–Llama-2-13b-Chat-GPTQ” folder on the Zima device at https://huggingface.co/TheBloke/Llama-2-13B-chat-GPTQ
rm -fr /var/lib/casaos/db/user.db
4. Restart your device
5. Re-enter ZimaOS for initialization
With a ZimaBoard performance somewhere between a Raspberry Pi and a MicroServer and a price positioning, the best use for the ZimaBoard for many gamers is undoubtedly to be a hundred-dollar, customizable, OpenWRT / pfSense x86 router with enough arithmetic power.
Based on this tutorial, we will demonstrate how to use the ZimaBoard’s pre-built system. After a few steps, this will pave the way for you to play around with the routing system you are familiar with.
Tips:
- This tutorial will install OpenWRT directly onto the ZimaBoard’s eMMC, overwrite and remove the pre-installed operating system. Please also save and backup your original system user data!
- OpenWRT Image, e.g., an image file with the .img suffix! If the .gz
On the PC, log in to ZimaBoard’s CasaOS panel via casaos.local
1. Upload the OpenWRT image prepared on your PC to the ZimaBoard storage
a.Click on the Files application, select a directory and click on the Upload Files button
2. From the local path, select Upload your OpenWRT image
3.Wait for the upload to complete
Login with your CasaOS account and password
Default Account Password
Account:casaos
Password:casaos
Enter lsblk and review to see if you are getting the target eMMC name, which should be mmcblk0
Unzip the image file (if your OpenWrt file is a zip archive)
gzip -d [.gz or .img.gz image name] |
Check that the decompression is working! Make sure there are no abnormalities in the image file
ls -lh |
Enter the following DD command to write the OpenWrt image uploaded to the ZimaBoard to the eMMC!
sudo dd if=/DATA/[upload path]/[name.img] of=/dev/mmcblk0 bs=1024k status=progress |
After the DD command has been executed, power off and reapply power to the ZimaBoard.
1. Configure your OpenWrt system IP address information and use a PC browser to log into the OpenWrt Luci page
{% note danger %} Attached is a tutorial on the OpenWrt IP address configuration command https://openwrt.org/docs/guide-user/network/openwrt_as_routerdevice {% endnote %}
2. Reboot and log in to your OpenWrt system
I prefer to run a purely separate system and service on each ZimaBoard. So, this is a much simpler way than booting OpenWRT on the ZimaBoard with a USB stick. If you are interested in having your ZimaBoard running dual systems at the same time, consider making a USB stick and switching the system the ZimaBoard is logged into via the Bios configuration.
For those interested in running CasaOS on your OpenWRT system, check out the tutorial!
]]>COVID-19 forced us to spend more time with our families. Previously, there was an introduction on how to build a home version of a 4K theater using ZimaBoard. Recently the theater is no longer enough for the family. So we found some fun games at home that are more suitable for adults and children. Good games can make family members closerand improve kid’s creative abilities.
Minecraft is a sandbox building game created by Markus Persson, founder of Mojang AB, and inspired by Endless Miner, Dwarf Fortress and Dungeon Keeper. The current lead developer is Jens Bergensten. Players can create and destroy a myriad of cubes in the game’s three-dimensional space and even experience different game modes on multiplayer servers versus single-player worlds to create exquisite buildings, creations, and artwork
By default, you know how to use ZimaBoard when reading this tutorial:ZimaBoard Tutorial
Similarly, here you have already purchased a My World account by default:MineCraft purchase link
Item | Description |
---|---|
Software | MineCraft Installation Links |
Paragraph | ZimaBoard 216 |
docker run -d \ |
.
Attention
Environment Variables EULA=TRUE
Be sure to always include -e EULA=TRUE in your commands and container definitions, as Mojang/Microsoft requires EULA acceptance.
Now open the My World client you installed earlier, here it is using MAC
If you don’t know your IP address, you can refer to the tutorial—“Find Your CasaOS IP Address“
By default, Minecraft servers are configured to run in Survival mode. You can change the mode using MODE where you can either provide the standard numerical values or the shortcut values:
|
Announce Player Achievements
|
More Information - Docker Minecraftf Server
1.Later there will be mc server docker application in CasaOS APP store (realize one minute to one click to install MC Server)
2.Zimaboard & Minecraft Advanced Version Play
The philosophy behind Minecraft is very simple to create a world that belongs to you; please guide your children correctly, participate with your children together, and control the gaming time. I believe you can get more beyond sheer joy and happiness.
]]>COVID-19 forced us to spend more time with our families. Previously, there was an introduction on how to build a home version of a 4K theater using ZimaBoard. Recently the theater is no longer enough for the family. So we found some fun games at home that are more suitable for adults and children. Good games can make family members closerand improve kid’s creative abilities.
Minecraft is a sandbox building game created by Markus Persson, founder of Mojang AB, and inspired by Endless Miner, Dwarf Fortress and Dungeon Keeper. The current lead developer is Jens Bergensten. Players can create and destroy a myriad of cubes in the game’s three-dimensional space and even experience different game modes on multiplayer servers versus single-player worlds to create exquisite buildings, creations, and artwork
By default, you know how to use ZimaBoard when reading this tutorial:ZimaBoard Tutorial
Similarly, here you have already purchased a My World account by default:MineCraft purchase link
Item | Description |
---|---|
Software | MineCraft Installation Links |
Paragraph | ZimaBoard 216 |
docker run -d \ |
.
Attention
Environment Variables EULA=TRUE
Be sure to always include -e EULA=TRUE in your commands and container definitions, as Mojang/Microsoft requires EULA acceptance.
Now open the My World client you installed earlier, here it is using MAC
If you don’t know your IP address, you can refer to the tutorial—“Find Your CasaOS IP Address“
By default, Minecraft servers are configured to run in Survival mode. You can change the mode using MODE where you can either provide the standard numerical values or the shortcut values:
|
Announce Player Achievements
|
More Information - Docker Minecraftf Server
1.Later there will be mc server docker application in CasaOS APP store (realize one minute to one click to install MC Server)
2.Zimaboard & Minecraft Advanced Version Play
The philosophy behind Minecraft is very simple to create a world that belongs to you; please guide your children correctly, participate with your children together, and control the gaming time. I believe you can get more beyond sheer joy and happiness.
]]>With a ZimaBoard performance somewhere between a Raspberry Pi and a MicroServer and a price positioning, the best use for the ZimaBoard for many gamers is undoubtedly to be a hundred-dollar, customizable, OpenWRT / pfSense x86 router with enough arithmetic power.
Based on this tutorial, we will demonstrate how to use the ZimaBoard’s pre-built system. After a few steps, this will pave the way for you to play around with the routing system you are familiar with.
Tips:
- This tutorial will install OpenWRT directly onto the ZimaBoard’s eMMC, overwrite and remove the pre-installed operating system. Please also save and backup your original system user data!
- OpenWRT Image, e.g., an image file with the .img suffix! If the .gz
On the PC, log in to ZimaBoard’s CasaOS panel via casaos.local
1. Upload the OpenWRT image prepared on your PC to the ZimaBoard storage
a.Click on the Files application, select a directory and click on the Upload Files button
2. From the local path, select Upload your OpenWRT image
3.Wait for the upload to complete
Login with your CasaOS account and password
Default Account Password
Account:casaos
Password:casaos
Enter lsblk and review to see if you are getting the target eMMC name, which should be mmcblk0
Unzip the image file (if your OpenWrt file is a zip archive)
gzip -d [.gz or .img.gz image name] |
Check that the decompression is working! Make sure there are no abnormalities in the image file
ls -lh |
Enter the following DD command to write the OpenWrt image uploaded to the ZimaBoard to the eMMC!
sudo dd if=/DATA/[upload path]/[name.img] of=/dev/mmcblk0 bs=1024k status=progress |
After the DD command has been executed, power off and reapply power to the ZimaBoard.
1. Configure your OpenWrt system IP address information and use a PC browser to log into the OpenWrt Luci page
{% note danger %} Attached is a tutorial on the OpenWrt IP address configuration command https://openwrt.org/docs/guide-user/network/openwrt_as_routerdevice {% endnote %}
2. Reboot and log in to your OpenWrt system
I prefer to run a purely separate system and service on each ZimaBoard. So, this is a much simpler way than booting OpenWRT on the ZimaBoard with a USB stick. If you are interested in having your ZimaBoard running dual systems at the same time, consider making a USB stick and switching the system the ZimaBoard is logged into via the Bios configuration.
For those interested in running CasaOS on your OpenWRT system, check out the tutorial!
]]>OpenMediaVault (OMV), a Debian Linux-based Network Attached Storage (NAS) solution for use in a home environment or small office, is a simple and easy-to-use out-of-box solution that can be easily installed and managed by any novice user and includes many standard data applications services such as SSH, SMB, DAAP Media Server, RSync. It can also be enhanced with modular design framework features for additional application extensions such as KVM, Docker, etc. On the other hand, the small size of ZimaBoard and the small size of the OMV means convenience for the user. Size really doesn’t matter!
If the image fails to write, you can use a disk tool such as Diskgenius to clear the partition and format information on the USB stick. Try writing the image again.
As the OMV installation process requires a networked environment in many places, it is important that the user connects Zima to a router or switch with a smooth Internet connection.
1.Insert the USB stick, connect the monitor with the miniDP cable, connect the keyboard, power on the ZimaBoard, and press the Del key on the keyboard continuously to enter the Bios.
2.By default, ZimaBoard’s BIOS uses its own eMMC as the preferred boot disk, as shown here
3. In Boot, adjust Boot Option #1 to partition 1 of the USB stick, as follows: "UEFI:Legend ZhenJBFast 1100"
is the partition where the OMV6 image is located, and "UEFI:Legend ZhenJBFast 1100
, Partition 1” is the remaining space on the USB stick. UEFI:Legend ZhenJBFast 1100, Partition 1"
is the remaining space on the USB stick, and the user should select "UEFI:Legend ZhenJBFast 1100"
as the boot preference.
4. After pressing Save & Exit, ZimaBoard will reboot and go to the OMV6 installation screen.
1.To initialize the installation, select Install and press enter
2.Select the language for the installation process; the default is English
3.By default, ZimaBoard has dual network ports, with enp2s0 being the one near the miniDP port and enp3s0 being the one near the power supply
4.When the installer asks the user to select the installation path of the OMV, please make sure it is set to “MMC/SD CARD”
5.The installer will ask the user to confirm that the ZimaBoard internal hard disk space is cleared of all contents and repartitioned
6.The installer then asks the user to set the initial password for the root account
tips:
Be sure to remember that this set of account’s passwords is required for subsequent background configuration operations.
7. When the installer asks the user to select the Debian image source, please make sure to select the user’s current country or region and choose the appropriate image source in it. Remember: This choice will greatly affect the user’s daily update/installation speed of various OMV plug-ins
8. When proceeding to the picture below, the fresh installation of OVM is complete, and the user can continue the OMV reboot after removing the USB drive.
]]>Please Note:
- If a wrong selection or setting is made during the installation process, you can press the Cancel button to go back to the installation progress directory and select the progress page the user needs to reset.
- After the new installation is complete, if the USB flash drive is removed before the OMV reboots, BIOS will automatically use the OMV boot partition in eMMC as the preferred boot disk, so users do not have to enter the BIOS again to set the Boot Option.
OpenMediaVault (OMV), a Debian Linux-based Network Attached Storage (NAS) solution for use in a home environment or small office, is a simple and easy-to-use out-of-box solution that can be easily installed and managed by any novice user and includes many standard data applications services such as SSH, SMB, DAAP Media Server, RSync. It can also be enhanced with modular design framework features for additional application extensions such as KVM, Docker, etc. On the other hand, the small size of ZimaBoard and the small size of the OMV means convenience for the user. Size really doesn’t matter!
If the image fails to write, you can use a disk tool such as Diskgenius to clear the partition and format information on the USB stick. Try writing the image again.
As the OMV installation process requires a networked environment in many places, it is important that the user connects Zima to a router or switch with a smooth Internet connection.
1.Insert the USB stick, connect the monitor with the miniDP cable, connect the keyboard, power on the ZimaBoard, and press the Del key on the keyboard continuously to enter the Bios.
2.By default, ZimaBoard’s BIOS uses its own eMMC as the preferred boot disk, as shown here
3. In Boot, adjust Boot Option #1 to partition 1 of the USB stick, as follows: "UEFI:Legend ZhenJBFast 1100"
is the partition where the OMV6 image is located, and "UEFI:Legend ZhenJBFast 1100
, Partition 1” is the remaining space on the USB stick. UEFI:Legend ZhenJBFast 1100, Partition 1"
is the remaining space on the USB stick, and the user should select "UEFI:Legend ZhenJBFast 1100"
as the boot preference.
4. After pressing Save & Exit, ZimaBoard will reboot and go to the OMV6 installation screen.
1.To initialize the installation, select Install and press enter
2.Select the language for the installation process; the default is English
3.By default, ZimaBoard has dual network ports, with enp2s0 being the one near the miniDP port and enp3s0 being the one near the power supply
4.When the installer asks the user to select the installation path of the OMV, please make sure it is set to “MMC/SD CARD”
5.The installer will ask the user to confirm that the ZimaBoard internal hard disk space is cleared of all contents and repartitioned
6.The installer then asks the user to set the initial password for the root account
tips:
Be sure to remember that this set of account’s passwords is required for subsequent background configuration operations.
7. When the installer asks the user to select the Debian image source, please make sure to select the user’s current country or region and choose the appropriate image source in it. Remember: This choice will greatly affect the user’s daily update/installation speed of various OMV plug-ins
8. When proceeding to the picture below, the fresh installation of OVM is complete, and the user can continue the OMV reboot after removing the USB drive.
]]>Please Note:
- If a wrong selection or setting is made during the installation process, you can press the Cancel button to go back to the installation progress directory and select the progress page the user needs to reset.
- After the new installation is complete, if the USB flash drive is removed before the OMV reboots, BIOS will automatically use the OMV boot partition in eMMC as the preferred boot disk, so users do not have to enter the BIOS again to set the Boot Option.
Tribute to the great OpenWRT Documentation, This article only documents the installation of OpenWRT on the ZimaBoard. There is currently another article on writing the OpenWRT system for the ZimaBoard eMMC.
OpenWRT is the best companion for the ZimaBoard USB stick login version– 5 steps to burn your favorite OpenWRT hombre firmware
Topics
With a performance between Raspberry Pi and MicroServer and a price positioning, the best use of the ZimaBoard for many gamers is undoubtedly to be a hundred-dollar , customizable, OpenWRT / pfSense x86 router with enough computing power. So, based on this simple tutorial, we will demonstrate how to make a USB stick boot disk and, after a few steps, log into OpenWRT.
For detailed steps, please see Universal Third Party System Installation
ZimaBoard via miniDP to HDMI / DP cable, access to the display, USB Keyboard to ZimaBoard
Insert the USB stick into the ZimaBoard, boot up and click “DEL” to log into the BIOS Page
In the Boot option, configure the USB flash drive as Boot Option #1, save the settings, and reboot. After boot, enter the USB drive OpenWRT
Configure your OpenWRT system IP address information and use a PC browser to log into the OpenWRT Luci page
Getting OpenWRT to run on a USB stick is a relatively simple way. But as an aspiring gamer, you can refer to the following tutorial if you wish to write your OpenWrt system to a ZimaBoard eMMC. If you are interested in running more interesting software services for network enhancement and home cloud data management on OpenWRT, check out this link!
Of course, there are other methods, and the OpenWRT firmware download address is also provided here—— Firmware Download Address
Please don’t abuse for the love of power
Tribute to the great OpenWRT Documentation, This article only documents the installation of OpenWRT on the ZimaBoard. There is currently another article on writing the OpenWRT system for the ZimaBoard eMMC.
OpenWRT is the best companion for the ZimaBoard USB stick login version– 5 steps to burn your favorite OpenWRT hombre firmware
Topics
With a performance between Raspberry Pi and MicroServer and a price positioning, the best use of the ZimaBoard for many gamers is undoubtedly to be a hundred-dollar , customizable, OpenWRT / pfSense x86 router with enough computing power. So, based on this simple tutorial, we will demonstrate how to make a USB stick boot disk and, after a few steps, log into OpenWRT.
For detailed steps, please see Universal Third Party System Installation
ZimaBoard via miniDP to HDMI / DP cable, access to the display, USB Keyboard to ZimaBoard
Insert the USB stick into the ZimaBoard, boot up and click “DEL” to log into the BIOS Page
In the Boot option, configure the USB flash drive as Boot Option #1, save the settings, and reboot. After boot, enter the USB drive OpenWRT
Configure your OpenWRT system IP address information and use a PC browser to log into the OpenWRT Luci page
Getting OpenWRT to run on a USB stick is a relatively simple way. But as an aspiring gamer, you can refer to the following tutorial if you wish to write your OpenWrt system to a ZimaBoard eMMC. If you are interested in running more interesting software services for network enhancement and home cloud data management on OpenWRT, check out this link!
Of course, there are other methods, and the OpenWRT firmware download address is also provided here—— Firmware Download Address
Please don’t abuse for the love of power
ZimaBlade is a compact, single-board server that transforms your storage needs into a seamless NAS experience. And not just on Earth, but even on Mars one day! Whether you’re a seasoned Linux enthusiast or a curious tech explorer, setting up your pocket-sized data sanctuary NAS with ZimaBlade is a breeze. Let’s dive in this tutorial!
What you need:
ZimaBlade: Your trusty single-board server!
SO-DIMM DDR3L: The memory module that powers your ZimaBlade.
Type-C 12V 3A Power Adapter: Keep your ZimaBlade juiced up.
MiniDP Cable: For connecting your display.
One to Two HDD or SSD (SATA Interface): Your storage heroes.
RJ45 Connector with LAN Connection: To keep your ZimaBlade networked.
USB Keyboard: For initial setup.
Screen: So you can see what’s happening during boot and setup.
You can find all the accessories in our Zima Store.
Also, give our quick-start video a glance. Let’s start!
Remove the black cover from ZimaBlade and open the transparent cover:
Use a screwdriver to open the transparent cover:
Insert the SO-DIMM until you hear a click.
Reassemble all the covers.
Connect ZimaBlade to your drive. Here, we use an HDD as an example:
To work properly, your drive needs data and a power supply from ZimaBlade. Use the SATA cable included in ZimaBlade package, which gets both data and power supply from ZimaBlade.
Connect ZimaBlade using an RJ45:
Connect ZimaBlade to a keyboard(USB) and a screen (miniDP):
Connect ZimaBlade to the power supply:
Use the type-C cable included in ZimaBlade package.
ZimaBlade’s type-C interface supports USB PD 3.1.
For long-term use with an HDD, consider using an external power supply.
Once you plug in the power, the device will automatically start. And then… boom! You’re in!
You’ll be prompted to enter the default account casaos
and password casaos
to login in.
Now, get ZimaBlade’s IP address:
Type ip addr
and press Enter
to see the IP address. It will be somting like 192.x.x.x
or 10.0.x.x
. (depending on your LAN configuration.)
The physical network interface enp2s0
IP address (eg :10.0.179.111
) has been noted, and it will be used for future login attempts if needed.
The IP addresses
127.x.x.x
(loopback) is for internal communication,10.x.x.x
(physical interface) is for network connections, and172.x.x.x
(Docker) is for container networking.
Open a browser on your phone or desktop computer and visit the IP address you just noted.
Follow the instructions to create a Web UI account.
After creating the account, you will be logged into the CasaOS Web UI.
Now, configure your disk. CasaOS will detect the disk connected. Click the storage setting button, then click the “Create Storage” button.
Choose the appropriate option for your needs. Your drive is now ready to be used as storage.
Use the “Files” app to upload and access your files!
Your ZimaBlade NAS is just set up! Enjoy!
If you encounter any issues during use, feel free to let us know at any time. You can also join our community and Discord to discuss more about NAS and ZimaBlade. We look forward to your feedback!
]]>ZimaBlade is a compact, single-board server that transforms your storage needs into a seamless NAS experience. And not just on Earth, but even on Mars one day! Whether you’re a seasoned Linux enthusiast or a curious tech explorer, setting up your pocket-sized data sanctuary NAS with ZimaBlade is a breeze. Let’s dive in this tutorial!
What you need:
ZimaBlade: Your trusty single-board server!
SO-DIMM DDR3L: The memory module that powers your ZimaBlade.
Type-C 12V 3A Power Adapter: Keep your ZimaBlade juiced up.
MiniDP Cable: For connecting your display.
One to Two HDD or SSD (SATA Interface): Your storage heroes.
RJ45 Connector with LAN Connection: To keep your ZimaBlade networked.
USB Keyboard: For initial setup.
Screen: So you can see what’s happening during boot and setup.
You can find all the accessories in our Zima Store.
Also, give our quick-start video a glance. Let’s start!
Remove the black cover from ZimaBlade and open the transparent cover:
Use a screwdriver to open the transparent cover:
Insert the SO-DIMM until you hear a click.
Reassemble all the covers.
Connect ZimaBlade to your drive. Here, we use an HDD as an example:
To work properly, your drive needs data and a power supply from ZimaBlade. Use the SATA cable included in ZimaBlade package, which gets both data and power supply from ZimaBlade.
Connect ZimaBlade using an RJ45:
Connect ZimaBlade to a keyboard(USB) and a screen (miniDP):
Connect ZimaBlade to the power supply:
Use the type-C cable included in ZimaBlade package.
ZimaBlade’s type-C interface supports USB PD 3.1.
For long-term use with an HDD, consider using an external power supply.
Once you plug in the power, the device will automatically start. And then… boom! You’re in!
You’ll be prompted to enter the default account casaos
and password casaos
to login in.
Now, get ZimaBlade’s IP address:
Type ip addr
and press Enter
to see the IP address. It will be somting like 192.x.x.x
or 10.0.x.x
. (depending on your LAN configuration.)
The physical network interface enp2s0
IP address (eg :10.0.179.111
) has been noted, and it will be used for future login attempts if needed.
The IP addresses
127.x.x.x
(loopback) is for internal communication,10.x.x.x
(physical interface) is for network connections, and172.x.x.x
(Docker) is for container networking.
Open a browser on your phone or desktop computer and visit the IP address you just noted.
Follow the instructions to create a Web UI account.
After creating the account, you will be logged into the CasaOS Web UI.
Now, configure your disk. CasaOS will detect the disk connected. Click the storage setting button, then click the “Create Storage” button.
Choose the appropriate option for your needs. Your drive is now ready to be used as storage.
Use the “Files” app to upload and access your files!
Your ZimaBlade NAS is just set up! Enjoy!
If you encounter any issues during use, feel free to let us know at any time. You can also join our community and Discord to discuss more about NAS and ZimaBlade. We look forward to your feedback!
]]>Many users do not know how to install the system after we have downloaded it. Do not know the clear installation steps, etc. This article will help users to solve the problem of installing the system
What you need to do on your computer to prepare.
ZimaBoard related preparation.
You may be asked to enter your system password during the process, just enter it and click OK.
The whole process will take a few minutes, depending on the size of your system image and the read/write speed of your USB drive.
After the ZimaBoard is plugged in, press the F11 key
/ Delete key
uninterrupted . When we insert the U disk boot disk, it will automatically display the USB key, select the USB key and press the Enter key
The new version of BIOS is under testing and will be released later.
Please ask for help in Discord if you encounter problems.
warning
If your ZimaBoard runs normally, upgrading the BIOS is not recommended!
Improper operation can cause the ZimaBoard to fail to start.
Many users do not know how to install the system after we have downloaded it. Do not know the clear installation steps, etc. This article will help users to solve the problem of installing the system
What you need to do on your computer to prepare.
ZimaBoard related preparation.
You may be asked to enter your system password during the process, just enter it and click OK.
The whole process will take a few minutes, depending on the size of your system image and the read/write speed of your USB drive.
After the ZimaBoard is plugged in, press the F11 key
/ Delete key
uninterrupted . When we insert the U disk boot disk, it will automatically display the USB key, select the USB key and press the Enter key
The new version of BIOS is under testing and will be released later.
Please ask for help in Discord if you encounter problems.
warning
If your ZimaBoard runs normally, upgrading the BIOS is not recommended!
Improper operation can cause the ZimaBoard to fail to start.
Currently, ZimaCube requires pressing the power button to start after being plugged in. Some users desire an auto-start function upon power being supplied.
Modify mainboard jumper pins.
Move the jumper cap position. The two pins near AUTO indicate the need to press the power button after plugging in, while the two pins near PWR1 indicate automatic startup upon plugging in.
Below is the position for requiring the power button press to start after power off:
Below is the position for automatic startup after plugging in:
You can modify the position according to your needs.
Currently, ZimaCube requires pressing the power button to start after being plugged in. Some users desire an auto-start function upon power being supplied.
Modify mainboard jumper pins.
Move the jumper cap position. The two pins near AUTO indicate the need to press the power button after plugging in, while the two pins near PWR1 indicate automatic startup upon plugging in.
Below is the position for requiring the power button press to start after power off:
Below is the position for automatic startup after plugging in:
You can modify the position according to your needs.
ZimaCube is a computing device that can meet your professional work needs. Through its modular design, it allows users to expand hardware according to personal requirements, including the installation of a Graphics Processing Unit (GPU). A GPU is crucial for users who need to handle extensive graphical processing and parallel computing tasks.
Utilizing GPU for hardware transcoding can greatly improve media processing performance. For instance, Plex Media Server can use the GPU on ZimaOS to enable efficient hardware transcoding (note: download the professional GPU version of Plex).
Before: | After: |
---|---|
For a list of Nvidia GPUs currently supported by ZimaOS, see the Current NVIDIA GPUs section:https://us.download.nvidia.com/XFree86/Linux-x86_64/555.58.02/README/supportedchips.html
On ZimaOS, you can use Open WebUI to experience advanced AI conversation clients.
It supports the latest language models, including but not limited to Llama3 and Gemma, and is compatible with OpenAI’s API. Additionally, Open WebUI will call on the ZimaCube Pro Creator’s built-in NVIDIA 2000 Ada GPU to reduce processing latency.
Most importantly, all your data (including login details) is locally stored on your device. Open WebUI ensures strict confidentiality under your authorization, with no external requests, protecting your privacy and enhancing your security.
Tasking AI is an intelligent task management tool that utilizes AI technology to help users more efficiently organize and manage daily tasks. It can intelligently prioritize, remind, and automate tasks, improving efficiency in work and life.
Anything AI is a multi-functional AI application that provides a variety of practical AI tools and services, including text generation, language translation, and speech recognition. It aims to simplify daily work and life for users through powerful AI technology.
With these AI applications, you can fully utilize the advantages of artificial intelligence to enhance your work efficiency and quality of life!
Please refer to this document::https://docs.zimaspace.com/zimacube/GPU-Expansion.html
This guide should help you successfully install a GPU on ZimaCube and understand its importance in various applications. We encourage you to try out the installation and explore more GPU functions to enhance your work efficiency and quality of life.
We look forward to hearing more about your experiences!
The ZimaCube supports low-profile graphics cards, typically around 64.41 mm (2.536 inches) in height. The PCIe slot provides up to 75W of power, so it is recommended to select graphics cards within this size and power range to ensure compatibility with ZimaCube’s compact design and power limitations.
Please note that other graphics cards may require external power for proper operation.
Note:We’ve compiled this list based on the drivers supported by the ZimaOS, with “verified” models marked accordingly. If you’ve successfully run Assist on a different graphics card model, please help us update this list by using the ‘Improve’ feature in the top right corner. Thank you for your contribution.
Category | Models |
---|---|
GeForce RTX 40 Series (Notebooks) | GeForce RTX 4090 Laptop GPU, GeForce RTX 4080 Laptop GPU, GeForce RTX 4070 Laptop GPU, GeForce RTX 4060 Laptop GPU, GeForce RTX 4050 Laptop GPU |
GeForce RTX 40 Series | NVIDIA GeForce RTX 4090 D, NVIDIA GeForce RTX 4090, NVIDIA GeForce RTX 4080, NVIDIA GeForce RTX 4070 Ti, NVIDIA GeForce RTX 4070, NVIDIA GeForce RTX 4060 Ti(verified), NVIDIA GeForce RTX 4060 |
GeForce RTX 30 Series (Notebooks) | GeForce RTX 3080 Ti Laptop GPU, GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Ti Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU |
GeForce RTX 30 Series | GeForce RTX 3090 Ti, GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti(verified), GeForce RTX 3060, GeForce RTX 3050 |
GeForce RTX 20 Series (Notebooks) | GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060, GeForce RTX 2050 |
GeForce RTX 20 Series | GeForce RTX 2080 Ti, GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060 SUPER, GeForce RTX 2060 |
GeForce MX500 Series (Notebooks) | GeForce MX570, GeForce MX550 |
GeForce MX400 Series (Notebooks) | GeForce MX450 |
GeForce MX300 Series (Notebooks) | GeForce MX350, GeForce MX330 |
GeForce MX200 Series (Notebooks) | GeForce MX250, GeForce MX230 |
GeForce MX100 Series (Notebooks) | GeForce MX150, GeForce MX130, GeForce MX110 |
GeForce GTX 16 Series (Notebooks) | GeForce GTX 1660 Ti, GeForce GTX 1650 Ti, GeForce GTX 1650 |
GeForce 16 Series | GeForce GTX 1660 SUPER, GeForce GTX 1650 SUPER, GeForce GTX 1660 Ti, GeForce GTX 1660, GeForce GTX 1650, GeForce GTX 1630 |
GeForce 10 Series | GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030, GeForce GT 1010 |
GeForce 10 Series (Notebooks) | GeForce GTX 1080, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050 |
GeForce 900 Series | GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950 |
GeForce 900M Series (Notebooks) | GeForce GTX 980, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, GeForce GTX 960M, GeForce GTX 950M, GeForce 945M, GeForce 940MX, GeForce 930MX, GeForce 920MX, GeForce 940M, GeForce 930M |
GeForce 800M Series (Notebooks) | GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M |
GeForce 700 Series | GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 745 |
NVIDIA TITAN Series | NVIDIA TITAN RTX, NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal), GeForce GTX TITAN X |
NVIDIA RTX Series | NVIDIA RTX 6000 Ada Generation, NVIDIA RTX 5880 Ada Generation, NVIDIA RTX 5000 Ada Generation, NVIDIA RTX 4500 Ada Generation, NVIDIA RTX 4000 Ada Generation, NVIDIA RTX 4000 SFF Ada Generation, NVIDIA RTX A6000, NVIDIA RTX A5500, NVIDIA RTX A5000, NVIDIA RTX A4500, NVIDIA RTX A4000H, NVIDIA RTX A4000, NVIDIA RTX A2000 12GB(verified), NVIDIA RTX A2000, NVIDIA A800 40GB Active, NVIDIA T1000 8GB, NVIDIA T1000, NVIDIA T600, NVIDIA T400 4GB, NVIDIA T400 |
NVIDIA RTX Series (Notebooks) | NVIDIA RTX 5000 Ada Generation Laptop GPU, NVIDIA RTX 4000 Ada Generation Laptop GPU, NVIDIA RTX 3500 Ada Generation Laptop GPU, NVIDIA RTX 3000 Ada Generation Laptop GPU, NVIDIA RTX 2000 Ada Generation Laptop GPU, NVIDIA RTX A5500 Laptop GPU, NVIDIA RTX A5000 Laptop GPU, NVIDIA RTX A4500 Laptop GPU, NVIDIA RTX A4000 Laptop GPU, NVIDIA RTX A3000 12GB Laptop GPU, NVIDIA RTX A3000 Laptop GPU, NVIDIA RTX A2000 8GB Laptop GPU, NVIDIA RTX A2000 Laptop GPU, NVIDIA RTX A1000 Laptop GPU, NVIDIA RTX A500 Laptop GPU, NVIDIA T1200 Laptop GPU , NVIDIA T600 Laptop GPU, NVIDIA T550 Laptop GPU, NVIDIA T500 |
Quadro RTX Series | Quadro RTX 8000, Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000 |
Quadro RTX Series (Notebooks) | Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000 |
Quadro Series | Quadro GV100, Quadro GP100, Quadro P6000, Quadro P5200, Quadro P5000, Quadro P4000, Quadro P2200, Quadro P2000, Quadro P1000, Quadro P620, Quadro P600, Quadro P400, Quadro M6000 24GB, Quadro M6000, Quadro M5000, Quadro M4000, Quadro M2000, Quadro K2200, Quadro K1200, Quadro K620 |
Quadro Series (Notebooks) | Quadro T2000, Quadro T1000, Quadro P5200, Quadro P5000, Quadro P4200, Quadro P3200, Quadro P4000, Quadro P3000, Quadro P2000, Quadro P1000, Quadro P600, Quadro P520, Quadro P500, Quadro M2200, Quadro M1200, Quadro M620, Quadro M520, Quadro M5500, Quadro M5000M, Quadro M4000M, Quadro M3000M, Quadro M2000M, Quadro M1000M, Quadro M600M, Quadro M500M, Quadro K2200M, Quadro K620M |
Quadro Blade/Embedded Series | Quadro P5000, Quadro P3000, Quadro M5000 SE, Quadro M3000 SE |
Quadro NVS Series | NVS 810 |
NVS Series | NVS 810 |
More to come…
]]>ZimaCube is a computing device that can meet your professional work needs. Through its modular design, it allows users to expand hardware according to personal requirements, including the installation of a Graphics Processing Unit (GPU). A GPU is crucial for users who need to handle extensive graphical processing and parallel computing tasks.
Utilizing GPU for hardware transcoding can greatly improve media processing performance. For instance, Plex Media Server can use the GPU on ZimaOS to enable efficient hardware transcoding (note: download the professional GPU version of Plex).
Before: | After: |
---|---|
For a list of Nvidia GPUs currently supported by ZimaOS, see the Current NVIDIA GPUs section:https://us.download.nvidia.com/XFree86/Linux-x86_64/555.58.02/README/supportedchips.html
On ZimaOS, you can use Open WebUI to experience advanced AI conversation clients.
It supports the latest language models, including but not limited to Llama3 and Gemma, and is compatible with OpenAI’s API. Additionally, Open WebUI will call on the ZimaCube Pro Creator’s built-in NVIDIA 2000 Ada GPU to reduce processing latency.
Most importantly, all your data (including login details) is locally stored on your device. Open WebUI ensures strict confidentiality under your authorization, with no external requests, protecting your privacy and enhancing your security.
Tasking AI is an intelligent task management tool that utilizes AI technology to help users more efficiently organize and manage daily tasks. It can intelligently prioritize, remind, and automate tasks, improving efficiency in work and life.
Anything AI is a multi-functional AI application that provides a variety of practical AI tools and services, including text generation, language translation, and speech recognition. It aims to simplify daily work and life for users through powerful AI technology.
With these AI applications, you can fully utilize the advantages of artificial intelligence to enhance your work efficiency and quality of life!
This guide should help you successfully install a GPU on ZimaCube and understand its importance in various applications. We encourage you to try out the installation and explore more GPU functions to enhance your work efficiency and quality of life.
We look forward to hearing more about your experiences!
The ZimaCube supports low-profile graphics cards, typically around 64.41 mm (2.536 inches) in height. The PCIe slot provides up to 75W of power, so it is recommended to select graphics cards within this size and power range to ensure compatibility with ZimaCube’s compact design and power limitations.
Please note that other graphics cards may require external power for proper operation.
Note:We’ve compiled this list based on the drivers supported by the ZimaOS, with “verified” models marked accordingly. If you’ve successfully run Assist on a different graphics card model, please help us update this list by using the ‘Improve’ feature in the top right corner. Thank you for your contribution.
Category | Models |
---|---|
GeForce RTX 40 Series (Notebooks) | GeForce RTX 4090 Laptop GPU, GeForce RTX 4080 Laptop GPU, GeForce RTX 4070 Laptop GPU, GeForce RTX 4060 Laptop GPU, GeForce RTX 4050 Laptop GPU |
GeForce RTX 40 Series | NVIDIA GeForce RTX 4090 D, NVIDIA GeForce RTX 4090, NVIDIA GeForce RTX 4080, NVIDIA GeForce RTX 4070 Ti, NVIDIA GeForce RTX 4070, NVIDIA GeForce RTX 4060 Ti(verified), NVIDIA GeForce RTX 4060 |
GeForce RTX 30 Series (Notebooks) | GeForce RTX 3080 Ti Laptop GPU, GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Ti Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU |
GeForce RTX 30 Series | GeForce RTX 3090 Ti, GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti(verified), GeForce RTX 3060, GeForce RTX 3050 |
GeForce RTX 20 Series (Notebooks) | GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060, GeForce RTX 2050 |
GeForce RTX 20 Series | GeForce RTX 2080 Ti, GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060 SUPER, GeForce RTX 2060 |
GeForce MX500 Series (Notebooks) | GeForce MX570, GeForce MX550 |
GeForce MX400 Series (Notebooks) | GeForce MX450 |
GeForce MX300 Series (Notebooks) | GeForce MX350, GeForce MX330 |
GeForce MX200 Series (Notebooks) | GeForce MX250, GeForce MX230 |
GeForce MX100 Series (Notebooks) | GeForce MX150, GeForce MX130, GeForce MX110 |
GeForce GTX 16 Series (Notebooks) | GeForce GTX 1660 Ti, GeForce GTX 1650 Ti, GeForce GTX 1650 |
GeForce 16 Series | GeForce GTX 1660 SUPER, GeForce GTX 1650 SUPER, GeForce GTX 1660 Ti, GeForce GTX 1660, GeForce GTX 1650, GeForce GTX 1630 |
GeForce 10 Series | GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030, GeForce GT 1010 |
GeForce 10 Series (Notebooks) | GeForce GTX 1080, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050 |
GeForce 900 Series | GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950 |
GeForce 900M Series (Notebooks) | GeForce GTX 980, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, GeForce GTX 960M, GeForce GTX 950M, GeForce 945M, GeForce 940MX, GeForce 930MX, GeForce 920MX, GeForce 940M, GeForce 930M |
GeForce 800M Series (Notebooks) | GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M |
GeForce 700 Series | GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 745 |
NVIDIA TITAN Series | NVIDIA TITAN RTX, NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal), GeForce GTX TITAN X |
NVIDIA RTX Series | NVIDIA RTX 6000 Ada Generation, NVIDIA RTX 5880 Ada Generation, NVIDIA RTX 5000 Ada Generation, NVIDIA RTX 4500 Ada Generation, NVIDIA RTX 4000 Ada Generation, NVIDIA RTX 4000 SFF Ada Generation, NVIDIA RTX A6000, NVIDIA RTX A5500, NVIDIA RTX A5000, NVIDIA RTX A4500, NVIDIA RTX A4000H, NVIDIA RTX A4000, NVIDIA RTX A2000 12GB(verified), NVIDIA RTX A2000, NVIDIA A800 40GB Active, NVIDIA T1000 8GB, NVIDIA T1000, NVIDIA T600, NVIDIA T400 4GB, NVIDIA T400 |
NVIDIA RTX Series (Notebooks) | NVIDIA RTX 5000 Ada Generation Laptop GPU, NVIDIA RTX 4000 Ada Generation Laptop GPU, NVIDIA RTX 3500 Ada Generation Laptop GPU, NVIDIA RTX 3000 Ada Generation Laptop GPU, NVIDIA RTX 2000 Ada Generation Laptop GPU, NVIDIA RTX A5500 Laptop GPU, NVIDIA RTX A5000 Laptop GPU, NVIDIA RTX A4500 Laptop GPU, NVIDIA RTX A4000 Laptop GPU, NVIDIA RTX A3000 12GB Laptop GPU, NVIDIA RTX A3000 Laptop GPU, NVIDIA RTX A2000 8GB Laptop GPU, NVIDIA RTX A2000 Laptop GPU, NVIDIA RTX A1000 Laptop GPU, NVIDIA RTX A500 Laptop GPU, NVIDIA T1200 Laptop GPU , NVIDIA T600 Laptop GPU, NVIDIA T550 Laptop GPU, NVIDIA T500 |
Quadro RTX Series | Quadro RTX 8000, Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000 |
Quadro RTX Series (Notebooks) | Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000 |
Quadro Series | Quadro GV100, Quadro GP100, Quadro P6000, Quadro P5200, Quadro P5000, Quadro P4000, Quadro P2200, Quadro P2000, Quadro P1000, Quadro P620, Quadro P600, Quadro P400, Quadro M6000 24GB, Quadro M6000, Quadro M5000, Quadro M4000, Quadro M2000, Quadro K2200, Quadro K1200, Quadro K620 |
Quadro Series (Notebooks) | Quadro T2000, Quadro T1000, Quadro P5200, Quadro P5000, Quadro P4200, Quadro P3200, Quadro P4000, Quadro P3000, Quadro P2000, Quadro P1000, Quadro P600, Quadro P520, Quadro P500, Quadro M2200, Quadro M1200, Quadro M620, Quadro M520, Quadro M5500, Quadro M5000M, Quadro M4000M, Quadro M3000M, Quadro M2000M, Quadro M1000M, Quadro M600M, Quadro M500M, Quadro K2200M, Quadro K620M |
Quadro Blade/Embedded Series | Quadro P5000, Quadro P3000, Quadro M5000 SE, Quadro M3000 SE |
Quadro NVS Series | NVS 810 |
NVS Series | NVS 810 |
More to come…
]]>Docker is platform that enables users to automate the deployment, scaling, and management of applications in lightweight containers. These containers bundle an application with all its dependencies, ensuring consistent performance across various environments. Docker’s efficiency lies in its ability to isolate applications, making them more portable and scalable.
ZimaOS is really impressive when we talk about Docker apps, streamlining the process with just a few clicks. ZimaOS is also a game-changer for NAS enthusiasts, pro users and studio users. Its intuitive interface simplifies data backup and management.
But do you really understand the path when using Dockers apps on ZimaOS? Can you distinguish between the ZimaOS path and the Docker apps path?
When you run a Docker container, it operates within its own filesystem, separate from the host system. Here’s a general overview of how Docker organizes paths:
Container Filesystem: Inside a Docker container, the file system is isolated from the host machine. Applications running in a container see their own root filesystem, which typically starts from /. For instance, if you have an application that stores data in /app/data within the container, this path exists solely within that container’s filesystem.
Volumes: To persist data beyond the lifecycle of a container, Docker uses volumes. Volumes are directories or files outside the container’s filesystem, usually located on the host system, and can be shared between containers. They are often mounted into containers at specific paths.
There are other data sharing modes, which you can learn here.
Let’s take plex, a popular media server application, as an example to understand how paths are organized within ZimaOS using Docker.
Docker App: Plex is distributed as a Docker app in ZimaOS’ app store. When you install Plex from ZimaOS’ app store, ZimaOS will specify several paths for various directories:
/config in container: this directory holds Plex’s configuration files. On ZimaOS, its volume path is /DATA/AppData/plex/config on ZimaOS, which is mounted to container’s /config to ensure configurations persist across container restarts.
/media in container: this is where Plex accesses your media files. Also, media files’ volume path is /DATA/Media on ZimaOS and it is mounted to containers’s /media.
Keep in mind that we want files stored in the host. This way, even if a container is stopped or recreated, the data remains intact.
You can find the detailed configuration by clicking Plex’s Settings. Besides, on this page, the volume path can be easily modified by clicking the grey icon next to the volume path.
By understanding Docker paths and how they integrate with applications like Plex, NAS enthusiasts and Homelabbers can efficiently manage their applications in a way that combines the flexibility of containerization with the reliability of persistent storage.
1X ZimaCube N100 prototype V2.0
1X Monitor
1X HDMI/DP Cable
1X Keyboard
1X Ethernet cable
1X USB flash drive (as installation disk)
Click on the official link below:
https://www.truenas.com/download-truenas-core/
Use Rufus, select the USB disk device and add the iso file;
Docker is platform that enables users to automate the deployment, scaling, and management of applications in lightweight containers. These containers bundle an application with all its dependencies, ensuring consistent performance across various environments. Docker’s efficiency lies in its ability to isolate applications, making them more portable and scalable.
ZimaOS is really impressive when we talk about Docker apps, streamlining the process with just a few clicks. ZimaOS is also a game-changer for NAS enthusiasts, pro users and studio users. Its intuitive interface simplifies data backup and management.
But do you really understand the path when using Dockers apps on ZimaOS? Can you distinguish between the ZimaOS path and the Docker apps path?
When you run a Docker container, it operates within its own filesystem, separate from the host system. Here’s a general overview of how Docker organizes paths:
Container Filesystem: Inside a Docker container, the file system is isolated from the host machine. Applications running in a container see their own root filesystem, which typically starts from /. For instance, if you have an application that stores data in /app/data within the container, this path exists solely within that container’s filesystem.
Volumes: To persist data beyond the lifecycle of a container, Docker uses volumes. Volumes are directories or files outside the container’s filesystem, usually located on the host system, and can be shared between containers. They are often mounted into containers at specific paths.
There are other data sharing modes, which you can learn here.
Let’s take plex, a popular media server application, as an example to understand how paths are organized within ZimaOS using Docker.
Docker App: Plex is distributed as a Docker app in ZimaOS’ app store. When you install Plex from ZimaOS’ app store, ZimaOS will specify several paths for various directories:
/config in container: this directory holds Plex’s configuration files. On ZimaOS, its volume path is /DATA/AppData/plex/config on ZimaOS, which is mounted to container’s /config to ensure configurations persist across container restarts.
/media in container: this is where Plex accesses your media files. Also, media files’ volume path is /DATA/Media on ZimaOS and it is mounted to containers’s /media.
Keep in mind that we want files stored in the host. This way, even if a container is stopped or recreated, the data remains intact.
You can find the detailed configuration by clicking Plex’s Settings. Besides, on this page, the volume path can be easily modified by clicking the grey icon next to the volume path.
By understanding Docker paths and how they integrate with applications like Plex, NAS enthusiasts and Homelabbers can efficiently manage their applications in a way that combines the flexibility of containerization with the reliability of persistent storage.
Ensure that the ZimaCube is powered off and unplugged.
Prepare the hard drive to be installed.
Step 1: Remove the front panel of the case.
Step 2: Remove the 6th bay.
Step 3: Turn counterclockwise to unscrew the screws securing the seventh drive.
Step 4: Remove the 7th bay.
Step 5: Freely install the SSD onto the 7th bay.
Step 6: Push the 7th bay into the correct position and tighten the screws clockwise.
1X ZimaCube N100 prototype V2.0
1X Monitor
1X HDMI/DP Cable
1X Keyboard
1X Ethernet cable
1X USB flash drive (as installation disk)
Click on the official link below:
https://www.truenas.com/download-truenas-core/
Use Rufus, select the USB disk device and add the iso file;
Whether you’re using a ZimaOS device for personal or professional purposes, understanding how to connect to it through various networks is essential. This guide will cover three main types of network connections: direct connection, Local Area Network (LAN), and Wide Area Network (WAN). Each method has unique benefits and applications, ensuring you can access and manage your data seamlessly, whether you’re at home or on the go.
This article is for understanding connections under different networks.
Direct connections are ideal for quick and straightforward setups, offering a fast and secure way to link devices without needing a broader network. This method is perfect for file transfers or using specific applications that require high-speed access.
Tips:If you encounter any problems during using Thounderbolt , you can get more detailed information here
What You Need:
Network cable or Thunderbolt cable for high-speed connections
ZimaOS device (ZimaCube Pro is Thunderbolt equipped) and client device (laptop, desktop PC, etc.)
Steps:
Establish the Connection: Use a standard network cable to connect your client device to ZimaOS device directly or utilize the Thunderbolt(for ZimaCube Pro users) cable for speeds up to 20G, ideal for demanding tasks.
Network Configuration: IP is assigned through auto-configuration features. And it will be like 169.254.x.x.
This Means Your Successful Connection: An IP like 169.254.x.x shown on screen indicates a direct connection success.
Application Example and Use Cases: Take advantage of the high-speed connection, particularly useful for video editing or other bandwidth-intensive tasks. It is ideal for scenarios where low-latency and high-speed data transfer are crucial.
Connecting your ZimaOS devices via a LAN provides a robust and stable network environment, perfect for households or small businesses where multiple devices need to share resources efficiently.
What You Need:
Router or network switch
ZimaOS device (ZimaCube Pro is 10G NIC equipped) and client device (phone, laptop, desktop PC, etc.)
Steps:
Connect to the Network: Connect your ZimaOS device and other client devices to the router or switch.
Network Configuration: Check that all devices are on the same subnet and can communicate with each other. It will be something like 192.168.x.x or 10.0.x.x, depending on your LAN configuration. You can manually assign static IP addresses for consistent device identification, or rely on DHCP for automatic assignment.
This Means Your Success Connection: An IP like 192.168.x.x shown on screen indicates a LAN connection success. The LAN IP depends on your LAN configuration.
Application Example and Use Cases: Stream and manage media content across devices, enjoying seamless access to your library. Best for environments needing reliable and fast local network access, such as media servers or shared file storage.
When you both have a direct connection and a LAN connection, which one will be chosen?
If you have read our tutorial 4 about SAMBA, an important way to experience NAS, you will probably master the right way to mount your NAS drive to your client device. The point is, there are two rules here to be noted:
Thunderbolt is preferred when you use the Zima app.
You can choose the specific connection by manually mounting folders through the corresponding IP.
WAN connections enable remote access to your ZimaOS devices, allowing you to connect from anywhere with the Internet connection. This is particularly useful for remote work or accessing personal data while traveling.
For enhanced security and ease of access, we use Zerotier to create a virtual network, simplifying the connection process.
What You Need:
Internet connection for each device
Obtain the ZimaOS device Remote Login ID. This ID is a Zerotier ID, which you can obtain from ZimaOS dashboard → Network → Remote Login.
For your Windows/Mac, a Zima APP 5 (Zerotier integrated) is needed.
Steps:
Establish the Connection: Download and launch the zima app on your Windows/Mac. Click the app icon to the right of the system taskbar and select Connect by Network ID. After that, you may need to input your WebUI’s username and password.
Network Configuration: Basically, you don’t need any further network configuration since Zima app has done these for you.
**This Means Your Success Connection: **You will be navigated to ZimaOS’ dashboard.
Application Example and Use Cases: Use WAN connections to securely access critical files or manage devices in emergencies. It is ideal for users needing to manage or access their ZimaOS devices remotely, ensuring continuous availability of important data.
Optional: Public IP address with a dynamic DNS configured would be an option, since you can access your device through a domain name directly.
No matter your needs, ZimaOS provides flexible and powerful connectivity options to suit any situation. From high-speed direct connections to convenient remote access via WAN, you can manage your devices and data effortlessly. Always consider security measures, especially when dealing with WAN connections, to protect your information and maintain smooth operations.
If you encounter any issues during use, feel free to let us know at any time. You can also join our community and Discord to discuss more about ZimaCube and ZimaOS. We look forward to your feedback!
]]>Ensure that the ZimaCube is powered off and unplugged.
Prepare the hard drive to be installed.
Step 1: Remove the front panel of the case.
Step 2: Remove the 6th bay.
Step 3: Turn counterclockwise to unscrew the screws securing the seventh drive.
Step 4: Remove the 7th bay.
Step 5: Freely install the SSD onto the 7th bay.
Step 6: Push the 7th bay into the correct position and tighten the screws clockwise.
Whether you’re using a ZimaOS device for personal or professional purposes, understanding how to connect to it through various networks is essential. This guide will cover three main types of network connections: direct connection, Local Area Network (LAN), and Wide Area Network (WAN). Each method has unique benefits and applications, ensuring you can access and manage your data seamlessly, whether you’re at home or on the go.
This article is for understanding connections under different networks.
Direct connections are ideal for quick and straightforward setups, offering a fast and secure way to link devices without needing a broader network. This method is perfect for file transfers or using specific applications that require high-speed access.
Tips:If you encounter any problems during using Thounderbolt , you can get more detailed information here
What You Need:
Network cable or Thunderbolt cable for high-speed connections
ZimaOS device (ZimaCube Pro is Thunderbolt equipped) and client device (laptop, desktop PC, etc.)
Steps:
Establish the Connection: Use a standard network cable to connect your client device to ZimaOS device directly or utilize the Thunderbolt(for ZimaCube Pro users) cable for speeds up to 20G, ideal for demanding tasks.
Network Configuration: IP is assigned through auto-configuration features. And it will be like 169.254.x.x.
This Means Your Successful Connection: An IP like 169.254.x.x shown on screen indicates a direct connection success.
Application Example and Use Cases: Take advantage of the high-speed connection, particularly useful for video editing or other bandwidth-intensive tasks. It is ideal for scenarios where low-latency and high-speed data transfer are crucial.
Connecting your ZimaOS devices via a LAN provides a robust and stable network environment, perfect for households or small businesses where multiple devices need to share resources efficiently.
What You Need:
Router or network switch
ZimaOS device (ZimaCube Pro is 10G NIC equipped) and client device (phone, laptop, desktop PC, etc.)
Steps:
Connect to the Network: Connect your ZimaOS device and other client devices to the router or switch.
Network Configuration: Check that all devices are on the same subnet and can communicate with each other. It will be something like 192.168.x.x or 10.0.x.x, depending on your LAN configuration. You can manually assign static IP addresses for consistent device identification, or rely on DHCP for automatic assignment.
This Means Your Success Connection: An IP like 192.168.x.x shown on screen indicates a LAN connection success. The LAN IP depends on your LAN configuration.
Application Example and Use Cases: Stream and manage media content across devices, enjoying seamless access to your library. Best for environments needing reliable and fast local network access, such as media servers or shared file storage.
When you both have a direct connection and a LAN connection, which one will be chosen?
If you have read our tutorial 4 about SAMBA, an important way to experience NAS, you will probably master the right way to mount your NAS drive to your client device. The point is, there are two rules here to be noted:
Thunderbolt is preferred when you use the Zima app.
You can choose the specific connection by manually mounting folders through the corresponding IP.
WAN connections enable remote access to your ZimaOS devices, allowing you to connect from anywhere with the Internet connection. This is particularly useful for remote work or accessing personal data while traveling.
For enhanced security and ease of access, we use Zerotier to create a virtual network, simplifying the connection process.
What You Need:
Internet connection for each device
Obtain the ZimaOS device Remote Login ID. This ID is a Zerotier ID, which you can obtain from ZimaOS dashboard → Network → Remote Login.
For your Windows/Mac, a Zima APP 5 (Zerotier integrated) is needed.
Steps:
Establish the Connection: Download and launch the zima app on your Windows/Mac. Click the app icon to the right of the system taskbar and select Connect by Network ID. After that, you may need to input your WebUI’s username and password.
Network Configuration: Basically, you don’t need any further network configuration since Zima app has done these for you.
**This Means Your Success Connection: **You will be navigated to ZimaOS’ dashboard.
Application Example and Use Cases: Use WAN connections to securely access critical files or manage devices in emergencies. It is ideal for users needing to manage or access their ZimaOS devices remotely, ensuring continuous availability of important data.
Optional: Public IP address with a dynamic DNS configured would be an option, since you can access your device through a domain name directly.
No matter your needs, ZimaOS provides flexible and powerful connectivity options to suit any situation. From high-speed direct connections to convenient remote access via WAN, you can manage your devices and data effortlessly. Always consider security measures, especially when dealing with WAN connections, to protect your information and maintain smooth operations.
If you encounter any issues during use, feel free to let us know at any time. You can also join our community and Discord to discuss more about ZimaCube and ZimaOS. We look forward to your feedback!
]]>Currently, ZimaCube requires pressing the power button to start after being plugged in. Some users desire an auto-start function upon power being supplied.
Modify mainboard jumper pins.
Move the jumper cap position. The two pins near AUTO indicate the need to press the power button after plugging in, while the two pins near PWR1 indicate automatic startup upon plugging in.
Below is the position for requiring the power button press to start after power off:
Below is the position for automatic startup after plugging in:
You can modify the position according to your needs.
Resetting CMOS is actually restoring BIOS settings to the factory default state, which can solve many problems caused by incorrect configuration, damaged settings, or hardware changes. It is a relatively safe and simple troubleshooting method, usually as the first step in solving complex system problems.
Turn off the computer and disconnect the power plug to ensure that the device is completely powered off.
Carefully remove the case side cover to allow access to the main board.
Use a small non-metallic tool (such as a plastic pick) to carefully remove the battery from the retaining clip.
Wait for 5-10 minutes to ensure that the capacitor is fully discharged.
Return the battery to its original position to ensure correct installation.
Reinstall the case side cover.
]]>Resetting CMOS is actually restoring BIOS settings to the factory default state, which can solve many problems caused by incorrect configuration, damaged settings, or hardware changes. It is a relatively safe and simple troubleshooting method, usually as the first step in solving complex system problems.
Turn off the computer and disconnect the power plug to ensure that the device is completely powered off.
Carefully remove the case side cover to allow access to the main board.
Use a small non-metallic tool (such as a plastic pick) to carefully remove the battery from the retaining clip.
Wait for 5-10 minutes to ensure that the capacitor is fully discharged.
Return the battery to its original position to ensure correct installation.
Reinstall the case side cover.
]]>Currently, ZimaCube requires pressing the power button to start after being plugged in. Some users desire an auto-start function upon power being supplied.
Modify mainboard jumper pins.
Move the jumper cap position. The two pins near AUTO indicate the need to press the power button after plugging in, while the two pins near PWR1 indicate automatic startup upon plugging in.
Below is the position for requiring the power button press to start after power off:
Below is the position for automatic startup after plugging in:
You can modify the position according to your needs.
Start by connecting a monitor and a keyboard to your device.
After powering on the device, press the Alt + F2 key combination, which typically brings you to a command line or setup interface.
At the command prompt, type root to log in as the root user.
Enter the command passwd-root to initiate the process of setting the root password.
Follow the prompts to enter a new password and confirm it. Make sure to choose a strong password that includes a combination of letters, numbers, and special characters.
With these detailed steps, you should be able to successfully enable SSH and set the root password, allowing you to securely access the device from other computers within the network.
Start by connecting a monitor and a keyboard to your device.
After powering on the device, press the Alt + F2 key combination, which typically brings you to a command line or setup interface.
At the command prompt, type root to log in as the root user.
Enter the command passwd-root to initiate the process of setting the root password.
Follow the prompts to enter a new password and confirm it. Make sure to choose a strong password that includes a combination of letters, numbers, and special characters.
With these detailed steps, you should be able to successfully enable SSH and set the root password, allowing you to securely access the device from other computers within the network.
This tutorial will guide you through how to create a home video surveillance system on CasaOS using Kerberos.io and ZimaBoard. We will use CasaOS’s Docker custom installation feature to simplify the installation and configuration process, and will also explain in detail how to configure an RTSP camera.
Since different manufacturers’ cameras have different ways of getting the RTSP link, please refer to your camera’s user manual or the manufacturer’s official website for relevant instructions, or log in to the camera’s management interface to find the RTSP link. In this tutorial, we successfully tested TP-Link and Tuya brand cameras and verified their compatibility with Kerberos.io. In addition, we expect the system to be compatible with cameras from brands such as Hikvision, Ezviz, Dahua, eufy, and Yousee.
services:
kerberos:
image: kerberos/kerberos # Use the kerberos/kerberos image
container_name: kerberos # Container name
ports:
- “8080:80” # Map host port 8080 to container port 80
volumes:
- ./config:/config # Mount the host’s config directory to /config in the container
- ./recordings:/etc/opt/kerberosio/capture # Mount the host’s recordings directory to /etc/opt/kerberosio/capture in the container
restart: unless-stopped # Container restart policy: restart automatically unless stopped manually
environment:
- TZ=Europe/London # Set the container’s timezone to Europe/London
- KERBEROSIO_SETTINGS_PORT=80 # Set the Kerberos service listening port to 80
- KERBEROSIO_SETTINGS_RECORDSTREAM=”/config/recordings” # Set the recording stream location to /config/recordings
5. Click Submit
6. Fill in ‘tag’: latset and ‘title’: kerberos
7. Submit and wait for the installation to complete
This tutorial will guide you through how to create a home video surveillance system on CasaOS using Kerberos.io and ZimaBoard. We will use CasaOS’s Docker custom installation feature to simplify the installation and configuration process, and will also explain in detail how to configure an RTSP camera.
Since different manufacturers’ cameras have different ways of getting the RTSP link, please refer to your camera’s user manual or the manufacturer’s official website for relevant instructions, or log in to the camera’s management interface to find the RTSP link. In this tutorial, we successfully tested TP-Link and Tuya brand cameras and verified their compatibility with Kerberos.io. In addition, we expect the system to be compatible with cameras from brands such as Hikvision, Ezviz, Dahua, eufy, and Yousee.
services:
kerberos:
image: kerberos/kerberos # Use the kerberos/kerberos image
container_name: kerberos # Container name
ports:
- “8080:80” # Map host port 8080 to container port 80
volumes:
- ./config:/config # Mount the host’s config directory to /config in the container
- ./recordings:/etc/opt/kerberosio/capture # Mount the host’s recordings directory to /etc/opt/kerberosio/capture in the container
restart: unless-stopped # Container restart policy: restart automatically unless stopped manually
environment:
- TZ=Europe/London # Set the container’s timezone to Europe/London
- KERBEROSIO_SETTINGS_PORT=80 # Set the Kerberos service listening port to 80
- KERBEROSIO_SETTINGS_RECORDSTREAM=”/config/recordings” # Set the recording stream location to /config/recordings
5. Click Submit
6. Fill in ‘tag’: latset and ‘title’: kerberos
7. Submit and wait for the installation to complete
Please refer to this document::https://docs.zimaspace.com/zimacube/GPU-Expansion.html
-This guide should help you successfully install a GPU on ZimaCube and understand its importance in various applications. We encourage you to try out the installation and explore more GPU functions to enhance your work efficiency and quality of life.
+This guide should help you successfully install a GPU on ZimaCube and understand its importance in various applications. We encourage you to try out the installation and explore more GPU functions to enhance your work efficiency and quality of life.
We look forward to hearing more about your experiences!
The ZimaCube supports low-profile graphics cards, typically around 64.41 mm (2.536 inches) in height. The PCIe slot provides up to 75W of power, so it is recommended to select graphics cards within this size and power range to ensure compatibility with ZimaCube’s compact design and power limitations.
Please note that other graphics cards may require external power for proper operation.
Note:We’ve compiled this list based on the drivers supported by the ZimaOS, with “verified” models marked accordingly. If you’ve successfully run Assist on a different graphics card model, please help us update this list by using the ‘Improve’ feature in the top right corner. Thank you for your contribution.
@@ -374,7 +373,7 @@- + PrevNext @@ -383,7 +382,7 @@
Contents - + Back to Topdiff --git a/zimacube/HDD-Interface-Usage-Guide.html b/zimacube/HDD-Interface-Usage-Guide.html index 1c6b19b282..44c5537384 100644 --- a/zimacube/HDD-Interface-Usage-Guide.html +++ b/zimacube/HDD-Interface-Usage-Guide.html @@ -43,8 +43,8 @@ - - + + @@ -575,7 +575,7 @@- + PrevNext diff --git a/zimacube/Hardware-Brief.html b/zimacube/Hardware-Brief.html index cfce6ee9d2..4b3ca388c0 100644 --- a/zimacube/Hardware-Brief.html +++ b/zimacube/Hardware-Brief.html @@ -46,8 +46,8 @@ - - + + @@ -187,7 +187,7 @@
- + PrevNext diff --git a/zimacube/Hardware-Details.html b/zimacube/Hardware-Details.html index fe7d594bab..9e0874c69f 100644 --- a/zimacube/Hardware-Details.html +++ b/zimacube/Hardware-Details.html @@ -43,8 +43,8 @@ - - + + @@ -158,7 +158,7 @@
Fan Interface Instructions
USB Port Instructions
diff --git a/zimacube/How-to-Install-ZimaOS.html b/zimacube/How-to-Install-ZimaOS.html index e47d93a023..f63a2a9d10 100644 --- a/zimacube/How-to-Install-ZimaOS.html +++ b/zimacube/How-to-Install-ZimaOS.html @@ -54,8 +54,8 @@ - - + + @@ -186,7 +186,7 @@diff --git a/zimacube/How-to-Install-and-Remove-the-7th-Bay.html b/zimacube/How-to-Install-and-Remove-the-7th-Bay.html index 94499e71f2..5fb87ad59d 100644 --- a/zimacube/How-to-Install-and-Remove-the-7th-Bay.html +++ b/zimacube/How-to-Install-and-Remove-the-7th-Bay.html @@ -50,8 +50,8 @@ - - + + @@ -172,7 +172,7 @@
- + Next diff --git a/zimacube/How-to-Open-SSH-in-ZimaOS.html b/zimacube/How-to-Open-SSH-in-ZimaOS.html index 6d4fa6e27a..2162d6834c 100644 --- a/zimacube/How-to-Open-SSH-in-ZimaOS.html +++ b/zimacube/How-to-Open-SSH-in-ZimaOS.html @@ -45,8 +45,8 @@ - - + + @@ -167,7 +167,7 @@
- + Next diff --git a/zimacube/How-to-understand-Docker-App's-paths-On-ZimaOS.html b/zimacube/How-to-understand-Docker-App's-paths-On-ZimaOS.html index eac2987a4b..68b13cc911 100644 --- a/zimacube/How-to-understand-Docker-App's-paths-On-ZimaOS.html +++ b/zimacube/How-to-understand-Docker-App's-paths-On-ZimaOS.html @@ -49,8 +49,8 @@ - - + + @@ -185,7 +185,7 @@
- + Next diff --git a/zimacube/Install-TrueNAS.html b/zimacube/Install-TrueNAS.html index 569458b7ba..3ebafcc562 100644 --- a/zimacube/Install-TrueNAS.html +++ b/zimacube/Install-TrueNAS.html @@ -54,8 +54,8 @@ - - + + @@ -187,7 +187,7 @@
diff --git a/zimacube/Install-UnRAID.html b/zimacube/Install-UnRAID.html index 823ac0cc28..fb573b18cd 100644 --- a/zimacube/Install-UnRAID.html +++ b/zimacube/Install-UnRAID.html @@ -59,8 +59,8 @@ - - + + @@ -184,7 +184,7 @@
- + PrevNext diff --git a/zimacube/Instructions-for-use-of-the-7th-Bay.html b/zimacube/Instructions-for-use-of-the-7th-Bay.html index 4fc625d4b2..05922f5cae 100644 --- a/zimacube/Instructions-for-use-of-the-7th-Bay.html +++ b/zimacube/Instructions-for-use-of-the-7th-Bay.html @@ -50,8 +50,8 @@ - - + + @@ -167,7 +167,7 @@
diff --git a/zimacube/PC-Direct.html b/zimacube/PC-Direct.html index f42d0753f9..08bf3275b3 100644 --- a/zimacube/PC-Direct.html +++ b/zimacube/PC-Direct.html @@ -57,8 +57,8 @@ - - + + @@ -247,7 +247,7 @@
- + PrevNext diff --git a/zimacube/Plex-and-GPU-Transcoding.html b/zimacube/Plex-and-GPU-Transcoding.html index 633cc0dcf4..e119f0a94f 100644 --- a/zimacube/Plex-and-GPU-Transcoding.html +++ b/zimacube/Plex-and-GPU-Transcoding.html @@ -52,8 +52,8 @@ - - + + @@ -233,7 +233,7 @@
- + PrevNext diff --git a/zimacube/Quick-Start.html b/zimacube/Quick-Start.html index 9e75c85c1a..69fc2bbc08 100644 --- a/zimacube/Quick-Start.html +++ b/zimacube/Quick-Start.html @@ -51,8 +51,8 @@ - - + + @@ -304,7 +304,7 @@
diff --git a/zimacube/RAID-SSD-Expansion.html b/zimacube/RAID-SSD-Expansion.html index 654b6055a6..f71066f71f 100644 --- a/zimacube/RAID-SSD-Expansion.html +++ b/zimacube/RAID-SSD-Expansion.html @@ -43,8 +43,8 @@ - - + + @@ -157,7 +157,7 @@
Title
Section
diff --git a/zimacube/Release-Note.html b/zimacube/Release-Note.html index ade626a3b6..ac54d7eef0 100644 --- a/zimacube/Release-Note.html +++ b/zimacube/Release-Note.html @@ -44,8 +44,8 @@ - - + + @@ -188,7 +188,7 @@diff --git a/zimacube/Resets-CMOS.html b/zimacube/Resets-CMOS.html index 9edf679650..50260f44bb 100644 --- a/zimacube/Resets-CMOS.html +++ b/zimacube/Resets-CMOS.html @@ -46,8 +46,8 @@ - - + + @@ -169,7 +169,7 @@
- + PrevNext diff --git a/zimacube/Tutorials.html b/zimacube/Tutorials.html index 6bb7874ebd..033ba3fb86 100644 --- a/zimacube/Tutorials.html +++ b/zimacube/Tutorials.html @@ -47,8 +47,8 @@ - - + + @@ -169,7 +169,7 @@
- + Next diff --git a/zimacube/User-Guide.html b/zimacube/User-Guide.html index 910efa5d31..0af72d8e6f 100644 --- a/zimacube/User-Guide.html +++ b/zimacube/User-Guide.html @@ -43,8 +43,8 @@ - - + + @@ -157,7 +157,7 @@
Title
Section
diff --git a/zimacube/ZimaCube-Motherboard-DIY-Fan-Guide-and-Specifications.html b/zimacube/ZimaCube-Motherboard-DIY-Fan-Guide-and-Specifications.html index b27021f74a..fd1bcf6a50 100644 --- a/zimacube/ZimaCube-Motherboard-DIY-Fan-Guide-and-Specifications.html +++ b/zimacube/ZimaCube-Motherboard-DIY-Fan-Guide-and-Specifications.html @@ -53,8 +53,8 @@ - - + + @@ -202,7 +202,7 @@< diff --git a/zimacube/ZimaOS-application-content.html b/zimacube/ZimaOS-application-content.html index b75f482ec8..c11db7d92b 100644 --- a/zimacube/ZimaOS-application-content.html +++ b/zimacube/ZimaOS-application-content.html @@ -43,8 +43,8 @@ - - + + @@ -157,7 +157,7 @@
Title
Section
diff --git a/zimacube/index.html b/zimacube/index.html index eed3e7fe17..fd7f1eca1f 100644 --- a/zimacube/index.html +++ b/zimacube/index.html @@ -50,8 +50,8 @@ - - + + @@ -282,7 +282,7 @@- + Next diff --git a/zimaos/7th-Bay-LED.html b/zimaos/7th-Bay-LED.html index c2a8164ce7..e6cd1e2a13 100644 --- a/zimaos/7th-Bay-LED.html +++ b/zimaos/7th-Bay-LED.html @@ -45,8 +45,8 @@ - - + + @@ -399,7 +399,7 @@
- + PrevNext diff --git a/zimaos/A-list-of-Contributions.html b/zimaos/A-list-of-Contributions.html index f353fada3b..c0b367ec6c 100644 --- a/zimaos/A-list-of-Contributions.html +++ b/zimaos/A-list-of-Contributions.html @@ -43,8 +43,8 @@ - - + + @@ -157,7 +157,7 @@
文章标题
段落标题
diff --git a/zimaos/Achieve-Fastest-Transfer-Speed.html b/zimaos/Achieve-Fastest-Transfer-Speed.html index e8d1c419c4..e18c2b3085 100644 --- a/zimaos/Achieve-Fastest-Transfer-Speed.html +++ b/zimaos/Achieve-Fastest-Transfer-Speed.html @@ -44,8 +44,8 @@ - - + + @@ -176,7 +176,7 @@- + PrevNext diff --git a/zimaos/Build-Apps.html b/zimaos/Build-Apps.html index 603eeafef1..d01fd4b9d5 100644 --- a/zimaos/Build-Apps.html +++ b/zimaos/Build-Apps.html @@ -44,8 +44,8 @@ - - + + @@ -364,7 +364,7 @@
- + PrevNext diff --git a/zimaos/Build-Multiple-Clones-using-rsync.html b/zimaos/Build-Multiple-Clones-using-rsync.html index 61c02b3247..803242cb7e 100644 --- a/zimaos/Build-Multiple-Clones-using-rsync.html +++ b/zimaos/Build-Multiple-Clones-using-rsync.html @@ -43,8 +43,8 @@ - - + + @@ -158,7 +158,7 @@
Build Multiple Clones using rsync
diff --git a/zimaos/Connect-with-Cloud-Drives.html b/zimaos/Connect-with-Cloud-Drives.html index 610b5b783d..387a29946a 100644 --- a/zimaos/Connect-with-Cloud-Drives.html +++ b/zimaos/Connect-with-Cloud-Drives.html @@ -45,8 +45,8 @@ - - + + @@ -181,7 +181,7 @@- + PrevNext diff --git a/zimaos/Data-Migration.html b/zimaos/Data-Migration.html index a399e1e6d2..44e0397eb1 100644 --- a/zimaos/Data-Migration.html +++ b/zimaos/Data-Migration.html @@ -49,8 +49,8 @@ - - + + @@ -184,7 +184,7 @@
diff --git a/zimaos/Detailed-Plex-Operation-Guide.html b/zimaos/Detailed-Plex-Operation-Guide.html index 82ca8d0a00..1321473c09 100644 --- a/zimaos/Detailed-Plex-Operation-Guide.html +++ b/zimaos/Detailed-Plex-Operation-Guide.html @@ -59,8 +59,8 @@ - - + + @@ -197,7 +197,7 @@
- + PrevNext diff --git a/zimaos/Features.html b/zimaos/Features.html index 8b558faf89..1775eff201 100644 --- a/zimaos/Features.html +++ b/zimaos/Features.html @@ -61,8 +61,8 @@ - - + + @@ -220,7 +220,7 @@
diff --git a/zimaos/Get-Network-ID.html b/zimaos/Get-Network-ID.html index 32f58f8b48..336212be44 100644 --- a/zimaos/Get-Network-ID.html +++ b/zimaos/Get-Network-ID.html @@ -47,8 +47,8 @@ - - + + @@ -174,7 +174,7 @@
- + PrevNext diff --git a/zimaos/Get-Started.html b/zimaos/Get-Started.html index 932e0658fb..0a01fa3492 100644 --- a/zimaos/Get-Started.html +++ b/zimaos/Get-Started.html @@ -58,8 +58,8 @@ - - + + @@ -212,7 +212,7 @@
- + PrevNext diff --git a/zimaos/How-to-Contribute.html b/zimaos/How-to-Contribute.html index 7d1d179162..7a0249cc5a 100644 --- a/zimaos/How-to-Contribute.html +++ b/zimaos/How-to-Contribute.html @@ -43,8 +43,8 @@ - - + + @@ -158,7 +158,7 @@
How to Contribute
diff --git a/zimaos/How-to-Manually-Download-the-Large-Language-Model.html b/zimaos/How-to-Manually-Download-the-Large-Language-Model.html index f4c377eb44..883e56ca85 100644 --- a/zimaos/How-to-Manually-Download-the-Large-Language-Model.html +++ b/zimaos/How-to-Manually-Download-the-Large-Language-Model.html @@ -43,8 +43,8 @@ - - + + @@ -158,7 +158,7 @@How to Manually Download the Large Lan diff --git a/zimaos/How-to-Open-SSH-in-ZimaOS.html b/zimaos/How-to-Open-SSH-in-ZimaOS.html index 2dd93a48a1..58f24044d8 100644 --- a/zimaos/How-to-Open-SSH-in-ZimaOS.html +++ b/zimaos/How-to-Open-SSH-in-ZimaOS.html @@ -45,8 +45,8 @@ - - + + @@ -167,7 +167,7 @@
- + PrevNext diff --git a/zimaos/How-to-download-and-install-ZimaClient.html b/zimaos/How-to-download-and-install-ZimaClient.html index bdf602baef..cffebd7008 100644 --- a/zimaos/How-to-download-and-install-ZimaClient.html +++ b/zimaos/How-to-download-and-install-ZimaClient.html @@ -43,8 +43,8 @@ - - + + @@ -157,7 +157,7 @@
文章标题
段落标题
diff --git a/zimaos/How-to-understand-Docker-App's-paths-On-ZimaOS.html b/zimaos/How-to-understand-Docker-App's-paths-On-ZimaOS.html index a94cb4a971..f3913c6105 100644 --- a/zimaos/How-to-understand-Docker-App's-paths-On-ZimaOS.html +++ b/zimaos/How-to-understand-Docker-App's-paths-On-ZimaOS.html @@ -49,8 +49,8 @@ - - + + @@ -185,7 +185,7 @@- + PrevNext diff --git a/zimaos/How-to-use-OpenAPI.html b/zimaos/How-to-use-OpenAPI.html index 381668b003..9d3fe2ff57 100644 --- a/zimaos/How-to-use-OpenAPI.html +++ b/zimaos/How-to-use-OpenAPI.html @@ -43,8 +43,8 @@ - - + + @@ -171,7 +171,7 @@
diff --git a/zimaos/Install-offline.html b/zimaos/Install-offline.html index 4473815388..18bb4140f5 100644 --- a/zimaos/Install-offline.html +++ b/zimaos/Install-offline.html @@ -47,8 +47,8 @@ - - + + @@ -182,7 +182,7 @@
Update offline
diff --git a/zimaos/Link-Synology-and-SMB-Shares.html b/zimaos/Link-Synology-and-SMB-Shares.html index 790f0a49cf..e75efa5765 100644 --- a/zimaos/Link-Synology-and-SMB-Shares.html +++ b/zimaos/Link-Synology-and-SMB-Shares.html @@ -55,8 +55,8 @@ - - + + @@ -184,7 +184,7 @@- + PrevNext diff --git a/zimaos/Media-Server-Setup-with-Jellyfin.html b/zimaos/Media-Server-Setup-with-Jellyfin.html index ed177d0772..d7d45e6930 100644 --- a/zimaos/Media-Server-Setup-with-Jellyfin.html +++ b/zimaos/Media-Server-Setup-with-Jellyfin.html @@ -51,8 +51,8 @@ - - + + @@ -235,7 +235,7 @@
- + PrevNext diff --git a/zimaos/More-RAID-Options.html b/zimaos/More-RAID-Options.html index fd46c403b9..22219d502d 100644 --- a/zimaos/More-RAID-Options.html +++ b/zimaos/More-RAID-Options.html @@ -49,8 +49,8 @@ - - + + @@ -177,7 +177,7 @@
- + PrevNext diff --git a/zimaos/NVR-Camera-Server.html b/zimaos/NVR-Camera-Server.html index 1cbd72064c..c19fc4f4b5 100644 --- a/zimaos/NVR-Camera-Server.html +++ b/zimaos/NVR-Camera-Server.html @@ -56,8 +56,8 @@ - - + + @@ -191,7 +191,7 @@
Click ‘Configuration’ Select ‘IP camera’ -Enter the obtained RTSP URL, for example: rtsp://admin:Hjj12345@10.0.171.52/stream1. +Enter the obtained RTSP URL, for example: rtsp://admin:Hjj12345@10.0.171.52/stream1. Configure the resolution and frame rate, for example: 720x480. After the configuration is completed, you can view the captured images and videos in the Kerberos interface You can also view the monitoring status in real time on the main interface @@ -200,7 +200,7 @@- + PrevNext diff --git a/zimaos/Networking.html b/zimaos/Networking.html index b8b150a025..56711457ea 100644 --- a/zimaos/Networking.html +++ b/zimaos/Networking.html @@ -43,8 +43,8 @@ - - + + @@ -157,7 +157,7 @@
文章标题
段落标题
diff --git a/zimaos/OpenAPI-Live-Preview.html b/zimaos/OpenAPI-Live-Preview.html index 3ff0a1ce24..7e4caf1bcb 100644 --- a/zimaos/OpenAPI-Live-Preview.html +++ b/zimaos/OpenAPI-Live-Preview.html @@ -43,8 +43,8 @@ - - + + @@ -173,7 +173,7 @@diff --git a/zimaos/Recover-Your-Password.html b/zimaos/Recover-Your-Password.html index 8c004168c3..cb7dd73f1f 100644 --- a/zimaos/Recover-Your-Password.html +++ b/zimaos/Recover-Your-Password.html @@ -47,8 +47,8 @@ - - + + @@ -175,7 +175,7 @@
diff --git a/zimaos/Romote-Access.html b/zimaos/Romote-Access.html index 0c5095be5e..855f56cf9f 100644 --- a/zimaos/Romote-Access.html +++ b/zimaos/Romote-Access.html @@ -51,8 +51,8 @@ - - + + @@ -190,7 +190,7 @@
- + PrevNext diff --git a/zimaos/Setup-Python.html b/zimaos/Setup-Python.html index 9a212cab4c..f0824ad82b 100644 --- a/zimaos/Setup-Python.html +++ b/zimaos/Setup-Python.html @@ -45,8 +45,8 @@ - - + + @@ -171,7 +171,7 @@
- + PrevNext diff --git a/zimaos/Sync-Photos-via-Configurable-CLI.html b/zimaos/Sync-Photos-via-Configurable-CLI.html index 5a9aaa5c70..4104db0290 100644 --- a/zimaos/Sync-Photos-via-Configurable-CLI.html +++ b/zimaos/Sync-Photos-via-Configurable-CLI.html @@ -52,8 +52,8 @@ - - + + @@ -182,7 +182,7 @@
- + PrevNext diff --git a/zimaos/Sync-Photos-with-Immich.html b/zimaos/Sync-Photos-with-Immich.html index c2f4eb68ca..f81df48aec 100644 --- a/zimaos/Sync-Photos-with-Immich.html +++ b/zimaos/Sync-Photos-with-Immich.html @@ -58,8 +58,8 @@ - - + + @@ -193,7 +193,7 @@
- + PrevNext diff --git a/zimaos/Thunderbolt-PC-Direct.html b/zimaos/Thunderbolt-PC-Direct.html index f2d722c34f..44e525dac9 100644 --- a/zimaos/Thunderbolt-PC-Direct.html +++ b/zimaos/Thunderbolt-PC-Direct.html @@ -51,8 +51,8 @@ - - + + @@ -298,7 +298,7 @@
- + PrevNext diff --git a/zimaos/User-Guide.html b/zimaos/User-Guide.html index 62966478d2..778c239ef4 100644 --- a/zimaos/User-Guide.html +++ b/zimaos/User-Guide.html @@ -41,8 +41,8 @@ - - + + @@ -155,7 +155,7 @@ diff --git a/zimaos/Using-Samba-as-a-Member.html b/zimaos/Using-Samba-as-a-Member.html index 0e8f40468a..8b90d4ebc8 100644 --- a/zimaos/Using-Samba-as-a-Member.html +++ b/zimaos/Using-Samba-as-a-Member.html @@ -53,8 +53,8 @@ - - + + @@ -198,7 +198,7 @@
- + PrevNext diff --git a/zimaos/ZFS-Setup.html b/zimaos/ZFS-Setup.html index d5d28dc432..fcf6a189c6 100644 --- a/zimaos/ZFS-Setup.html +++ b/zimaos/ZFS-Setup.html @@ -46,8 +46,8 @@ - - + + @@ -166,7 +166,7 @@
- + PrevNext diff --git a/zimaos/index.html b/zimaos/index.html index 5738e90827..3f467de9bb 100644 --- a/zimaos/index.html +++ b/zimaos/index.html @@ -47,8 +47,8 @@ - - + + @@ -237,7 +237,7 @@
diff --git a/zimaos/migrate-files-from-Synology-to-ZimaCube.html b/zimaos/migrate-files-from-Synology-to-ZimaCube.html index a1e7b01077..a60e50c983 100644 --- a/zimaos/migrate-files-from-Synology-to-ZimaCube.html +++ b/zimaos/migrate-files-from-Synology-to-ZimaCube.html @@ -49,8 +49,8 @@ - - + + @@ -187,7 +187,7 @@
- + PrevNext diff --git a/zimaos/set-your-SSH.html b/zimaos/set-your-SSH.html index bb3aaf5da8..c534da1c68 100644 --- a/zimaos/set-your-SSH.html +++ b/zimaos/set-your-SSH.html @@ -46,8 +46,8 @@ - - + + @@ -165,7 +165,7 @@
- + PrevNext diff --git a/zimaos/share-via-link.html b/zimaos/share-via-link.html index 2be4bf6cc8..a512ab9ea7 100644 --- a/zimaos/share-via-link.html +++ b/zimaos/share-via-link.html @@ -43,8 +43,8 @@ - - + + @@ -186,7 +186,7 @@
- + PrevNext diff --git a/zimaos/v-1.2.2.html b/zimaos/v-1.2.2.html index 09d0c03c40..15a2f18d64 100644 --- a/zimaos/v-1.2.2.html +++ b/zimaos/v-1.2.2.html @@ -43,8 +43,8 @@ - - + + @@ -185,7 +185,7 @@
diff --git a/zimaos/v-1.2.3.html b/zimaos/v-1.2.3.html index f8c180bafa..0c821bd745 100644 --- a/zimaos/v-1.2.3.html +++ b/zimaos/v-1.2.3.html @@ -44,8 +44,8 @@ - - + + @@ -200,7 +200,7 @@
diff --git a/zimaos/v-1.2.4.html b/zimaos/v-1.2.4.html index 730e69912f..f7039a4f58 100644 --- a/zimaos/v-1.2.4.html +++ b/zimaos/v-1.2.4.html @@ -44,8 +44,8 @@ - - + + @@ -179,7 +179,7 @@
- + PrevNext