August 22, 201411 yr I've been running two servers for a few years now. Server 1 and server 2. Server 2 has recently starting playing up. When it boots, it starts and runs. I can add content and remove content. Parity syncs fine. I've added unmenu and dynamix and some plugins on both servers. Both running 5.0.5 On server 2 it all installs fine but it doesn't keep dynamix after a reboot. It keeps the plugins working but doesn't show in the web GUI. I know this because it keeps sending me emails. SSH stops working after a while too. If it's left for a few weeks the web GUI either doesn't come up or it does and when I select take array offline it seems to freeze. Only way around is turn switch it off, start it again and let it sync parity. Attached is the current syslog. Is there anything else I need to provide to get help? I've got older syslogs which quite likely has valuable info regarding the shutdown but they are quite large. Here are some snippets taken from the end of them: Aug 1 19:29:52 Tower2 powerdown[28663]: Initiating Shutdown with '' Aug 1 19:29:52 Tower2 shutdown[28664]: shutting down for system halt Aug 1 19:29:53 Tower2 init: Switching to runlevel: 0 Aug 1 19:29:55 Tower2 rc.unRAID[28683][28684]: Powerdown V2.06 Aug 1 19:29:55 Tower2 rc.unRAID[28683][28685]: Stopping Plugins. Aug 1 19:29:55 Tower2 rc.unRAID[28683][28693]: Running: "/etc/rc.d/rc.cachedirs stop" Aug 1 19:29:55 Tower2 cache_dirs: killing cache_dirs process 11051 Aug 1 19:30:00 Tower2 rc.unRAID[28683][28696]: cache_dirs stopped Aug 1 19:30:00 Tower2 rc.unRAID[28683][28719]: Running: "/etc/rc.d/rc.sysstat stop" Aug 1 19:30:00 Tower2 rc.unRAID[28683][28723]: Stopping unRAID. Aug 1 19:30:01 Tower2 rc.unRAID[28683][28746]: Killing active pids on the array drives Aug 1 19:30:01 Tower2 rc.unRAID[28683][28749]: Cannot stat /mnt/cache: No such file or directory Aug 1 19:30:01 Tower2 rc.unRAID[28683][28749]: Cannot stat /mnt/cache: No such file or directory Aug 1 19:30:01 Tower2 rc.unRAID[28683][28750]: Sync filesystems Aug 1 19:30:02 Tower2 rc.unRAID[28683][28756]: Umounting the drives Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md1 umounted Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md2 umounted Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md3 umounted Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md4 umounted Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: /dev/md5 umounted Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: /dev/md6 umounted Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: umount2: Device or resource busy Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: umount: /mnt/disk7: device is busy. Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: (In some cases useful info about processes that use Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: the device is found by lsof( or fuser(1)) Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: umount2: Device or resource busy Aug 1 19:30:03 Tower2 rc.unRAID[28683][28769]: Active pids left on the array drives Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: USER PID ACCESS COMMAND Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: /dev/md7: root 28629 ..c.. find Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: Aug 1 19:30:03 Tower2 rc.unRAID[28683][28773]: Stopping the Array Aug 1 19:30:03 Tower2 rc.unRAID[28683][28779]: /root/mdcmd: line 11: echo: write error: Device or resource busy Aug 1 19:30:03 Tower2 kernel: mdcmd (161): stop Aug 1 19:30:03 Tower2 kernel: md: 2 devices still in use. Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: --- /tmp/mdcmd.28683.1^I2014-08-01 19:30:03.544252359 +0100 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: +++ /tmp/mdcmd.28683.2^I2014-08-01 19:30:08.553930818 +0100 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: @@ -124,7 +124,7 @@ Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevSize.7=1465138552 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevId.7=SAMSUNG_HD154UI_S1XWJ1KZ204639 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevNumErrors.7=0 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: -rdevLastIO.7=1406917803 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: +rdevLastIO.7=1406917808 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevSpinupGroup.7=0 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: diskNumber.8=8 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: diskName.8= Aug 19 16:39:49 Tower2 powerdown[9139]: Powerdown initiated Aug 19 16:39:49 Tower2 powerdown[9143]: Powerdown V2.06 Aug 19 16:39:49 Tower2 rc.unRAID[9145][9146]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts. Aug 19 16:39:49 Tower2 powerdown[9151]: Initiating Shutdown with '' Aug 19 16:39:49 Tower2 shutdown[9152]: shutting down for system halt Aug 19 16:39:49 Tower2 init: Switching to runlevel: 0 Aug 19 16:39:53 Tower2 emhttp: Unmounting disks... Aug 19 16:39:53 Tower2 emhttp: shcmd (309): umount /mnt/disk7 |& logger Aug 19 16:39:53 Tower2 logger: umount: /mnt/disk7: device is busy. Aug 19 16:39:53 Tower2 logger: (In some cases useful info about processes that use Aug 19 16:39:53 Tower2 logger: the device is found by lsof( or fuser(1)) Aug 19 16:39:53 Tower2 emhttp: Retry unmounting disk share(s)... Aug 19 16:39:56 Tower2 rc.unRAID[9168][9169]: Powerdown V2.06 Aug 19 16:39:56 Tower2 rc.unRAID[9168][9170]: Stopping Plugins. Aug 19 16:39:56 Tower2 rc.unRAID[9168][9178]: Running: "/etc/rc.d/rc.cachedirs stop" Aug 19 16:39:58 Tower2 emhttp: Unmounting disks... Aug 19 16:39:58 Tower2 emhttp: shcmd (310): umount /mnt/disk7 |& logger Aug 19 16:39:58 Tower2 logger: umount: /mnt/disk7: device is busy. Aug 19 16:39:58 Tower2 logger: (In some cases useful info about processes that use Aug 19 16:39:58 Tower2 logger: the device is found by lsof( or fuser(1)) Aug 19 16:39:58 Tower2 emhttp: Retry unmounting disk share(s)... Aug 19 16:40:01 Tower2 rc.unRAID[9168][9181]: cache_dirs stopped Aug 19 16:40:01 Tower2 rc.unRAID[9168][9204]: Running: "/etc/rc.d/rc.sysstat stop" Aug 19 16:40:01 Tower2 rc.unRAID[9168][9208]: Stopping unRAID. Aug 19 16:40:02 Tower2 rc.unRAID[9168][9231]: Killing active pids on the array drives Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/user/*: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/user/*: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/cache: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/cache: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9235]: Sync filesystems Aug 19 16:40:03 Tower2 rc.unRAID[9168][9237]: Umounting the drives Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md1: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md1 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md2: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md2 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md3: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md3 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md4: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md4 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md5: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md5 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md6: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md6 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Device or resource busy Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /mnt/disk7: device is busy. Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: (In some cases useful info about processes that use Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: the device is found by lsof( or fuser(1)) Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Device or resource busy Aug 19 16:40:03 Tower2 rc.unRAID[9168][9249]: Active pids left on the array drives Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: USER PID ACCESS COMMAND Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: /dev/md7: root 8718 ..c.. find Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: Aug 19 16:40:03 Tower2 rc.unRAID[9168][9253]: Stopping the Array Aug 19 16:40:03 Tower2 rc.unRAID[9168][9259]: /root/mdcmd: line 11: echo: write error: Device or resource busy Aug 19 16:40:03 Tower2 kernel: mdcmd (102): stop Aug 19 16:40:03 Tower2 kernel: md: 2 devices still in use. Aug 19 16:40:03 Tower2 emhttp: Unmounting disks... Aug 19 16:40:03 Tower2 emhttp: shcmd (311): umount /mnt/disk7 |& logger Aug 19 16:40:03 Tower2 logger: umount: /mnt/disk7: device is busy. Aug 19 16:40:03 Tower2 logger: (In some cases useful info about processes that use Aug 19 16:40:03 Tower2 logger: the device is found by lsof( or fuser(1)) Aug 19 16:40:03 Tower2 emhttp: Retry unmounting disk share(s)... Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: --- /tmp/mdcmd.9168.1^I2014-08-19 16:40:03.310623845 +0100 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: +++ /tmp/mdcmd.9168.2^I2014-08-19 16:40:08.320314003 +0100 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: @@ -124,7 +124,7 @@ Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevSize.7=1465138552 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevId.7=SAMSUNG_HD154UI_S1XWJ1KZ204639 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevNumErrors.7=0 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: -rdevLastIO.7=1408462803 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: +rdevLastIO.7=1408462808 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevSpinupGroup.7=0 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: diskNumber.8=8 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: diskName.8= tower2.txt
August 22, 201411 yr Aug 21 22:52:44 Tower2 kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.\ Put your flash drive in your PC and run checkdisk on it. This is sometimes a false alarm. Aug 21 22:52:44 Tower2 logger: Installing system plugins\ Aug 21 22:52:44 Tower2 logger: installing plugin: dynamix.plugin.control-2.1.1-noarch-bergware\ Aug 21 22:52:44 Tower2 logger: file /tmp/plugin-startup: successfully wrote INLINE file contents\ Aug 21 22:52:44 Tower2 logger: /bin/bash /tmp/plugin-startup ... missing Dynamix webGui plugin !!!\ Aug 21 22:52:44 Tower2 logger: failed\ Aug 21 22:52:44 Tower2 logger: installing plugin: dynamix.webGui-2.2.7-noarch-bergware\ Aug 21 22:52:44 Tower2 logger: file /tmp/plugin-startup: successfully wrote INLINE file contents\ Aug 21 22:52:44 Tower2 logger: /bin/bash /tmp/plugin-startup ... success\ You are installing dynamix plugin control in the wrong place. It needs to be in /boot/config/plugins (user plugins) but you have it in /boot/plugins (system plugins). This causes it to try to install before the dynamix webgui installs and it is failing. Also, whatever program you are using to create this syslog file is adding formatting characters to it. Never use that program to edit files on your flash drive.
August 23, 201411 yr Author Thanks for that. Thats why I get Dynamix GUI but no plugins. Sorted now. I put the flash drive in a windows PC and it offered CheckDisk straight away. It's back in and running again now. Still had to install SSH before I could use it. Maybe a issue checkdisk might have fixed?? When I tried to shutdown it couldn't unmount all the drives. I ran this command on each drive: fuser -k /mnt/disk1 It was disk 7 that wasn't unmounting for some reason. At least using that command I didn't have to do a parity check after start up. I'll have to keep an eye on it next time.
Archived
This topic is now archived and is closed to further replies.