I can not access my server on my network and attached one of my syslogs. I was trying to preclear a new drive to replace one that I believe has failed and the server crashed on the last step of the preclear. I have been getting random crashes quite often and trying to narrow down the problem. I did a memtest and it came back with no errors.

 

Any help would be appreciated because I am a newb at this stuff and trying to learn as I go. Thanks alot.

syslog801.txt

Another crash today and still not able to access server on network. I can access it through telnet and browser though. I turned the server back on after crash and then went and created this syslog.

2011-8-4-syslog.txt

I am sorry about all the newb questions but I have been trying and now seeking help from the experts.

 

I am also having trouble getting unmenu to install. I am attaching a text doc of what I am doing in my telnet session. 

unmenu.txt

The syslog definitely indicates a problem. Are you running any add-ons? What type of PSU? Check the cabling.

The syslog definitely indicates a problem. Are you running any add-ons? What type of PSU? Check the cabling.

 

I was not running any add ons, PSU is a Antec Neo Eco 620watt, and cabling looks fine.

 

I have been having problems with crashes for a long time. When I saw one of my drives with a red ball I was thinking it was a bad drive. So I ran preclear on a new drive unsuccessfully because server would crash.

 

 

I formatted my flash drive and now put 5.0beta 8 on it. I am now stuck on parity sync which will probably take days. The server has not crashed since the format of flash drive. I am able to access unraid through web browser and telent but still not over network.

 

I am attaching my current syslog since I formatted the flash drive.

syslog8-5-11.txt

Well I spoke too soon as my server just turned off. How would I get the syslog now before I reboot? Had the parity sync at about 20% after about 9 hours and now this.

Well I spoke too soon as my server just turned off. How would I get the syslog now before I reboot? Had the parity sync at about 20% after about 9 hours and now this.

 

The best thing that can be done is open a telnet session to the server and run a

tail -n 100 -f /var/log/syslog

 

That will list the last 100 lines in the syslog and continually update as stuff is written to the syslog.  Run the above from a computer that does not go to sleep or shut down ever.  When the server crashes next time you will have a log file that is nearly as up to date as you can get.  That will tell us much much more then getting a syslog after the reboot.

 

Once the crash happens again post the text you get from the above command.

Here is a smart report of drive 2 and current syslog.

smart2.txt

syslog.txt

Based on current and pending reallocated sectors disk2 is failing fast.

Based on current and pending reallocated sectors disk2 is failing fast.

 

Yeah I had someone else tell me that. The drive is only about 5 months old and already failing. I am glad the people on this forum are helpful and knowledgeable because I would be lost with troubleshooting.

 

Problem is that I do not know if the drive is backed up. I tried a parity sync when I formatted my flash drive with v50beta8 but only got to 20% before server crashed. I have drives ready that I need to run preclear on but I do not want to lose data on failing drive. 

Do you have a parity disk in place?