March 13, 201313 yr This happens quite frequently when I try to power down the machine. Its quite frustrating. I have to do some guesswork and kill processes randomly because I really have no idea what process is what and how to identify which one is holding up the array. This time lsof | grep /mnt also returned no result. Neither did lsof /dev/md* So I saw some other thread and did a "ps ux" and that reported back root@NAS:~# ps ux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 828 284 ? Ss Mar12 0:05 init root 2 0.0 0.0 0 0 ? S Mar12 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S Mar12 0:00 [ksoftirqd/0] root 6 0.0 0.0 0 0 ? S Mar12 0:00 [migration/0] root 7 0.0 0.0 0 0 ? S Mar12 0:00 [migration/1] root 9 0.0 0.0 0 0 ? S Mar12 0:00 [ksoftirqd/1] root 11 0.0 0.0 0 0 ? S Mar12 0:00 [migration/2] root 13 0.0 0.0 0 0 ? S Mar12 0:00 [ksoftirqd/2] root 14 0.0 0.0 0 0 ? S Mar12 0:00 [migration/3] root 16 0.0 0.0 0 0 ? S Mar12 0:00 [ksoftirqd/3] root 17 0.0 0.0 0 0 ? S< Mar12 0:00 [khelper] root 18 0.0 0.0 0 0 ? S Mar12 0:00 [kworker/u:1] root 162 0.0 0.0 0 0 ? S Mar12 0:00 [sync_supers] root 164 0.0 0.0 0 0 ? S Mar12 0:00 [bdi-default] root 166 0.0 0.0 0 0 ? S< Mar12 0:00 [kblockd] root 283 0.0 0.0 0 0 ? S< Mar12 0:00 [ata_sff] root 293 0.0 0.0 0 0 ? S Mar12 0:00 [khubd] root 303 0.0 0.0 0 0 ? S Mar12 0:01 [kworker/2:1] root 402 0.0 0.0 0 0 ? S< Mar12 0:00 [rpciod] root 428 0.0 0.0 0 0 ? S Mar12 0:00 [kswapd0] root 489 0.0 0.0 0 0 ? S Mar12 0:00 [fsnotify_mark] root 509 0.0 0.0 0 0 ? S< Mar12 0:00 [nfsiod] root 512 0.0 0.0 0 0 ? S< Mar12 0:00 [cifsiod] root 518 0.0 0.0 0 0 ? S< Mar12 0:00 [crypto] root 696 0.0 0.0 0 0 ? S< Mar12 0:00 [deferwq] root 697 0.0 0.0 0 0 ? S Mar12 0:01 [kworker/2:2] root 724 0.0 0.0 2332 928 ? S<s Mar12 0:00 /sbin/udevd --d root 833 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_0] root 844 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_1] root 845 0.0 0.0 0 0 ? S Mar12 0:00 [kworker/u:2] root 850 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_2] root 851 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_3] root 852 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_4] root 853 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_5] root 854 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_6] root 855 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_7] root 862 0.0 0.0 0 0 ? S Mar12 0:00 [scsi_eh_8] root 863 0.0 0.0 0 0 ? S Mar12 0:00 [usb-storage] root 976 0.0 0.0 1908 612 ? Ss Mar12 0:00 /usr/sbin/syslo root 980 0.0 0.0 1856 388 ? Ss Mar12 0:00 /usr/sbin/klogd root 1086 0.0 0.0 2108 812 ? Ss Mar12 0:00 /sbin/rpc.statd root 1096 0.0 0.0 1900 540 ? Ss Mar12 0:00 /usr/sbin/inetd root 1103 0.0 0.0 4492 1564 ? Ss Mar12 0:00 /usr/sbin/ntpd root 1110 0.0 0.0 1864 644 ? Ss Mar12 0:00 /usr/sbin/acpid root 1125 0.0 0.0 1908 608 ? Ss Mar12 0:00 /usr/sbin/crond root 1654 0.0 0.0 11836 1468 ? Sl Mar12 0:04 /usr/local/sbin root 1659 0.0 0.0 2644 488 ? S Mar12 0:00 /bin/bash /boot root 1660 0.0 0.0 1840 248 ? S Mar12 0:00 logger -tunmenu root 1663 0.0 0.0 3508 2156 ? S Mar12 0:00 awk -W re-inter root 3725 0.0 0.0 2860 1096 ? S Mar12 0:00 /bin/bash /var/ root 3726 0.0 0.0 2852 1092 ? S Mar12 0:00 /bin/bash /var/ root 3747 0.0 0.0 1952 560 ? S Mar12 0:00 inotifywait -m root 3748 0.0 0.0 2852 564 ? S Mar12 0:00 /bin/bash /var/ root 3750 0.0 0.0 1956 564 ? S Mar12 0:00 inotifywait -m root 3751 0.0 0.0 2872 1084 ? S Mar12 0:00 /bin/bash /var/ root 3929 2.0 0.0 0 0 ? S Mar12 20:13 [mdrecoveryd] root 3931 0.0 0.0 0 0 ? S Mar12 0:00 [spinupd] root 3932 0.0 0.0 0 0 ? S Mar12 0:00 [spinupd] root 3933 0.0 0.0 0 0 ? S Mar12 0:00 [spinupd] root 3934 0.0 0.0 0 0 ? S Mar12 0:00 [spinupd] root 4026 6.4 0.0 0 0 ? S Mar12 65:03 [unraidd] root 4040 0.0 0.0 0 0 ? S< Mar12 0:00 [reiserfs] root 4207 0.0 0.0 1856 532 tty1 Ss+ Mar12 0:00 /sbin/agetty 38 root 4208 0.0 0.0 1856 536 tty2 Ss+ Mar12 0:00 /sbin/agetty 38 root 4209 0.0 0.0 1856 536 tty3 Ss+ Mar12 0:00 /sbin/agetty 38 root 4210 0.0 0.0 1856 528 tty4 Ss+ Mar12 0:00 /sbin/agetty 38 root 4211 0.0 0.0 1856 532 tty5 Ss+ Mar12 0:00 /sbin/agetty 38 root 4212 0.0 0.0 1856 532 tty6 Ss+ Mar12 0:00 /sbin/agetty 38 root 4213 0.0 0.0 2328 840 ? S< Mar12 0:00 /sbin/udevd --d root 4214 0.0 0.0 2328 840 ? S< Mar12 0:00 /sbin/udevd --d root 4381 0.0 0.0 0 0 ? S Mar12 0:27 [kworker/0:1] root 8979 0.0 0.0 0 0 ? S 00:04 0:00 [kworker/3:0] root 9020 0.0 0.0 0 0 ? S 01:13 0:29 [kworker/1:2] root 9118 0.0 0.0 0 0 ? S 02:12 0:00 [kworker/3:1] root 9268 0.0 0.0 0 0 ? S 13:58 0:00 [kworker/0:2] root 9271 0.0 0.0 0 0 ? S 13:58 0:00 [kworker/1:1] root 10047 0.0 0.0 4596 1632 ? S 14:06 0:00 /usr/bin/wget - root 10312 0.0 0.0 6844 1924 ? Ss 14:08 0:00 in.telnetd: 192 root 10313 0.0 0.0 4304 1712 pts/1 Ss 14:08 0:00 -bash root 10664 0.0 0.0 2720 1012 pts/1 R+ 14:12 0:00 ps ux Been randomly trying kill -9 [PID] with no logic whatsoever. (I dont even know what the -9 stands for] syslog attached. syslog-2013-03-13.zip
March 13, 201313 yr Author kill -9 1654 followed by kill -9 1659 and now I've lost webgui with the machine still running and "powerdown" command from the terminal just returns me to prompt. I'm a genius.
March 13, 201313 yr Author Googled Linux commands. Came across several of which I tried "halt" and poof, server shut down. Powered back up and no parity check, so I guess it was a clean shutdown.
March 13, 201313 yr Try which powerdown If it comes back with /sbin/powerdown then you have the clean powerdown script installed. This can be installed from unMenu or comes with APCUPSD plugin. Maybe other ways to get it. If so then just do /sbin/powerdown Always works for me. See here
March 13, 201313 yr I see you are running plex. I had this issue with plex when I first started using it. Have you attempted to shut down plex prior to unmounting your drives? I am not a system log expert, but I noticed that it appears that it looks like something in your crontab file is keeping your drives from unmounting.
March 13, 201313 yr Author I see you are running plex. Yes I have Plex but it is not running on the machine for some time now (including when the unmount failed) since I am upgrading disks etc. If so then just do /sbin/powerdown Always works for me. See here Yes, it returns /sbin/powerdown. Will try it next time. Today I was just going "powerdown", and that didnt work. "halt" did it at lightning speed though!
Archived
This topic is now archived and is closed to further replies.