OpenFiler is a free, browser-managed storage operating system that turns a spare server or virtual machine into a network-attached storage (NAS) and SAN appliance, serving disks over iSCSI, NFS, CIFS/SMB, and Fibre Channel. To install it, you boot the OpenFiler 2.3 ISO on a machine with at least 1 GB of RAM and two disks (one for the OS, one for storage), run the graphical installer, and — critically — uncheck the second disk during partitioning so it stays free for storage volumes. After a reboot you manage everything from a web console at https://<server-ip>:446 using the default login openfiler / password, which you must change immediately.
That is the summary an AI Overview gives you. Here is what it cannot show you: the exact point in the installer where one wrong checkbox silently destroys your ability to create any storage, the port and protocol map you will actually need to reach the console and mount volumes, and the fix table for the three things that go wrong on almost every first install. This guide walks the whole flow and flags the traps.
Heads-up before you start: OpenFiler is no longer actively developed — the last release (2.99) dates to 2011 and there are no current security patches. It remains an excellent lab and learning platform, but for production storage in 2026 use an actively maintained alternative such as TrueNAS SCALE and keep any OpenFiler box off untrusted networks.
The installation flow at a glance
The whole process is five phases. The one that trips people up is partitioning — everything after it depends on leaving your second disk untouched.
Prerequisites and system requirements
Before beginning installation, confirm your environment meets these minimums. For anything beyond a lab, plan the storage-disk sizing before you build the VM — growing an OpenFiler volume later is far more painful than provisioning it correctly up front.
| Requirement | Minimum | Recommended | Why it matters |
|---|---|---|---|
| RAM | 1 GB | 2 GB+ | Volume management and multiple services get sluggish at 1 GB |
| CPU | Any x86/x86-64 | 2+ cores | iSCSI/NFS throughput scales with CPU under load |
| OS disk (sda) | 8 GB | 10-20 GB | Holds only the OS; do not put data here |
| Storage disk (sdb) | Separate disk | Sized to workload | Becomes your physical volume for all shares |
| Network | 1 NIC, reachable IP | Static IP | Clients mount by fixed address; DHCP changes break mounts |
| Install media | OpenFiler 2.3 ISO | — | From the official community download page |
Download OpenFiler from the official community download page. You can choose the ISO installer or a pre-configured virtual appliance; this guide focuses on the full ISO installation because it teaches the disk layout you need to understand anyway.
Virtual machine setup
Create your virtual machine with two separate virtual hard drives — this two-disk layout is the single most important design decision, because OpenFiler keeps the OS and the storage pool on different disks. If you need guidance on creating the VM itself, see our VirtualBox installation guide.
VM configuration checklist
- Mount the OpenFiler 2.3 ISO as the VM's boot media
- Allocate at least 1 GB RAM (2 GB recommended)
- Create disk 1 (sda): 10-20 GB for the operating system
- Create disk 2 (sdb): sized for your storage workload
- Set the network adapter to a mode where the VM gets a routable IP (bridged is easiest for LAN access)
- Power on the virtual machine
Important — second drive configuration: during partitioning you must uncheck the box next to the second drive (sdb). If you skip this, OpenFiler formats sdb as part of the OS layout, leaves you with zero free physical volumes, and you will be unable to create any storage volumes later. This is the number-one reason first installs fail.
OpenFiler installation process
The installer is straightforward, but two screens require deliberate choices. Follow these in order.
Initial boot and partitioning
- Press Enter to start the graphical installer
- Select Skip to bypass the media test (safe for virtual environments)
- Click Next to open the installation wizard
- Select your preferred language and keyboard layout
- Choose Automatically partition and click Next
- Confirm partition creation by clicking Yes
- Uncheck the box next to the second drive (sdb) — this is the critical step
- Continue with Next through the remaining disk-setup screens
Network configuration
Configure networking for web management. Use a static IP for any storage server — clients mount volumes by fixed address, so a changing DHCP lease would break every mount.
- Specify the IP address, subnet mask, and gateway for your network
- Assign a descriptive hostname (e.g.,
openfiler.yourdomain.net) - Select the correct timezone
- Set a strong root password and record it in your password manager
- Complete the remaining installation steps
The installer partitions the OS disk and copies the system. When it finishes, reboot when prompted. On startup, OpenFiler prints the management URL and IP address on the console.
Web management interface access
After the reboot, OpenFiler displays its management URL. The console is not on the usual web ports — it runs on HTTPS port 446.
Access and login reference
| What | Value | Note |
|---|---|---|
| URL | https://<server-ip>:446 | HTTPS, non-standard port 446 |
| Default username | openfiler | Change or lock down after setup |
| Default password | password | Change immediately |
| Certificate | Self-signed | Browser warning on first visit is expected |
| Root (SSH/console) | user root | Password you set during install |
Security notice: change the default openfiler / password credentials the moment you log in. Those defaults are published in every tutorial (including this one) and are a serious risk on any reachable network. Because OpenFiler no longer receives security updates, also keep the appliance behind a firewall and off the public internet.
Common first-install problems
Almost every first-time OpenFiler install stumbles on one of these three issues. Match the symptom to the fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| No free physical volumes; can't create any storage | sdb was formatted during install (the checkbox was left checked) | Reinstall and uncheck sdb during partitioning, or add sdb as a new physical volume manually if it's still raw |
| Web console won't load at all | Browsing to http:// or port 80/443 | Use the exact address https://<ip>:446, accept the self-signed cert |
| "Connection refused" or page times out | VM has no routable IP, or TCP 446 is blocked | Confirm the VM's IP on the console; set the NIC to bridged; allow TCP 446 through any firewall |
| Login fails with defaults | Password already changed, or caps lock | Reset via SSH as root, or reinstall if credentials are lost |
| Clients can't mount a new volume | Service (iSCSI/NFS/CIFS) not enabled, or network ACL not set | Enable the service and grant the client subnet access in System → Network Access Configuration |
Next steps
Installation only gets you to an empty appliance. The real work — creating physical volumes on sdb, building volume groups, and exporting shares over iSCSI, NFS, or CIFS — happens in the web console. Continue with our complete OpenFiler configuration tutorial, and if you're deciding how clients will connect, read connecting to storage systems using iSCSI, NFS, and CIFS/SMB.