February 20, 201016 yr Hi All, Noob looking for advice. I have a 3 HD setup I downloaded earlier this month to test out unraid. Was just dabbling around with things andliking it so far, and today I decided to really jump in and start moving some of my big important file librariess over. About 5 minutes into the transfer, I get a window from my sending computer saying it lost connection. (I've done several transefers before of over a GB with no problem this was the first one) So here's what I did: Tried to get to the unRAID web interface, no dice wont respond. Logged in through telnet tried to shut the unRAID box down with linux commands and it would respond to my shutdown request, and echo that the server was shutting down but would just hang (waited 5-10 minutes several times). After several failed attempts to shut down through telnet I brought it down hard with the power button. It's running headless so when I powered it back up, I could hear lots of things going on in the drive but couldn't connect to the webserver. Eventually I connected may 5 10 minutes later, and it had disk1 listed as unformatted which was disconcerting... then it hangs again, and I can hear the drives working so I let it be and hope for the best... then maybe 10 minutes later I can connect, disk1 looks OK now, and looks like it still has all my data. It imediately launched into a parity check without my prompting. Just wondering what I should be doing to make sure everything is OK, diagnostics etc. Nothing critical on there yet so good time to iron out things. I do have unMENU installed but when I look at syslog all I see is events after the reboot. What should I be doing to figure out what happened and make sure my data is OK?
February 20, 201016 yr ... then it hangs again, and I can hear the drives working so I let it be and hope for the best... then maybe 10 minutes later I can connect, disk1 looks OK now, and looks like it still has all my data. It imediately launched into a parity check without my prompting. The server started a parity check because of the cold reboot. Check out the troubleshooting section of the wiki: http://lime-technology.com/wiki/index.php?title=Troubleshooting
February 21, 201016 yr Chance of something bad happening just because of a simple power loss, or turning it off incorrectly is very slim. I'd still avoid it at all costs though.
February 21, 201016 yr Author Woke up this morning to the parity check frozen at 65%... and the drives all spun down... Tried to take the array down and now the management console is not working either....
February 21, 201016 yr It is time for you to attach a monitor and keyboard, and reboot. then, capture a syslog after the parity check starts once more. Odds are good your syslog is filling with errors, and eventually you are running out of RAM. Joe L.
February 21, 201016 yr What should I be doing to figure out what happened and make sure my data is OK? Run a memory test, at least for several passes. Make absolutely certain the memory voltage, timings, and clock speed are correct for your specific memory strips. Some BIOS automatically set it and get it right. Others get it wrong. Do not leave it to chance, set it manually instead of leaving it at "auto" When you reboot, capture a syslog so you can attach it to your next post. Do not run headless... not until you get the hardware issues ironed out. Joe L.
Archived
This topic is now archived and is closed to further replies.