antron12345 Posted December 22, 2014 Share Posted December 22, 2014 I had a perfect running system using an asrock motherboard amd cpu with 2 gig memory. I wanted to get something faster and ready fro V6 so I purchased an asrock 990fx extreme 9 AMD 8 core CPU fx8350 and 16 gig memory I already had the controller -SUPERMICRO AOC-SASLP-MV8 PCI-Express x4 I didn't change anything on my boot usb drive and when I tried to start the array the system just hangs (freezes) and I cannot do anything put hit the power button. I removed all the plugins and the system does the same. I install V6 on the USB drive and I get the same results when I try to start the array. Please any help will be great the array is down and im going crazy. Thank you Link to comment
excaluber Posted December 22, 2014 Share Posted December 22, 2014 did you make sure each drive was assigned in the same slot on the new OS? Also did you remember to put your key file in the config folder of the new OS? I had my key file in the wrong spot on the flash drive and it wouldn't let me start the array either. Link to comment
antron12345 Posted December 22, 2014 Author Share Posted December 22, 2014 Thanks for the reply Yes the key file is in the config folder (not on the root) The drives are in the right slots but I did notice that the sd(x) are different. The array did start a few time and was working fine then it started freezing up and hanging. Link to comment
RobJ Posted December 22, 2014 Share Posted December 22, 2014 Please see the first 3 posts of this thread. It would be nice to have a baseline syslog where everything appears to be working (even if only a small part of your array is installed), and a syslog where errors or undesirable behavior is occurring. It's always best when building a new system to test it fully before adding all your drives and controllers. I assume you have tested (such as long memory tests) that the system worked fine before the UnRAID hardware was added. If not, you may need to add and remove components, and test until you isolate what component appears to be failing. I did notice that the sd(x) are different. That is normal, expected. Link to comment
antron12345 Posted December 22, 2014 Author Share Posted December 22, 2014 I attached the syslog after a reboot. The array is not started. I have also attached the system specs from the info button on the web page Thanks you syslog_12122014.txt sysem_specs.txt Link to comment
eschultz Posted December 22, 2014 Share Posted December 22, 2014 I attached the syslog after a reboot. The array is not started. I have also attached the system specs from the info button on the web page Thanks you Move these two devices that are plugged in to your motherboard to different sata connections: ST3000DM001-1CH166 Z1F47J81 ST3000DM001-1CH166 Z1F47J7N There seems to be a driver issue with those two sata connections (maybe something's up with the ASMedia ASM1061 chip powering them) and unRAID is using a PATA driver instead of SATA. Link to comment
RobJ Posted December 22, 2014 Share Posted December 22, 2014 I suspect it may be a BIOS configuration issue. Make sure that all SATA configuration options are set to AHCI, or at least a native SATA option, not an IDE emulation choice. Replace the SATA cable to the Seagate 3TB with serial # ending in J7N. It is showing CRC errors which typically indicate a bad SATA cable. Motherboard has an Intel gigabit networking chipset, but is currently connecting at only 100mbps. Link to comment
antron12345 Posted December 22, 2014 Author Share Posted December 22, 2014 You guys are gods. I move the drives to different ports on the motherboard and changed out some cables, that fixed the issue with the system just freezing. of cause now the system needs to rebuild the parity drive as a check since the system came down a few time unclean. Link to comment
antron12345 Posted December 22, 2014 Author Share Posted December 22, 2014 Once the system is sable I will check why the network card is not getting set to 1gig. Also while the system was rebuilding the drive on of the 2tb drives (sn: WRED) went to disabled. I have placed a new drive in the system and am rebuilding the data once again. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.