February 22, 201313 yr The array stops at random times, for no apparent reason. If I start the array again, it can run for hours or days without any problems, until it suddenly stops again. I'm able to access the web interface and telnet when this happens. I recently upgraded to 5.0-rc11 from an earlier version of unraid. I think it was a 5.0-beta version, not sure which. But the problem persisted :'( All the drives seems to be perfectly fine, no SMART errors. I've had this problem for a couple of months now. Does anyone have a clue what the problem might be? The syslog seems to resets itself, so when the array goes down it doesn't give me any information about the array(well, not anything I can understand anyway ). Is there other logs I can check? Btw. when I start the array again, a parity-check will run. I'm not sure if that is a indication of the problem or if it suppose to happen when the array goes down unexpectedly. Unraid server: Unraid 5.0-rc11 (+ simpleFeatures) Gigabyte - GA-MA74GM-S2H CPU: AMD AthlonTM II X2 250 - 3 GHz Cache: 128 kB Memory: 4 GB - 667 MHz Parity Drive: Samsung Spinpoint F4EG DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Western Digital RE4 Cache Drive: Seagate Barracuda 7200.11 Link to syslog
February 22, 201313 yr the parity check is because the array is rebooted without proper shut down, nothing you can do about it, it has nothing to do with the reason of the umavailability itself. Try the following to save your syslog: Create a file called savelog in the /config dir of your flashdrive, contents as follows: #!/bin/bash # save syslog cp /var/log/syslog /mnt/cache/syslog.txt Now add the following lines to your GO file: # Setting up savelog cp /boot/config/savelog /etc/cron.hourly/savelog chmod +x /etc/cron.hourly/savelog Now your syslog will be saved to your cachedrive every hour. Save it immediately after startup to avoid it getting written over.
February 28, 201313 yr Author The script doesn't run. The syslog.txt are not stored on the cache drive. Am I doing something wrong?
February 28, 201313 yr did you save it as a MS-DOS file, or a UNIX/Linux file? See here: http://lime-technology.com/wiki/index.php/FAQ#Why_do_my_scripts_have_problems_with_end-of-lines.3F Is the file actually in /etc/cron.hourly ? Type ls -l /etc/cron.hourly to see if it is.
March 1, 201313 yr Author did you save it as a MS-DOS file, or a UNIX/Linux file? See here: http://lime-technology.com/wiki/index.php/FAQ#Why_do_my_scripts_have_problems_with_end-of-lines.3F I saved it as a MS-DOS file. I'll create the file again, this time as a linux file. Is the file actually in /etc/cron.hourly ? Type ls -l /etc/cron.hourly root@Tower:~# ls -l /etc/cron.hourly total 4 -rwxr-xr-x 1 root root 68 2013-02-28 12:10 savelog* root@Tower:~# Looks like it
March 7, 201313 yr Author My array went down again. And I have the syslog. But I didn't get any wiser, maybe you guys can get something out of it? Thanks again for all the help syslog.txt
March 7, 201313 yr See my sig to disable all add-ons. Disable add-ons and see if the problem goes away.
March 7, 201313 yr Jup... rename all .PLG files to .NO (or something else) and reboot... You have email notifications incorrectly configured causing a massiveamount of messsages in your syslog, in some circumstances even that can cause issues.. So turn that off (it will be a plugin so if you remove it that will be gone also)
March 13, 201313 yr Author The array went down again, the only add-on that was enabled was "simpleFeatures.core.webGUI-1.0.5-noarch-1.plg". This is a big mystery. The syslog looks fine, to me atleast . The array just suddenly stops syslog.txt
March 13, 201313 yr I know the author of simple features stated that if using rc11 the new version .11 I believe of simple features was needed. Personally I would go to stock unraid by disabling simple features test and see if problem goes away or persists. If it goes away then install add ons one at a time to see where it goes south.
March 13, 201313 yr Author I'm using the latest version of "SimpleFeatures", but I will try and disable the last add-on that is still enabled and see if that does the trick. Thanks again for the help Edit: I didn't have the lastest version I will make an attempt using the latest version after I have tried stock unraid.
March 20, 201313 yr Author Went back to stock unraid, but the problem persist :'( I have no idea what to do next, everything seems to work just fine until the array goes down for no apparent reason syslog.txt
March 20, 201313 yr Try running memtest to rule out a memory problem. Also, is your server accessible from the public Internet? It appears you're getting a public ip address through DHCP. The syslog doesn't have any info on the error that's causing the array to go down. Could you try one of these steps to see if you can can capture a little more information.
March 21, 201313 yr Author Try running memtest to rule out a memory problem. Also, is your server accessible from the public Internet? It appears you're getting a public ip address through DHCP. The syslog doesn't have any info on the error that's causing the array to go down. Could you try one of these steps to see if you can can capture a little more information. I will try and run memtest for a while and see if the memory is the culprit. No, the server is not accesible from internet, it's behind a firewall here at work. I will try and see if I can capture more information. Thanks again for all the help
March 22, 201313 yr Author Memtest have been running for 20 hours, and no errors. So the memory looks to be perfectly fine The syslog doesn't seem to be of any help, it shows no errors, the array just stops. Unraid are working before and after the array goes down, so no crashes or errors of any kind. Is there something I haven't looked at, something that may cause the array to suddenly stop? Edit: I'm "tailing the syslog", hopefully I might capture the moment the array goes down.
April 2, 201313 yr Author Hello again! The array went down again, well, no surprise there The syslog, which was tailed when the array went down, are attached. Just ignore the smtp errors, I haven't configured that bit yet. Other than that, it doesn't seem to be any other errors The syslog just suddenly end when the array goes down, with no errors. Any idea what is going on? Unraid runs perfectly when the array is up, it can't be a hardware problem, can it? syslogtail.txt
April 2, 201313 yr The array stops at random times, for no apparent reason. If I start the array again, it can run for hours or days without any problems, until it suddenly stops again. I'm able to access the web interface and telnet when this happens. I recently upgraded to 5.0-rc11 from an earlier version of unraid. I think it was a 5.0-beta version, not sure which. But the problem persisted :'( All the drives seems to be perfectly fine, no SMART errors. I've had this problem for a couple of months now. Does anyone have a clue what the problem might be? The syslog seems to resets itself, so when the array goes down it doesn't give me any information about the array(well, not anything I can understand anyway ). Is there other logs I can check? Btw. when I start the array again, a parity-check will run. I'm not sure if that is a indication of the problem or if it suppose to happen when the array goes down unexpectedly. Unraid server: Unraid 5.0-rc11 (+ simpleFeatures) Gigabyte - GA-MA74GM-S2H CPU: AMD AthlonTM II X2 250 - 3 GHz Cache: 128 kB Memory: 4 GB - 667 MHz Parity Drive: Samsung Spinpoint F4EG DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Western Digital RE4 Cache Drive: Seagate Barracuda 7200.11 Link to syslog You say it stops but you can still access the web interface and telnet. Do you mean that the web interface shows the array as stopped? And then you can start it again from the web interface? And then it starts a parity check? Just trying to make sure I understand. Usually an automatic parity check happens when rebooting after not stopping the array but this doesn't seem like what you are describing. One thing missing from the specs in your first post is the power supply. What is it?
April 3, 201313 yr Author The array stops at random times, for no apparent reason. If I start the array again, it can run for hours or days without any problems, until it suddenly stops again. I'm able to access the web interface and telnet when this happens. I recently upgraded to 5.0-rc11 from an earlier version of unraid. I think it was a 5.0-beta version, not sure which. But the problem persisted :'( All the drives seems to be perfectly fine, no SMART errors. I've had this problem for a couple of months now. Does anyone have a clue what the problem might be? The syslog seems to resets itself, so when the array goes down it doesn't give me any information about the array(well, not anything I can understand anyway ). Is there other logs I can check? Btw. when I start the array again, a parity-check will run. I'm not sure if that is a indication of the problem or if it suppose to happen when the array goes down unexpectedly. Unraid server: Unraid 5.0-rc11 (+ simpleFeatures) Gigabyte - GA-MA74GM-S2H CPU: AMD AthlonTM II X2 250 - 3 GHz Cache: 128 kB Memory: 4 GB - 667 MHz Parity Drive: Samsung Spinpoint F4EG DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Seagate Barracuda 7200.11 DATA Drive: Western Digital RE4 Cache Drive: Seagate Barracuda 7200.11 Link to syslog You say it stops but you can still access the web interface and telnet. Do you mean that the web interface shows the array as stopped? And then you can start it again from the web interface? And then it starts a parity check? Just trying to make sure I understand. Usually an automatic parity check happens when rebooting after not stopping the array but this doesn't seem like what you are describing. One thing missing from the specs in your first post is the power supply. What is it? That's correct. But because I haven't seen it happen in real time, it might be due to a reboot like you said. So the question is, why does it reboot? Might it be a unstable psu? I have lot's of psu's here at work, I can try and change the psu and see if that helps. Corsair HX620.
April 3, 201313 yr Author Please disable all add-ons. I've tried that. I have also gone back to stock unraid, but the array is still going down :'( Edit: Most likely the unraid server reboots, why haven't I thought of that before, it's quit obvious that's what happening. It must be a hardware issue. I know the RAM is ok, and the drives. So my first stop are the psu. I will change it and see what happens. Edit2: It just rebooted while I was sitting here, psu change is next on the agenda
April 4, 201313 yr Author That is correct. They are running because I have tried stock unraid, with no add-ons, and it still reboots. So I installed the add-ons again, because running without them had no effect. I have changed the psu to see if the server stops rebooting at random times. Because all the evidence seem to point to a hardware issue. It didn't occur to me that the problem wasn't the array going down, but the whole server. So the times when I discovered the array wasn't running, I assumed that it had stopped, not that the whole server had rebooted. The server had been so stable in the past, so I immediately focused on the software instead of the hardware.
April 5, 201313 yr Author Changed the psu, it still reboots. So ram, HDD's and PSU are okay. So it must be the motherboard that are faulty, or can the problem lie elsewhere?
Archived
This topic is now archived and is closed to further replies.