March 18, 201412 yr This evening I was trying to move a file from my unraid server to my computer when I got an error telling me I cannot complete this because one of my Tower users was the file owner. I managed to get in with putty, replace the owner (chown) and change the folders to 777 access and this let me move the files. I then tried to get to the web console to run newperms. While I have been on 5.x for a while, I figured this is the best way to just catch everything that was not working. However, the screen was blank, so I was not able to get in. I went to unmenu and things there were even more strange. It was reporting the array offline, when clearly it was not, so i thought at this point I would just reboot. The only problem is I get this error. /sbin/reboot: Permission denied I received a similar permission denied error when I tried to manually run newperms. It was actually the reason I switched to the manual Linux commands. Mar 17 21:50:29 Tower in.telnetd[5819]: connect from 192.168.0.99 (192.168.0.99) (Routine) Mar 17 21:50:31 Tower login[5820]: ROOT LOGIN on '/dev/pts/0' from '192.168.0.99' (Logins) Mar 17 22:06:52 Tower emhttp: shcmd (228): /usr/sbin/hdparm -y /dev/sdb $stuff$> /dev/null (Drive related) Mar 17 22:06:52 Tower emhttp: _shcmd: shcmd (228): exit status: 126 (Other emhttp) Mar 17 22:21:54 Tower kernel: mdcmd (1497): spindown 5 (Routine) Mar 17 22:21:55 Tower kernel: mdcmd (1498): spindown 11 (Routine) Mar 17 22:22:15 Tower kernel: mdcmd (1499): spindown 0 (Routine) Mar 17 22:26:06 Tower kernel: mdcmd (1500): spindown 1 (Routine) Mar 17 22:26:07 Tower kernel: mdcmd (1501): spindown 3 (Routine) Mar 17 22:26:07 Tower kernel: mdcmd (1502): spindown 4 (Routine) Mar 17 22:26:08 Tower kernel: mdcmd (1503): spindown 6 (Routine) Mar 17 22:46:12 Tower kernel: mdcmd (1504): spindown 7 (Routine) Mar 17 22:46:13 Tower kernel: mdcmd (1505): spindown 8 (Routine) Mar 17 22:46:13 Tower kernel: mdcmd (1506): spindown 9 (Routine) Mar 17 22:46:14 Tower kernel: mdcmd (1507): spindown 10 (Routine) Mar 17 22:46:14 Tower kernel: mdcmd (1508): spindown 12 (Routine) Mar 17 22:47:01 Tower crond[1218]: exit status 126 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Mar 17 22:47:01 Tower crond[5978]: unable to exec /usr/sbin/sendmail: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null Mar 17 23:17:49 Tower kernel: mdcmd (1509): spindown 2 (Routine) Mar 17 23:18:10 Tower kernel: mdcmd (1510): spindown 9 (Routine) Mar 17 23:26:20 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:26:20 Tower unmenu[1235]: sh: /usr/sbin/smartctl: Permission denied Mar 17 23:26:21 Tower last message repeated 55 times Mar 17 23:26:21 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:26:35 Tower last message repeated 3 times Mar 17 23:26:35 Tower unmenu[1235]: sh: /sbin/modprobe: Permission denied Mar 17 23:26:35 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:26:35 Tower unmenu[1235]: sh: /usr/sbin/smartctl: Permission denied Mar 17 23:26:35 Tower last message repeated 13 times Mar 17 23:26:54 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:27:35 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:29:45 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:29:57 Tower last message repeated 2 times Mar 17 23:29:57 Tower unmenu[1235]: sh: /usr/bin/wget: Permission denied Mar 17 23:30:08 Tower last message repeated 9 times Mar 17 23:30:09 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:30:09 Tower unmenu[1235]: sh: /usr/sbin/smartctl: Permission denied Mar 17 23:30:09 Tower last message repeated 7 times Mar 17 23:45:06 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:46:03 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:46:26 Tower last message repeated 6 times Mar 17 23:47:01 Tower crond[1218]: exit status 126 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Mar 17 23:47:01 Tower crond[8643]: unable to exec /usr/sbin/sendmail: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null Mar 17 23:47:06 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:47:15 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:47:15 Tower unmenu[1235]: which: no bwm-ng in (/bin:/sbin:/usr/bin:/usr/sbin) Mar 17 23:47:18 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:47:18 Tower unmenu[1235]: which: no bwm-ng in (/bin:/sbin:/usr/bin:/usr/sbin) Mar 17 23:47:18 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:47:22 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied Mar 17 23:47:45 Tower kernel: mdcmd (1511): spindown 5 (Routine) Mar 17 23:49:07 Tower unmenu[1235]: sh: /usr/bin/strings: Permission denied
March 18, 201412 yr Author So, is my best bet a hard reset and hope my flash is accessible, or should I look to try something else?
March 18, 201412 yr The array should be stopped and rebooted using only the stock webGUI interface, e.g., "/tower".
March 18, 201412 yr Author As noted, the stock GUI is not available. When attempting to access the page, all I get is a white page. If I try restarting the webgui/emhttp, I get an error, permission denied. If I try just reboot, permission denied. Not too sure what and why things went crazy, but the system is running 5.0.4
March 19, 201412 yr Author Tried Firefox and chrome Just went and tried ie as well, same thing. It resolves, but I end up on a blank white page.
March 19, 201412 yr Classic event of "GUI goes unresponsive"... once more. In that case it's good to have the clean powerdown script installed (see my sig). If not, well - 2 options: 1. search the forum for instructions how to stop the array and unmount the drives (preferred option) 2. hit the reset button (will cause a parity check after unclean shutdown) Take the opportunity to install the powerdown script.
March 19, 201412 yr Author Classic event of "GUI goes unresponsive"... once more. In that case it's good to have the clean powerdown script installed (see my sig). If not, well - 2 options: 1. search the forum for instructions how to stop the array and unmount the drives (preferred option) 2. hit the reset button (will cause a parity check after unclean shutdown) Take the opportunity to install the powerdown script. Thats what was so strange. I have powerdown installed and when executed I got permission denied there too. I tried everything and in the event did the dirty with a press of the reset button. Array came up stopped because of not supported shutdown. GUI was back and I was able to execute powerdown -r again, so in that regard things are functional again. As to what happened before, I have no idea.
March 19, 201412 yr Author Wiki - To cleanly Stop the array from the command line I knew this had to be out there. I ended up pressing the reset button this morning. I will certainly note these directions in the event there is a next time. But lets hope not.
March 19, 201412 yr Author It was the first time in a while that things got all screwy like that. The last time my flash was all geeked out and I couldn't upgrade. Had to format/checkdisk and start over after which things were fine. But other than that I consider myself lucky to have not experienced anything too crazy. Any time something like this happens, I get so nervous thinking about the data that is out there. Sure, it can most all be replaced, but not my idea of fun. Ideal would be a second server I could mirror certain directories to.
Archived
This topic is now archived and is closed to further replies.