June 18, 201214 yr I don't frequent these forums but came the other day to look into adding some more disks to an Antec 1200. I noticed the threads on wdidle and the ears drives. So I went to work disabling the parking feature on all of them. The machine booted and everything looked good. Let's call that Day 0. Day 1. Web gui will not respond. Found several commands in the forum for restarting that I tried via telnet to get it working but no dice. After a few reboots and then a complete powerdown things got back to normal. Day 3. Disk 4 reports itself as bad. I unnassign it, recheck all cabling, assign it and it starts the rebuild with 1 error. Day 5. Disk 3 has reported 93 errors sometime around 7pm last night. I know it could be a freak thing but it seems my tower is now seeing unstability and disk errors that weren't commonplace before I disabled intellipark. Should I re-enable? Should I re-enable at the lower frequency instead of totally disabling? Here are some of the errors from last night. I can post a syslog but I thought this was more of a general question. Jun 17 18:51:58 Tower kernel: end_request: I/O error, dev sdj, sector 3874079887 Jun 17 18:51:58 Tower kernel: ata9: EH complete Jun 17 18:51:58 Tower kernel: md: disk3 read error Jun 17 18:51:58 Tower kernel: handle_stripe read error: 3874079824/3, count: 1 Jun 17 18:51:58 Tower kernel: md: disk3 read error Jun 17 18:51:58 Tower kernel: handle_stripe read error: 3874079832/3, count: 1 Jun 17 18:51:58 Tower kernel: md: disk3 read error Thanks.
June 19, 201214 yr i don't know about the intellipark, but i think it would be a good idea to run a smart test on those HDDs. Did you end up adding another drive? Is it possible that may've tipped your PSU pass its limits?
June 20, 201214 yr Author I haven't run smart yet. It just seemed too coincidental that issues cropped up after disabling it so I thought I would see what other users experienced. On a side note, I ran a parity check for the hell of it last night and disk 4 failed again.
June 21, 201214 yr Really need to see the syslogs to properly characterize the disk errors. And the individual SMART reports too.
June 21, 201214 yr Author OK...will do. disk 4 is probably shot. Over 2 million on LLC count. I imagine this is because where I store pictures. When my sagetv server goes into standby it cycles through pictures on disk 4. I am thinking it displays a few pics then parks the head every 8 seconds? syslogweb.txt smart.txt
June 21, 201214 yr Do wdidle with /s300. I currently have over 30 green drives that are perfectly fine with this. I personally have had 2 3TB drives have issues after running /d on them. My 2TB drives are fine with it totally disabled, but my 3TB drives were far from it. After running it they developed very loud clicking sounds. I immediately set it to /s300 and they've been running error free for almost a year now. I'd recommend just setting all green drives to /s300. I'd also make sure you are running the latest version: http://support.wdc.com/product/download.asp?groupid=609&sid=113
June 21, 201214 yr Author I may try 300. I just set them all back to 8 last night to see if issues remain.
June 22, 201214 yr OK...will do. disk 4 is probably shot. Over 2 million on LLC count. I imagine this is because where I store pictures. When my sagetv server goes into standby it cycles through pictures on disk 4. I am thinking it displays a few pics then parks the head every 8 seconds? The syslog you attached does not have any errors at all, so not much help. Would you possibly have the June 17 syslog, from which you extracted a few lines in your first post? Apart from that really high LLC, Disk 4 looks fine, does not seem to have hurt it, yet! One comment, usable RAM appears to be 767MB. I saw a comment somewhere wondering if that number meant bad RAM. I don't think so, I believe it indicates a motherboard with 1GB of RAM with 256MB reserved for onboard video. You might check your BIOS settings, to see if you can decrease that reserved video RAM, since you only need a little for the consoles, no graphics. That would provide more system RAM, could help in the future, when you upgrade from that v4.5.6!
June 23, 201214 yr Author On first pass it doesn't look like I have the one from the 17th. I disabled and re-enabled 4 again and it completed with 754 errors according to the web gui. I don't see much in the syslog though? At this point should I upgrade to the latest 4.7? I think if I run another parity check 4 will fail again. Replace 4 rebuild then upgrade?
June 23, 201214 yr On first pass it doesn't look like I have the one from the 17th. I disabled and re-enabled 4 again and it completed with 754 errors according to the web gui. I don't see much in the syslog though? At this point should I upgrade to the latest 4.7? I think if I run another parity check 4 will fail again. Replace 4 rebuild then upgrade? If I feel a disk is failing the absolute first thing I do is replace it. Everything else can wait, a failing disk can end up being a disaster if you keep putting it off.
June 24, 201214 yr Author I was just reading in 4.7 I guess it has an extra setting for AF drives. I was just trying to avoid the jumper vs. no jumper stuff. Also I wasn't totally convinced that wdidle wasn't the issue.
Archived
This topic is now archived and is closed to further replies.