DoeBoye Posted August 9, 2011 Share Posted August 9, 2011 I basically just created a bootable DOS usb stick, put wdidle3.exe on it, removed my unraid usb stick from my server, booted up with the dos usb stick and ran "wdidle3 /d" and it did the job on all my WD drives. Thanks for the great idea about swapping USB sticks. I was all ready to pull them out one at a time and update in another box!!! FYI: I did have to move the drives one by one onto mobo sata ports, as wdidle could not see drives on the Supermicro cards... Link to comment
marlin Posted August 10, 2011 Share Posted August 10, 2011 Once, you load dos from the USB, you cannot access unraid. You do need a monitor and keyboard to do this. Maybe you can get a way without a monitor, but that's something that can be discussed later if it's absolutely necessary. Anyways, to do one drive at a time, I unplug all but one drive and used wdidle3 and kept doing it one after the other. Is it possible to telenet/putty into the unRaid box once you switch the USB sticks? Link to comment
gabbott Posted August 10, 2011 Share Posted August 10, 2011 Once, you load dos from the USB, you cannot access unraid. You do need a monitor and keyboard to do this. Maybe you can get a way without a monitor, but that's something that can be discussed later if it's absolutely necessary. Anyways, to do one drive at a time, I unplug all but one drive and used wdidle3 and kept doing it one after the other. Is it possible to telenet/putty into the unRaid box once you switch the USB sticks? No. Because if you are booting from a DOS usb stick, it won't have a SSH or telnet daemon running. Link to comment
marlin Posted August 10, 2011 Share Posted August 10, 2011 Thanks for the quick reply, will dig out the CRT and dusty old keyboard Link to comment
thejinx0r Posted August 10, 2011 Share Posted August 10, 2011 OK, I'm finally getting around to doing this. I tried unetbootin first, but for some reason it didn't work for me (I would get to an A:\ prompt instead of a C:\ prompt, and it wouldn't let me switch to C:\, so I couldn't run WDIDLE). So, just for future references: I haven't used windows in a long time, and I thought I had to "cd c:". That doesn't work. You just need to type "c:" I thought too that I couldn't switch to c:, but it took me a while to figure that one out. Link to comment
PeterB Posted August 10, 2011 Share Posted August 10, 2011 I haven't used windows in a long time, and I thought I had to "cd c:". That doesn't work. You just need to type "c:" I thought too that I couldn't switch to c:, but it took me a while to figure that one out. For those of us who are old enough to have worked with CP/M and CP/M86, and then MS-DOS, this will all be second nature! Link to comment
Rajahal Posted August 10, 2011 Author Share Posted August 10, 2011 Ah, I was trying c:\. I guess the slash isn't necessary. I think the last time I used DOS I was about 12 years old and I was running commands like c:\megarace.exe Link to comment
Heretic Posted August 25, 2011 Share Posted August 25, 2011 did any of you with those enormous high load cycles use the disk for system tasks? it is said linux logs data at a timed interval long enough for the heads to park every time before the next log. this can be one of the reason for very high numbers 2 of the disk i have I used WDidle after installing them, i think i might have forgotten it on the last one. by the way the advice was to set the timer to 5 minutes (value 300) which would fix the problem described above. here are my numbers Statistics for /dev/sdc WDC_WD20EARS 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 192 173 021 Pre-fail Always - 5358 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 498 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 - 4040 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 150 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 83 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 595 194 Temperature_Celsius 0x0022 120 108 000 Old_age Always - 30 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 Statistics for /dev/sdd WDC_WD20EARS 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 190 169 021 Pre-fail Always - 5500 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 550 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 - 4020 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 150 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 82 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 701 194 Temperature_Celsius 0x0022 123 110 000 Old_age Always - 27 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 Statistics for /dev/sdf WDC_WD20EARS 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 190 171 021 Pre-fail Always - 5475 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 236 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 097 097 000 Old_age Always - 2745 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 - 29 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1585 194 Temperature_Celsius 0x0022 125 114 000 Old_age Always - 25 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 the new drive has 1585 LCC in 2745 hours compared to the highest old drive having 701 in 4020 hours on a side note the new disk is accessed much less as the other disks so the count would be higher if used as much as the others even so my numbers seem far from shocking and for now I don't think i have to use wdidle on the last disk Link to comment
Rajahal Posted August 25, 2011 Author Share Posted August 25, 2011 I don't run any system tasks on my drives, just standard NAS usage. I do seed torrents from them, so my drives are probably accessed more often than most. Link to comment
smakovits Posted October 31, 2011 Share Posted October 31, 2011 I am getting ready to run this on all my drives since I have some high counts, but I am debating RMA-ing all old drives...reason being, when I look at mymain and all the yellow highlights of the load counts, I dont like it. Call it OCD, but I rather it not be there. Luckily I only have 8 drives at the moment, one is new so it leaves 7. I figure RMA all with the advanced RMA, I get 7 new drives, disable and preclear each and then one at a time add them to the array and rebuild the data. It would be a 2 week process as it takes 24 hours to preclear and about the same to rebuild the data. I guess I could preclear all at once, so that would shave a few days... Any thoughts or am I just crazy and being OCD about seeing the highlighted load counts. Link to comment
lionelhutz Posted October 31, 2011 Share Posted October 31, 2011 Yes, you are crazy unless your LCC is running into many, many 100's of thousands. Just wdiddle3 the drives and set the timer to a longer value as already suggested in this thread. You click the LCC link or something like that and unMENU allows you to store a custom limit for those values which will get them off the SMART report screen. Obviously, set the limit to some value higher than it currently is to allow for the LCC count to increase some more. Peter Link to comment
Rajahal Posted October 31, 2011 Author Share Posted October 31, 2011 I agree with lionelhutz. Don't RMA 7 drives just because they have tripped the LCC count in MyMain. You need to watch them over the course of a few months to see if the LCCs are increasing too rapidly, or if they are a non-issue. I found that I had to disable IDLE3 on certain of my WD green drives, but not all. I prefer to run with the original power-saving firmware with more aggressive head parking algorithms whenever possible. Link to comment
smakovits Posted November 3, 2011 Share Posted November 3, 2011 OK, I will just work to disable then... Just a note, the brand new drive I put in a week ago, 4616 LLC already... Also, what is IDLE3? Is that something else I should worry about? Thanks Link to comment
Rajahal Posted November 3, 2011 Author Share Posted November 3, 2011 IDLE3 is the firmware on the drives that tells the head to park very frequently (after just a short period of inactivity). It is the culprit for the high LCC counts. WDIDLE is the software you run to modify the firmware. For any one curious, here's the current state of my drives: Link to comment
smakovits Posted November 3, 2011 Share Posted November 3, 2011 OK, so I should just worry about disabling via WDIDLE and then modifying the count to a number that wont flag things. Then just monitor drive health for the future to make sure things continue to function. Just out of curiosity, how long does it take for WDIDLE to do its thing? Is it pretty quick? Would it also be recommended to do a reboot after each run to ensure that the disk is still functional and recognized by the OS? Link to comment
Rajahal Posted November 3, 2011 Author Share Posted November 3, 2011 WDIDLE is pretty much instantaneous. I don't think a reboot is necessary, but it won't hurt. Link to comment
Lantesh Posted November 7, 2011 Share Posted November 7, 2011 Prior to reading this thread I had no idea about Intellipark, and that this was an issue. Thankfully when I checked my LCC counts they weren't bad at all. I decided to go ahead, and run wdidle3.exe on all my drives, and turn the timer off for each one. I don't run my unRAID box 24/7, so I can live with it using a little more electricity. I'd rather know that my drives will last longer. Thanks for the heads up on this issue. I would have never known otherwise. Link to comment
lionelhutz Posted November 7, 2011 Share Posted November 7, 2011 Prior to reading this thread I had no idea about Intellipark, and that this was an issue. Thankfully when I checked my LCC counts they weren't bad at all. I decided to go ahead, and run wdidle3.exe on all my drives, and turn the timer off for each one. I don't run my unRAID box 24/7, so I can live with it using a little more electricity. I'd rather know that my drives will last longer. Thanks for the heads up on this issue. I would have never known otherwise. Why bother "fixing" it if the counts weren't bad since there's no proof that keeping the LCC's low by low I mean below a million or so) will help with drive life?? Peter Link to comment
dave_m Posted November 7, 2011 Share Posted November 7, 2011 I've used the WDIDLE3 utility on both my EARS drive as well as my one EADS drive, but I haven't disabled the idle parking completely, just changed it to the highest possible value. I think the command is WDIDLE3 /S 300 and it's slowed the increase down to a reasonable level. Link to comment
jtown Posted November 19, 2011 Share Posted November 19, 2011 Was just reading up on this thread and see that all of my older WDC drives and Samsung 203 drives show load cycle counts in the 30,000-40,000 range with power on hours in the thousands. My Hitachi, Seagate, and Samsung 204 (patched!) drives show load cycle counts of just under a thousand with a similar number of power on hours. I also have 3 EARX drives that I've just added in the past week which already have rapidly growing load cycle counts. I found it interesting that the older Samsungs have load cycle counts similar to the WDC drives. Has anyone else noticed this with the older F3 Samsungs? Is there anything that can be done about those drives? I'm not overly concerned as the drives will be nearly a decade old before they hit their max load count rating but I'm still curious. Link to comment
skank Posted July 13, 2012 Share Posted July 13, 2012 Once ive put widdle on usb drive, How should i use the command? I see different things, like setting to 300 seconds or something else, so if im right: 1) Wdidle3.exe /D Or 2) Wdidle3.exe /S 300 So which one should i do? Link to comment
skank Posted July 13, 2012 Share Posted July 13, 2012 Heres my info Parity, power on 2642. Load cycle count 5855 Disk 1, power on 2646. Load cycle. 7448 Disk 2 power on 3479. Load cycle 9216 Disk 3 power on 1791 Load cycle 9539 Link to comment
Turbobuickguy Posted July 13, 2012 Share Posted July 13, 2012 As with anything, there are different opinions on what to do. I have 2 2TB ears drives, the llc's went up 70,000 approx. in 6 months. I chose the /s 300. What drives do you have, and are the llc's going up rapidly? Link to comment
skank Posted July 13, 2012 Share Posted July 13, 2012 As with anything, there are different opinions on what to do. I have 2 2TB ears drives, the llc's went up 70,000 approx. in 6 months. I chose the /s 300. What drives do you have, and are the llc's going up rapidly? All wd20ears Llc are in post above Link to comment
skank Posted July 13, 2012 Share Posted July 13, 2012 Heres my info Parity, power on 2642. Load cycle count 5855 Disk 1, power on 2646. Load cycle. 7448 Disk 2 power on 3479. Load cycle 9216 Disk 3 power on 1791 Load cycle 9539 I guess nothing wrong? So am i right when i say, if its not broken dont fix it. And i should leave it as it is and check again in one year? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.