wgstarks

Thanks Squid. I may disable checking for updates. Wish it wasn't global though. Looks like CA Auto Update isn't compatible with 6.1.9 though. Hopefully at some point soon I'll be able to schedule a tech support session with LT and figure out exactly what's causing the issue with current versions of unRAID and what hardware I'll have to replace. LT support is rather expensive though so I'm having to wait for a time when I can be sure of no interruptions. Don't want to be paying $90/hr while I'm trying to unclog the toilet.

Previous post was clipped. Here's the rest- I've reverted back to 2017.02.05 which was the latest working version I had in backup. This is working good for me for now, I'll just have to remember not to update (unless you have some other suggestion?). Hopefully gfgardim will correct the min version level so that CA won't keep prompting me to update (if I'm understanding that process correctly).

@kyis Looks like it's not in the list. root@Brunnhilde:~# lsblk -h Usage: lsblk [options] [<device> ...] Options: -a, --all print all devices -b, --bytes print SIZE in bytes rather than in human readable format -d, --nodeps don't print slaves or holders -D, --discard print discard capabilities -e, --exclude <list> exclude devices by major number (default: RAM disks) -f, --fs output info about filesystems -h, --help usage information (this) -i, --ascii use ascii characters only -m, --perms output info about permissions -l, --list use list format ouput -n, --noheadings don't print headings -o, --output <list> output columns -P, --pairs use key="value" output format -r, --raw use raw output format -t, --topology output info about topology Available columns: NAME device name KNAME internal kernel device name MAJ:MIN major:minor device number FSTYPE filesystem type MOUNTPOINT where the device is mounted LABEL filesystem LABEL UUID filesystem UUID RO read-only device RM removable device MODEL device identifier SIZE size of the device STATE state of the device OWNER user name GROUP group name MODE device node permissions ALIGNMENT alignment offset MIN-IO minimum I/O size OPT-IO optimal I/O size PHY-SEC physical sector size LOG-SEC logical sector size ROTA rotational device SCHED I/O scheduler name RQ-SIZE request queue size TYPE device type DISC-ALN discard alignment offset DISC-GRAN discard granularity DISC-MAX discard max bytes DISC-ZERO discard zeroes data For more information see lsblk(8). root@Brunnhilde:~#

@kyis Here's the results- root@Brunnhilde:~# lsblk -nbP -o name,type,label,size,mountpoint,fstype,serial lsblk: unknown column: serial root@Brunnhilde:~# lsblk -nbP -o name,type,label,size,mountpoint,fstype NAME="md1" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk1" FSTYPE="" NAME="md2" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk2" FSTYPE="" NAME="md3" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk3" FSTYPE="" NAME="md4" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk4" FSTYPE="" NAME="md5" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk5" FSTYPE="" NAME="md6" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk6" FSTYPE="" NAME="sda" TYPE="disk" LABEL="" SIZE="320072933376" MOUNTPOINT="" FSTYPE="" NAME="sda1" TYPE="part" LABEL="" SIZE="320071532544" MOUNTPOINT="/mnt/disks/ST332062_0A" FSTYPE="ext4" NAME="sdb" TYPE="disk" LABEL="" SIZE="15512174592" MOUNTPOINT="" FSTYPE="" NAME="sdb1" TYPE="part" LABEL="UNRAID" SIZE="15512173568" MOUNTPOINT="/boot" FSTYPE="vfat" NAME="sdc" TYPE="disk" LABEL="" SIZE="8001563222016" MOUNTPOINT="" FSTYPE="" NAME="sdc1" TYPE="part" LABEL="" SIZE="8001563172352" MOUNTPOINT="" FSTYPE="" NAME="sdd" TYPE="disk" LABEL="" SIZE="1000204886016" MOUNTPOINT="" FSTYPE="" NAME="sdd1" TYPE="part" LABEL="" SIZE="1000203091968" MOUNTPOINT="/mnt/cache" FSTYPE="xfs" NAME="sde" TYPE="disk" LABEL="" SIZE="8001563222016" MOUNTPOINT="" FSTYPE="" NAME="sde1" TYPE="part" LABEL="" SIZE="2199023255040" MOUNTPOINT="" FSTYPE="" NAME="sdf" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" NAME="sdf1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" NAME="sdg" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" NAME="sdg1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" NAME="sdh" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" NAME="sdh1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" NAME="sdi" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" NAME="sdi1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" NAME="sdj" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" NAME="sdj1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" NAME="sdk" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" NAME="sdk1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" NAME="loop0" TYPE="loop" LABEL="" SIZE="21474836480" MOUNTPOINT="" FSTYPE="btrfs" root@Brunnhilde:~# serial showed "unknown column" so I dropped it.

If you're using a mobile browser you'll need to switch to a desktop.

There is a "Notes" section that allows you to record which bay the drive is in. Even better is a spreadsheet with all the info (stored on another machine) since if your server won't boot you'll really be up a creek.

I notice that the new version has much more empty space between display selections (Disks, Ops, etc). Was this necessary to fix some issue or could it be reverted back to the previous view? Was nice not to have to do a bunch of swiping.

Looks like nothing? root@Brunnhilde:~# lsblk -nbP -o name,type,label,size,mountpoint,fstype,serial 2>/dev/null root@Brunnhilde:~#

@kyis thanks for the link. I'll grab the previous version from there if I don't still have it in CA Backup.

Thanks. I may just uninstall this until these issues are addressed then. I've got an 8TB drive in hot standby so probably won't need to preclear anything soon. Hopefully I'll get the issue with current versions of unRAID resolved by then and this will all be moot anyway.

Wish I could. Apparently there is some incompatibility between 6.2+ and some SuperMicro motherboards and/or Intel CPU's. https://forums.lime-technology.com/topic/53728-server-no-longer-boots-into-624-only-619/ It is my understanding that CA will prevent installation of plugins that aren't compatible with the installed version of unRAID? Is there some way to revert to the previous version of this plugin?

Anyone have any ideas. Not sure if this is something serious. Should I uninstall the preclear plugin until this problem is addressed?

Thanks

Saw a comment in another thread that when running OpenVPN-AS as a docker on my unRAID server it won't be possible to access the other services provided by the server (shares, other dockers, webgui, etc). Is this true?

Wasn't really an uninstall. My server just decided it doesn't want to reliably boot 6.2+ anymore. Seems to be some problem with SuperMicro motherboards and/or Xeon E3-1230's. I'll need to check and see if there are any other plugins installed that won't run on 6.1.9.

Is there still a folder on the flash drive /config/plugins/ca.update.applications with .cron files in there? Looks like that's it. Should I move it to "Removed Plugins"?

Not sure, but I think this is an Auto Update error- Feb 19 04:45:01 Brunnhilde crond[1658]: exit status 127 from user root /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1 I no longer have the Auto Update plugin installed though. Diagnostics

After updating to 2017.02.16a I'm seeing this in the UD section of Main- Warning: array_filter() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/preclear.disk/assets/lib.php on line 83. Uninstalled the preclear plugin and the warning disappeared, but came right back when I reinstalled. Diagnostics

Exit status 2 means the file system is full and the script sa is unable to write to the log files. Can you show the result of df -h /var and df -h /var/log Results- root@Brunnhilde:~# df -h /var Filesystem Size Used Avail Use% Mounted on - 7.8G 725M 7.1G 10% / root@Brunnhilde:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 128M 7.0M 122M 6% /var/log That looks alright. Have you tried to uninstall and re-install the plugin? Looks like that fixed it. Thanks bonienl.

Exit status 2 means the file system is full and the script sa is unable to write to the log files. Can you show the result of df -h /var and df -h /var/log Results- root@Brunnhilde:~# df -h /var Filesystem Size Used Avail Use% Mounted on - 7.8G 725M 7.1G 10% / root@Brunnhilde:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 128M 7.0M 122M 6% /var/log

My fault. I had meant that you should use "Prefered" if it was available, but I didn't express that very well.

Tried posting this in general support and I hate double posting but maybe this might get more notice. I'm getting an error in my log every 60 seconds for the past few days- Feb 16 22:42:01 Brunnhilde crond[1658]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Should be set to "Only" or "Prefered" if you have that option.

Already reported- http://lime-technology.com/forum/index.php?topic=48972.msg539675#msg539675

Seems to be a problem with the name of the iPhone app. Did you change the name?