The appeal is straightforward: reuse hardware, keep files under your control, and reduce dependence on a paid storage quota. OpenMediaVault provides the foundation as a free, open-source network-attached storage system built on Debian Linux, with browser-based administration and file-sharing services. The software is free; operating a dependable photo archive still takes equipment, electricity, backups, and attention.
What this Google Photos alternative actually replaces
Aguilar describes installing OpenMediaVault, connecting storage drives, and administering the resulting server through a browser on his home network. His account establishes a working personal storage setup—not a tested, feature-for-feature replacement for Google Photos.
OpenMediaVault’s advertised capabilities include storage management, file sharing, software updates, disk-health monitoring, and extensions through plugins. Those are useful building blocks, but they should not be confused with a complete photo-management workflow.
The account does not identify an application for automatic phone uploads, face recognition, searchable photo collections, or mobile album sharing. Anyone following this approach should therefore treat it as a self-hosted storage alternative first, with the photo-app experience still to be planned.
The cloud-storage pressure behind the project is real, although rising prices are not established by this account. Google documents up to 15 GB of standard account storage shared across Gmail, Drive, and Photos. When that storage is full, new photos and videos cannot be backed up to Photos; remaining over quota for two years can also put existing content at risk of deletion under Google’s policies.
Bottom line: This project addresses where the files live. It does not, by itself, reproduce everything people enjoy about a cloud photo service.
Before installing: distinguish the three storage roles
The most consequential omission in the original walkthrough is the difference between installation media and permanent storage.
For a conventional dedicated-drive setup, think in three parts:
- Installer USB: boots the installation environment.
- System drive: holds OpenMediaVault and its operating system.
- Data drive or drives: hold the photo library.
OpenMediaVault’s documentation recommends the dedicated-drive installation method for a fresh x86/AMD64 machine. Its prerequisites also distinguish system storage from data storage; the standard system drive is not intended to double as a shared data volume.
An 8 GB thumb drive, as mentioned in Aguilar’s account, is therefore not a complete storage plan. Nor does “old PC” automatically mean suitable PC. The project’s prerequisites list 1 GiB RAM as a minimum while recommending 8 GiB or more, and explain that performance depends on the network interface, network capacity, storage, and concurrent users.
Most importantly, installation is destructive. The official ISO instructions warn that the selected system disk loses its existing data and recommend disconnecting other disks before installation. They also say the installer picks the first available disk—an excellent reason not to leave your only photo archive attached.
A safer OpenMediaVault installation sequence
For the documented OpenMediaVault 8.x dedicated-drive route, the installation outline is:
- Back up anything important on the prospective server.
- Disconnect data disks, leaving the intended system disk available alongside the installation media.
- Download the official ISO and write it to bootable media. OMV’s instructions name Etcher or the Linux
ddutility. - Connect the server to a working network with internet access and boot the installer.
- Complete the installation prompts, including setting the root password.
- Remove the installer, boot from the installed system, and reconnect the data drives afterward.
Aguilar used Rufus from a Windows PC. That is his reported method, but the official OMV instructions inspected here do not establish his specific Rufus mode and partition-setting advice as universal.
After startup, the console can display the server’s local IP address. Open that address in a browser. OMV documents the initial web credentials as username admin and password openmediavault; these are separate from the root password created during installation. Change the default web password promptly.
The documentation also says root SSH access is enabled by default and recommends disabling that behavior through Services | SSH after installation. If SSH administration is needed, arrange an appropriate alternative account before removing your existing access.
Connecting drives is not the same as sharing them
A USB drive does not become a properly configured network share merely because it is plugged in.
OpenMediaVault requires filesystems to be mounted through its web interface so they are registered in its configuration database. Only then can those volumes be used for shared folders. If a drive contains existing photos, distinguish mounting its filesystem from creating or deleting one: OMV’s documentation explicitly warns that its filesystem deletion operation removes filesystem signatures.
For Windows access, configure a shared folder and expose it through SMB/CIFS, with an authorized user and suitable permissions. A private Samba share requires credentials; write access also depends on the underlying filesystem permissions, not just the share’s access setting.
Once that share works, Windows 11 can give it a familiar drive letter:
- Open File Explorer and select This PC.
- Choose More (…) > Map network drive, or right-click This PC and select that command.
- Pick an available drive letter.
- Enter the network folder path and optionally select Reconnect at sign-in.
- Select Finish and authenticate when required.
Before copying the whole library, use a small test folder. Confirm that an authorized account can copy and reopen a photo, and that access matches your intended permissions. That is a more meaningful success test than simply seeing the server’s dashboard.
Common setup snags
- The disk exists but is unavailable for shared folders: confirm its filesystem was mounted through OMV’s interface.
- You can read files but cannot write: check both share permissions and filesystem permissions. OMV documents that restricted filesystem access can override an allowed Samba write setting.
- Windows cannot connect: Microsoft identifies an unavailable host and insufficient permissions as common causes. Confirm the server is running and the account is authorized.
Backups are part of the build, not an optional extra
Moving every photo onto one server drive gives you a new primary copy, not a resilient archive.
CISA’s 3-2-1 guidance calls for:
- Three copies: the primary data plus two backups.
- Two different media types.
- One copy off-site.
Aguilar names BorgBackup and Restic as possible backup tools, but does not provide a tested configuration. Restic’s documentation confirms encrypted, authenticated repository storage and deduplication. It also makes an important limitation clear: encryption does not prevent an attacker with sufficient storage access from deleting backups.
Whatever tool you choose, include a restore test. Government-hosted backup guidance specifically recommends restoring a file or folder periodically rather than assuming a completed backup job guarantees recovery.
More control, with a maintenance bill attached
The original account recommends a VPN or reverse proxy for access away from home, but supplies no configuration. Neither should be treated as a completed security solution merely because its name appears on a checklist. For this project, establish reliable local access and recoverable backups before expanding its reach.
The “free” claim also needs boundaries. Aguilar provides no measured power consumption, electricity rate, drive-replacement budget, or comparable cloud plan, so his experience cannot establish a break-even point.
The sensible conclusion is narrower—and still worthwhile. OpenMediaVault can give suitable spare hardware a second career as browser-managed network storage, including shares accessible from Windows. Whether that becomes your preferred photo solution depends on the upload workflow, backup strategy, and maintenance commitment you build around it.
Owning the storage is empowering. Being its administrator is the part that does not come with an unsubscribe button.