abhi.ko

WOW - that was not what I was hoping to hear! Thank you for looking at it though! I have 6 Seagate Barracuda 7200.14 drives out of a total of 8 in the build. The other 2 are a Hitachi and a Samsung SSD (cache). Only 7 out of these 8 are being used the 8th one is just a back up or an extra drive (2TB). It seems highly unlikely that all Seagate drives have failed at the same time (there are 6 of those messages in the log, one each for each of the drves), and I am hoping that this isn't the case. Could I ask what does AF mean - is that what got you to think that these 6 are failing?

Hi, I just changed my case as I recently bought a Fractal Design R4 - I removed and replaced all my hardware from the old box to the new one. Everything went well - except for the fact that i am nt able to access the web GUI or UU after the change. If connected to a monitor I can see that the boot process goes through fine and I can login and excute commands through the command line. But the tower in inaccessible when headless, not even via telnet (host not found). I have verified that all the hardware and the connection via the NIC is working fine. Attaching the most recent syslog. ifconfig eth0 does return my IP address as it was before and ensures that the tower is connected to the net. I have tried going stock 5.0.5 without any plugins but that hasn't worked either. Confirmed that the SATA controller is running in AHCI mode and that all the drives are being recognized at boot by the BIOS. So all hardware seems to be working fine - not sure why the web GUI is not coming up. Any and all help is appreciated. Thanks, Abhi syslog-20140314-114619.zip

Thanks a ton Tom! I have no logical reason why I picked NFS over SMB to map my XMBC locations, but if that is all that needs to be fixed then that is just editing an xml file (for each XBMC installation - I have 5) to fix it and change to SMB. Now that I heard your opinion on NFS I will try doing exactly that and switch it all to SMB. I will try what you suggested for the disable-reboot-enable sequence first though and see if everything works out with NFS before switching to SMB. For right now no crashes after disabling spindown but something interesting I noticed, had a few instances of the web GUI(emhttp freezing or not responding) and also Telnet returns a "host not found" message but the media is playing on my HTPC while that is happening - any idea why that would be? I am trying to access it from multiple locations but nothing has crashed it yet. Not sure if that is the end of that issue or whether it is just a matter of time before it comes back (sorry my previous experiences have made me a skeptic).

Tried the spinup and down in Maintenance mode at least 15 times without issues. Now trying to run with spindown disabled for all the disks, so far no issues but noticed this at the end of the active syslog, does that indicate something: Dec 13 17:00:56 Tower emhttp: Restart NFS... Dec 13 17:00:56 Tower emhttp: shcmd (127): exportfs -ra |& logger Dec 13 17:00:56 Tower logger: exportfs: Warning: /mnt/user/TV Shows does not support NFS export. Dec 13 17:00:56 Tower logger: exportfs: Warning: /mnt/user/Other Media does not support NFS export. Dec 13 17:00:56 Tower emhttp: shcmd (128): /usr/local/sbin/emhttp_event svcs_restarted Dec 13 17:00:56 Tower emhttp_event: svcs_restarted Dec 13 17:00:56 Tower emhttp: shcmd (129): /usr/local/sbin/emhttp_event started Dec 13 17:00:56 Tower emhttp_event: started Dec 13 17:00:56 Tower avahi-daemon[1797]: Service "Tower" (/services/smb.service) successfully established. Dec 13 17:01:07 Tower rpc.statd[1134]: nsm_parse_reply: can't decode RPC reply Dec 13 17:01:45 Tower last message repeated 3 times Dec 13 17:02:49 Tower last message repeated 5 times Dec 13 17:03:53 Tower last message repeated 5 times Dec 13 17:04:56 Tower last message repeated 5 times Dec 13 17:06:00 Tower last message repeated 5 times Dec 13 17:07:04 Tower last message repeated 5 times Dec 13 17:08:08 Tower last message repeated 5 times Dec 13 17:09:11 Tower last message repeated 5 times Dec 13 17:10:15 Tower last message repeated 5 times Dec 13 17:11:19 Tower last message repeated 5 times Dec 13 17:12:22 Tower last message repeated 5 times sdg is my cache drive and it was spun down I believe (blinking green light) when it crashed the last time.

Okay I spoke too soon. Crash/Freeze happened a few minutes after my last post. 3 more lines on the syslog, the complete syslog until the crash is posted here. Now the system is running (meaning the fans are spinning and the system LED's are blinking/on) but it is in-accessible or frozen everyother way. Not sure what is causing this, hope the attached syslg gives us some clue as to what is going on. syslog.txt

Okay Thank you for taking a look at it Tom. I am doing what you suggested now on a complete stock 5.0.4 fresh install on my flash drive. I had to hard reboot the system so it is running a parity check on reboot, I am letting it run the parity check unless you think that I should I stop it. So far it is up and running, I have a copyof the syslog from the telnet session attached here for reference - the system is still running - so this log s before the crash. Not sue if this information is useful but wanted to share. No I haven't tried stopping the NFS shares, especially since all my XMBC paths are defined using the NFS share, but I defenitely can try that if that is what you suggest. Has "enabling NFS shares" been known to cause these issues? I can get a new set of RAM sticks and try with those, but is there a way to test and be sure what part of the the hardware is causing the issue. If not Memtest then is there some other we can tell?? Thanks for the help again. syslog.txt

Okay bad news is that the server is still crashing/freezing up and it is more frequent than before. I have upgraded to 5.0.4 but still the problem is not solved. I haven't been able to access the server for over 2 weeks now, did not have time to post here till now. Getting to the point where I think I will have to ditch unRAID altogether and go for some other OS, but I am worried whether the migration would be painless and simple. Trust me when I say this that this is not what I wanted to do, but the issues I've had to deal with the last couple of months has got me to the point where I am thinking I would be happy if I can get to access the server, unRAID unfortunately is broken for me and I do not know how to fix it. Unless some kind hearted soul here can help me or Tom himself or his team can provide some customer service I will have to migrate to other solutions. I am thnking FreeNAS or WHS - does anyone have any insights on what can be done here or on how to migrate to another server OS please? All help is welcome. I can try and capture the log by adding the script that doorunrun suggested to transfer the log writing to the USB drive so that it will show us what is causin the freeze up? Does any one have any suggestions please?

I got to thank you for the script doorunrun - I haven't had any issues so far after I have tried that and it looks like my assumption that 4GB was enough was wrong. So far no system crashes after the 5.0.2 upgrade and no webgui crashes after your script was added to the go file. So looks like I am back in business. I did install Plex and uu (and a few packages) yesterday and it has been running fine so far, planning to install crashplan and that would be it. Hope the 4GB should do for that much. So thank you again. I will close out this thread after a couple more days if everything seems okay.

root@Tower:/# ps x | grep emhttp 1227 ? Sl 0:03 /usr/local/sbin/emhttp 4348 pts/1 S+ 0:00 grep emhttp This is right now and now everything is running fine, will try this again if it crashes later and let you know what it says. But honestly doorunrun's 2 line script seems like it did something - haven't had any issues since I added that to the go file and rebooted. Installed uu and Plex and it all seems to be going great (so far - fingers crossed).

I believe that's the spindown command for one of the drives (sdg). In my case I started seeing those show up for a SSD cache drive and there's no point in trying to spin it down. So I remove the option for that drive, FWIW. Okay thanks for that, sdg is my cache drive. So the system did not crash and I have been using it pretty much throughout since upgrading to 5.0.2, however emhttp crashed and never came up again so had to reboot from telnet to get it running again. Everything else is working fine and have had no issues. Wonder what is causing the webgui to go down? Any ideas?

Okay the server is still running but the webgui has crashed. I can still access shares and the system through telnet but tower/main is not accessible. Saw this in the log corresponding to the time when the crash happened, not sure if this means anything (complete log attached below): Nov 26 08:47:42 Tower emhttp: shcmd (59): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Is this related to the spaces in the share names('TV Shows' and 'Other Media') for nfs that I had mentioned before? syslog.txt

Thanks for the suggestion doorunrun. Will defenitely try it. I have 4 GB of RAM - and no addons installed right now, so if something is hogging my memory then it has to be unRAID itself, I amnot sure why it would though. But it would be defentely worth a try. So thank you! Meanwhile just an update - I just upgraded to 5.0.2 and the syste hasn't crashed yet, I am accessing shares and disks and trying to replicate the circumstances that used to cause the crash before but it is going great so far, no issues. That does not mean that it won't only upgraded this morning - not enough time has passed to tell one way or the other. So keeping my fingers crossed and if everything goes fine for a couple of days then I will try installing a few addons (Plex Server and maybe upgrade the webGUI) and report back. It is a good thing that I am on vacation this week I am still puzzled what was causing the issue, guess we will never know if the 5.0.2 solved it. Here is my config, same exact config that has been working without issues for over a year. CPU: AMD A4-3400 2.7Ghz - http://www.newegg.com/Product/Product.aspx?Item=N82E16819103955 MoBo: ECS A75-FM2 (6 SATA 3 ports, USB 3.0) - http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=743866 RAM: PNY XLR8 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) - http://www.newegg.com/Product/Product.aspx?Item=N82E16820178265 PSU: Corsair AX 430W ATX - http://www.newegg.com/Product/Product.aspx?Item=N82E16817139026&Tpk=cx%20430 Case: NZXT Source 210 Black (8 x 3.5" Internal HDD drive bays) - http://www.newegg.com/Product/Product.aspx?Item=N82E16811146075 USB: Transcend 2 GB USB stick - for unRAID - http://www.amazon.com/Transcend-JetFlash-V30-Flash-TS8GJFV30E/dp/B00284AOSY/ref=sr_1_5?ie=UTF8&qid=1337112892&sr=8-5 I have an Intel NIC installed and used instead of the onboard one. I also have a SATA exapnsion card (I am pretty sure I used this one foor the unraid box) - http://www.newegg.com/Product/Product.aspx?Item=N82E16816124045 to which the cache drve is plugged in al the data and parity drives are plugged to the on board SATA 3 ports. Thanks!

Also sometimes the tower stays unresponsive for a long time (web gui does not work,nor does the shares or the telnet session) and then all of a sudden it comes back. I keep refreshing the web gui and after say 15 minutes of not responding it starts working. Absolutely no idea what is going on. it just did that and there is absolutely nothing I can see in the log which shows anything. Nov 25 17:47:37 Tower kernel: mdcmd (31): spindown 0 Nov 25 18:01:46 Tower mountd[1277]: authenticated mount request from MYIP:51255 for /mnt/user/Other Media (/mnt/user/Other Media) Nov 25 18:01:51 Tower mountd[1277]: authenticated mount request from MYIP:51270 for /mnt/user/TV Shows (/mnt/user/TV Shows) Nov 25 18:09:38 Tower kernel: mdcmd (32): spindown 3 Nov 25 18:16:39 Tower kernel: mdcmd (33): spindown 4 Nov 25 18:20:15 Tower mountd[1277]: authenticated mount request from MYIP:52819 for /mnt/user/Other Media (/mnt/user/Other Media) Nov 25 18:37:50 Tower kernel: mdcmd (34): spindown 4 Nov 25 19:38:45 Tower mountd[1277]: authenticated mount request from MYIP:58755 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 19:40:35 Tower mountd[1277]: authenticated mount request from MYIP:58904 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 19:45:09 Tower mountd[1277]: authenticated mount request from MYIP:59262 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 19:52:02 Tower kernel: mdcmd (35): spindown 1 Nov 25 19:53:50 Tower mountd[1277]: authenticated mount request from MYIP:59912 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 19:55:13 Tower kernel: mdcmd (36): spindown 3 Nov 25 19:55:24 Tower kernel: mdcmd (37): spindown 4 Nov 25 20:02:15 Tower mountd[1277]: authenticated mount request from MYIP:60521 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 20:31:45 Tower mountd[1277]: authenticated mount request from MYIP:62721 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 20:55:46 Tower mountd[1277]: authenticated mount request from MYIP:64515 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 20:57:36 Tower mountd[1277]: authenticated mount request from MYIP:64649 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 20:59:05 Tower kernel: mdcmd (38): spindown 1 Nov 25 20:59:26 Tower kernel: mdcmd (39): spindown 3 Nov 25 21:01:57 Tower emhttp: shcmd (68): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Nov 25 21:02:01 Tower mountd[1277]: authenticated mount request from MYIP:64975 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 21:10:51 Tower mountd[1277]: authenticated mount request from MYIP:49274 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 21:19:16 Tower mountd[1277]: authenticated mount request from MYIP:49886 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 21:31:29 Tower kernel: mdcmd (40): spindown 4 Nov 25 21:35:21 Tower mountd[1277]: authenticated mount request from MYIP:51108 for /mnt/user/Movies (/mnt/user/Movies) Nov 25 21:48:46 Tower mountd[1277]: authenticated mount request from MYIP:52126 for /mnt/user/Movies (/mnt/user/Movies)

Here is the new syslog, system has been running since the last reboot and I have been accessing shares/disks without issues till now. SysLog_unRAID.txt

No it does not matter which disk is accessed. Sometimes it just crashes like right now for no apparent reason. I have not accessed tower in over 3-4 hours and came back now to see that it is unresponsive. Not necessarily. Not all activity causes a crash, I was watching videos and movies non stop for at least 3 hours yesterday and then sometime today morning through XBMC. All files are stored on tower - no problems occured through out this time. emhttp crashed a couple of time but it came right back. Just restarted the tower right now and it took a really long time to start the array and saw this in the log Nov 25 16:08:28 Tower logger: exportfs: Warning: /mnt/user/TV Shows does not support NFS export. Nov 25 16:08:28 Tower logger: exportfs: Warning: /mnt/user/Other Media does not support NFS export. PSU: Corsair AX 430W ATX - http://www.newegg.com/Product/Product.aspx?Item=N82E16817139026&Tpk=cx%20430 HDD: 1 parity (3TB) & 5 Data (3TB) - 1 Cache (2TB). Parity and 4 Data disks are these - Seagate Barracuda 7200 RPM 3TB http://www.newegg.com/Product/Product.aspx?Item=N82E16822148844&Tpk=ST3000DM001 1 Data is Hitachi Deskstar 3TB http://www.amazon.com/Hitachi-Deskstar-7K3000-HDS723030ALA640-SATA-600/dp/B004D8KO7Y and cache is the 2TB version of the Seagate Barracuda - http://www.newegg.com/Product/Product.aspx?Item=N82E16822148834

Thank You! Sorry for the late reply, but just got back home yesterday. Read and tried the steps outlined by Tom but getfattr –d /mnt/disk1/Movies did not not give any messages or errors for any top level directories on disks 1 -5 and cache. So did not have to run the script. The crashes are still happening especially when I try performing any kind of reading or writing activity - the whole tower just freezes up.

Okay just got a chance to finish running it on all the disks (md1 - md5 & sdg1(cache)) - all came back with no corruptions found. Using Telnet instead of SSH has got putty working so I can login remotely to the system. Also I disabled the mover and looks like the crashes have also stopped for the time being. I would like to use a cache disk and enable mover at some point, hopefully we can figure out what is casuing this and fix the issue soon. Thank you for everyone's help so far.

That's a good question! I think when your system goes totally unresponsive AND you can't telnet to the box that says more than emhttp is just dying. The fact that the locally connected keyboard stops working would, to me, indicate a big lockup. I don't recall seeing the amount of memory you are using, but I think the syslog indicates 4GB. Is that right? Yes it is 4GB and the memtest passed with 6 tests - all pases.

Okay maybe that is what is not woking. So if I change it to port 23 and telnet it should work right? But does that give us any clue as to why the system is crashing. Or are these 2 seperate issues?

Thank you for taking a look. I have not tried running in a safe mode, since it was completely stock, but will try and report once I get back home. I am travellling for work this week. I do use nfs a lot, all my xbmc paths are using the nfs share and so does a few other programs. But if that is worth a try then I can stop nfs and see if it works. (At this point I am up for trying anything to get the tower running without crashin after a few hours ). It just randomly occurs, but sometimes emhttp crashes and then recovers on its own, and atother times everything stops. The hardware is as stock as it can get the only addition was an Intel NIC and a SATA port expansion card. Keyboard, right now since I plugged in a monitor I am using one, otherwise no, and the crashes are happening with and without....!!!Checked the flash with a flash drive checking utiltiy and found no errors, memtest ran okay with 6 passes, so no problem with the hardware that I could identifiy.

putty screenshot.

Well putty configuration has not changed before and after the reinstall, and it is after the reinstall that putty was not working. My saved unRaid profile is what I am cliking on to try and get connected, but I either get timed out or the host cannot be found error. Host name: tower; Port: 22; Type: ssh. (screenshot attached). So not sure what I am doign wrong!!! The other saved putty profile was for crashplan, but since the new install is stock I have not installed crashplan yet. Anyways does the telenet issue help explaining the crashes or were you just curious? Because even with a monitor attached I can see that the ystem becomes unresponsive. Since the last update I even ran a flash drive check and found no errors at all. unRaid still crashes, any indication of what is causing this from the log files.

No for both. Telnet never seems to work even when the server is running. Should I install the ssh package for it to work? Sent from my SCH-I535 using Tapatalk

The system has crashed as before - fans are running, shares are not accessible!

Here are the logs - thanks in advance for taking a look! Unraid_Log_-_real_time.txt Unraid_Sys_log.txt