I can still access the shares with AFP and can telnet in.  But I cant start the emhttp again.

 

root@Tower:/usr/local/sbin# ./emhttp
Segmentation fault

 

This has happened about 30% of the time I started the mover manually.  It's PROPERLY annoying.  Here is the log from after I ran mover.  I'm not sure if it reveals anything.

 

...
Apr  7 23:42:00 Tower logger: .d..t...... 1 New Sort After Watching/Ken Hom Travels with a Hot Wok/
Apr  7 23:42:00 Tower logger: ./1 New Sort After Watching/
Apr  7 23:42:00 Tower logger: .d..t...... 1 New Sort After Watching/
Apr  7 23:42:00 Tower logger: moving Applications/
Apr  7 23:42:00 Tower logger: ./Applications/.AppleDB
Apr  7 23:42:00 Tower logger: .d..t...... ./
Apr  7 23:42:00 Tower logger: .d..t...... Applications/
Apr  7 23:42:00 Tower logger: .d..t...... Applications/.AppleDB/
Apr  7 23:42:00 Tower logger: ./Applications/
Apr  7 23:42:00 Tower logger: .d..t...... Applications/
Apr  7 23:42:00 Tower logger: moving personal/
Apr  7 23:42:00 Tower logger: ./personal/.AppleDB
Apr  7 23:42:00 Tower logger: .d..t...... personal/
Apr  7 23:42:00 Tower logger: .d..t...... personal/.AppleDB/
Apr  7 23:42:00 Tower logger: ./personal/
Apr  7 23:42:00 Tower logger: .d..t...... personal/
Apr  7 23:42:00 Tower logger: mover finished
Apr  7 23:57:13 Tower emhttp: shcmd (45): /usr/sbin/hdparm -y /dev/sdd &> /dev/null
Apr  7 23:57:24 Tower kernel: mdcmd (25): spindown 1
Apr  7 23:57:35 Tower kernel: mdcmd (26): spindown 0
Apr  7 23:57:36 Tower kernel: mdcmd (27): spindown 3
Apr  8 03:40:01 Tower logger: mover started
Apr  8 03:40:01 Tower logger: skipping */
Apr  8 03:40:01 Tower logger: mover finished
Apr  8 04:12:23 Tower kernel: mdcmd (28): spindown 1
Apr  8 04:15:54 Tower kernel: mdcmd (29): spindown 2
Apr  8 04:16:15 Tower kernel: mdcmd (30): spindown 3
Apr  8 18:57:54 Tower in.telnetd[14950]: connect from 192.168.1.145 (192.168.1.145)
Apr  8 18:57:56 Tower login[14951]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.145'
Apr  8 18:57:59 Tower login[14951]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.145'
Apr  8 19:01:19 Tower emhttp: unRAID System Management Utility version 5.0-rc10
Apr  8 19:01:19 Tower emhttp: Copyright (C) 2005-2012, Lime Technology, LLC
Apr  8 19:01:19 Tower emhttp: Plus key detected, GUID:
Apr  8 19:01:19 Tower emhttp: diskFsStatus.1 not found
Apr  8 19:01:19 Tower kernel: emhttp[15007]: segfault at 0 ip b7505760 sp bff84760 error 4 in libc-2.11.1.so[b748c000+15c000]
root@Tower:/usr/local/sbin# 

 

I then have no options but to powerdown and start again.  Here's the output from that:

oot@Tower:/boot# powerdown
Capturing information to syslog. Please wait...
version[15231]: Linux version 3.4.24-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #1 SMP Mon Jan 7 16:44:53 PST 2013
ls: cannot access /dev/hd[a-z]: No such file or directory
ls: cannot access /dev/hd[a-z]: No such file or directory
/etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect
/etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect
/etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect
/etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect
/etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect
/etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect
status[15301]: State: STARTED
status[15301]: D#           Model / Serial          Status         Device    
status[15301]: 0                  /                 DISK_OK        sde       
status[15301]: 1                  /                 DISK_OK        sdc       
status[15301]: 2                  /                 DISK_OK        sdf       
status[15301]: 3                  /                 DISK_OK        sdb       
status[15301]: 4                  /                 DISK_NP        rdevName. 
status[15301]: 5                  /                 DISK_NP        rdevName. 
status[15301]: SMART overall health assessment
ls: cannot access /dev/hd[a-z]: No such file or directory
status[15301]: /dev/sda: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
status[15301]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
status[15301]: /dev/sda: Unknown USB bridge [0x090c:0x1000 (0x1100)]
status[15301]: Smartctl: please specify device type with the -d option.
status[15301]: Use smartctl -h to get a usage summary
status[15301]: /dev/sdb: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
status[15301]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
status[15301]: SMART overall-health self-assessment test result: PASSED
status[15301]: /dev/sdc: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
status[15301]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
status[15301]: SMART overall-health self-assessment test result: PASSED
status[15301]: /dev/sdd: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
status[15301]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
status[15301]: Device is in STANDBY mode, exit(2)
status[15301]: /dev/sde: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
status[15301]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
status[15301]: SMART overall-health self-assessment test result: PASSED
status[15301]: /dev/sdf: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
status[15301]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
status[15301]: SMART overall-health self-assessment test result: PASSED
status[15301]: No active PIDS on the array
Removing old syslog: /boot/logs/syslog-20130330-162630.txt
Saving current syslog: /boot/logs/syslog-20130408-191424.txt
-rwxrwxrwx 1 root root 285793 2013-04-08 19:14 /boot/logs/syslog-20130408-191424.txt
  adding: syslog.txt (deflated 89%)

Broadcast message from root (pts/0) (Mon Apr  8 19:14:24 2013):

The system is going down for system halt NOW!

 

A few of the times, parity had to be checked.  No errors (thank god).  Thankfully this was one of the times parity did not have to be checked.  I did search the forums and found others have had this issue, but I don't see a solution.  I have no plugins installed except for unmenu.

 

The strange behavior is, I can still access tower:8080 in the beginning.  But after a few minutes, It also stops responding similar to tower/main.  It doesn't matter if I access tower:8080 immediately after web interface crashed, or wait hours before accessing.  It always stops responding after a couple of minutes.  Does that make sense?

 

I hope someone can help me see what's going on? Should I never invoke mover manually?

I have no problems starting mover manually so I suspect that is not your problem.  However quite what it is I have no idea.

 

With unRAID 5.0 you cannot restart emhttp without rebooting.  Attempting to do so is just likely going to confuse things.