TL;DR
- "Not recording" can mean no schedule, a full disk, a channel with recording disabled, or playback that does not match the live view.
- Check the recording schedule first; it is the most common cause and the easiest to fix.
- Then check disk health and capacity; a failed or full disk stops recording without a dramatic alarm.
- Confirm the channel's record stream and codec, then check time sync and firmware.
- Test playback before leaving; a live image does not prove the recorder is writing to disk.
An NVR that shows live video but records nothing is a quiet failure. The operator assumes the system is working because the screen is alive, and the problem is discovered only when someone asks for footage from last week. By then, the missing period cannot be recovered.
This guide gives a practical sequence for HIK NVR troubleshooting when recording stops or never starts. Work through the schedule, the disk, the channel settings, time sync and firmware. The order moves from the most common configuration cause to the least common hardware cause.
1. What "not recording" actually means
Before changing settings, define the symptom. Is there no recording at all, or only for one channel? Is the timeline empty, or does it show gaps? Does playback show a different period from what the operator expects? Does the recorder report a disk error?
Those states point to different causes. A single channel with no recording is usually a channel setting. All channels with no recording is usually the schedule, the disk or the recorder. A recording that stops after a few days is often a disk or retention problem. A recording that plays but is shorter than expected is often an overwrite or capacity issue.
Write down the time window, the channel and what changed recently. A firmware update, a disk replacement, a schedule change or a time-zone change are common triggers. The timeline of changes is often more useful than the symptom alone.
Test playback on the recorder itself, not only in the mobile app. The app may show a cached or live image that hides a recording problem. The recorder's playback timeline is the authoritative view.
2. Fix 1 — Check the recording schedule
The schedule is the first thing to check because it is the most common cause and the easiest to correct. A recorder can be healthy and a camera can be online while the schedule tells the recorder not to record.
Open the recording schedule and confirm the channel is set to record during the period in question. Check whether the schedule is continuous, motion-based or alarm-based. A motion schedule on a quiet scene may produce very little footage, which can look like "not recording".
Check the day-of-week and holiday settings. A schedule that excludes weekends or holidays will leave gaps that look like failures. Check the time zone and daylight-saving settings; a one-hour shift can make a recording appear to start late.
Confirm the channel is enabled for recording and that the record type matches the expectation. Some recorders separate scheduled, motion and alarm recording; a channel may be recording only one type. If the site expects continuous recording, set it explicitly rather than relying on a default.
After changing the schedule, save and confirm the recorder shows the channel as recording. Then wait a few minutes and check the playback timeline for new footage.
Check the record mode for each stream. Some recorders record the main stream continuously and the sub-stream on motion. A channel may appear to be recording while the timeline only shows motion clips. Confirm which stream the operator expects.
If the site uses a holiday calendar, confirm the calendar is applied to the right channels.
Confirm the schedule is applied to the correct channel group. Some recorders let you copy a schedule from one channel to another; a failed copy leaves a channel on the default schedule, which may be different from what the site expects.
3. Fix 2 — Check the disk and storage
If the schedule is correct, check the disk. A failed, full or unmounted disk stops recording without a dramatic alarm on many recorders.
Open the storage status page and confirm the disk is detected, healthy and formatted. Check the remaining capacity and the estimated retention. A disk that is full and set to stop recording will not overwrite; a disk set to overwrite will keep recording but shorten the retention.
Check the disk health indicators, such as S.M.A.R.T. status, reallocated sectors and temperature. A disk that is failing may record intermittently or corrupt the index, which makes footage hard to find even when it exists. Replace a suspect disk before it fails completely.
Confirm the disk is assigned to the recording pool and the channel is allowed to write to it. Some recorders support multiple disks or groups; a channel may be assigned to a group that is full or offline.
If the recorder has RAID, check the array status. A degraded array may still record, but a failed rebuild or a second failure can stop recording.
Check the disk's file system and format. A disk formatted by another recorder or a PC may not be usable. Format it in the recorder after backing up any required footage.
If the recorder supports disk groups, confirm the channel is assigned to a group with space.
Check the disk's write speed and interface. A slow or failing drive can cause dropped frames and gaps even when the capacity looks sufficient.
Check the disk's power and cabling. A loose SATA or power connector can cause a disk to drop out intermittently. Reseat the cables and confirm the disk stays detected under load.
4. Fix 3 — Check channel and stream recording settings
If the disk is healthy, check what the channel is actually writing. A camera can stream live while the recorder is set to record a stream it cannot decode or a stream that is disabled.
Confirm the channel's record stream. Many cameras provide a main stream and a sub-stream; the recorder may be set to record the sub-stream, which produces lower quality than expected, or to a stream that is not available. Match the record stream to the project requirement.
Check the codec. A camera set to H.265 may not be supported by an older recorder or firmware. If the live view works but the recording is empty, switch the camera to H.264 as a test. If recording starts, the codec is the issue.
Check the frame rate and bitrate. A very high bitrate may exceed the recorder's incoming bandwidth, causing dropped frames or failed recording. A very low bitrate may produce a recording that is technically present but too poor to use.
Confirm the channel is not in a special mode such as "preview only" or "disabled recording". Some recorders allow a channel to be added for live view without recording;
If the camera and recorder are from different vendors, confirm the ONVIF profile. The ONVIF profiles define which functions are interoperable; recording may work under one profile but not another.
Check the recording resolution and frame rate against the project requirement. A recorder may downscale the stream to save bandwidth,
Check the channel's recording priority. Some recorders allow a channel to be set as low priority, which reduces its bitrate or frame rate when the recorder is busy.
Check the channel's motion sensitivity and pre/post-record settings. A motion schedule with low sensitivity may miss events, and a short pre/post buffer may cut off the moments before and after the trigger. Review these settings alongside the schedule.
5. Fix 4 — Check time sync and NTP
Time is part of recording. If the recorder's clock is wrong, the footage may be written under the wrong date and appear missing during a search. A large time jump can also create gaps in the timeline.
Check the recorder's date, time and time zone. Confirm daylight-saving settings match the site. Then check whether the recorder is using NTP. The NTP project provides the standard time-sync protocol; most recorders can use a local server or a public pool.
Let the cameras sync from the recorder, or point both at the same NTP source. If cameras and recorder disagree by minutes, exported clips and search results become confusing. A consistent clock is as important as a working disk.
After correcting the time, check the playback timeline around the change. A time correction can create an apparent gap; confirm that new recordings appear at the correct time
Check the recorder's time after a power outage. Some recorders lose time if the battery is depleted; others resync from NTP.
Export a short clip and play it on a PC.
Check the NTP server reachability. A recorder that cannot reach its NTP server may drift; a local NTP server on the camera VLAN is often more reliable than a public pool. Confirm the server address and the firewall rules.
6. Fix 5 — Check firmware and recorder capacity
The last layer is the recorder's firmware and capacity. A recorder that is at its channel, bandwidth or decoding limit may accept cameras but fail to record them reliably.
Check the firmware version and release notes. A camera released after the recorder's firmware may stream but not record correctly until the recorder is updated. Update during a maintenance window and verify recording afterwards.
Check the incoming bandwidth and the number of recording channels. A recorder may support 32 channels for live view but fewer for recording at full resolution. If the site has grown, a larger recorder or a second recorder may be the correct fix.
Check the recorder's logs for disk errors, stream rejections and authentication failures. The log often points directly to the layer that is failing. Export the log before clearing it, so the evidence is preserved.
Finally, test with a known-good camera on the same channel. If the known-good camera records, the original camera or its stream settings are the problem.
Check the recorder's hard disk compatibility list. A drive that is not on the list may work initially and then drop out under continuous write load.
Confirm the recorder's power supply is stable. A recorder that reboots silently can miss recording periods.
Keep the recorder's firmware and the camera's firmware documented.
Test recording with the mobile app disconnected. If the recorder records correctly without the app but stops when the app is connected, the app or a network setting is interfering with the stream.
7. Diagnostic table: symptom to action
| Symptom | Most likely cause | First action |
|---|---|---|
| No recording on one channel | Channel record setting or stream | Check schedule and record stream |
| No recording on all channels | Schedule, disk or recorder | Check schedule, disk status and logs |
| Recording stops after a few days | Disk full or retention | Check capacity and overwrite policy |
| Playback shows wrong date | Time zone or NTP | Correct time and verify timeline |
| Live works, recording empty | Codec or stream mismatch | Try H.264 and the main stream |
| Disk error or degraded RAID | Disk failure | Replace the disk and rebuild |
Use the table as a checklist, not a verdict. The same symptom can have more than one cause, and the logs usually narrow it down. Record the result next to each row so the next engineer can see what was already ruled out.
8. Prevention checklist
- Confirm the recording schedule and save it explicitly.
- Check disk health and remaining retention every month.
- Use surveillance-grade drives, not desktop drives.
- Enable NTP on the recorder and let cameras sync from it.
- Test playback after every firmware update.
- Keep a spare drive and a known-good camera for testing.
- Monitor disk errors and recording failures.
- Document the schedule, stream settings and retention policy.
A recording system is only as good as its last verified playback. A short monthly check prevents the discovery of a silent failure weeks later.
Keep the recorder's storage report in the handover file. A capacity and retention baseline makes it obvious when a disk is degrading or a camera bitrate has changed. Finally, verify the recording after any change, not only after a failure. A schedule or firmware change can silently alter behaviour. A quick playback check is the difference between a working system and a surprise. It takes a minute and prevents a week of missing footage.
9. FAQ
Why is my HIK NVR not recording? The most common causes are a disabled schedule, a full or failed disk, a channel set to preview only, or a codec the recorder cannot record. Check the schedule and disk first.
Why does live view work but playback is empty? The channel may be set to preview only, or the record stream may be disabled or unsupported. Check the channel's record settings and codec.
How do I know the disk is full? Open the storage status page and check capacity and retention. A disk set to stop when full will not overwrite; a disk set to overwrite will shorten retention.
Can a failed disk still show live video? Yes. Live view comes from the camera stream; recording depends on the disk. A failed disk can leave live view working while recording stops.
Why is the recording time wrong? Check the time zone, daylight-saving settings and NTP. A clock error makes footage appear under the wrong date.
Should I use desktop drives in an NVR? No. Surveillance-grade drives are designed for continuous write workloads. Desktop drives are more likely to fail under constant recording.
Can a firmware update fix recording problems? Sometimes. A firmware bug can affect recording, but update only after ruling out the schedule, disk and stream settings.
Why does the recorder show recording but playback is empty? The index may be corrupted or the recording may be on a different disk group. Check the disk health and rebuild the index if the recorder supports it. How much retention should I plan for? Agree the number of days first, then size the disk. Can a camera record to its own SD card if the NVR fails? Why is the recording shorter than the retention target? The disk may be undersized, the bitrate may be higher than planned, or the recorder may reserve space for other functions. Recalculate the storage budget.
Recommended HIK NVRs
If the diagnosis points to an undersized or failed recorder, these in-stock models cover common channel counts. Confirm the exact suffix and quantity before ordering.
| Model | Channels | Resolution | Price | Product |
|---|---|---|---|---|
| DS-7608NXI-K2 | 8 | 4K | $218.00 | View |
| DS-7616NI-M2 | 16 | 8K | $336.00 | View |
| DS-7732NI-I4-24P | 32 | 4K | $655.00 | View |
| DS-9632NI-M8 | 32 | 4K | $898.00 | View |
Need robust HIK NVRs, surveillance-grade hard drives, or bulk project support? Send your camera list and retention target to our wholesale team for model selection, disk sizing and bulk pricing.
Contact Hikdistribution Wholesale Team · Submit an Inquiry for Bulk Pricing