Hi everyone

sorry my first post is about a problem but i just need someones advice before i start messing and make things worst, i have read the system log and to me is dosn`t look very good but most of it is foreign to me anyway.

i just need to know what has happened and what i should do next, the drive is fairly new about 3 months old and had minimum use since this week when i have  put lots of data on

 

thanks for your time

Craig

 

Edit: also i have stopped the array and disk is showing no device , not installed

syslog.zip

Check sata and power connections to drive

thanks for your help i have just shutdown checked sata and power all seemed fine, i booted back up and disk is identified and back in the array but the red dot is still there, does that mean theres still a problem?

thanks Craig

Edit: the data that was sent was 180gb containing 800 files could that cause errors?

Edit 2: sorry would pressing Clear Statistics clear red dot?

Post a SMART report. See here: http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F

Hi

Here it is thanks for your help

everything is running fine can read data on drive just red dot is still there

smart.txt

This is just the smart report for one drive and from the syslog it doesn't appear to be the problem drive.

Post smart reports of all drives (zipped into one file) and maybe a screenshot.

hi i think this is what you want, what do you need a screen shot of?

 

Edit: sde is drive with red ball

smart.zip

A screenshot of unRAID main showing the red ball. Just want to make sure I understand the current state of your array.

hi thanks

Here it is, i was just reading the trouble shooting section posted earlier and it mentions sata cables being tie wrapped, could that really cause an issue because  all 5 satas are tied together.

 

chrome_2013-12-30_19-59-05-29.zip

Has anybody noticed what might be the problem?

everything seems to be working ok i can see all the data i sent before the red ball i  have not tried writing anything to the server yet ,

im just wondering if the red ball will go when the problem is fixed or if  i have to do something to remove it?

http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F

 

http://lime-technology.com/wiki/index.php/Troubleshooting#Re-enable_the_drive

Im just reading through that to most people here it might seem basic but it takes me a few reads for it to make sense

so before i go through the re enable  of the drive do my syslog for that drive look ok?

this part is the only part that has numbers next to it that should be at zero

UDMA_CRC_Error_Count 3

 

could that be caused by cross talk?

 

sorry for simple questions and i appreciate you helping me

Maybe. If the cables looks very neat then then that is likely the issue. Ideally, each SATA cable is exactly the correct length with no slack. The shortest distance between 2 points is a straight line. SATA cables may be loosely tied at right or oblique angles. Under no circumstances should they be bundled in parallel. They are thin and routing each individually should not effect airflow. It should look like tossed spaghetti. Who built the server?

I built the server last year it is a large case with 4 hdd per 5.25 bay

it was built with all new parts and drives, i have all 5 sata drives tied together for neatness i never even thought of cross talk and it the same for my main rig

looks like its time to mess up my sata cables

 

Edit: how it is at the min

photo.zip

Looks bad.

Right last night i re enabled the drive with the red ball and it went back green

then i did a parity check and it went back red should i not of parity checked?

Right last night i re enabled the drive with the red ball and it went back green

then i did a parity check and it went back red should i not of parity checked?

It just indicates that writes to that drive are still failing.  Did you look in the syslog yet? Are there still CRC errors?  Did you cut the tie-wraps and get some space between those SATA cables yet?

 

If you did not correct the possible causes of the CRC errors, why did you suspect they would go away on their own?

 

Joe L.

Hi Joe its going through a data re-build at the minute i have cut cable ties and given as much space  but it went red as soon as parity started, i have swapped the sata cable and connected to another sata port on the  motherboard to  see if that helps,

should i do the parity check once the data has rebuild then syslog if theres a problem, or syslog before parity check?

thankyou for your help

Hi Joe its going through a data re-build at the minute i have cut cable ties and given as much space  but it went red as soon as parity started, i have swapped the sata cable and connected to another sata port on the  motherboard to  see if that helps,

should i do the parity check once the data has rebuild then syslog if theres a problem, or syslog before parity check?

thankyou for your help

syslog first.