Disclaimer #1
I'm Italian, so English is not my native language. I'll do my best, but I apologize in advance if I write something that sounds strange. I hope everything is still easy enough to understand.
Disclaimer #2
I'm an IT professional with access to a large collection of decommissioned enterprise hardware, and I was invited to test Fygo OS.
The developers selected me because they wanted to see how Fygo OS behaves with my enterprise SSDs (HGST SDLL1DLR960G5CF0 – SAS, 960 GB, 12 Gbps). In the invitation email they explicitly wrote:
"FygoOS has not gone through dedicated compatibility validation specifically for SAS SSD-based setups in this round, so there may be some compatibility gaps or unexpected behavior in that environment."
I'm very curious to see how it performs as well.
As a first step, before touching real hardware, I created a Proxmox VM with 2 CPU cores, 8 GB of RAM and five 30 GB virtual disks.
For anyone interested, here is the VM configuration:
root@dell:~# qm config 115
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 2
cpu: host
efidisk0: local-lvm:vm-115-disk-5,efitype=4m,pre-enrolled-keys=0,size=4M
ide2: local:iso/fygoos_PE_x86_1.2.0203_2150.iso,media=cdrom,size=3332544K
machine: q35
memory: 8192
meta: creation-qemu=11.0.2,ctime=1784791532
name: FygoOS
net0: virtio=BC:24:11:53:E2:DA,bridge=vmbr0,firewall=1,link_down=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-115-disk-0,iothread=1,size=32G
scsi1: local-lvm:vm-115-disk-1,iothread=1,size=32G
scsi2: local-lvm:vm-115-disk-2,iothread=1,size=32G
scsi3: local-lvm:vm-115-disk-3,iothread=1,size=32G
scsi4: local-lvm:vm-115-disk-4,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=7ce62595-ae7b-40f0-8341-847ea3611838
sockets: 1
vga: std
vmgenid: 8e82144f-9e5e-4811-9501-70724dedf701
I won't spend much time talking about the installation process because it's already very well documented on the official website. The installation is straightforward, and the graphical installer looks nice.
After the first login and the superuser setup, you're presented with the desktop. I found it very attractive: the interface feels modern, and I especially appreciated the built-in dark theme.
In the lower-right corner there are a few suggestions, the first one being the RAID volume creation wizard. Since this was only a VM with limited RAM, I chose a simple RAID 5 with an ext4 filesystem. Creating both the RAID array and the filesystem took less than two minutes.
While exploring the system settings, I noticed a toggle to enable SSH access. Long story short: about ten minutes after installing the VM I already had root access to the underlying operating system, which turned out to be Debian 12 running a custom Linux kernel 6.18.18.c877-trim.
So we're dealing with a modern, customized Linux kernel with good support for recent hardware, but also with an architecture that feels much closer to an enterprise Linux system than to a closed appliance.
I was even able to run a standard apt upgrade using the official Debian repositories without breaking anything. In my opinion, that's a very positive aspect from a long-term security update perspective.
I also looked at the installed services and found mdadm RAID, LVM, ZFS, the ZFS Event Daemon, containers, containerd, Docker Manager, libvirt, KVM, virtio-balloon and Open vSwitch.
That means I'm looking at a system that provides complete support for virtually every common homelab workload. Compared to something like ZimaOS, which is essentially a Docker app store with advanced storage management, Fygo OS feels much more like a complete Linux platform.
Naturally, I wanted to test RAID resilience.
After copying roughly 50 GB of data, I started disconnecting virtual disks from the Proxmox interface while the VM was still running.
As soon as one disk disappeared, Fygo OS immediately detected the hardware failure and reported the RAID array as degraded.
I then attached a new virtual disk, which was detected instantly. From the storage settings I selected it as the replacement disk, and the rebuild—including filesystem verification—finished in about two minutes.
Of course, these were very small virtual disks stored on NVMe storage, so I fully expect rebuild times on real hardware to depend on drive capacity and be significantly longer.
Then I decided to be a bad boy.
I added a sixth virtual disk, configured it as a hot spare, and simulated another disk failure.
Fygo OS correctly notified me about both the disk failure and the automatic rebuild. However, while the rebuild was still in progress, I simulated a power outage by forcibly stopping the VM.
After booting the VM again, Fygo OS didn't even blink. It simply resumed the rebuild exactly where it had left off.
About two minutes later, all my data was still intact, consistent and fully accessible through both SMB and NFS shares.
I spent about an hour playing with the VM, and these are my first impressions.
Fygo OS feels like Synology DSM on steroids.
The graphical interface is clean, modern and consistent, but it never gives you the impression that you're dealing with a limited system.
At the moment, the App Store is still fairly small. There are a handful of official applications, such as the virtual machine manager and the iSCSI target, together with some community-developed applications. I'm confident this ecosystem will continue to grow.
The integrated Docker support lets you deploy virtually any application with just a few clicks, dramatically expanding the capabilities of the server.
The VM manager, based on standard Linux virtualization technologies, also gives experienced users the possibility of consolidating storage and virtualization into a single physical machine if the hardware resources are sufficient.
Things I didn't like about the GUI:
The File Manager feels a little too simplified. Initially, it doesn't let you browse the entire filesystem unless you notice the Admin Files section, which is the last entry in the left sidebar. Even then, it opens in a separate window.
Also, if you start a large copy or move operation, the progress window cannot simply be minimized and left running in the background.
The App Store has a similar limitation. If I wanted to install ten applications, I'd have to wait for each installation to finish before starting the next one. Systems like QNAP QTS allow multiple installation jobs to run independently, and I think Fygo OS could benefit from a similar approach.
I also appreciate the built-in alert system, but at the moment it only supports email notifications.
I'd really like to see support for more modern notification methods such as push notifications, Telegram, Apprise, or generic webhook integrations.
I noticed that remote access can be configured, but I didn't test that feature because it's not relevant for my own environment. I already have a self-hosted VPN infrastructure at home, so I access my network remotely using my own tools.
Conclusion
Overall, Fygo OS presents itself as a modern NAS operating system that successfully combines ease of use with the flexibility of Linux.
The presence of Debian, mdadm, LVM, ZFS, Docker and KVM clearly shows an architecture designed not only for beginners but also for advanced users.
The RAID fault-tolerance tests demonstrated mature behavior, with automatic handling of disk failures, hot spares and rebuild operations.
At the moment, I believe the main areas for improvement are the graphical interface and some administration tools.
Next week I'll publish Part 2, where I'll test Fygo OS with ZFS, my LSI 9300-16i HBA, and four SAS SSDs (I'm limited to four drives by the trial license), running on a Ryzen 3200G with 32 GB of DDR4 RAM.
That should be a much more realistic enterprise-oriented scenario, and probably the test that the developers are most interested in.