Reply
Highlighted
Member
Posts: 191
Registered: ‎05-06-2011
Kudos: 42
Solutions: 3
Accepted Solution

NVR Hard Drive Replacement

I have an AirVision NVR 2 years old in remote location which has a Hard Drive screaming.  Is it possible to replace the drive and/or worthwhile effort.  I havent retrieved the NVR nor have I ever attempted to open up the FoxConn hardware to inspect.  Thinking it might be a plug in drive.

"The floggings will continue until morale improves." Capt Bligh 1789.

Accepted Solutions
Ancient Member
Posts: 32,661
Registered: ‎05-05-2012
Kudos: 10449
Solutions: 1619

Re: NVR Hard Drive Replacement

If you replace it with the same size drive, you should be able to clone the old drive to the new provide the old drive does not have corrupt sectors.

 

2 years sounds to new for it to be an airVision branded NVR.  I'm sure they switched over to the UniFi branding long before that.  The UniFi branded NVRs also have a CPU fan that might be prone to failure after around the 2 year mark so the screaming might be the fan and not the drive.

View solution in original post


All Replies
Established Member
Posts: 912
Registered: ‎09-25-2014
Kudos: 274
Solutions: 49

Re: NVR Hard Drive Replacement

Yes it is possible to replace the drive. Ubiquiti doesn't offer anyway to flash your new drive though so you would be settings up your own Linux box and installing UniFi Video on it.

Ancient Member
Posts: 32,661
Registered: ‎05-05-2012
Kudos: 10449
Solutions: 1619

Re: NVR Hard Drive Replacement

If you replace it with the same size drive, you should be able to clone the old drive to the new provide the old drive does not have corrupt sectors.

 

2 years sounds to new for it to be an airVision branded NVR.  I'm sure they switched over to the UniFi branding long before that.  The UniFi branded NVRs also have a CPU fan that might be prone to failure after around the 2 year mark so the screaming might be the fan and not the drive.

Member
Posts: 191
Registered: ‎05-06-2011
Kudos: 42
Solutions: 3

Re: NVR Hard Drive Replacement

Thanx Raceboy.  I should have searched the Forum as I see quite a lot on this. Kind of paniced with the screaming NVR call. I have one other non-ubiquiti FoxConn chassis running Ubuntu 16.04 LTS with both NVR and Wifi applications which has been rock stable so I should be ok with doing that.

 

One other question - What is the real meaning of "Thin 2 1/2 drive" I see mentioned as required.  I see form factor measurments but nothing about a replacement being Thin.  Dont want to get the wrong form factor.  Would like to replace with 1 TB capacity.

"The floggings will continue until morale improves." Capt Bligh 1789.
Member
Posts: 191
Registered: ‎05-06-2011
Kudos: 42
Solutions: 3

Re: NVR Hard Drive Replacement

Oh yea, the Fan!!!  Will have to check that out.  I have had to replace fans on APC UPSs and they were screaming!!

"The floggings will continue until morale improves." Capt Bligh 1789.
Member
Posts: 191
Registered: ‎05-06-2011
Kudos: 42
Solutions: 3

Re: NVR Hard Drive Replacement

The screaming NVR was in fact the fan.  Found that the fan turns on and off as needed and has a FoxCon sticker on it.  The NVR is an appearant FoxConn NT510 model and the fan is labeled as such.  There are numerous sources for the exact part.

"The floggings will continue until morale improves." Capt Bligh 1789.
Regular Member
Posts: 391
Registered: ‎05-24-2017
Kudos: 144
Solutions: 11

Re: NVR Hard Drive Replacement

Hey guys -- if you have SSH access to your NVR you can install smartctl on to the NVR and check the SMART status of the drive to see what's up.  I've got two that have some reallocated sectors but haven't failed hard yet -- when they get worse or finally fail I'll replace them likely with a WD drive instead of Seagate.  I also build my own NVRs w/ NUC PCs that are great -- been using the identical drives the UBNT appliance has but will go w/ WD black or red drives as I think they are more reliable.  I PXE boot Debian 7 with minimal install and then put the UBNT software on w/ dpkg and it's great.  I'm curious if anyone has successfully installed Debian 7 on a UBNT NVR appliance w/ a replaced disk -- The Debian 7 they put on it has a newer kernel and possibly other stuff along w/ their Nginx based web interface for basic IP configuration.  I'm hoping to install Debian 7 stock like I do on my NUC based NVRs on the UBNT appliance and have it work only sacrificing the config web interface that's on port 80/443...  I don't mind setting IP addr from SSH or console.

 

Here's the commands to get smartctl on there:

 

root@bnpdeli-nvr:~# apt-get install smartmontools
Reading package lists... Done
Building dependency tree       
Reading state information... Done
smartmontools is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

In my example smartmontools is already installed.  If it doesn't go due to apt being out of date, do an "apt-get update" to have it grab the latest package info from the debian mirrors and try the "apt-get install smartmontools" again.

 

Once installed you can check the drive health with:

 

root@bnpdeli-nvr:~# smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.18.63-ubnt] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST2000LM015-2E8174
Serial Number:    WDZA2JCQ
LU WWN Device Id: 5 000c50 0ac1cb296
Firmware Version: SDM1
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   10
ATA Standard is:  Not recognized. Minor revision code: 0x001f
Local Time is:    Sat Feb 16 10:29:23 2019 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x71) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   073   064   006    Pre-fail  Always       -       18859960
  3 Spin_Up_Time            0x0003   099   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       36
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       2
  7 Seek_Error_Rate         0x000f   088   060   045    Pre-fail  Always       -       703458638
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       86560770893687
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       36
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   060   049   040    Old_age   Always       -       40 (Min/Max 23/45)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       3
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       16
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1579
194 Temperature_Celsius     0x0022   040   051   000    Old_age   Always       -       40 (0 14 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       120787365275508
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       77077677240
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       333954275
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

root@bnpdeli-nvr:~# 

This one hasn't tripped SMART and the OS hasn't seen block device errors yet since the drive has been able to remap the 2 bad sectors.  The numbers to watch are reallocated sector count and g-sense error rate.  These are zero on a perfect drive.

 

The "dmesg" command can also help to tell if you've gotten errors up to the OS yet such as "sda: I/O error" or similar.  This one is clean so far.

 

Good luck!

Reply