Jump to content

3 Orange Dots - Help


Recommended Posts

Posted

Looking for some assistance.  I've got a system that I had two orange dots yesterday (one of them is the parity) and while trying to resolve I've now got 3.  Running Version 4.4.2.

 

I was going to run smartctl but I'm missing a library.  Forum searches left me in some kind of loop and wondering what and where I need to download the file in question.

 

screenshot_unraid.jpg

 

Any help would be appreciated.

 

I've already tried reseating all the hardware, replacing sata cables, replacing the sata drive bays, replacing the sata card.  Only thing left is to replace the power supply and motherboard.  Things seemed to go down hill after installing the 2 TB WD drives for me a while back.

syslog_120511.txt

Posted

Please post a telnet session showing the output of smartctl.

 

Would love to; however, I'm unable to run it due to this error:  "error while loading shared libraries: libstdc++.so.6"

 

The wiki states:

If you get an error like "error while loading shared libraries: libstdc++.so.6", then you are using a version (such as v4.4.2) that is missing a required library. Please see this post.

 

Which lead me to this post:

http://lime-technology.com/forum/index.php?topic=2817.msg23548#msg23548

 

Which references:

2nd Edit: I noticed that the 4.4final and 4.5beta releases of unRAID do not have a working "smartctl" command.  To get it working you must install a missing library file it uses. If you do not, this script will still clear the drive, but the feature where it compares SMART reports from before and after the clearing process will not work.

See this post for more details: http://lime-technology.com/forum/index.php?topic=2817.msg23548#msg23548

 

 

Which just references itself.  So I'm stuck at trying to figure out what I need to download or install to run smartctl.  Any help is certainly appreciated.

 

Posted

Backup the config directory on the flash. Prepare the flash as a new install and the restore the config directory except for the go file if yours is edited.

Posted

So I tried to run reiserfsck --check on Disk6 and Disk7 [reiserfsck --check /dev/md6 & reiserfsck --check /dev/md7]and they both reported the following:

bread: Cannot read the block (2): (Input / Output error)

 

Any thoughts about where to go from here?

Posted

I performed the following on both Data Disks:

reiserfsck --check /dev/sdg1

 

No Corruptions Found (Not sure if any other data is critical to report here)

 

-------------

reiserfsck --check /dev/sdf1

 

No Corruptions Found

 

Seems a bit odd that all the problems are with the newer drives and the old ones are thriving.

 

 

Posted

I should also note that the two orange dotted data drives are connected via an expansion card ADPE4S (While the parity drive is not).  Could that be the source of my problems?  I have replaced it already with a new one but that didn't solve the problem.

 

The mother board is a JETWAY JNC92-330-LF ATOM330.  I also have a Koutech IO-PSA420 SATA II Raid Card in the system.

 

I'm open to any and all suggestions.  My 4 year old daughter wants to watch movies again. :)

Posted

Thanks for the response.

 

How do I find out if the card is dead?

 

The drives and temp are showing up so I'm assuming it is getting something from the drives.

 

I don't have any spare Sata ports to move the drives to.  I'm hesitant to switch the drives to the working drives sata port for fear of doing more damage.

Posted

Do you have a spare computer and a spare hard drive? Swap the card over and test with another hard drive. Write zeros on the test drive to see if there's an issue with the controller.

 

Also, when the array is stopped, you should be able to mount and check data integrity on the 'failed' disks.

Posted

I don't believe I have a motherboard that will accept that card without purchasing one. And I think if I have to purchase another motherboard, I may go with one that has 6 sata ports so there's one less moving part in the equation.

 

How do I check data integrity on the 'failed' disks?

 

Also, can anyone take a look at the log reports I've posted to verify I'm not missing anything?  I'm no expert at deciphering the code. :)

Posted

All three SMART reports are for the same drive:

Model Family:     Western Digital Caviar Blue Serial ATA family
Device Model:     WDC WD3200AAKS-00L9A0
Serial Number:    WD-WMAV29626551

Posted

Backup the config directory on the flash. Prepare the flash as a new install and the restore the config directory except for the go file if yours is edited.

 

Backup the config directory on the flash. Prepare the flash as a new install and the restore the config directory except for the go file if yours is edited.

 

Ok, when I updated to 4.7 and followed the instructions above, 4.7 reports those two drives as missing.  This may be why the smart reports didn't run properly?

 

Does this provide any clues?

 

screenshot-2011_12_11_22_43_52.jpg.c921b30642ae5f7200db24ceedcce448.jpg

Posted

Ok.  I bought a new motherboard to verify it wasn't the PSA420 giving me grief.

 

Unfortunately, after reassigning drives, I still have 3 Orange Dots.

 

Anxious to resolve this and tired of spending money on unnecessary replacement parts...so if anyone could guide me in a direction it would be greatly appreciated.

 

Is there a direct email I can send this to rather than through the forum?

Posted

Does unraid 4.7 have initconfig?

 

That could be the best way to go here. If you've verified the drives are fine, and hardware is ok, could have been a splutter somewhere along the line. Initiating config will remove the warning on the drive, and you'll just need to rebuild parity again.

 

Bit of a risk, but with 3 drives shown to be on the fritz you've got nothing to loose. Presume you have backups?

 

 

Posted

Is there detailed documentation on what the mysterious orange dots mean and how to trouble shoot them?  I haven't been able to find any helpful information.

 

I still think a smart report on the drives would be good but have been unable to do them because I'm running 4.42.  

Posted

Does unraid 4.7 have initconfig?

 

That could be the best way to go here. If you've verified the drives are fine, and hardware is ok, could have been a splutter somewhere along the line. Initiating config will remove the warning on the drive, and you'll just need to rebuild parity again.

 

Bit of a risk, but with 3 drives shown to be on the fritz you've got nothing to loose. Presume you have backups?

 

 

 

Not sure about the initconfig. 

I'm actually not sure if the drives are fine.  I thought I had performed smart reports on the data drives, but apparently the reports are all from the same cache drive as another member pointed out.  Probably due to the issue of going from 4.42 to 4.7 in order to do the smart report.

 

The unraid is my main data.  I don't have any backups of the data.  I'm ok with losing the last two drives and parity if that's worst case and my only option.  In your recommendation above, is there a chance I'll lose all the drives, or just the orange drives in question?

Posted

if you initconfig and reassign the good drives you will only loose what is on the 2 orange dot data disks.

 

 

can we get a syslog from this latest boot please??

 

 

From a quick glance it looks like there may be no FS recognized on the disk anymore.  There is a thread here talking about something similar, though I will need to search for it later.

Posted

if you initconfig and reassign the good drives you will only loose what is on the 2 orange dot data disks.

 

 

can we get a syslog from this latest boot please??

 

 

From a quick glance it looks like there may be no FS recognized on the disk anymore.  There is a thread here talking about something similar, though I will need to search for it later.

 

You bet.

 

I've updated to 4.7 - the same three drives are orange although their SDx assignments are slightly different on the newer ASUS motherboard.  sdd and sdc are now the orange data drives.

 

I was now able to perform a smart test.  I've attached the logs and the syslog.  Hopefully it will lead to somewhere.  Thanks for the help.

smart_asus_sdc_121511.txt

smart_asus_sdd_121511.txt

syslog_asus_121511.txt

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...