ST3500418AS - Hoping to solve some errors
March 20th, 2012, 15:22
Background:
This has been plagueing me for a year or so, but it hasn't really bothered me enough to a point where I take control and fix the issue (bad, I know). But I've decided I finally get this solved once and for all. I'm running 4 500GB seagate drives in a Raid 0 array. On boot they show up on my raid screen as:
Error Occurred
Available
Available
Available
(I've tried rotating sata cables around but that doesnt change anything, I've also tried chkdsk, and some of the self tests including the one in seagate tools, but no luck)
It's been like that for ages, here's the SMART results. A lot of the values seem over so I'm wondering if there is any one particular area I should start with. I'd prefer not doing an OS format (was thinking low level) reinstall, but I am open to doing that if needed.
Additional random information:
I'm only mentioning this part because it's humorous. This all started happening when a bag of oranges fell on top of my raid stack and caused one of the sata cables to spark. I feel like it's probably physical damage of some sort from that event but hoping to get some input anyway.
Cheers, let me know if you have any questions for me.
This has been plagueing me for a year or so, but it hasn't really bothered me enough to a point where I take control and fix the issue (bad, I know). But I've decided I finally get this solved once and for all. I'm running 4 500GB seagate drives in a Raid 0 array. On boot they show up on my raid screen as:
Error Occurred
Available
Available
Available
(I've tried rotating sata cables around but that doesnt change anything, I've also tried chkdsk, and some of the self tests including the one in seagate tools, but no luck)
It's been like that for ages, here's the SMART results. A lot of the values seem over so I'm wondering if there is any one particular area I should start with. I'd prefer not doing an OS format (was thinking low level) reinstall, but I am open to doing that if needed.
Additional random information:
I'm only mentioning this part because it's humorous. This all started happening when a bag of oranges fell on top of my raid stack and caused one of the sata cables to spark. I feel like it's probably physical damage of some sort from that event but hoping to get some input anyway.
Cheers, let me know if you have any questions for me.
Re: ST3500418AS - Hoping to solve some errors
March 21st, 2012, 1:40
According to http://en.wikipedia.org/wiki/S.M.A.R.T., attribute 183 is a SATA Downshift Error Count, at least in Western Digital and Samsung drives. The fact that this attribute has fallen below the threshold in the first drive suggests that it may be having a problem with the SATA data interface (orange juice on the connector pins? 
).
You might like to rerun the SMART check using HDDScan. Its author is associated with Seagate in a technical capacity, so one would expect that the actual function of attribute #183 would be reported differently (rather than "vendor specific").
).You might like to rerun the SMART check using HDDScan. Its author is associated with Seagate in a technical capacity, so one would expect that the actual function of attribute #183 would be reported differently (rather than "vendor specific").
Re: ST3500418AS - Hoping to solve some errors
March 21st, 2012, 14:11
Thanks for the reply. I start off with version 3.1 which didn't detect anything. Version 3.3 (the latest) shows these results:
I'm not able to select the SMART Offline Tests (all the possibilities are greyed out). Any other possible tools to try? I'll take a look tonight when I power down my machine to see if the connecter on the one drive that showed the error looks damaged in anyway.
I'm not able to select the SMART Offline Tests (all the possibilities are greyed out). Any other possible tools to try? I'll take a look tonight when I power down my machine to see if the connecter on the one drive that showed the error looks damaged in anyway.
Re: ST3500418AS - Hoping to solve some errors
March 24th, 2012, 20:59
Sorry, your software tools won't be able to access a drive's SMART data when it is behind a RAID controller.
However, smartmontools may be able to do it, but I don't know if they will report the name of the attribute any differently.
Anyway, it appears that ver 3.1 of HDDScan reports it as "unknown attribute":
http://www.techsupportforum.com/forums/ ... 70124.html
In version 3.3 it is reported as "SATA Downshift Error Count":
http://www.techsupportforum.com/forums/ ... 1292432277
However, smartmontools may be able to do it, but I don't know if they will report the name of the attribute any differently.
Anyway, it appears that ver 3.1 of HDDScan reports it as "unknown attribute":
http://www.techsupportforum.com/forums/ ... 70124.html
In version 3.3 it is reported as "SATA Downshift Error Count":
http://www.techsupportforum.com/forums/ ... 1292432277
Powered by phpBB © phpBB Group.