Hi,

 

I migrated my home server to unraid 6 during the christmas vacation. Let me say I was trilled with the product, but now I don't know if I will continue with this software, but before I will try the forum for help. I work in an IT company and repair computer or now a day fix the user ....

I know my way around a pc, but linux is not my speciality. Here my spec

 

Rosewill RSV-L4412 - 4U Rackmount Server Case or Chassis, 12 SATA / SAS Hot-swap Drives

Corsair CX600

ASUS Sabertooth X79

Core I7 3820

Corsair Vengence 8x 4Go 1600mhz DDR3

MegaRAID SAS 9240-8i (flashed in it mode)

12x 3to WD Red WD30EFRX

3x SSD 480 Go (One Sandisk, Two Kingston)

8gb kingston 108 flash drive

Dual Gigabyte Intel pro/1000 nic

900va cyberpower ups

 

unraid 6.1.9

 

VM & Docker disable for the moment until a fix is found for my problem

 

pluggin

Unassigned Devices

Preclear Disks

Powerdown Package (2.20)

Fix Common Problems

Dynamix System Information

Dynamix System Buttons

Dynamix SSD TRIM  - nothing configured

Dynamix Schedules  - parity check on monday

Dynamix File Integrity  - nothing configured

Dynamix Active Streams

Community Applications

 

 

The server had many spec, evolving with my problem but this is the final build and my last problem is that I have a drive that report faulty after a week or two in the best of time. See with my log.

 

- All disk as been pre-clear and tested with wd diag, most of them are brand new.

- The problem appear only on my first and last bay of my case, one onboad one on the lsi card

- The two rack 4x3 are now brand new (http://www.newegg.ca/Product/Product.aspx?Item=N82E16816132037)

- When I swap the disk the problem will appear on the new drive in the same slot of the rack

- What troubling me the most, yesterday I received my new rack to replace the one that was faulty the problem was still present on disk11 (lsi card). I done a new config because I'm out of idea and now the problem is back on my parity drive (on board)

- When I plug the disk directly to the cable no error but I haven't tested more than 2 weeks

- Cable for the onboard sata are brand new, new cable for the lsi are on the way, but now the problem is not on one of my lsi controller port so I don't think it's the cable

- Worked fine for about three weeks in total since the final build

- One of my collegue have the same box and had problem because the cable was too tight together, so I removed all the cable management

- Last week it was up and running I done 3 or 4 parity check to see it I will get an error on a disk all was fine, but in the night of sunday to monday (sheduled parity check) error was found disk11 was faulty.

- Memtest as runned for 5 days without errors

 

So I'm out of idea, out of focus on this diagnostic since it's been months having problem with it.

With the error I got tonight I will try other onboard sata cable since the 4x3 rack is new.

 

Thank you for your help.

unserver-smart-20160610-2155.zip

unserver-syslog-20160610-2136.zip

Both the smart report and the syslog indicate that your parity drive has dropped offline so no information can be found for it.    You probably need to power cycle the machine to get the SMART information.

 

One idea - have you tried an alternative power supply?    A power supply that is running near its limit (or one developing a fault) can lead to random disks dropping offline.

 

BTW:  with v6 it is best to include the diagnostics file (Tools->Diagnostics) as that provides more comprehensive information about what was happening and your system configuration.

Hi,

 

Thank you for your quick reply, I will pick up a new power supply from my work tomorrow, but my power reading on my ups tell me about an average of 135w idle and a little more than 180 on rebuild.

 

I attached the log

unserver-smart-20160610-2339.zip

unserver-diagnostics-20160610-2341.zip

Hi,

 

Following your hint about the power supply I done some modification to the wiring and removed some molex splitter to the hdd cage. I used some good quality splitter but it seem to be a good advice because I was able to rebuild the parity drive without error.

 

Now only time will tell if it was the problem since the begining. I was so blinded by the problem I got that I never looked at this side of the problem.

 

Thank you for now