September 14, 201213 yr UNRAID5B12A The system is working and can access the plugins directly but I cannot access the unraid menus. I telnet: root@Tower39:~# killall emhttp root@Tower39:~# nohup /usr/local/emhttp & [1] 26659 root@Tower9:~# nohup: ignoring input and appending output to `nohup.out' If i press enter then this appears [1]+ Segmentation fault nohup /usr/local/sbin/emhttp Joe
September 14, 201213 yr UNRAID5B12A The system is working and can access the plugins directly but I cannot access the unraid menus. I telnet: root@Tower39:~# killall emhttp root@Tower39:~# nohup /usr/local/emhttp & [1] 26659 root@Tower9:~# nohup: ignoring input and appending output to `nohup.out' If i press enter then this appears [1]+ Segmentation fault nohup /usr/local/sbin/emhttp Joe Don't know where you learned those commands, but they ONLY worked on early versions of unRAID (4.7 and prior). You cannot re-start emhttp 5.X versions. It will error with a segment violation. You must stop the arrray and reboot. Joe L.
September 14, 201213 yr Author Joe L, Thanks - I had them written down - must have been when i was running ver 4.7 - thought they were still valid. I shut it down via command line and rebooted. Menus are back, but slow as it was doing a parity check and it started over , of course. Unraid - Balls are all green but it sure takes a long long time to change array status from starting to started... 1 percent parity - finally started Is there a way to tell what is process is slowing things down so much? Joe
September 14, 201213 yr Is there a way to tell what is process is slowing things down so much? Post a syslog.
Archived
This topic is now archived and is closed to further replies.