March 23, 201313 yr Hey all, I setup a new 5.0-rc11 server about the time rc11 was released and slowly have been moving my data to the server. Everything has been running great, which has included a few normal powerdowns or restarts. I left my server running for some 20+ days without using it so I decided to shut it down, which I left off for about 4 days. I powered it back on today and I cannot get the normal UnRaid menu (port 80) to come up, it wont even prompt the login. I can however get to UnMenu (8080). I have tried now to killall emhttp and restarting by /usr/local/sbin/emhttp &. Sometimes port 80 acts like its responding, but nothing is ever returned. Any idea how I fix this? ERRORS in Syslog: Mar 23 08:14:32 NAS emhttp: unRAID System Management Utility version 5.0-rc11 Mar 23 08:14:32 NAS emhttp: Copyright © 2005-2012, Lime Technology, LLC Mar 23 08:14:32 NAS emhttp: Plus key detected, GUID: ########## Mar 23 08:14:32 NAS emhttp: diskFsStatus.1 not found Mar 23 08:14:32 NAS kernel: emhttp[32732]: segfault at 0 ip b754d760 sp bfae2c30 error 4 in libc-2.11.1.so[b74d4000+15c000]
March 23, 201313 yr First a system log might get you more response, but a google search revealed the following thread http://lime-technology.com/forum/index.php?topic=19560.0 Hope this helps. Burt
March 23, 201313 yr You cannot kill and restart emhttp that way in the 5.X series. It worked in 4.7, but the only recourse on 5.X is to reboot.
March 23, 201313 yr Author Maybe the diskFsStatus.1 not found is unrelated and caused by me stopping emhttp manually. I have attached my syslog in case anyone can help. Burt, I ran through that thread. I reformatted my USB, restored files and did a chkdisk. Still no luck. Thanks,
March 24, 201313 yr Looks to me like one of your add-ons is attempting to access the array before the array is fully initialized and started with everything mounted. That prevents unRAID from completing its start up. Disable your add-ons, reboot, and then figure out which is the culprit by adding in one at a time and rebooting after each one. This is a common issue with the add-ons as they are not coded to deal with the array start up taking a longer time than usual (or at all). I've personally see unRAID take over 30 minutes to mount a drive after a non-clean shut down as it replays transactions in its journal before eventually mounting a drive. A program attempting to access the mounted directory would prevent the start up from completing. Joe L.
Archived
This topic is now archived and is closed to further replies.