Hi,

 

i bought 2 days ago 3 x Samsung HDD 500 Go, HDD are recognized by unRAID system, the disk1 & 2 are green status but the parity disk is red status with 288 errors.

 

i tested the 'Start will bring the array on-line and start Parity-Sync' option but it don't work.

 

Please help.

Hi,

 

i bought 2 days ago 3 x Samsung HDD 500 Go, HDD are recognized by unRAID system, the disk1 & 2 are green status but the parity disk is red status with 288 errors.

 

i tested the 'Start will bring the array on-line and start Parity-Sync' option but it don't work.

 

Please help.

Best bet...

You may have a bad cable, a bad connection to the parity drive, a bad power supply, or, least likely, a bad parity drive. It has been taken off-line by the unRaid server due to the errors you have seen.

 

Stop the array (if it is not already stopped) Unassign  the parity drive on  the devices page.  Start the array.

Then... Stop  the array, reassign the parity drive, and start it again.  It should then re-calculate parity (this will take several hours with 500Gig drives)

 

If the parity drive does not come back online,  stop the array once more, power down, then check your cabling to the parity drive. After you re-seat the cables on the parity drive/controller/motherboard, power up again and re-assign the parity drive as described above.

 

Post a copy of your syslog if you still have problems.

 

Joe L.

 

Exactly right, thank you Joe.

Thanks Joe for your answer, i made your procedure and parity disk is orange (yellow ?) color, no errors. Orange color is normal ?

Is Parity-Sync running?

Yes Party-Sync running, but i copied some files and now i have some parity errors, i check my cable now.

Thanks Joe for your answer, i made your procedure and parity disk is orange (yellow ?) color, no errors. Orange color is normal ?

It should turn green once  parity calculation has completed.  You should have a progress status of the parity calc on the bottom of your screen.  It should give you an idea of how long it will take to complete the parity calculation on your drives.

for reference on parity sync, 750gb parity, 2 750gb data and one 320gb data, approximately 6 hours for full parity sync.

Thanks for answer,

 

unfortunately i always have some parity errors, i checked my cable (they're new) and it's ok.

 

I don't understand.

 

Thanks for answer,

 

unfortunately i always have some parity errors, i checked my cable (they're new) and it's ok.

 

I don't understand.

 

 

New does not mean "working".  Make sure they are short cables and (if IDE) not rounded.

 

 

Bill

Thanks for answer,

 

unfortunately i always have some parity errors, i checked my cable (they're new) and it's ok.

 

I don't understand.

 

 

New does not mean "working".  Make sure they are short cables and (if IDE) not rounded.

 

 

Bill

And, if  IDE, make sure they are 80 conductor cables, not the older style 40 conductor cables. 

80 conductor cables usually have a gray connector, a blue connector, and a black connector.

Older  40 conductor cables usually have all connectors the same color. (they have fewer wires between the connectors too)

Hi,

 

my SATA cables are short. It's too strange.

 

So i must give up unRAID.

Hi,

 

my SATA cables are short. It's too strange.

 

So i must give up unRAID.

 

You give up way too easily.  It could be the drives - please follow the advice already given and attach the syslog.

 

 

Bill

Hi,

 

my SATA cables are short. It's too strange.

 

So i must give up unRAID.

 

You give up way too easily.  It could be the drives - please follow the advice already given and attach the syslog.

 

 

Bill

I agree, you give up far too easily.

 

Think of this... whatever operating system you put into place using your current hardware will have exactly the same errors when writing to your disks.  unRaid is detecting the errors and showing you that they exist.  Ignoring the errors and loading an OS that does not report on the errors might make you feel better, but odds are good your stored data will not be reliable. Odds are very high the errors will still occur, silently corrupting your files.  You may never have an error that wipes out a precious file, but I personally would not want to play the odds.

 

Something is marginal in your array.  It could be anything... memory, the motherboard, the CPU, the clock speed, the power supply, a SATA cable, or one of your disk drives.  The only way to figure it out is to isolate each in turn.  Nobody on this forum can assist with additional advice if you do not post a copy of your syslog.

 

Joe L.