February 22, 201115 yr These are the drives I am actually running in my new unraid build. I have another seagate drive in my main build for over a year now and it is still running great. I have seen a lot of posts about updating the firmware to cc35 on these drives. Both of mine actually have cc95. tried looking around the internet...not much info on this yet. Anyone have any thoughts on cc95?
February 22, 201115 yr I hadn't seen CC95 firmware anywhere, so I'm not certain if I would try out CC35 or not.
February 24, 201115 yr Author http://lime-technology.com/forum/index.php?topic=10930.msg104361#msg104361 only concerning thing is this: otherwise the Start_Stop_Count on the CC95's was increasing by a thousand every day. They just kept spinning up and down on CC95, CC35 fixed that problem how do I check this to make sure mine is not doing the same thing
February 24, 201115 yr SMART report and examine the attribute, smartctl -A /dev/sd#, where you specify the appropriate drive.
February 24, 201115 yr Author SMART report and examine the attribute, smartctl -A /dev/sd#, where you specify the appropriate drive. at 100 right now... doesn't seem to be a problem?
February 24, 201115 yr It should not increase too, the RAW value, much over the course of an hour. Some folks were seeing increases well over 1000 an hour, meaning the head was parking at once every 4 seconds. For a comparison here's how my main drives: Seagate 2TB LP: Start_Stop_Count = 436, Power_On_Hours = 4512. 3 WD 2TB EADS: Start_Stop_count = 1342, Power_On_Hours=13925, Load_Cycle_Count=1318; Start_Stop_count = 1074, Power_On_Hours=13846, Load_Cycle_Count=1043; Start_Stop_count = 1098, Power_On_Hours=13933, Load_Cycle_Count=1076
March 1, 201115 yr Author It should not increase too, the RAW value, much over the course of an hour. Some folks were seeing increases well over 1000 an hour, meaning the head was parking at once every 4 seconds. For a comparison here's how my main drives: Seagate 2TB LP: Start_Stop_Count = 436, Power_On_Hours = 4512. 3 WD 2TB EADS: Start_Stop_count = 1342, Power_On_Hours=13925, Load_Cycle_Count=1318; Start_Stop_count = 1074, Power_On_Hours=13846, Load_Cycle_Count=1043; Start_Stop_count = 1098, Power_On_Hours=13933, Load_Cycle_Count=1076 since laast looking at this thread it is only up to like 800 for stop start count... this is normal behavior? geez 1000 in an hour would be a lot. Were you guys seeing this right away or after having the drives for awhile?
March 1, 201115 yr I never experienced any of those issues, be is large increases in start_stop_counts or load_cycle_counts but then again I forced my CC34 drives to CC35 on day one. So your drive in 4 days increased it's Start_Stop_Count by over 700. That's more than my drive has seen in 6 Months! My same drive which is serving as Parity is now at a count of 445 over 4612 hours, so it increased by 9 over the course of 100 hours. I know it's different drive makers and all, but your drive is closing in on my WD EADS drives which have been running for over 19 months. I don't know if it's a real issue for you or not, but might be worth checking out.
March 1, 201115 yr Author I never experienced any of those issues, be is large increases in start_stop_counts or load_cycle_counts but then again I forced my CC34 drives to CC35 on day one. So your drive in 4 days increased it's Start_Stop_Count by over 700. That's more than my drive has seen in 6 Months! My same drive which is serving as Parity is now at a count of 445 over 4612 hours, so it increased by 9 over the course of 100 hours. I know it's different drive makers and all, but your drive is closing in on my WD EADS drives which have been running for over 19 months. I don't know if it's a real issue for you or not, but might be worth checking out. hmm ... well I have been doing parity and just rebuilt my drive because I was changing to 4k alignment. Also I Have been adding a lot of data to it. Does that affect it? If I did decide to go to cc35 does that erase data on the drive at all?
March 1, 201115 yr I have seen reports of others flashing their drives to CC35 without losing data. It should be non-destructive. It might be worth looking around the other hard drive support forum websites to see what others have seen or experienced before acting.
March 1, 201115 yr I updated the firmware to CC35 without any data loss, though there wasn't a lot on it and I had backed it up prior to the upgrade. Also, at the time the drive was in a Win 7 machine and formatted NTFS.
March 1, 201115 yr I have two ST2000DL003 with firmware CC32 as well as one ST31500541AS with firmware CC34. None of these are showing unusual start/stop counts. s/s hrs ST2000DL003 CC32 23 / 587 ST2000DL003 CC32 20 / 336 ST31500541AS CC34 486 / 5899
March 2, 201115 yr I have two ST2000DL003 with firmware CC32 as well as one ST31500541AS with firmware CC34. None of these are showing unusual start/stop counts. s/s hrs ST2000DL003 CC32 23 / 587 ST2000DL003 CC32 20 / 336 ST31500541AS CC34 486 / 5899 It was only on the CC95 firmware that it happened.
March 2, 201115 yr I've upgraded 5 drives to CC35 from either CC32 or CC34 with no issue. I have reported in another thread though that the clicking noise during spin up and spin down seems more pronounced since I upgraded to CC35. I've since set my spindown timer to 4 hours and I don't hear any clicking during file transfers or when the drives are spinning.
March 2, 201115 yr I noticed the clicking then spinning down more after upgrading to 35 also. Only issue has been one of the eight died during initial preclear. The replacement has precleared three times with zero issues.
March 17, 201115 yr What is the cause of the clicking anyways? I'm hearing it, though its faint, but it's annoying me. I have a Seagate 2TB but the 64mb version running as a data drive in my unRAID box, running CC32: === START OF INFORMATION SECTION === Device Model: ST2000DL003-9VT166 Serial Number: 5YD20NGP Firmware Version: CC32 User Capacity: 2,000,398,934,016 bytes Thanks.
Archived
This topic is now archived and is closed to further replies.