Support
How to Install, Initialise or Replace an NVR Hard Drive Safely
Storage Installation
Summary
Follow the four stages below to diagnose a new or replacement surveillance HDD must be installed and prepared without losing evidence, configuration or device ownership.
Applies to
- Diskless or upgradeable NVRs
- Single-disk recorders and like-for-like replacements
Difficulty and time
Difficulty: Advanced
Estimated time: 30 to 60 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when a new or replacement surveillance HDD must be installed and prepared. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: the recorder has no storage, shows an uninitialised disk, or needs a failed disk replaced.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Export required footage and configuration before removing an old disk; photograph bay order on multi-disk recorders.
Never hot-plug an NVR disk unless the exact model supports it
Power the recorder down before internal disk work unless the manufacturer explicitly documents hot-swap support. Initialising the wrong disk can destroy evidence.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- The recorder was purchased diskless
- The old HDD has failed
- The replacement capacity is unsupported
- The new disk has not been initialised
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: the recorder has no storage, shows an uninitialised disk, or needs a failed disk replaced.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Export required footage and configuration before removing an old disk; photograph bay order on multi-disk recorders.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Main Menu > Storage > HDD, Disk or HDD Management. Do not change anything until the displayed state is recorded.
- Open Main Menu > Storage > HDD, Disk or HDD Management. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Confirm the recorder model, supported drive count and maximum supported capacity.
- Identify whether existing disks contain required footage or form part of an array.
- Photograph drive bays, cables and disk order before hardware work.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Shut the NVR down through its menu, isolate power and follow ESD precautions before opening it.
- Install a compatible surveillance-rated SATA drive with the correct screws, data cable and power connector.
- Restore power, open HDD Management and confirm the expected model and capacity are detected.
- Initialise only the new empty disk, then enable the intended overwrite and recording policy.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Confirm the new disk reports Normal or Healthy.
- Check every required camera has a recording schedule.
- Create and play a fresh local recording from two different channels.
- Restart once and confirm the disk and recordings remain available.
Controlled support test
Situation: The reported symptom was: the recorder has no storage, shows an uninitialised disk, or needs a failed disk replaced.
Solution used: The current state was recorded in Main Menu > Storage > HDD, Disk or HDD Management, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in TP-Link VIGI Recording and Storage guide before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| the recorder has no storage, shows an uninitialised disk, or needs a failed disk replaced | new recorder supplied without storage, failed HDD, incompatible capacity, or incomplete initialisation | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when the recorder does not detect a known-compatible disk, multiple disks or RAID are involved, or footage preservation is required.
Send the order number if available, exact model, firmware or app version, screenshot of Main Menu > Storage > HDD, Disk or HDD Management, the failure time, and the result of the local proof test.
Related support guides
- Recording, Playback and Export - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- NVR Buying Guide - Recorder planning guide.
- CCTV Buying Guide - General CCTV planning guide.
Relevant product categories
- CCTV Products - General CCTV products.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Where should I click first for install NVR hard drive?
Start at Main Menu > Storage > HDD, Disk or HDD Management. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Confirm the new disk model and full expected capacity appear on the storage screen, then verify its status is Normal after initialisation.
-
What must I avoid changing during the first check?
Power the recorder down before internal disk work unless the manufacturer explicitly documents hot-swap support. Initialising the wrong disk can destroy evidence.
-
How do I prove the correction worked?
Record and locally play fresh footage, restart the NVR and confirm both the disk status and recording schedule remain healthy.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Main Menu > Storage > HDD, Disk or HDD Management, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.
















