New user here.  I just built a system based on the ASRock E3C226D2I motherboard.  It has 8 GB ECC ram and three 4TB Seagate NAS drives connected to the onboard SATA 3 connectors.

 

Before loading unRAID I ran 3 cycles of memtest and it reported no errors.  I am running unRAID 5.0.5 + Dynamix.  Preclear on all three drives has been running for about 18 hours, it is in the "Post-Read" phase. 

 

However, syslog is full of these errors:

 

Jan 23 17:24:09 Tower emhttp: Device inventory:

Jan 23 17:24:09 Tower emhttp: ST4000VN000-1H4168_Z300T01R (sdb) 3907018584

Jan 23 17:24:09 Tower emhttp: ST4000VN000-1H4168_Z300T009 (sdc) 3907018584

Jan 23 17:24:09 Tower emhttp: ST4000VN000-1H4168_Z300T071 (sdd) 3907018584

Jan 23 17:24:09 Tower emhttp: shcmd (13709): /usr/local/sbin/emhttp_event driver_loaded

Jan 23 17:24:09 Tower emhttp_event: driver_loaded

Jan 23 17:24:09 Tower kernel: md: unRAID driver removed

Jan 23 17:24:09 Tower kernel: md: unRAID driver 2.2.0 installed

Jan 23 17:24:09 Tower kernel: read_file: error 2 opening /boot/config/super.dat

Jan 23 17:24:09 Tower kernel: md: could not read superblock from /boot/config/super.dat

Jan 23 17:24:09 Tower kernel: md: initializing superblock

Jan 23 17:24:09 Tower kernel: mdcmd (1): import 0 0,0

Jan 23 17:24:09 Tower kernel: mdcmd (2): import 1 0,0

Jan 23 17:24:09 Tower kernel: mdcmd (3): import 2 0,0

Jan 23 17:24:09 Tower emhttp: shcmd (13710): rmmod md-mod |& logger

Jan 23 17:24:09 Tower emhttp: shcmd (13711): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger

Jan 23 17:24:09 Tower emhttp: shcmd (13712): udevadm settle

Jan 23 17:24:09 Tower kernel: md: unRAID driver removed

Jan 23 17:24:09 Tower kernel: md: unRAID driver 2.2.0 installed

Jan 23 17:24:09 Tower kernel: read_file: error 2 opening /boot/config/super.dat

Jan 23 17:24:09 Tower kernel: md: could not read superblock from /boot/config/super.dat

Jan 23 17:24:09 Tower kernel: md: initializing superblock

 

The attached zip has the smart* files from preclear and the full syslog a partial syslog, the file was too big to upload.

 

The CPU is at 35 deg and the drives are running about 30, so heat shouldn't be an issue.

 

What should I do?

Archive.zip

There are no errors shown here that aren't expected at this point. The super.dat errors are there because you haven't defined an array yet, and every time the web interface is accessed, it reloads the unraid driver so it can detect hot swapped drives.

 

In short, nothing wrong, nothing to see here, move along. 

 

In the future, if you need to attach a syslog, zip it up and attach it. Even REALLY huge syslogs zip into fairly tiny packages, because of all the repeated text.

 

Also, I know dynamix is pretty and all, but I really recommend getting the basic array functions all working before making changes and putting addons into the equation. Dynamix is not authored or supported by Lime Technology, so if you have any issues, chances are the first troubleshooting step is going to be "remove all addons and try again".

Thank you!  I closed the browser an hour ago and haven't had any more errors.  I really appreciate the help, I was getting worried

 

I did try to upload the whole syslog.1 file, but it was 284k zipped and the forum wouldn't take it.

 

I really recommend getting the basic array functions all working before making changes and putting addons into the equation.

 

I was trying to follow the directions here:

  http://lime-technology.com/wiki/index.php/Configuration_Tutorial

except I substituted Dynamix for unMENU.  That didn't help a lot though, since Dynamix doesn't have "screen" I ended up using the console to run preclear on all three drives at once.

 

Thanks again!