I'm officially going nuts over this issue now so I figured I'd post here and see if anyone has any advice (fingers crossed).

 

Basically I've built two servers with identical parts ordered at the same time. The first server I built and loaded with 14 2TB drives works just fine. The initial parity sync went just fine and I've transferred 11TB of data to the machine already without any problems.

 

The second server which I built the same day has given me nothing but grief. The initial parity sync will kickoff just fine but it stalls between 60% and 68% every time. It doesn't matter how many drives, which order they are in, etc. It always fails and the screen looks like the attached screenshot.

 

As far as hardware I can rule out ram and the psu as I've already tried swapping out both.

 

If anyone has any advice or ideas I'd be very grateful.

 

Thanks,

Andrew

syslog.zip

These errors are in your syslog.  It might be the one disk

Dec 14 05:15:40 Security-Archive kernel: mptscsih: ioc0: attempting task abort! (sc=f752bcc0)

Dec 14 05:15:40 Security-Archive kernel: sd 1:0:1:0: [sdc] CDB: cdb[0]=0x28: 28 00 98 ff 39 f7 00 04 00 00

Dec 14 05:15:40 Security-Archive kernel: mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000)

Dec 14 05:15:40 Security-Archive kernel: mptscsih: ioc0: task abort: SUCCESS (sc=f752bcc0

 

disk = /dev/sdc

Hmm, I'll remove that disk and give it another go. Thanks for catching that!

 

Thanks,

Andrew

Well, I had high hopes but unfortunately the same thing happened this time as well. Screenshot and syslog attached.

 

Thanks,

Andrew

syslog.zip

Does anyone have any idea what could be causing this? I'm completely lost at this point.

 

Thanks,

Andrew

Does anyone have any idea what could be causing this? I'm completely lost at this point.

 

Looking at your syslog, i am surprised you can even start your parity check process.

 

(a) since you mentioned you have two sets of HW, so you might want to compare BIOS/jumper setting first, make sure both have same setting

 

(b) Your syslog shown unRAID has problems to read temperature throuhg IOCTL that is why temperature reading are all zero

 

Dec 14 06:02:44 Security-Archive emhttp: disk_temperature: ioctl (smart_enable): Invalid argument

 

 

© The fact unRAID can not probe your disk during importing already told you there are something wrong, i don't think all disks are bad at same time. you might want to start your debugging from common part such as SATA controller.

 

Dec 14 06:03:07 Security-Archive kernel: md: initializing superblock

Dec 14 06:03:07 Security-Archive kernel: md0: import: scsi_inquiry (std inquiry) error: -14

Dec 14 06:03:07 Security-Archive kernel: md0: import: scsi_inquiry (vpd: unit ser no) error: -14

Dec 14 06:03:07 Security-Archive kernel: md: import disk0: [8,16] (sdb) <no model> <no serial_no> offset: 63 size: 1953514552

Dec 14 06:03:07 Security-Archive kernel: md: disk0 new disk

 

Dec 14 06:02:12 Security-Archive kernel: Fusion MPT base driver 3.04.12

Dec 14 06:02:12 Security-Archive kernel: Copyright © 1999-2008 LSI Corporation

Dec 14 06:02:12 Security-Archive kernel: Fusion MPT SAS Host driver 3.04.12

Dec 14 06:02:12 Security-Archive kernel: mptsas 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

Dec 14 06:02:12 Security-Archive kernel: mptbase: ioc0: Initiating bringup

Dec 14 06:02:12 Security-Archive kernel: ioc0: LSISAS1068E B3: Capabilities={Initiator}

 

Dec 14 12:19:07 Security-Archive kernel: mptscsih: ioc0: attempting task abort! (sc=f77906c0)

Dec 14 12:19:07 Security-Archive kernel: sd 1:0:2:0: [sdd] CDB: cdb[0]=0x28: 28 00 99 4f ec 4f 00 04 00 00

Dec 14 12:19:07 Security-Archive kernel: mptbase: ioc0: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000)

Dec 14 12:19:07 Security-Archive kernel: mptscsih: ioc0: task abort: SUCCESS (sc=f77906c0)

Dec 14 12:19:39 Security-Archive kernel: mptscsih: ioc0: attempting task abort! (sc=f77906c0)

Dec 14 12:19:39 Security-Archive kernel: sd 1:0:2:0: [sdd] CDB: cdb[0]=0x28: 28 00 99 4f ec 4f 00 04 00

 

I'm 100% sure all of the jumper and bios settings are the same. I've compared both machines twice. The SATA controller could definitely be the problem though. I'm going to connect a couple drives directly to the MB SATA ports and see what happens.

Well, it seems to be the SATA controller. Luckily I have a spare because I ordered one too many so I'll give that a shot tomorrow.