February 6, 201313 yr For a clean startup check dgaschk's signature: Revert to stock system: 1. Rename the /boot(flash)/config/plugins directory. 2. Rename boot(flash)/extra/. 3. Use the stock go file (boot(flash)/config/go). Stock go file: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp &
February 6, 201313 yr Author For a clean startup check dgaschk's signature: Will a clean startup affect the existing array/parity? And I've just caught this in memory info. Which is a different story to the last one I posted. total used free shared buffers cached Mem: 1812168 1779684 32484 0 57016 1633544 -/+ buffers/cache: 89124 1723044 Swap: 0 0 0 Edit: Seems when array is up, ram is used. Main menu still inaccessible when ram free.
February 6, 201313 yr Will a clean startup affect the existing array/parity? And I've just caught this in memory info. Which is a different story to the last one I posted. total used free shared buffers cached Mem: 1812168 1779684 32484 0 57016 1633544 -/+ buffers/cache: 89124 1723044 Swap: 0 0 0 It will not affect array/parity just disable all addons packages and plugins
February 6, 201313 yr Author It will not affect array/parity just disable all addons packages and plugins Ok thanks.
February 6, 201313 yr Clean startup makes no difference. Piece of shit is what I think Post a new syslog with no add ons installed that covers from bootup to the time period in which you lose connectivity.
February 6, 201313 yr Clean startup makes no difference. Piece of shit is what I think It initially shows the WEBUI and then doesn't? after how much time? is this time constant or can it vary?
February 7, 201313 yr Author Clean startup makes no difference. Piece of shit is what I think Post a new syslog with no add ons installed that covers from bootup to the time period in which you lose connectivity. It's clean, nothing even remotely indicates a problem. emhttp just hangs. Clean startup makes no difference. Piece of shit is what I think It initially shows the WEBUI and then doesn't? after how much time? is this time constant or can it vary? After a reboot it'll display the login screen fine, then 1-2 seconds later of inactivity the menu becomes inaccessible. In an above post somewhere I posted the process that exists and doesn't close. If I click lots, I get more of these processes. I've used apache on a web server before and connections are constantly made/closed for http web requests. When this problem occurs in unraid the process is made, but doesn't close.. which I believe to result in loss of http access.
February 7, 201313 yr Clean startup makes no difference. Piece of shit is what I think Post a new syslog with no add ons installed that covers from bootup to the time period in which you lose connectivity. It's clean, nothing even remotely indicates a problem. emhttp just hangs. Looks like you forgot to attach it. No way to help without it.
February 7, 201313 yr I'm curious what browser you've been accessing it with? I wonder if one is more likely to cause these hung sessions than others. Because I can go hours to days before it hangs. I use ipad safari, rockmelt on pc, ie 9+10, and chrome. I haven't tried to test one exclusively yet to see if that might be it.
February 7, 201313 yr Author Looks like you forgot to attach it. No way to help without it. I wasn't home. Nothing shows up in logs, my first post contains a syslog. I'm curious what browser you've been accessing it with? I wonder if one is more likely to cause these hung sessions than others. Because I can go hours to days before it hangs. I use ipad safari, rockmelt on pc, ie 9+10, and chrome. I haven't tried to test one exclusively yet to see if that might be it. Since I got Win8, Firefox. Also tried IE 10. Which raises a question I've been meaning to ask, are unraid users using Win8 fine with the unraid main menu?
February 7, 201313 yr Looks like you forgot to attach it. No way to help without it. I wasn't home. Nothing shows up in logs, my first post contains a syslog.That syslog is only 8 minutes long, and was captured while you still had plugins starting. Please capture a new complete syslog after the box has been up for a while, and is exhibiting the problems.
February 7, 201313 yr Will a clean startup affect the existing array/parity? And I've just caught this in memory info. Which is a different story to the last one I posted. total used free shared buffers cached Mem: 1812168 1779684 32484 0 57016 1633544 -/+ buffers/cache: 89124 1723044 Swap: 0 0 0 It will not affect array/parity just disable all addons packages and plugins Your reading this output incorrectly. I've highlighted the correct value for free in red.
February 8, 201313 yr Author Anything of interest here? I see RX packets are getting dropped.. root@Fridge:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1f:d0:8f:e4:f5 inet addr:10.1.1.3 Bcast:10.1.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2817179 errors:0 dropped:90 overruns:0 frame:0 TX packets:4991564 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:205519519 (195.9 MiB) TX bytes:2896968714 (2.6 GiB) Interrupt:42 Base address:0xe000
February 8, 201313 yr Author Well through processes of deleting and restoring unraid files, I've now ended up with "boot error". It's fair to say I now hate unraid and fear for my data Edit: Seems executing the "make_bootable" batch file has fixed that. Still i've lost confidence in trying to fix unraid
February 8, 201313 yr Anything of interest here? I see RX packets are getting dropped.. root@Fridge:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1f:d0:8f:e4:f5 inet addr:10.1.1.3 Bcast:10.1.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2817179 errors:0 dropped:90 overruns:0 frame:0 TX packets:4991564 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:205519519 (195.9 MiB) TX bytes:2896968714 (2.6 GiB) Interrupt:42 Base address:0xe000 Never good. Those should all be 0 as you know.
February 10, 201313 yr Author Not solved yet, but an update on what i've tried. It's becoming more intriguing the deeper I dig. After discovering my HDDs operating between 48 and 54oC (they hadn't spun down!) I decided to look into the problem even further and being the weekend I have time to play around (despite wanting to be outside!). Server is now out of the tv cabinent to make changes. I tried using a fresh install on 2 different usb devices, neither detected with my mobo. So I backed up my usb drive and made a fresh install. I can now rule out the following with a degree of confidence: A fresh install of unraid -> problem still exists. [Assumption made that unRAID OS is not the problem] I changed the router -> problem still exists. [Assumption made that the router is not the problem] All HDD's disconnected -> problem still exists. [Assumption made that cables are OK] I noticed that my only server fan isn't always spinning up from being turned on (and it has it's own rail from psu). I'm thinking the fault may be hardware based, and the fan is leading me to think it could be the PSU. So I haven't got another USB drive to test (though if unraid it loads into RAM, I can rule this out?). And PSU I can't test as I don't have a spare, nor do I have spare RAM (it passed Memtest). Thinking I will need to get these to continue though. Could a PSU be responsible for the main menu becoming inaccessible, affecting LAN connections? Forgot to mention I've found some microsoft-ds connections (Assumably Samba through windows) becoming hung too. Though the rest of the server operates normally, something isn't quite right here. Thoughts please?
February 10, 201313 yr Author Problem still exists using New RAM and new PSU. Edit: May have just had a break through! Stay tuned!
February 10, 201313 yr Author Removed post for further testing, but it is a result of program interference! And for those thinking I should've tested for this first, I did. However thinking back when I did exit all programs to test, it was after unraid was hung (unaware of this at the time), and therefore (at the time) dismissed as the potential issue. Update #1 Originally thought Trend Micro Titanium Maximum Security 2013 was at fault, but withdrew that after noticing an anomaly (to do with method of exiting applications). Update #2 Narrowed the problem down to 2 applications (out of 4 that I suspected). They are Trend Micro Titanium Maximum Security 2013 and Comodo Firewall 2013 (v6). Here's where it gets interesting. I used IE10 to test the following combinations and whether main menu works without hanging. Trend off, Comodo on = no Trend on, Comodo off = no Trend off, Comodo off = yes (firefox also works) Next step try to allow unraid to work with these applications, or I'll have to find alternatives. Update #3 Have decided to kill 2 birds with 1 stone and rid my PC's of Trend+Comodo for a much better suite of Kaspersky.
February 10, 201313 yr Author I am marking this as solved. The problematic software (trend micro and comodo firewall) has been removed. All tests thus far suggest the problem has been rectified. If something comes up I'll be sure to update here. Thanks to all who took the time to make suggestions. My server, as a result of recent events, now has twice the memory,. Plus I have a el cheapo PSU for future diagnostic purposes As to why all of this occured, it was due to my clean install upgrade to Windows 8 which resulted in all the latest software being installed. Two of which broke my unraid main menu. Which consequently caused http to hang.
February 10, 201313 yr did you try to connect to unRaid from another pc or smartphone when it hung? was it just the pc problem or did unRaid really get stuck?
February 10, 201313 yr Author did you try to connect to unRaid from another pc or smartphone when it hung? was it just the pc problem or did unRaid really get stuck? I'm guessing you haven't read the thread? When the array was up everything operated as per normal. All PC/media clients could access shares, could write to them & speeds were normal. Yes I had tried from other PCs. I used my Windows 8 laptop (with same apps installed) and once from Windows 7 machine. Had I known now, I could've rebooted the server and tried accessing from Windows 7 machine and would've saved a lot of time narrowing it down to Windows 8. However I reckon I would've put blame on the OS, rather than the apps. It was the http part of unraid that was getting stuck, only after getting accessed with a browser, which broke trying to access the main menu from any PC. A work-a-round was to install a browser refresh program which kept the connection open - but this was never going to be a long term solution as whenever it was stopped I would need to reboot server to fully fix the hung session as I found killing emhttp was unreliable.
Archived
This topic is now archived and is closed to further replies.