Clip: Disk not ready (0)

[hotbrass]

I just started getting this error yesterday on all of my cameras:

2/2/2019 11:47:32 AM Clips: D:: 12, 6.90G/860.0G (+60.6G) (2)
2/2/2019 11:47:10 AM frontyard: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Rover1: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Indoor: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Frontdoor: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Backdoor: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Backporch: Clip: Disk not ready (0)

My disk is fine, my folders are fine, nothing was changed(in months) and this error just keeps popping up and it starts a new set of continuous recordings for all six of my cameras. And it happens several times a day and fills up my disk.

Any ideas as to why this is happening?

 

[fenderman]

I just started getting this error yesterday on all of my cameras:

2/2/2019 11:47:32 AM Clips: D:: 12, 6.90G/860.0G (+60.6G) (2)
2/2/2019 11:47:10 AM frontyard: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Rover1: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Indoor: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Frontdoor: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Backdoor: Clip: Disk not ready (0)
2/2/2019 11:47:10 AM Backporch: Clip: Disk not ready (0)

My disk is fine, my folders are fine, nothing was changed(in months) and this error just keeps popping up and it starts a new set of continuous recordings for all six of my cameras. And it happens several times a day and fills up my disk.

Any ideas as to why this is happening?

are you recording to NAS?

 

[hotbrass]

Thanks fenderman. No, recording to another drive in my computer. BI is installed on my C: drive and storage is installed on D: drive. And it has worked for years, problem just started yesterday. Disk checks out fine, rebooted, ran maintenance, rebuilt database, refreshed, did everything I can think of yesterday and today.

 

[fenderman]

Thanks fenderman. No, recording to another drive in my computer. BI is installed on my C: drive and storage is installed on D: drive. And it has worked for years, problem just started yesterday. Disk checks out fine, rebooted, ran maintenance, rebuilt database, refreshed, did everything I can think of yesterday and today.

delete the DB folder and restart blue iris so the database regenerates.

 

[hotbrass]

Will give it a try later. Walking out the door and will report when I get home. Thank you!

 

[hotbrass]

Nothing changed. I shut everything down and formatted the D: drive and it was working fine for a little while then it started back again with the "Clip: Disk not ready (0)" error and starts a new set of continuous recordings for all six of my cameras. And it just did it again while I am typing. Now I have 18 clips running.

 

[fenderman]

Nothing changed. I shut everything down and formatted the D: drive and it was working fine for a little while then it started back again with the "Clip: Disk not ready (0)" error and starts a new set of continuous recordings for all six of my cameras. And it just did it again while I am typing. Now I have 18 clips running.

I would email support. What did you use to test the disk?

 

[looney2ns]

Nothing changed. I shut everything down and formatted the D: drive and it was working fine for a little while then it started back again with the "Clip: Disk not ready (0)" error and starts a new set of continuous recordings for all six of my cameras. And it just did it again while I am typing. Now I have 18 clips running.

But did you delete the DB as @fenderman suggested?

 

[hotbrass]

As I posted I not only deleted it I reformatted the disk. I now have 48 clips and the same error.

federman, I am not on a support plan.

I used diskcheck.

 

[fenderman]

As I posted I not only deleted it I reformatted the disk. I now have 48 clips and the same error.

federman, I am not on a support plan.

I used diskcheck.

Use a disk diagnostic package recommend by the manufacturer of the drive. I will to bet the disk is defective

If not you'll have to get a support plan.

 

[bp2008]

This is a good tool for disk diagnostics. GSmartControl :: Home & News

 

[hotbrass]

Thanks bp2008! I have a spare hard drive that I use for backup on another computer and I have formatted it and installed it in my BI computer as a D: drive. It has been running for about 25 minutes and all is well so far.

I am doing an extended self test on another computer with the offending disk. It passed the short self test and all windows tests. The disk is in an external disk caddy and I can feel it is vibrating more than I would expect. So it may be an intermittent problem and the disk drive is just going bad. But so far no errors. Will report back in the morning.

Thanks all!

 

[bp2008]

That program will also tell you the number of reallocated sectors (can be a sign of a failing drive), temperatures the drive has reached, and that sort of thing. Though a lot of those SMART fields are difficult to interpret since they are not well-standardized.

 

[hotbrass]

Extended Self Test completed without error.

There appears to be nothing wrong with this drive.

However, I think it is going out since the other drive I used to replace it is the exact same drive and BI is working fine, so far. So I am taking it out of service and using it for a backup drive so it does not have to spin all the time.

Thank you everyone!

PS - And yes I know the drives I have been using are cheap, so I am getting a new 4tb drive from work that was never used and was a backup for a server we took out of service in December.

For your amusement:

smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-b17763] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST1000DM003-1SB102
Serial Number: Z9A2EXGL
LU WWN Device Id: 5 000c50 0911480a3
Firmware Version: CC43
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Feb 03 00:48:05 2019 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

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: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off 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: ( 105) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 081 063 006 - 148984793
3 Spin_Up_Time PO---- 099 096 000 - 0
4 Start_Stop_Count -O--CK 099 099 020 - 1573
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 076 060 045 - 43626862
9 Power_On_Hours -O--CK 094 094 000 - 5286
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 884
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
188 Command_Timeout -O--CK 100 100 000 - 0 0 5
189 High_Fly_Writes -O-RCK 099 099 000 - 1
190 Airflow_Temperature_Cel -O---K 062 058 040 - 38 (Min/Max 24/39)
193 Load_Cycle_Count -O--CK 100 100 000 - 1738
194 Temperature_Celsius -O---K 038 017 000 - 38 (0 17 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 015 001 000 - 148984793
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 3199h+58m+17.350s
241 Total_LBAs_Written ------ 100 253 000 - 22847537936
242 Total_LBAs_Read ------ 100 253 000 - 461749631
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x24 GPL R/O 512 Current Device Internal Status Data log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 4120 Device vendor specific log
0xa8 GPL,SL VS 129 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xb0 GPL VS 4800 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL,SL VS 10 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 5286 -
# 2 Short offline Completed without error 00% 5284 -

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.

SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 39 Celsius
Power Cycle Min/Max Temperature: 25/39 Celsius
Lifetime Min/Max Temperature: 17/42 Celsius
Under/Over Temperature Limit Count: 0/0

SCT Data Table command not supported

SCT Error Recovery Control command not supported

Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 884 --- Lifetime Power-On Resets
0x01 0x010 4 5286 --- Power-on Hours
0x01 0x018 6 22879260960 --- Logical Sectors Written
0x01 0x020 6 113895338 --- Number of Write Commands
0x01 0x028 6 462625664 --- Logical Sectors Read
0x01 0x030 6 4398076 --- Number of Read Commands
0x01 0x038 6 - --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 4 --- Spindle Motor Power-on Hours
0x03 0x010 4 4 --- Head Flying Hours
0x03 0x018 4 1738 --- Head Load Events
0x03 0x020 4 0 --- Number of Reallocated Logical Sectors
0x03 0x028 4 0 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 8 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 39 --- Current Temperature
0x05 0x010 1 36 --- Average Short Term Temperature
0x05 0x018 1 36 --- Average Long Term Temperature
0x05 0x020 1 42 --- Highest Temperature
0x05 0x028 1 18 --- Lowest Temperature
0x05 0x030 1 37 --- Highest Average Short Term Temperature
0x05 0x038 1 23 --- Lowest Average Short Term Temperature
0x05 0x040 1 36 --- Highest Average Long Term Temperature
0x05 0x048 1 23 --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 55 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 13 --- Specified Minimum Operating Temperature
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS

 

[daru84]

This question is long ago already but maybe it can help somebody who has the same problem:

Go into Options-->Startup-->Uncheck "Run as a Windows service"

Works for me after I tried everything including deleting the db folder.

 

[fenderman]

This question is long ago already but maybe it can help somebody who has the same problem:

Go into Options-->Startup-->Uncheck "Run as a Windows service"

That is not the problem. Even if it was, it doesnt resolve the issue for someone wanting to run as a service.

 

[daru84]

I had the same problem..that solution worked for me. And after it started to record again you surely can re-activate that service.

 

[redlancer]

Just had this problem pop up the other day. BI stopped saving new recordings and was throwing a disk not ready and other db errors. Hadn't changed anything in months. I do save to a NAS, so figured something was out of whack with permissions or something but also checked out fine.

Stumbled into this thread and got to the 'uncheck windows service' solution and also thought no way that will fix it. However, fixed it right away, Recordings worked fine as soon as it wan't running as windows service. Re-enabled as widows service and got the same disk not ready ad-to-db errors again. Possibly a windows and/or BI update broke the service option?

I did notice that when I opened the BI interface I had to put in my password for the login. I don't remember this being the case up until just today (always saved it previously), so maybe the login information isn't getting passed through the service correctly so the while the service is running, BI isn't logged in under the hood.

 

[daru84]

Hi redlancer,

I am glad I could help you with my own experience!

Just another idea from me to solve your problem to re-enable as windows service: Try to delete the videos in New/ Stored Folder and the database folder. Delete the Clip History in BI. After that restart BI and re-enable as windows service. That might work.

 

[fenderman]

Just had this problem pop up the other day. BI stopped saving new recordings and was throwing a disk not ready and other db errors. Hadn't changed anything in months. I do save to a NAS, so figured something was out of whack with permissions or something but also checked out fine.

Stumbled into this thread and got to the 'uncheck windows service' solution and also thought no way that will fix it. However, fixed it right away, Recordings worked fine as soon as it wan't running as windows service. Re-enabled as widows service and got the same disk not ready ad-to-db errors again. Possibly a windows and/or BI update broke the service option?

I did notice that when I opened the BI interface I had to put in my password for the login. I don't remember this being the case up until just today (always saved it previously), so maybe the login information isn't getting passed through the service correctly so the while the service is running, BI isn't logged in under the hood.

See the release notes for the update on instructions on how to reenable the service.