Caelum is deployed via a single universal ISO image, which installs identically on VMware / vSphere, Proxmox VE, Hyper-V, KVM/libvirt and bare-metal.
For the installation media, the recommended path is BIOS / Legacy (on Hyper-V: a Generation 1 VM). UEFI boot of the ISO is validated on Proxmox VE and KVM, with Secure Boot disabled. Once installed, the appliance works either way, in BIOS as well as in UEFI; its disk is hybrid.
Installation happens in two stages:
- System installation (text-based wizard at ISO boot) — keyboard, appliance name, network, then writes the Caelum OS to the target disk. ~3 minutes.
- Initial configuration (web setup wizard
https://<ip>/setup) — administrator account, network, storage pool, Active Directory, telemetry.
Prerequisites#
| Resource | Minimum | Recommended |
|---|---|---|
| vCPU | 2 | 4 |
| RAM | 8 GB | 16 GB or more |
| OS disk | 32 GB, dedicated | 32 GB SSD |
| Data disk(s) | 1 separate disk ≥ 10 GB (for the pool) | as needed |
| Network adapter | 1 (VMXNET3 / virtio recommended) | — |
| Firmware (to boot the ISO) | BIOS / Legacy, or UEFI without Secure Boot (validated on Proxmox / KVM) | BIOS / Legacy |
The ISO image is 1.4 GB. If the machine does not have enough memory to install it, the installer stops before writing anything and tells you how much memory is missing.
Important points:
- The OS and the data are on separate disks. Plan for a disk dedicated to the OS (≥ 32 GB) and at least one additional disk for the storage pool. The data disk can be added before or after installation.
- Preferably use a VM with a single OS disk at install time to avoid any ambiguity about the target disk, then add the data disk(s) afterward.
- Boot firmware for the ISO: preferably use BIOS / Legacy for the installation media (recommended path). UEFI boot of the ISO is validated on Proxmox VE and KVM, provided Secure Boot is disabled; on other hypervisors, if in doubt, stay on BIOS / Legacy. Once installed, the appliance works either way, in BIOS as well as in UEFI; its disk is hybrid. On Hyper-V, create a Generation 1 VM for installation.
- Network: the installer offers DHCP or a static IP (Network step).
Addressing can be changed later in the web wizard (or from the console via
sudo galilo-set-ip):
# Console — set a static IP before the web wizard
sudo galilo-set-ip
- The HTTPS certificate is self-signed: accept the browser warning on first connection.
Creating the VM for your platform#
The same ISO installs everywhere. Only the VM creation differs. In every
case: mount the ISO caelum-<version>.iso as a CD/DVD drive, boot from it,
then follow Part A.
VMware vSphere / ESXi#
- New VM → Custom, guest Linux / Debian 12 (64-bit).
- Firmware BIOS recommended for the installation media (safe path).
- Disk 1 (OS): 32 GB (Thin). Disk 2 (data): ≥ 10 GB (100 GB here). VMware Paravirtual (pvscsi) controller.
- VMXNET3 network adapter.
- Datastore: mount the ISO from a datastore (e.g. Datastore ISO → CD/DVD → Datastore ISO File), with Connect at power on checked.
- Boot: CD/DVD first for installation, then the OS disk.
Proxmox VE#
- Create VM, q35, BIOS SeaBIOS recommended for the media. OVMF (UEFI) also works: add an EFI disk and untick Pre-Enroll keys (Secure Boot disabled).
- VirtIO Block disks: OS 32 GB + data ≥ 10 GB.
- VirtIO (paravirtualized) network.
- CD/DVD: ISO
caelum-…iso; boot order CD then OS disk.
Microsoft Hyper-V#
- Generation 1 VM (BIOS) for installation (safe recommended path for the media).
- VHDX disks: OS 32 GB + data ≥ 10 GB.
- DVD Drive: ISO image; place it before the disk in the boot order.
KVM / libvirt (virt-manager)#
virt-installor virt-manager, firmware BIOS (SeaBIOS) recommended for the media; UEFI (OVMF) without Secure Boot also works.- virtio disks: OS 32 GB + data ≥ 10 GB; virtio network.
- CD-ROM = the ISO; boot CD then disk.
Bare-metal (physical server)#
- Write the ISO to a USB stick (Linux/macOS) or with Rufus/balenaEtcher (Windows):
# Linux/macOS — write the ISO to a USB stick (double-check the /dev/sdX device)
sudo dd if=caelum-<version>.iso of=/dev/sdX bs=4M status=progress
- Boot from the stick in Legacy/BIOS (recommended path for the media; in UEFI, disable Secure Boot). Plan for a disk dedicated to the OS (≥ 32 GB) and at least one data disk for the pool.
Target disk: to avoid any ambiguity about the disk letter (sda/sdb depending on enumeration), the simplest approach is to attach only the OS disk at install time, then add the data disk(s) before the Storage step of the web wizard (Rescan disks button).
Part A — System installation (ISO wizard)#
Boot the machine from the Caelum ISO. The installation wizard starts automatically.
A.1 — Welcome screen#
The wizard summarizes its 5 steps (keyboard, name, network, disk, confirmation) and warns that the target disk will be entirely erased. The administrator account, storage and Active Directory are configured afterward, from the web wizard.
➡️ Press Enter to begin (Esc to cancel).

A.2 — Keyboard layout (step 1/5)#
Select your keyboard layout (arrows ↑↓, Enter) so that the rest is comfortable to type. 10 layouts available (US, AZERTY, QWERTZ, etc.). The choice is kept on the installed system.

A.3 — Appliance name (step 2/5)#
Enter the appliance hostname (lowercase letters, digits, hyphens — e.g.
caelum-paris). A name is suggested by default. If the appliance is to join an
Active Directory domain, keep the short name to 15 characters or fewer.

A.4 — Network (step 3/5)#
Choose DHCP (automatic) or Static IP. For a static IP, enter the
address, the netmask (255.255.255.0 or 24), the gateway and the DNS
servers. An optional DNS search domain can be added in both cases.

A.5 — Target disk (step 4/5)#
Select the installation disk. The OS will entirely overwrite this disk.
Each line shows the size, model, identifier (WWN or serial number) and disk
state: empty, IN USE (partitions, ZFS, LVM or a filesystem — erased if
chosen) or TOO SMALL (cannot be selected). A disk already in use is never
preselected. Choose the disk that the firmware boots from (usually the dedicated
OS disk), comparing size and identifier with your hypervisor.

A.6 — Confirmation (step 5/5)#
Review the summary (keyboard, name, network, disk, image size). To confirm
erasure, type YES then Enter (an empty Enter = cancel).

A.7 — Installation#
The disk image is written to the target with a progress bar (~25 GB, 1 to 3 minutes).
A.8 — Done#
Once the "Installation complete" screen is displayed, press Enter: the installer ejects the media and restarts the machine. If the hypervisor re-inserts the ISO, its boot menu starts the installed disk by default after 5 seconds ("Install Caelum" remains available to reinstall).

A.9 — First boot#
On first boot, the appliance configures itself (key generation, service
startup) and displays a console banner with its IP and the
configuration URL. Note the IP, then open https://<ip>/setup in a browser.

Need to change the IP before the web setup? Log in to the console as
galilo-debug (password shown on the local console, below the banner) and run
sudo galilo-set-ip.
Part B — Initial configuration (web wizard)#
Open https://<ip>/setup and accept the self-signed certificate warning.
The wizard has 7 steps; the FR / EN buttons at the top right switch the
language.
B.1 — Appliance name (step 1/7)#
Check the hostname (prefilled with the name entered in the installer; 15 characters at most for the short name) and choose the time zone.

B.2 — Network (step 2/7)#
The wizard shows the current configuration. Click Keep current network to
keep it, or switch between DHCP and static IP. For a static IP, provide
the interface, the address, the netmask (255.255.255.0 or 24), the
gateway, the DNS servers and, if needed, a DNS search domain. The wizard waits
until the new configuration is actually applied before offering the next step.


If you change the IP, the wizard automatically redirects to the new
address (https://<new-ip>/setup). Reconnect there if your browser does not
follow.
B.3 — Administrator account (step 3/7)#
Create the local administrator account (login + password). The root
account will be locked at the end of the configuration.

B.4 — Storage (step 4/7)#
Select the data disk(s) to include in the storage pool and choose the topology (single disk, mirror, RAID-Z…). Do not select the OS disk. Click Create pool. You can also attach an iSCSI LUN from this step, or click Configure later to create the pool later from the console (Storage → Pools).


If no disk appears, check that a data disk is properly attached on the hypervisor side then click Rescan disks. A disk already carrying a signature (old pool/filesystem) must be erased before use.
B.5 — Active Directory (step 5/7)#
Join an Active Directory domain, or click Skip to configure access later.

B.6 — Telemetry (step 6/7)#
Telemetry is enabled by default, on the basis of legitimate interest in tracking versions so security fixes can be shipped. A daily send of pseudonymous data linked to the licence: installation_id, version, hypervisor, licence type and number, counters of shares, files, volumes and SMB users, high-availability indicator, and first-installation date. The hostname is sent only if it is checked. Sending can be disabled at any time in System › Privacy.

B.7 — Review (step 7/7)#
Review the entire configuration and finalize.

B.8 — Login#
Configuration is complete: the root account is locked and the interface
switches to the login screen of the administration console. Sign in with
the administrator account created in step B.3. The console opens in English;
the EN / FR selector in the top bar changes the language.

B.9 — Dashboard#
You reach the dashboard of the Caelum console: number of pools, volumes, shares, catalogued files and cloud destinations, pool capacity, Cache-S3 archiving, storage trend and recent activity. The appliance is operational — you can create shares, configure cloud destinations, schedule snapshots, etc.
Since 0.65, the administration console served at https://<ip>/ is the
new interface. The previous one remains available at https://<ip>/legacy
(the /setup wizard still uses the previous look).

What's next?#
- SMB/NFS shares: Storage → Shares.
- Cloud archiving (S3): Archiving → Cloud destinations + Archiving → Policies.
- Snapshots & replication: Storage → Snapshots / Storage → Replication.
- Updates: Settings → Updates. For one-click updates, first connect your galilo.io portal account in Diagnostics → Support → Link an account; without Internet, install from a file.
- Day-to-day administration: see the administration guide.
Troubleshooting#
On reboot: "Operating System not found" or switch to PXE / network boot. The VM tried to boot an empty disk. Common causes:
- The ISO is still mounted and the VM rebooted from it, or the boot order points to an empty disk → detach the ISO and put the OS disk first in the boot order.
- Install done on the wrong disk (multi-disk VM) → reinstall on the disk that the firmware boots from, or leave only a single disk during install.
The install is "instant" (a few seconds). Abnormal: a real image write takes 1-3 min ("Written: … GB" counter). If it is instant, the media is probably corrupted — re-download the ISO and verify the SHA-256 before trying again.
The ISO does not boot in UEFI. Check that Secure Boot is disabled, or switch the installation media back to BIOS / Legacy firmware (recommended path). On Hyper-V, create a Generation 1 VM. The installed appliance then works either way, in BIOS as well as in UEFI.
The installer reports that memory is missing. The installer keeps its media in memory: give the VM more RAM (8 GB minimum for the appliance, 16 GB recommended). Nothing has been written to the disk.
The VM stops at an EFI "Boot Manager". Select "Boot normally" (Enter). If it falls into "unsuccessful", switch the VM back to BIOS/Legacy.
Storage step: "No free disk detected" although a disk exists. The disk carries a residual signature (old pool/filesystem from a recycled disk). Erase it on the hypervisor side, or from the console (double-check the device — destructive operation), then Rescan disks:
# If an old pool is auto-imported, destroy it first
sudo zpool destroy <name>
# Then erase the disk's residual signatures
sudo wipefs -a /dev/sdX && sudo sgdisk --zap-all /dev/sdX
After changing the IP in the wizard, "site inaccessible". The appliance
switched to the new IP: reconnect at https://<new-ip>/setup.
Certificate warning in the browser. Normal: the certificate is self-signed by default. Accept the exception, or import your own certificate (Settings → TLS).
Need a static IP without DHCP. Set it in the installer's Network step. On
an appliance that is already installed, log in to the console as
galilo-debug (password shown on the local console) and run:
sudo galilo-set-ip
ISO installation guide (installation in BIOS / Legacy, dedicated OS disk + at least one data disk for the pool).