NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Spin down seems not to be working after firmware update
Hey there!
I'm using a ReadyNAS NV+ and use it mainly for simple dumb storage, torrenting, and backups, nothing real complicated. For this reason, power consumption and noise pollution is important to me: the NAS doesnt need to be on constantly and spinning down is preferred. I want to leave the machine on for various reasons, but I very much appreciate the option for spin-down.
I recently changed a few things. First, I inserted two extra Seagate disks (in addition to two smaller WDCs) and second, I upgraded to RAIDiator 4.1.8. For some reason, this seems to have disturbed the spin-down option. The NAS is now constantly humming at full power/sound, and doesnt spin down even after prolonged periods. The good news is that Time Machine is now working in proper order after giving me a LOT of trouble previously. I have no way of telling of whether that is related.
Anyway, I'm hoping that somebody can help me on this. I'm no techie (judging by the level I've seen portrayed on this forum anyway 8) ), so I'm hoping that this problem might be solved with a few tweaked settings here and there. Thanks!!
I'm using a ReadyNAS NV+ and use it mainly for simple dumb storage, torrenting, and backups, nothing real complicated. For this reason, power consumption and noise pollution is important to me: the NAS doesnt need to be on constantly and spinning down is preferred. I want to leave the machine on for various reasons, but I very much appreciate the option for spin-down.
I recently changed a few things. First, I inserted two extra Seagate disks (in addition to two smaller WDCs) and second, I upgraded to RAIDiator 4.1.8. For some reason, this seems to have disturbed the spin-down option. The NAS is now constantly humming at full power/sound, and doesnt spin down even after prolonged periods. The good news is that Time Machine is now working in proper order after giving me a LOT of trouble previously. I have no way of telling of whether that is related.
Anyway, I'm hoping that somebody can help me on this. I'm no techie (judging by the level I've seen portrayed on this forum anyway 8) ), so I'm hoping that this problem might be solved with a few tweaked settings here and there. Thanks!!
10 Replies
Replies have been turned off for this discussion
- Most likely one or more of your drives doesn't like noflushd which is the daemon (process) responsible for spindown.
If you go to Frontview's Logs and click "Download all logs" then extract the contents of disk_smart.log and post-back here, maybe someone can tell if your drive type is unsuitable for use with spindown. - I resently upgrade my NV+ to 4.1.8 too and I can confirm that the power option for spinning down the disks is not working anymore.
I also have a problem with NV+ creating a new database and scanning the media folder, every freaking time I turn on the NV+.
I'm considering creating a new support ticket for this, but like always, Netgear support only wants to do a factory restore :(
Anybody familliar with this problem? - Thanks maxblack for the tip. It seems unlikely to me that they wouldnt be compatible, since both drive types advertise being power and sound efficient.
I've scanned the log, but don't really see anything I think should be relevant here. What should I be looking for exactly? Thanks for the help so far!
Heres the log:
***** smartctl output for hdc *****
smartctl version 5.36 [sparc64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: WDC WD5000AAKX-001CA0
Serial Number: WD-WCAYUH527677
Firmware Version: 15.01H15
User Capacity: 500,107,862,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Nov 21 22:16:27 2011 CET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: (8880) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 90) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 144 142 021 Pre-fail Always - 3800
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 619
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 3811
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 608
194 Temperature_Celsius 0x0022 115 102 000 Old_age Always - 28
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 18 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 18 occurred at disk power-on lifetime: 9 hours (0 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:34.339 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:34.181 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:34.024 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.868 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.710 SMART WRITE LOG
Error 17 occurred at disk power-on lifetime: 9 hours (0 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:34.181 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:34.024 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.868 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.710 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.552 SMART WRITE LOG
Error 16 occurred at disk power-on lifetime: 9 hours (0 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:34.024 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.868 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.710 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.552 SMART WRITE LOG
ec 00 01 01 00 00 a0 00 10:02:33.372 IDENTIFY DEVICE
Error 15 occurred at disk power-on lifetime: 9 hours (0 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:33.868 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.710 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.552 SMART WRITE LOG
ec 00 01 01 00 00 a0 00 10:02:33.372 IDENTIFY DEVICE
Error 14 occurred at disk power-on lifetime: 9 hours (0 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:33.710 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:33.552 SMART WRITE LOG
ec 00 01 01 00 00 a0 00 10:02:33.372 IDENTIFY DEVICE
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.
***** smartctl output for hde *****
smartctl version 5.36 [sparc64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: WDC WD5000AAKX-001CA0
Serial Number: WD-WCAYUH655485
Firmware Version: 15.01H15
User Capacity: 500,107,862,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Nov 21 22:16:28 2011 CET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: (9000) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 91) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 142 140 021 Pre-fail Always - 3875
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 757
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 3812
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 746
194 Temperature_Celsius 0x0022 111 101 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 18 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 18 occurred at disk power-on lifetime: 10 hours (0 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:36.158 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:36.000 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.844 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.687 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.529 SMART WRITE LOG
Error 17 occurred at disk power-on lifetime: 10 hours (0 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:36.000 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.844 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.687 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.529 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.371 SMART WRITE LOG
Error 16 occurred at disk power-on lifetime: 10 hours (0 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:35.844 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.687 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.529 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.371 SMART WRITE LOG
ec 00 01 01 00 00 a0 00 10:02:35.191 IDENTIFY DEVICE
Error 15 occurred at disk power-on lifetime: 10 hours (0 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:35.687 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.529 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.371 SMART WRITE LOG
ec 00 01 01 00 00 a0 00 10:02:35.191 IDENTIFY DEVICE
Error 14 occurred at disk power-on lifetime: 10 hours (0 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 e0 4f c2 40 00 10:02:35.529 SMART WRITE LOG
b0 d6 01 e0 4f c2 40 00 10:02:35.371 SMART WRITE LOG
ec 00 01 01 00 00 a0 00 10:02:35.191 IDENTIFY DEVICE
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.
***** smartctl output for hdg *****
smartctl version 5.36 [sparc64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST2000DL003-9VT166
Serial Number: 5YD5SFF3
Firmware Version: CC3C
User Capacity: 2,000,398,934,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Not recognized. Minor revision code: 0x29
Local Time is: Mon Nov 21 22:16:28 2011 CET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 612) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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.
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 117 100 006 Pre-fail Always - 161607680
3 Spin_Up_Time 0x0003 091 090 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 39
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1069005
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 391
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 8
183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 42950328330
189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0
190 Unknown_Attribute 0x0022 070 067 045 Old_age Always - 521469982
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 7
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 39
194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (Lifetime Min/Max 0/21)
195 Hardware_ECC_Recovered 0x001a 021 020 000 Old_age Always - 161607680
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 - 188845417038114
241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 172611295
242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1012428249
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.
***** smartctl output for hdi *****
smartctl version 5.36 [sparc64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST2000DL003-9VT166
Serial Number: 5YD5RQVP
Firmware Version: CC3C
User Capacity: 2,000,398,934,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Not recognized. Minor revision code: 0x29
Local Time is: Mon Nov 21 22:16:29 2011 CET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 612) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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.
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 116 100 006 Pre-fail Always - 115519912
3 Spin_Up_Time 0x0003 091 090 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 39
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 641096
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 374
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 8
183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 25770196998
189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0
190 Unknown_Attribute 0x0022 072 070 045 Old_age Always - 487915548
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 7
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 39
194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (Lifetime Min/Max 0/21)
195 Hardware_ECC_Recovered 0x001a 020 017 000 Old_age Always - 115519912
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 - 278146377056549
241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 20777326
242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 600779155
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. - Well the reason I suggested the SMART log was simply because it has the drive types in there--maybe someone here has knowledge about compatibility (I do not).
The other log to look at would be the daemon.log, to see if there are even any ATTEMPTS to spin-down the disks e.g.
Nov 7 23:33:57 ReadyNAS noflushd[9653]: Spinning down disks.
Nov 7 23:34:00 ReadyNAS noflushd[9653]: Disks spinning up after 0 minutes.
Nov 7 23:54:26 ReadyNAS noflushd[9653]: Spinning down disks.
Nov 7 23:54:40 ReadyNAS noflushd[9653]: Disks spinning up after 0 minutes.
Nov 8 00:14:41 ReadyNAS noflushd[9653]: Spinning down disks.
Nov 8 00:19:10 ReadyNAS noflushd[9653]: Disks spinning up after 4 minutes.
Nov 8 00:39:23 ReadyNAS noflushd[9653]: Spinning down disks.
Nov 8 04:00:11 ReadyNAS noflushd[9653]: Disks spinning up after 200 minutes.
Do you see any such activity in yours? 4.1.8 *sorta* worked for me, i.e. spin-downs were not a problem (spin-UPS are lotsa problems). I might have been inclined to suggest you downgrade firmware to 4.1.7, but you said Time Machine works now where before it didn't. Were you running 4.1.7 before? - Interesting! The last entry matching noflush were succesful spindowns on Oct 26. After that, no such entries appear. Am I correct in assuming this means no spin-down attempt has been made?
I can also see some type of connect being constantly renewed, see my code below. Could this be what prevents the spin-down?
Nov 21 04:00:05 DinjensNAS ntpdate[2276]: no server suitable for synchronization found
Nov 21 04:51:48 DinjensNAS udhcpc[1299]: Sending renew...
Nov 21 04:51:48 DinjensNAS udhcpc[1299]: Lease of 192.168.1.36 obtained, lease time 28800
Nov 21 06:25:22 DinjensNAS ntpdate[2929]: no server suitable for synchronization found
Nov 21 08:00:05 DinjensNAS ntpdate[3083]: no server suitable for synchronization found
Nov 21 08:51:49 DinjensNAS udhcpc[1299]: Sending renew...
Nov 21 08:51:49 DinjensNAS udhcpc[1299]: Lease of 192.168.1.36 obtained, lease time 28800
Nov 21 12:00:05 DinjensNAS ntpdate[3468]: no server suitable for synchronization found
Nov 21 12:51:49 DinjensNAS udhcpc[1299]: Sending renew...
Nov 21 12:51:49 DinjensNAS udhcpc[1299]: Lease of 192.168.1.36 obtained, lease time 28800
Nov 21 16:00:06 DinjensNAS ntpdate[3859]: no server suitable for synchronization found
Nov 21 16:51:50 DinjensNAS udhcpc[1299]: Sending renew... - Btw, yes I was running 4.1.7 before, and a working Time Machine definitely has more priority over spin-downs! :-) Besides, I'm still in the phase where I'm looking to have cake and eat it too 8-)
Correct, that would tell me that you did something on 10/26 that stopped noflushd from running. Have you done any reboots since then? If not, by all means do a System reboot. Oh, I'm running 4.1.4 atm so forgot something obvious: look in your processes.log to see if noflushd is running. Its command should look like e.g. "noflushd -v -n 15" for 15 minutes for example. Even if it is there in your logs, I would try a reboot.sdinjens wrote: The last entry matching noflush were succesful spindowns on Oct 26. After that, no such entries appear. Am I correct in assuming this means no spin-down attempt has been made?
It seems you are using your NAS as a DHCP server, and gizmo .36 wants to renew its lease every 4 hours (why I dunno, since 28800 is 8 hrs afaik?) but you certainly have your spin-down set for less than 240 minutes, yes? I don't use DHCP but doubt it requires a Read operation on your HDDs which will cause a spin-up.
Also, I notice you've not put a proper time server into the ReadyNAS clock setting; it's not affecting spindown but you should do this right anyway (unless your NAS is not connected to the 'net).- Thanks Max.
Processes.log didnt indicate any noflushd process running, and a reboot seemed to power it up again. Also thanks for the NTP tip. I'll update tomorrow if the problems seem to have gone away.
In the mean time, where do you get all this knowledge from? I'd love to get a bit deeper understanding of my ReadyNAS but have no idea where to start. Any tips appreciated.
Thanks!
In my case I had a couple problems that I wanted to solve; one was that my drives would spin-down, but then they would spin-up immediately ("after 0 minutes", not good for the drives) and at other times I didn't want (0200, 0400, 0625) and so I tried to figure-out what was responsible. I finally abandoned noflushd in favor of Power Timer, and modified a cron job or two to fit my new power-on window (in my case I only use the NV+ to backup my few PCs to once per day, and also once each month). I also learned a lot trying to get a USB drive formatted as EXT2 and then working the way I wanted it.sdinjens wrote: ...where do you get all this knowledge from? I'd love to get a bit deeper understanding of my ReadyNAS but have no idea where to start.
The above required implementing the SSH patch and using puTTY to get bash on the NV+ Debian-based Linux. I'm no Linux whiz, but at least I was exposed to it before, thus knowing just enough to be dangerous within the NV+ although the only real mods I've done were to the cron jobs.
Ultimately IMO the best (maybe the only?) way to learn the ReadyNAS is to solve some problem you have with it, one that is meaningful to you. :)- Thanks, a simple reboot has indeed worked! Didnt think to do one since it did one automatically at firmware upgrade, but there you go.
Thanks for the tips - I've started to dive deeper into why Transmission isnt working on my NAS, seems like a good excuse as any to learn more about it :-P
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
