I. M. Fletcher Posted July 9, 2006 Share Posted July 9, 2006 I'm setting up my array for the first time. I've got 5 disks. I started the Parity SYnc last night at about midnight. It's now 10 hours later and it's only 20% done. What is going on? Quote Link to comment
I. M. Fletcher Posted July 9, 2006 Author Share Posted July 9, 2006 I went ahead and stopped it. I'm not going to wait 50 hours for this thing to build. Should I being doing this directly on the server instead of through windows? If so, what are the commands. The 3 pages of documentation that came with the USB doesn't help me at all, especially since I know nothing about linux. Thanks Quote Link to comment
JeffAtlanta Posted July 9, 2006 Share Posted July 9, 2006 From what I've followed on the boards, most likely a DMA issue. You might want to stop the parity sync and verify. Quote Link to comment
I. M. Fletcher Posted July 9, 2006 Author Share Posted July 9, 2006 I rebooted and started it again. It's working fine now. It's only taking 5 hours this time. The problem I'm having now is that one of my drives has reported 30 errors so far. Not good. Is the drive bad or is something else going on? Quote Link to comment
I. M. Fletcher Posted July 9, 2006 Author Share Posted July 9, 2006 State: OK Green Light: Flashing Temp: Not Reading * Errors: 28 Is the drive toast? I hope not. Hitcachi is terrible to deal with for warranty issues. Quote Link to comment
limetech Posted July 9, 2006 Share Posted July 9, 2006 Normally "Flashing Light" in the Management Utility along with "*" for temperature indicates the drive is spun down. (If you send a SMART command to a drive already spun down, e.g., to get it's temperature, the drive will spin back up, hence the s/w will not try to get the temperature if it detects the drive is spun down.) Another possibility is a communicaton problem with the drive preventing the SMART command from competing correctly. I suggest you move the drive to another slot and see if you see the same behavior. In any case, should take from 3-5 hours to rebuild parity depending on size and number of drives installed. Quote Link to comment
I. M. Fletcher Posted July 11, 2006 Author Share Posted July 11, 2006 The array seemed to be operating fine. I went ahead and loaded some data onto the drives (but not the drive that I'm suspicous of). I rebooted to make sure everything was functioning. Parity check initiated on reboot and I let it room. A couple hours later I came back and the server had frozen. The drives were all spinning but I couldn't access anything. The monitor was blank and the web management just went to www.towerrecords.com (which is annoying btw) I'll mess around with it more tomorrow. Quote Link to comment
daquint Posted July 14, 2006 Share Posted July 14, 2006 The monitor was blank and the web management just went to www.towerrecords.com (which is annoying btw) If theres anything on sale, please post in Good Deals forum! Sorry, i couldnt pass it up. Quote Link to comment
jimwhite Posted July 15, 2006 Share Posted July 15, 2006 The array seemed to be operating fine. I went ahead and loaded some data onto the drives (but not the drive that I'm suspicous of). I rebooted to make sure everything was functioning. Parity check initiated on reboot and I let it room. A couple hours later I came back and the server had frozen. The drives were all spinning but I couldn't access anything. The monitor was blank and the web management just went to www.towerrecords.com (which is annoying btw) I'll mess around with it more tomorrow. sounds like you have some memory issues.... try slowing the memory down in the bios.... i.e. change CAS=2 to CAS=2.5, for instance.... Jim Quote Link to comment
limetech Posted July 17, 2006 Share Posted July 17, 2006 I'll mess around with it more tomorrow. How is your system running now? Quote Link to comment
dschur Posted July 18, 2006 Share Posted July 18, 2006 Time for a "What happened to I M Fletcher, has he abandoned UnRaid thread?" Sorry, couldn't resist. Glad to see you back Tom. Quote Link to comment
lovingHDTV Posted July 18, 2006 Share Posted July 18, 2006 When my system was having these issues, they were caused by DMA errors. They were finaly cleared up by putting all my harddrives on the second power supply and having the first power supply only power the system board. Still not sure why this was necessary as the supply is plenty big enough for 3 drives, but I can't argue with the results. Try the telnet window from a different system, and monitor the syslog file. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.