October 16, 201015 yr Yesterday I added a Supermicro SAS LV8 card to my system, along with a pre-cleared Samsung 1 TB drive. Installation went very smoothly, and unRAID immediately picked up the presence of the drive. I began copying data over to the new drive, and ran into a problem. unRAID detected multiple sync errors, and began a parity check. There were 332 errors, and unRAID successfully synced parity overnight. I started to copy more data this morning, and the system rebooted. Unfortunately, I hadn't captured the previous syslog from last night, but have attached this morning's. syslog.conf
October 16, 201015 yr Author Hardware-wise I'm running five drives on my motherboard's controller (Gigabyte GA-MA78GM-S2H), and one on the new Supermicro card. My power supply is a Corsair 650TX. I have 6GB of RAM in two pairs. Oh, and the system is running another parity check. No errors so far.
October 17, 201015 yr Author Since I just installed the Supermicro card, I'm going to assume for now that something in that sub-system is at fault. I bought two cables, so I'll restart the array with the second cable and see if that fixes it. After that, I guess I'll put the Samsung back on the eSATA port, to eliminate the controller card as a contender. If I reassign disk5 to the eSATA port after powering down and moving the disk, will that mess up parity, or just my user shares?
October 17, 201015 yr Author Latest syslog, just before I rebooted and replaced the SAS to SATA cable. syslog.txt
October 18, 201015 yr Did you run a Memtest on the system before trusting it. It may be a coincidence that it is now showing problems with the SM card installed. First: check in the BIOS to see that the memory timing and voltages are being set correctly. Some boards get it right and some get it wrong. Second: Remove the card, run a memtest overnight. Then install the card and run another memtest.
October 19, 201015 yr Author I ran memtest and prime95 back when I first got the components. This is stuff I'm reusing, and had been in use for over a year. I'm re-running memtest again just in case, but I strongly suspect that it's the new controller card. Reads and writes to drives on the motherboard controller work faultlessly, as they have since I built the server. But writes to the drives on the new controller cause random reboots, which in turn cause parity checks. I'm going to start a new post in the hardware section, since this doesn't really involve the unRAID software itself.
Archived
This topic is now archived and is closed to further replies.