February 7, 201610 yr Hi, I used the plugin manager to upgrade from 6.0 to 6.1 latest, and upgrade dynamix to the latest version After the upgrade, I rebooted the server, and started the array, but then it got stuck 'mounting disks'.. emhttp is not responding, but I can see that all disks are actually mounted (data accessible in ssh) The last logline in syslog is: emhttp: shcmd (94): /usr/local/sbin/update_cron &> /dev/null Here is the full log: Feb 7 21:07:54 NAS emhttp: Start array... Feb 7 21:07:54 NAS kernel: mdcmd (36): start STOPPED Feb 7 21:07:54 NAS kernel: unraid: allocating 26820K for 1280 stripes (4 disks) Feb 7 21:07:54 NAS kernel: md1: running, size: 1953514552 blocks Feb 7 21:07:54 NAS kernel: md2: running, size: 1953514552 blocks Feb 7 21:07:54 NAS kernel: md3: running, size: 1953514552 blocks Feb 7 21:07:54 NAS emhttp: shcmd (74): udevadm settle Feb 7 21:07:54 NAS emhttp: Mounting disks... Feb 7 21:07:54 NAS emhttp: shcmd (75): /sbin/btrfs device scan |& logger Feb 7 21:07:54 NAS logger: Scanning for Btrfs filesystems Feb 7 21:07:54 NAS emhttp: shcmd (76): mkdir -p /mnt/disk1 Feb 7 21:07:54 NAS emhttp: shcmd (77): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 |& logger Feb 7 21:07:54 NAS kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Feb 7 21:07:54 NAS kernel: REISERFS (device md1): using ordered data mode Feb 7 21:07:54 NAS kernel: reiserfs: using flush barriers Feb 7 21:07:54 NAS kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Feb 7 21:07:54 NAS kernel: REISERFS (device md1): checking transaction log (md1) Feb 7 21:07:54 NAS kernel: REISERFS (device md1): Using r5 hash to sort names Feb 7 21:07:54 NAS emhttp: shcmd (78): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 |& logger Feb 7 21:07:54 NAS emhttp: reiserfs: resizing /mnt/disk1 Feb 7 21:07:54 NAS emhttp: shcmd (79): mkdir -p /mnt/disk2 Feb 7 21:07:54 NAS emhttp: shcmd (80): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Feb 7 21:07:54 NAS kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Feb 7 21:07:54 NAS kernel: REISERFS (device md2): using ordered data mode Feb 7 21:07:54 NAS kernel: reiserfs: using flush barriers Feb 7 21:07:54 NAS kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Feb 7 21:07:54 NAS kernel: REISERFS (device md2): checking transaction log (md2) Feb 7 21:07:54 NAS kernel: REISERFS (device md2): Using r5 hash to sort names Feb 7 21:07:54 NAS emhttp: shcmd (81): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Feb 7 21:07:54 NAS emhttp: reiserfs: resizing /mnt/disk2 Feb 7 21:07:54 NAS emhttp: shcmd (82): mkdir -p /mnt/disk3 Feb 7 21:07:54 NAS emhttp: shcmd (83): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 |& logger Feb 7 21:07:54 NAS kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Feb 7 21:07:54 NAS kernel: REISERFS (device md3): using ordered data mode Feb 7 21:07:54 NAS kernel: reiserfs: using flush barriers Feb 7 21:07:54 NAS kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Feb 7 21:07:54 NAS kernel: REISERFS (device md3): checking transaction log (md3) Feb 7 21:07:54 NAS kernel: REISERFS (device md3): Using r5 hash to sort names Feb 7 21:07:54 NAS emhttp: shcmd (84): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger Feb 7 21:07:55 NAS emhttp: reiserfs: resizing /mnt/disk3 Feb 7 21:07:55 NAS emhttp: shcmd (85): mkdir -p /mnt/cache Feb 7 21:07:55 NAS emhttp: shcmd (86): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/sdf1 /mnt/cache |& logger Feb 7 21:07:55 NAS kernel: REISERFS (device sdf1): found reiserfs format "3.6" with standard journal Feb 7 21:07:55 NAS kernel: REISERFS (device sdf1): using ordered data mode Feb 7 21:07:55 NAS kernel: reiserfs: using flush barriers Feb 7 21:07:55 NAS kernel: REISERFS (device sdf1): journal params: device sdf1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Feb 7 21:07:55 NAS kernel: REISERFS (device sdf1): checking transaction log (sdf1) Feb 7 21:07:55 NAS kernel: REISERFS (device sdf1): Using r5 hash to sort names Feb 7 21:07:55 NAS emhttp: shcmd (87): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/sdf1 /mnt/cache |& logger Feb 7 21:07:55 NAS emhttp: shcmd (88): sync Feb 7 21:07:56 NAS emhttp: shcmd (89): mkdir /mnt/user0 Feb 7 21:07:56 NAS emhttp: shcmd (90): /usr/local/sbin/shfs /mnt/user0 -disks 14 -o noatime,big_writes,allow_other |& logger Feb 7 21:07:56 NAS emhttp: shcmd (91): mkdir /mnt/user Feb 7 21:07:56 NAS emhttp: shcmd (92): /usr/local/sbin/shfs /mnt/user -disks 15 5120000000 -o noatime,big_writes,allow_other -o remember=330 |& logger Feb 7 21:07:56 NAS emhttp: shcmd (93): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule:#0120 4 * * * /usr/local/sbin/mover |& logger#012" Feb 7 21:07:56 NAS emhttp: shcmd (94): /usr/local/sbin/update_cron &> /dev/null Could it be that the dynamix upgrade is acting up? I thought it might be docker but I don't think its initialized yet? docker version Client version: 1.7.1 Client API version: 1.19 Go version (client): go1.4.2 Git commit (client): 786b29d4 OS/Arch (client): linux/amd64 Get http:///var/run/docker.sock/v1.19/version: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? What am I doing wrong?
February 7, 201610 yr Community Expert You mean you upgraded both before rebooting? I wonder if that scenario was ever tested. The recent separate upgrade for dynamix was only released after 6.1.7. I know there were some changes between 6.0 and 6.1 that broke a lot of plugins.
February 7, 201610 yr Author Yes (and yes, it was probably a bad call ), I don't use any other plugins, just some docker containers I don't use any other plugins, perhaps I should downgrade dynamix back? (any help on how-to would be much appreciated)
February 7, 201610 yr Author UPDATE: turns out I am using a custom plugin (running a script when disks are mounted, /usr/local/emhttp/plugins/z_custom_scripts/event/disks_mounted) I moved it from there for now, and array seems to start quickly Will have to see how to get it working w/ the new version of unRAID. Thanks!
Archived
This topic is now archived and is closed to further replies.