“Storage Not Initialized” on a UDM Pro Max with empty drive bays: diagnosis and the risks of Erase and Format

Ubiquiti’s specifications identify three forms of storage on the Pro Max: two 3.5-inch bays for recording drives, a built-in 128 GB SSD, and 32 GB of eMMC.¹ The SSD is always present. The bays remain empty until hard drives are installed, typically for UniFi Protect recordings.

When no hard drive is installed, the built-in SSD is the only drive represented by the page’s statement that “all available drives” contain unrecognized data.

In late September 2026 we examined two Pro Max consoles that showed the warning, both on UniFi OS 5.1.33 with UniFi Network 10.6.106, both with empty bays. The Storage page renders state supplied to the browser by the console’s storage service. We read that state directly without modifying it and compared the readings with the displayed page.

• The storage service reported a healthy SSD. The storage service reported the internal SSD healthy and mounted, with no listed issues and an error count of zero. The system volume was also healthy, and both bays were reported as empty slots.
• The reported capacity figures matched. The page’s “Used” figure was exactly the storage service’s used space plus its system reserve. The page was reading the same healthy disk and assigning an incorrect status.
• The warning appeared without a firmware change or restart. On one console, nightly captures of the Storage page showed “Drive Not Found” up to 21 September and “Storage Not Initialized” from 22 September. The UniFi OS and Network versions were the same before and after, and the console had not restarted.
• The system log contained no storage events. Nearly three weeks of system-log entries on the other console contained no storage events.
• Other models on the same release reported normal storage states. A UDM Pro with no drive showed “Drive Not Found”. A UDM Pro and a UDM SE, each with one hard drive, showed their storage as fully operational. Only the two Pro Max consoles with empty bays showed the warning.

With the site’s approval, we followed the page’s first recommendation and performed a graceful restart on one console. The console returned to service in about three minutes and every device reconnected. The page continued to display “Storage Not Initialized”, while the storage service continued to report a healthy SSD. The restart did not resolve the warning on that console.

• Both consoles showed a discrepancy between the page and the storage service. The service reported a healthy built-in SSD while the page labelled that same disk uninitialized. On one console, the warning appeared without a firmware change or restart. A subsequent restart of one console did not clear the warning.
• The cause of the classification remains unconfirmed. A change in how the page interprets storage data is consistent with the evidence. We have no access to Ubiquiti’s code and found no published explanation from Ubiquiti as of 20 October 2026.
• Ubiquiti’s documentation does not address this warning. Its help article on drive and storage health lists statuses such as Optimal, Drive Failure Detected, Drive at Risk of Failure and UniFi Data Found, and has no entry for “Storage Not Initialized”.² The release notes for UniFi OS 5.1.33 do not mention storage.³
• The findings apply to a limited sample. Two consoles do not establish that every Pro Max exhibits this behaviour, or that the same message on another model has the same cause.

On 20 October 2026 we re-checked both consoles. The restarted console remained on UniFi OS 5.1.33, the release installed when the warning appeared, with no newer release offered to it. Daily readings from the other console’s storage service consistently reported healthy storage through that date.

Most public threads concerning this message involve hard drives installed in devices such as a new recorder, a Cloud Key or a Pro Max with a newly added surveillance drive.⁴ Owners report that reformatting, reseating the drives or changing the protection level did not clear the warning. The threads we found contain no confirmed resolution.

An installed drive may contain data the console does not recognize. One example is a drive transferred from another console, which Ubiquiti reports as “UniFi Data Found”.² In that case, Erase and Format deletes the drive’s contents, including existing recordings. Back up any required data and contact Ubiquiti support before erasing the drive.

1. Confirm that both drive bays are empty. On the Storage page, both bays should read “No Drive Detected”, and neither should contain a physical drive. If a drive is installed, follow the guidance in section 05.
2. Read the storage table. The console itself should be listed at about 117 GB with a modest amount used. That is the built-in SSD.
3. Confirm normal application operation. UniFi Network and any other installed applications should open and work normally. On the consoles we examined, no other function was affected.
4. Confirm backups are current. In the console’s backup settings, the latest cloud backup should be recent. Download an additional backup to a computer to retain a copy independently of the console.
5. Read the system log. Search the console’s system log for storage, disk or drive entries around the day the warning appeared. On the consoles we examined there were none.

If all five checks are satisfied, the evidence is consistent with the same display fault. Report it to Ubiquiti support with a screenshot of the Storage page, your UniFi OS and Network versions, and a note that both bays are empty. If any check fails, such as an application failing to start, a missing backup or disk errors in the log, treat the condition as a storage problem and contact Ubiquiti support before making changes.

A later UniFi OS release may correct the page; a release can also introduce a similar change in behaviour. Our article on when to update UniFi firmware, and when to wait explains how to schedule updates so that changes in console behaviour can be associated with a specific date.

On a Pro Max with empty bays, the only drive the button can act on is the built-in SSD, which holds the console’s application data. Erasing healthy storage does not correct a status label; it forces the console to rebuild its application data or, in the worst case, to be restored from backup. Neither repeated restarts nor a factory reset addresses this fault.

• A restart did not resolve the observed warning. On the console we restarted, the warning persisted while the storage service continued to report healthy storage.
• A factory reset erases the console’s configuration. The evidence identifies an incorrect status label. Resetting the configuration does not constitute a storage repair.

Preserve the console’s current state, maintain current backups and await a correction from Ubiquiti. When monitoring a console with this documented condition, assess storage health from the storage service’s readings. A conflicting Storage page warning should be treated as a display fault.