March 7, 201214 yr When stopping the array, the web UI says: Stop SMB...Spinning up all drives...Sync filesystems... And just sits there. I've had this once before and I got fed up and just powered off, but of course it had to parity check on the next startup so I'm somewhat reluctant to do that again. Plus it's hardly a healthy solution. Anyway, the HDD indicator light doesn't even blip which implies it's not touching the HDD.. All my apps are stopped (plex, sickbeard, transmission, couchpotato, sabnzbd) although occasionally on the cache drive I see root@Tower:~# lsof /dev/sdd1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME find 14465 root cwd DIR 8,49 432 67882 /mnt/cache/.custom/plexlib/Application Support/Plex Media Server/Metadata/TV Shows/f/6aee27ae8da036af1f7d07b83ba669fc433cc27.bundle/Contents/com.plexapp.agents.thetvdb/seasons/2/episodes/8/thumbs . It's intermittent and I don't know what's causing it to run but most of the times I try lsof /dev/sdd1 it doesn't list it. unMenu says that the array is still started but SMB is down (obviously as that's the first step). It seems to kill the WebUI and also for some reason becomes inaccessible by its name and instead I have to contact it by its IP address. lsof returns nothing (quite literally): root@Tower:~# lsof /dev/sda1 root@Tower:~# lsof /dev/sdb1 root@Tower:~# lsof /dev/sdc1 root@Tower:~# lsof /dev/sdd1 I'm currently trying just disconnecting the network cable for 5 minutes but I doubt it'll do anything Syslog: Mar 7 22:36:44 Tower emhttp_event: stopping_svcs Mar 7 22:36:44 Tower emhttp: shcmd (133): ps axc | grep -q rpc.mountd Mar 7 22:36:44 Tower emhttp: _shcmd: shcmd (133): exit status: 1 Mar 7 22:36:44 Tower emhttp: Stop SMB... Mar 7 22:36:44 Tower emhttp: shcmd (134): /etc/rc.d/rc.samba stop |& logger Mar 7 22:36:44 Tower emhttp: Spinning up all drives... Mar 7 22:36:44 Tower emhttp: shcmd (135): /usr/sbin/hdparm -S0 /dev/sdd &> /dev/null Mar 7 22:36:44 Tower emhttp: Sync filesystems... Mar 7 22:36:44 Tower emhttp: shcmd (136): sync Mar 7 22:36:44 Tower kernel: mdcmd (43): spinup 0 Mar 7 22:36:44 Tower kernel: mdcmd (44): spinup 1 Mar 7 22:36:44 Tower kernel: mdcmd (45): spinup 2 Mar 7 22:36:57 Tower emhttp: shcmd (137): /usr/local/sbin/emhttp_event unmounting_disks Mar 7 22:36:57 Tower emhttp_event: unmounting_disks Mar 7 22:37:12 Tower transmission-daemon[20708]: Saved "/mnt/cache/.custom/transmission/conf/settings.json" (bencode.c:1721) Mar 7 22:37:12 Tower transmission-daemon[20708]: DHT Saving 156 (156 + 0) nodes (tr-dht.c:366) Mar 7 22:37:12 Tower transmission-daemon[20708]: Saved "/mnt/cache/.custom/transmission/conf/dht.dat" (bencode.c:1721) Mar 7 22:37:12 Tower transmission-daemon[20708]: Port Forwarding Stopped (port-forwarding.c:181) Mar 7 22:37:12 Tower transmission-daemon[20708]: Port Forwarding (UPnP) Stopping port forwarding through "http://192.168.0.1:80/WANIPConnection", service "urn:schemas-up np-org:service:WANIPConnection:1" (upnp.c:169) Mar 7 22:37:12 Tower transmission-daemon[20708]: Port Forwarding State changed from "Forwarded" to "Not forwarded" (port-forwarding.c:93) Mar 7 22:37:12 Tower transmission-daemon[20708]: Closing session Mar 7 22:37:14 Tower plex-rc.plex: Stopping Plex... Mar 7 22:37:15 Tower plex-rc.plex: PMS is still runnig Mar 7 22:37:15 Tower plex-rc.plex: PMS with PID 10670 killed Mar 7 22:37:15 Tower plex-rc.plex: PMS is still runnig Mar 7 22:37:15 Tower plex-rc.plex: PMS with PID 20462 killed Mar 7 22:42:05 Tower unmenu-status: Starting unmenu web-server Mar 7 22:43:36 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:44:18 Tower last message repeated 100 times Mar 7 22:44:29 Tower last message repeated 51 times Mar 7 22:45:17 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:45:32 Tower last message repeated 38 times Mar 7 22:45:37 Tower dhcpcd[941]: eth0: carrier lost Mar 7 22:45:37 Tower kernel: tg3 0000:02:00.0: eth0: Link is down Mar 7 22:45:48 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:46:17 Tower last message repeated 100 times Mar 7 22:46:25 Tower dhcpcd[941]: eth0: carrier acquired Mar 7 22:46:25 Tower kernel: tg3 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex Mar 7 22:46:25 Tower kernel: tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX Mar 7 22:46:25 Tower dhcpcd[941]: eth0: rebinding lease of 192.168.0.2 Mar 7 22:46:26 Tower dhcpcd[941]: eth0: acknowledged 192.168.0.2 from 192.168.0.1 Mar 7 22:46:26 Tower dhcpcd[941]: eth0: checking for 192.168.0.2 Mar 7 22:46:30 Tower dhcpcd[941]: eth0: leased 192.168.0.2 for 3600 seconds Mar 7 22:46:30 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:46:42 Tower last message repeated 75 times Mar 7 22:46:47 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:47:18 Tower last message repeated 134 times Mar 7 22:47:18 Tower last message repeated 24 times Mar 7 22:47:22 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:47:56 Tower last message repeated 167 times Mar 7 22:48:03 Tower last message repeated 67 times Mar 7 22:48:09 Tower dhcpcd[941]: eth0: carrier lost Mar 7 22:48:09 Tower kernel: tg3 0000:02:00.0: eth0: Link is down Mar 7 22:48:12 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:48:55 Tower last message repeated 100 times Mar 7 22:50:05 Tower last message repeated 168 times Mar 7 22:50:19 Tower last message repeated 66 times Mar 7 22:50:27 Tower dhcpcd[941]: eth0: carrier acquired Mar 7 22:50:27 Tower kernel: tg3 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex Mar 7 22:50:27 Tower kernel: tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX Mar 7 22:50:27 Tower dhcpcd[941]: eth0: rebinding lease of 192.168.0.2 Mar 7 22:50:28 Tower dhcpcd[941]: eth0: acknowledged 192.168.0.2 from 192.168.0.1 Mar 7 22:50:28 Tower dhcpcd[941]: eth0: checking for 192.168.0.2 Mar 7 22:50:33 Tower dhcpcd[941]: eth0: leased 192.168.0.2 for 3600 seconds Mar 7 22:50:34 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:50:44 Tower last message repeated 65 times Mar 7 22:50:50 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:51:26 Tower last message repeated 167 times Mar 7 22:51:48 Tower last message repeated 120 times Mar 7 22:51:52 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:52:28 Tower last message repeated 167 times Mar 7 22:52:51 Tower last message repeated 139 times Mar 7 22:53:32 Tower sshd[15163]: Accepted password for root from 192.168.0.9 port 49454 ssh2 Mar 7 22:53:32 Tower sshd[15217]: lastlog_filetype: Couldn't stat /var/log/lastlog: No such file or directory Mar 7 22:53:32 Tower sshd[15217]: lastlog_openseek: /var/log/lastlog is not a file or directory! Mar 7 22:53:32 Tower sshd[15217]: lastlog_filetype: Couldn't stat /var/log/lastlog: No such file or directory Mar 7 22:53:32 Tower sshd[15217]: lastlog_openseek: /var/log/lastlog is not a file or directory! Mar 7 22:53:34 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:54:10 Tower last message repeated 143 times Mar 7 22:54:40 Tower last message repeated 158 times Mar 7 22:54:46 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:55:16 Tower last message repeated 169 times Mar 7 22:55:21 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:55:58 Tower last message repeated 167 times Mar 7 22:56:19 Tower last message repeated 118 times Mar 7 22:56:26 Tower plex-rc.plex: Nothing to Stop Mar 7 22:56:58 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:57:28 Tower last message repeated 129 times Mar 7 22:57:34 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:58:04 Tower last message repeated 156 times Mar 7 22:58:10 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:58:42 Tower last message repeated 134 times Mar 7 22:59:07 Tower last message repeated 126 times Mar 7 22:59:15 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:59:15 Tower last message repeated 29 times Mar 7 22:59:22 Tower unmenu[15446]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M Mar 7 22:59:57 Tower last message repeated 167 times Mar 7 23:00:07 Tower last message repeated 72 times Mar 7 23:00:14 Tower unmenu[3269]: bad method - 311871 22365842 181759809 3880860 228555 21392311 172974664 16008790 0 4600390 19916390311871-^M
March 7, 201214 yr Author It seems even my server is now bored, all drives except the cache drive have now spun down. I assume the cache drive is still spun up because I had to kill a few things that run from it a little while after. Though here's a thing - why does the cache drive even need to be unmounted when the array stops? Maybe I should just remove it as the cache drive and have it permanently mounted for my apps. EDIT: It eventually stopped. I went through trying a load of different things, including killing the cache_dirs process, and even doing a ps for "bash". Saw that there were a couple of notify things running (including a sickbeard one for some reason, a command telling sickbeard that the array is shutting down despite the fact that sickbeard was already dead), and killing that was the final straw that eventually lead to the array shutting down properly. Either way, it seems that it's caused by a load of random things, half of which I can't even remember, needing to be killed. I'd mark this as solved but really it's not..
March 7, 201214 yr Author Sorry to triple post but they're all significant updates. So now I just had the exact opposite problem in that the array would not finish starting. It was of course plugin related again - just curious as to how I go about adding a delay on plugin initialisation on startup? The general advice I've heard is simply "add a delay" with no indication as to how. I looked in the /boot/config/go script and there was no mention of plugins. Or better still a way to get whatever program/script tells emhttp "the array is now started" (it goes in the syslog so there is clearly some kind of signal) to also say "now is probably a better time to start plugins than when we start starting the array".
April 16, 201214 yr Did you figure out how to add a delay? I bought a 16gb flash drive to install my plugins to but I need to be able to start snap first before the others to mount it.
Archived
This topic is now archived and is closed to further replies.