January 5, 201412 yr I have a continuous issue with a disabled drive. I have changed the drive as well as the cables and can't see what else I can do. The preclear report and the syslog are attached - maybe someone smarter than me is able to identify what's going wrong
January 5, 201412 yr Author This what I read in another discussion: "The SMART report also lists a number of CRC errors. That is usually noise pickup on the SATA cables from adjacent power or SATA cables. 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - <font color="red">17 Do you have the cables to the drives tie-wrapped together? If so, cut the tie-wraps and get some distance between the cables" I don't see these errors in my syslog so Is that needed in general? New news to me.... Sent from my iPad using Tapatalk
January 5, 201412 yr SATA cables should never be bundled in parallel. They should look like tossed spaghetti and can be loosely tied at right or oblique angles. The drive in the pre-clear reports is not present in the syslog. The only indication that the drive is disabled comes at the end of the syslog. At what time did the disk become disabled?
January 6, 201412 yr Author Thanks for the confirmation about the cabling dgaschk. With the latest syslog update the pre cleared drive should be included as well. However the log from yesterday doesn't seem to be available; at least not around the time (12:30) when the drive became disabled. Anyhow, the data rebuild process went without any hassle, doing a parity check now. 54% are done, 5h to go any actually w/o any errors. ...just guessing...the "old" drive seems to be fine as well? I checked the pre clear report and in my opinion it's ok. Do you think the same?
Archived
This topic is now archived and is closed to further replies.