November 24, 20169 yr Not sure if it really matters or not but I usually change "prefer" to "cache only" after Mover is finished.
November 24, 20169 yr Author v1.8.1 is available ! 2016-11-24 - 1.8.1 - Create correct config file (unbalance.conf) - Fix UI not opening from settings page - Check for config file presence This should fix a couple of issues with the plugin. Hope it works ok for you !
November 24, 20169 yr Author v1.8.2 is available ! 2016-11-24 - 1.8.2 - Fix other references of unbalance.cfg - Improve flag handling Hope this fixes some issues that have been reported.
November 25, 20169 yr Author v1.8.3 is available ! 2016-11-25 - 1.8.3 - Keep separate config files (one for plugin system, one for app) Well, just restored functionality as it was in 1.8.0 (separate config files), but made some changes to how the server component handles the settings. If you installed 1.8.1, 1.8.2 or are having any problems, delete /boot/config/plugins/unbalance/unbalance.conf (you will need to setup your options again )
November 29, 20169 yr Performed a dry run calc and it gave me all these permissions issues. As instructed, ran Fix Common Problems and there were no problems with permissions. I don't use Dockers. Please advise.
December 1, 20169 yr Author Performed a dry run calc and it gave me all these permissions issues. As instructed, ran Fix Common Problems and there were no problems with permissions. I don't use Dockers. Please advise. Hi Fuggin, those permissions issues are more like warnings. If Fix Common Problems doesn't find any issues, you should be ok. Also, if you run calc again after Fix Common Problems, do you still get the warnings ? In any case, I'll check if I'm on sync with FCP issue detection.
December 1, 20169 yr Author v1.8.4 is available. 2016-12-01 - 1.8.4 - Fix open UI from settings (6.2.x) This should solve the issue with opening the UI from the settings page for all unRAID versions.
December 2, 20169 yr Performed a dry run calc and it gave me all these permissions issues. As instructed, ran Fix Common Problems and there were no problems with permissions. I don't use Dockers. Please advise. Hi Fuggin, those permissions issues are more like warnings. If Fix Common Problems doesn't find any issues, you should be ok. Also, if you run calc again after Fix Common Problems, do you still get the warnings ? In any case, I'll check if I'm on sync with FCP issue detection. Yes...I get the warnings all the time even after doing a rescan of FCP. I just didn't want to risk moving anything until I was sure. Thx!
December 8, 20169 yr Hi all, I have a similar problem with the permission errors in unBALANCE. I run a 'calculate' and it returns 12,000 "file" permission errors (no "directory" issues) such as:- 12000 files(s) with a permission other than '-rw-rw-rw-' or '-r--r--r--' I run the FCP 'Docker safe' permissions tool and it seems to do nothing to as far as unBALANCE is concerned. Running another 'calculate' returns the same amount of errors. I manually edited permissions using the command line and got it down to 100 or so 'file' permission errors but it created two new 'directory' issues. I then ran the FCP tool again thinking this might work now however it fixed the directory issues but returned the 12000 file permission errors again. I also found a couple of scripts from gfjardim on these forums and they were:- find /mnt/user/ -type f ! \( -user "nobody" -o -group "users" -o -perm "660" \) -exec chmod 660 '{}' \; -exec chown nobody:users '{}' \; find /mnt/user/ -type d ! \( -user "nobody" -o -group "users" -o -perm "770" \) -exec chmod 770 '{}' \; -exec chown nobody:users '{}' \; I cant follow exactly what the commands are doing (lack of knowledge) but i assume its 'find everything that isn't nobody:users and perms 770 for dirs (or 660 for files) and changes it to this. I ran these two commands on /mnt/disk1/ as going by the unBALANCE log this is disk with the 'offending' files on it. I also tried changing a portion of the scripts above to -exec chmod 666 as this is what i believe unBALANCE is looking for but this also didn't work. I don't want to run the move without correct permissions for obvious reasons and would love to get this working properly. I am sure this is user or configuration error my end but i just cant work it out. Any help appreciated. Cheers. I tried both of these and they also didn't remove the permission issues.
December 9, 20169 yr Author ... I manually edited permissions using the command line and got it down to 100 or so 'file' permission errors but it created two new 'directory' issues. I then ran the FCP tool again thinking this might work now however it fixed the directory issues but returned the 12000 file permission errors again. ... Hi mgladwin, Hopefully you can help me look into this. In your log file (/boot/logs/unbalance.log), you should have a lot of lines starting with these messages: perms:User != nobody perms:Group != users perms:Folder perms != rwxrwxrwx perms:File perms != rw-rw-rw- or -r--r--r-- (mostly the last one, by what you're saying) Can you sample a couple of them and check the actual owner/permission on your disk ? Feel free to pm, if you need some assistance.
December 9, 20169 yr ... I manually edited permissions using the command line and got it down to 100 or so 'file' permission errors but it created two new 'directory' issues. I then ran the FCP tool again thinking this might work now however it fixed the directory issues but returned the 12000 file permission errors again. ... Hi mgladwin, Hopefully you can help me look into this. In your log file (/boot/logs/unbalance.log), you should have a lot of lines starting with these messages: perms:User != nobody perms:Group != users perms:Folder perms != rwxrwxrwx perms:File perms != rw-rw-rw- or -r--r--r-- (mostly the last one, by what you're saying) Can you sample a couple of them and check the actual owner/permission on your disk ? Feel free to pm, if you need some assistance. Hi jbrodriguez, Thanks for your reply. Here are a couple of lines from my unBALANCE log as requested:- I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU2.TTF I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU3.DAH Here is the permissions as I see them on disk:- -rw-rw-rw- 1 nobody users 117028 Mar 31 2003 MENU2.TTF -rw-rw-rw- 1 nobody users 9578 Jul 5 2005 MENU3.DAH I hope this is what you meant. Are those lines in the log checking the file perms are either rw-rw-rw- or -r--r--r-- ? Or are the lines in the log the permission warnings?
December 9, 20169 yr Author ... Here are a couple of lines from my unBALANCE log as requested:- I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU2.TTF I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU3.DAH Here is the permissions as I see them on disk:- -rw-rw-rw- 1 nobody users 117028 Mar 31 2003 MENU2.TTF -rw-rw-rw- 1 nobody users 9578 Jul 5 2005 MENU3.DAH I hope this is what you meant. Are those lines in the log checking the file perms are either rw-rw-rw- or -r--r--r-- ? Or are the lines in the log the permission warnings? Thanks for the quick reply mgladwin ! Yes, the app checks that the files have either a "rw-rw-rw-" or a "r--r--r--" permission. But I see an issue in the code: the check is inverted I'm uploading a release to fix this.
December 9, 20169 yr Author v1.8.5 is available ! 2016-12-09 - 1.8.5 - Fix logic that checks for file permissions - Fix notifyMove setting This should fix the the incorrect warnings about file permissions.
December 9, 20169 yr ... Here are a couple of lines from my unBALANCE log as requested:- I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU2.TTF I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU3.DAH Here is the permissions as I see them on disk:- -rw-rw-rw- 1 nobody users 117028 Mar 31 2003 MENU2.TTF -rw-rw-rw- 1 nobody users 9578 Jul 5 2005 MENU3.DAH I hope this is what you meant. Are those lines in the log checking the file perms are either rw-rw-rw- or -r--r--r-- ? Or are the lines in the log the permission warnings? Thanks for the quick reply mgladwin ! Yes, the app checks that the files have either a "rw-rw-rw-" or a "r--r--r--" permission. But I see an issue in the code: the check is inverted I'm uploading a release to fix this. Great work! All my warnings have gone. Thanks jbrodriguez!
December 9, 20169 yr Bizmo, ok .. I thought that the first command was the one crashing. The message is just a warning, since there are multiple instances where permission issues cause problems with rsync. The Docker Safe New Permissions resets permissions in the best possible way. I had another idea ... when it's sitting idle as you mention .. can you do a ps aux | grep unbalance and a ps aux | grep find ... that would tell us if it's really running or not Sorry it took me a while to get back, still having the same problem here. The output to those is as follows BEFORE hitting calculate root@Tower:~# ps aux | grep unbalance nobody 7700 0.0 0.0 13312 9800 ? Sl 09:06 0:00 /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 root 29430 0.0 0.0 9652 1840 pts/0 S+ 16:31 0:00 grep unbalance root@Tower:~# ps aux | grep find root 29583 0.0 0.0 9652 1880 pts/0 S+ 16:31 0:00 grep find AFTER hitting calculate root@Tower:~# ps aux | grep unbalance root 30233 0.0 0.0 9652 1800 pts/0 S+ 16:32 0:00 grep unbalance root@Tower:~# ps aux | grep find root 30243 0.0 0.0 9652 1792 pts/0 S+ 16:32 0:00 grep find
December 10, 20169 yr Author ... BEFORE hitting calculate root@Tower:~# ps aux | grep unbalance nobody 7700 0.0 0.0 13312 9800 ? Sl 09:06 0:00 /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 root 29430 0.0 0.0 9652 1840 pts/0 S+ 16:31 0:00 grep unbalance root@Tower:~# ps aux | grep find root 29583 0.0 0.0 9652 1880 pts/0 S+ 16:31 0:00 grep find AFTER hitting calculate root@Tower:~# ps aux | grep unbalance root 30233 0.0 0.0 9652 1800 pts/0 S+ 16:32 0:00 grep unbalance root@Tower:~# ps aux | grep find root 30243 0.0 0.0 9652 1792 pts/0 S+ 16:32 0:00 grep find So, it still seems to be crashing Please do the following - Disable the plugin from the unRAID settings. - From the console, type sudo -H -u nobody bash -c "/usr/local/emhttp/plugins/unbalance/unbalance -port 6237" - Open your browser to the unbalance url (http://<server>:6237) - Hit calculate It should crash, but what I'm interested in is what's shown in the console. Can you post the whole output ? Feel free to send me a pm if you prefer.
December 10, 20169 yr Author ... Great work! All my warnings have gone. Thanks jbrodriguez! That's good to know mgladwin !
December 11, 20169 yr Author v1.8.6 is available ! 2016-12-11 - 1.8.6 - Account for setuid, setgid and/or sticky bit This fixes an issue that crashed the app when files/folders had setuid, setgid and/or sticky bit set in the permissions. Thanks to Bizmo for helping troubleshoot this.
December 11, 20169 yr Attempted to get the update, but am getting this: plugin: installing: https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/unbalance.plg plugin: downloading https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/unbalance.plg plugin: downloading: https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/unbalance.plg ... done Warning: simplexml_load_file(): /tmp/plugins/unbalance.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /tmp/plugins/unbalance.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /tmp/plugins/unbalance.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error Just wanted to let you know..
December 11, 20169 yr Author ... plugin: xml parse error Just wanted to let you know.. Thanks a lot for the heads up nacat78 !
December 12, 20169 yr What speed do people get when running unbalance? Mine seems pretty low 35-45MB/s
December 12, 20169 yr Author What speed do people get when running unbalance? Mine seems pretty low 35-45MB/s Well, it's still a parity-protected write, I believe those speeds are good in general, unless you get higher speeds when you write to any of your disks (say to a user share).
December 17, 20169 yr Well I finally had room to perform some data moves. But I keep getting this error kick out. I have ran New Permissions a few times also. Can someone shed some light on what I can try or what the problem could be. It is preventing me from completely emptying a drive. I: 2016/12/17 08:00:11 core.go:808: unRaid/Videos/Picture 040.mpg I: 2016/12/17 08:00:11 core.go:808: unRaid/Videos/Picture 065.mpg I: 2016/12/17 08:00:12 core.go:808: unRaid/Videos/Picture 068.mpg I: 2016/12/17 08:00:14 core.go:808: unRaid/Videos/Picture 071.mpg I: 2016/12/17 08:00:15 core.go:808: unRaid/Videos/STUDIO_STUDIOARCH_7194612318.mp4 I: 2016/12/17 08:00:15 core.go:808: unRaid/Videos/STUDIO_TOWEROFTERRORBRIDE_7193594537.mp4 I: 2016/12/17 08:00:15 core.go:808: unRaid/Videos/STUDIO_TOWEROFTERRORBRIDE_7193690113.mp4 I: 2016/12/17 08:00:16 core.go:808: unRaid/Videos/clip-2009-09-05 12;03;38.mov I: 2016/12/17 08:00:17 core.go:808: unRaid/Videos/clip-2009-09-05 12;13;10.mov I: 2016/12/17 08:00:27 core.go:808: I: 2016/12/17 08:00:27 core.go:808: sent 83,777,541,532 bytes received 18,228 bytes 39,903,576.93 bytes/sec I: 2016/12/17 08:00:27 core.go:808: total size is 83,757,031,044 speedup is 1.00 W: 2016/12/17 08:00:27 shell.go:105: moveProgress: waitError: exit status 23 W: 2016/12/17 08:00:27 core.go:819: Move command (rsync -avRX --partial "unRaid/Videos" "/mnt/disk5/") was interrupted: exit status 23 : Partial transfer due to error I: 2016/12/17 08:00:27 unraid.go:391: Unraid Box Condition: &{NumDisks:6 NumProtected:0 Synced:2016-12-08 17:10:14 -0600 CST SyncErrs:0 Resync:0 ResyncPos:0 State:STARTED Size:7059818254336 Free:3208549273600 NewFree:3208549273600} I: 2016/12/17 08:00:27 unraid.go:392: Unraid Box SourceDiskName: I: 2016/12/17 08:00:27 unraid.go:393: Unraid Box BytesToMove: 0 I: 2016/12/17 08:00:27 unraid.go:404: Id(1); Name(disk1); Path(/mnt/disk1); Device(sdg); Type(Data); FsType(reiserfs); Free(233.6G); NewFree(233.6G); Size(1.8T); Serial(ST2000DM001-1CH164_Z1E3KGNY); Status(DISK_OK); Bin(<nil>) I: 2016/12/17 08:00:27 unraid.go:404: Id(2); Name(disk2); Path(/mnt/disk2); Device(sdc); Type(Data); FsType(reiserfs); Free(1.7T); NewFree(1.7T); Size(1.8T); Serial(ST2000DM001-1CH164_Z1E3KH8B); Status(DISK_OK); Bin(<nil>) I: 2016/12/17 08:00:27 unraid.go:404: Id(3); Name(disk3); Path(/mnt/disk3); Device(sdf); Type(Data); FsType(xfs); Free(232.1G); NewFree(232.1G); Size(1.8T); Serial(ST2000DM001-1CH164_Z1E3KHTW); Status(DISK_OK); Bin(<nil>) I: 2016/12/17 08:00:27 unraid.go:404: Id(4); Name(disk4); Path(/mnt/disk4); Device(sdb); Type(Data); FsType(xfs); Free(465.5G); NewFree(465.5G); Size(465.5G); Serial(Hitachi_HTS725050A7E630_TF0500Y9HVUEXA); Status(DISK_OK); Bin(<nil>) I: 2016/12/17 08:00:27 unraid.go:404: Id(5); Name(disk5); Path(/mnt/disk5); Device(sde); Type(Data); FsType(xfs); Free(306.6G); NewFree(306.6G); Size(465.5G); Serial(Hitachi_HTS727550A9E364_J3360081HATKJD); Status(DISK_OK); Bin(<nil>) I: 2016/12/17 08:00:27 unraid.go:404: Id(30); Name(cache); Path(/mnt/cache); Device(sdh); Type(Cache); FsType(xfs); Free(24.4G); NewFree(24.4G); Size(55.9G); Serial(OCZ-VERTEX3_OCZ-217TQ913Z1HZ8FL1); Status(DISK_OK); Bin(<nil>) I: 2016/12/17 08:00:29 core.go:921: unBALANCE - MOVE operation INTERRUPTED I: 2016/12/17 08:00:29 core.go:922: Started: Dec 17, 2016 07:25:27 Ended: Dec 17, 2016 08:00:27 Elapsed: 34m59.15s Move command (rsync -avRX --partial "unRaid/Videos" "/mnt/disk5/") was interrupted: exit status 23 : Partial transfer due to error These are the commands that were executed:
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.