Vivotek

Vivotek SD Card Corrupted? Enterprise Troubleshooting Guide

Resolve SD card corruption in Vivotek cameras with step-by-step diagnostics using VAST Security Station and brand-specific tools. Enterprise-focused solutions for IT administrators.

Is this your issue?

Camera shows offline in the VMS dashboard but responds to ping
RTSP stream drops intermittently despite stable network link
Firmware update stuck in pending state in the management platform
VAST Security Station reports 'SD Card Error' in Device Health
Camera reboots unexpectedly during recording sessions
PoE negotiation fails — switch port shows Class 0 instead of expected Class 3
SD card not detected during initial setup or after reboot

Sound familiar? The guide below will help you fix it.

Resolve Vivotek SD Card Corruption: Enterprise Troubleshooting Guide

SD card corruption in Vivotek cameras can disrupt recording and playback functionality, particularly in mission-critical environments. This issue often stems from incompatible card specifications, improper formatting, or hardware degradation. The solution involves brand-specific tools like VAST Security Station and Vivotek's Network Diagnostics utility. This guide provides targeted steps for IT administrators and security integrators to resolve the issue efficiently.

Quick Checks for Vivotek SD Card Corruption

Begin with these 30-second checks to identify immediate issues:

Verify VMS Dashboard Status: In VAST Security Station, check if the camera is marked as Offline or Degraded. A degraded status may indicate partial SD card failure.
Inspect PoE Link Light: Confirm the switch port's PoE light is solid (Class 3) and not flickering. Flickering may indicate power instability affecting the card.
Ping the Camera IP: Use ping [camera_ip] from the VMS server to confirm network connectivity. A successful ping does not guarantee SD card functionality.
Check Status LED: For FD9391-EHTV or IB9391-EHT models, a red blinking LED may indicate SD card errors. Hold the reset button for 10 seconds to initiate a factory reset if necessary.
Power Cycle the Camera: Disable the switch port for 30 seconds, then re-enable to reset the camera and SD card.

Step-by-Step Troubleshooting

Verify SD Card Specifications

Ensure the SD card complies with Vivotek's requirements: Class 10 or higher, exFAT or FAT32 format, and endurance rating ≥ 1000 P/E cycles. Use a card reader to inspect the file system. If the card is formatted as NTFS or uses a non-compatible brand (e.g. non-Samsung, non-SanDisk), replace it with a certified Vivotek-compatible card.

Run VAST System Health Check

In VAST Security Station, navigate to Device Management → System Health. Look for SD Card Errors under the Local Storage section. If errors are reported, use the SD Card Diagnostic Tool (accessible via the Advanced Tools menu) to run a full disk scan. This tool will identify bad sectors or file system inconsistencies.

Reformat SD Card via VAST

If the card is readable but corrupted, use the SD Card Reformat feature in VAST Security Station. Navigate to Camera Settings → Storage Management → Reformat SD Card. Confirm the action, as this will erase all data. After reformatting, restart the camera and verify that the card is now detected.

Check Firmware Channel Compatibility

Access the camera's web interface via http://[camera_ip]. Navigate to Firmware Management and confirm the camera is on the Stable channel. If it's on the Beta channel, switch to Stable to avoid firmware-related corruption. For enterprise deployments, use the Staged Rollout feature in VAST to apply updates without disrupting the SD card.

Analyze Network Traffic with Shepherd

Use the Shepherd device discovery tool to scan for SD card-related anomalies. Launch Shepherd, select Network Diagnostics, and filter by Vivotek devices. Look for RTSP stream drops or unresponsive SD card access in the logs. If Shepherd detects inconsistent latency (more than 50ms) between the camera and VMS server, adjust QoS policies on your switch to prioritize video traffic.

Advanced Diagnostics and Recovery

Initiate Packet Capture

If SD card corruption persists, use Wireshark to capture RTSP traffic from the camera. Filter by rtsp and look for TCP retransmissions or RTSP 503 errors, which may indicate SD card write failures. Save the capture file and submit it to Vivotek support for analysis.

Repair VMS Database Corruption

In VAST Security Station, go to Database Management → Consistency Check. This will verify the VMS database for inconsistencies that may be causing SD card errors. If corruption is detected, initiate a Database Repair and restart the VMS server after completion.

Enterprise Support Escalation

If all steps fail, submit a support ticket via https://vivotek.zendesk.com. Include: camera model, firmware version, VAST System Health Check report, and packet capture logs. For urgent cases, request a VMS Database Repair or RMA Process for the camera.

Root Causes and Prevention

Enterprise-Specific Causes

SD card corruption in Vivotek cameras often stems from: incompatible card specifications, firmware incompatibility, or network instability. In enterprise environments, ensure all cameras are on a dedicated VLAN with QoS policies prioritizing video traffic. Avoid using non-endurance-rated SD cards in 24/7 recording scenarios.

UK-Specific Considerations

Under the Consumer Rights Act 2015, UK users have a 6-year right to bring a claim for faulty goods for faulty SD cards. However, this applies only if the card is not a consumable item. For enterprise deployments, replace SD cards every 1-2 years to prevent wear-related failures. Use surveillance-rated cards (e.g. Samsung PRO Endurance) and ensure PoE budget headroom is maintained across switches.

Prevention and Long-Term Care

Schedule Firmware Updates

Use VAST Security Station's Firmware Management to schedule updates on Stable channel only. Avoid Beta firmware for mission-critical systems. Enable Staged Rollout to apply updates across devices without disrupting SD card functionality.

Monitor PoE Budget

Use the PoE Budget Calculator in VAST to ensure no switch port exceeds 802.3af Class 3 requirements. For large deployments, deploy PoE++ switches to avoid power exhaustion, which can indirectly cause SD card failures.

Implement Redundant Storage

For critical systems, enable Edge Storage Failover in VAST Security Station. This routes recordings to an NVR or cloud storage if the SD card fails, ensuring continuous operation.

Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.

Replacement Decisions

SD cards in Vivotek cameras typically last 1-2 years with continuous use. Replace cards if: file system errors persist, write speeds drop below 10MB/s, or corruption occurs after 300+ reboots. For enterprise environments, use Samsung PRO Endurance or SanDisk High Endurance cards rated for 1000+ P/E cycles. Always verify card compatibility via Vivotek's official documentation before deployment.

What if this wasn't your problem to solve?

scOS detects suspicious activity — not motion. It only alerts you when something matters, like a person would. Designed to be left alone. All features included.

Detects Suspicious Activity

Not motion — actual suspicious behaviour. Like a person would notice.

Designed to Be Left Alone

No settings to tweak. No app to check. It just works.

All Features Included

No subscriptions. No tiers. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

For network-level causes of SD card corruption, first verify VLAN assignments in your switch configuration. Ensure the camera is on a dedicated VLAN with no conflicting IP ranges. Check PoE budget on the switch port—Vivotek cameras require 802.3af compliance. If multiple cameras share the same switch, confirm no power exhaustion is occurring. Use the VAST Security Station to run a network diagnostics report, which will highlight misconfigured VLANs or power negotiation failures. If the issue persists, consult your switch's SNMP logs for Class 0 errors, which indicate failed PoE negotiation.

In VAST Security Station, navigate to **Device Management** → **Camera Settings** to re-register the camera. Ensure the camera's firmware is up to date via the **Firmware Management** tab. If the camera is still not detected, use the **Shepherd device discovery tool** to scan for orphaned devices on the network. If the camera appears in Shepherd but not in VAST, restart the VAST service or reconfigure the camera's ONVIF profile in the **Advanced Settings** menu. Verify that the camera's RTSP stream URL is correctly configured in the VMS integration settings.

Vivotek cameras support two firmware channels: **Stable** and **Beta**. To check the current channel, log into the camera's web interface via the **Firmware Management** menu. If the camera is on the Beta channel and experiencing corruption, switch to the Stable channel. For enterprise deployments, use the **Staged Rollout** feature in VAST Security Station to apply firmware updates across multiple devices. If corruption occurs post-update, initiate a **Firmware Rollback** via the same menu. Always verify firmware compatibility with your camera model before applying updates.

To escalate support for SD card corruption, access Vivotek's enterprise support portal at https://vivotek.zendesk.com. Submit a support ticket with the following details: camera model (e.g. FD9391-EHTV), firmware version, and a **VAST System Health Check** report. Include any packet captures from the camera's RTSP stream using Wireshark or similar tools. For critical environments, request a **VMS Database Repair** via the VAST Security Station's **Advanced Diagnostics** menu. If hardware failure is suspected, initiate the **RMA Process** through the support portal, providing serial numbers and failure symptoms.

All Troubleshooting Guides