I hope that someone can help me here.

 

UNRAID 4.7 Final.

 

I have had an UNRAID system for a year or so now and I last added a drive maybe 6-8 months ago. The system has 8 x 1.5Tb Seagate ST31500 drives and a 1.5Tb Samsung HD145U drive. Six of the drives are attached to the motherboard controller and three to a cheapo PCI 4 port controller. All has been fine for months with no errors reported.

 

I have just Swapped the cheap a cheerfull PCI 4 port controller for the SM MVS 8port. Once I got that up and running and all seemed fine I added a 2TB WD Ears drive, jumpered, but it refused to respond when I tried a pre clear, even if I tried the -z option.  So I removed the jumper, this is a new drive never formatted etc, and tried the preclear script again with the block 64 option, which started OK. It is still running, it has gone through the pre-clear read and is now 9% through the post read.

 

However I have just noticed that one of the other disks now has a red dot next to it, it is one of the 1.5Tb Seagates and it is one that is attached to the SM 8 port controller, it is also the one that I wrote data to last night whilst the pre-clear on the other drive was is progress.

 

Is the drive failing just a coincidence? What should I do?

 

I have attached a syslog and hope that you can help.

 

Thanks

 

Ridley

syslog0602.zip

Your syslog is unusable as you probably have attached only the last 3000 lines (all with same HD errors).

 

My first guess is cabling issue as IMHO the expensive and fancy "SFF8087 to 4 SATA" brand name cables are using cheap non-locking connectors on the SATA side.

 

On the other hand EBay has cheaper and if you look at the picture and check with the vendor "locking" versions.

 

If not a data cable check the power cables - you already had 9 drives and are bound to start using some splitters or MOLEX to SATA power adapters. Some of them are outright bad.

 

Check first all the cabling and post your system configuration, especially the PSU as you may have hit a ceiling here too.

 

Re the syslog

 

I followed the instructions on the wiki and that is all that was resturned, how do I get the entire syslog?

 

As to your ideas WRT the cabling I have checked everything, would you suggest I reenable the drive and do a parity check?

 

Ridley