derekos

I was able to get this working by running it manually from shell with -port 8999. But I don't know why it wont start on 6237.

Not using ipv6, only ipv4. Port not in use: root@tower:~# lsof -i :6237 root@tower~#

I have uninstalled and reinstalled. Through APPS and by pasting URL. It will not start. F: 2019/07/05 01:24:22 server.go:149: Unable to start on http: listen tcp: address tcp/6237: unknown port F: 2019/07/05 01:24:13 server.go:149: Unable to start on http: listen tcp: address tcp/6237: unknown port I: 2019/07/05 01:24:22 app.go:51: unbalance v5.5.0-1104-b9678b5-v2019.02.12b starting ... I: 2019/07/05 01:24:22 app.go:59: No config file specified. Using app defaults ... I: 2019/07/05 01:24:22 server.go:77: Starting service Server ... I: 2019/07/05 01:24:22 server.go:94: Serving files from /usr/local/emhttp/plugins/unbalance I: 2019/07/05 01:24:22 server.go:155: Server started listening https on :6238 I: 2019/07/05 01:24:22 server.go:145: Server started listening http on :6237 I: 2019/07/05 01:24:22 array.go:46: starting service Array ... I: 2019/07/05 01:24:22 planner.go:52: starting service Planner ... I: 2019/07/05 01:24:22 core.go:101: starting service Core ... F: 2019/07/05 01:24:22 server.go:149: Unable to start on http: listen tcp: address tcp/6237: unknown port W: 2019/07/05 01:24:22 core.go:116: Unable to read history: open /boot/config/plugins/unbalance/unbalance.hist: no such file or directory I: 2019/07/05 01:25:16 app.go:51: unbalance v5.5.0-1104-b9678b5-v2019.02.12b starting ... I: 2019/07/05 01:25:16 app.go:59: No config file specified. Using app defaults ... I: 2019/07/05 01:25:16 server.go:77: Starting service Server ... I: 2019/07/05 01:25:16 server.go:94: Serving files from /usr/local/emhttp/plugins/unbalance I: 2019/07/05 01:25:16 server.go:155: Server started listening https on :6238 I: 2019/07/05 01:25:16 array.go:46: starting service Array ... I: 2019/07/05 01:25:16 planner.go:52: starting service Planner ... I: 2019/07/05 01:25:16 server.go:145: Server started listening http on :6237 I: 2019/07/05 01:25:16 core.go:101: starting service Core ... F: 2019/07/05 01:25:16 server.go:149: Unable to start on http: listen tcp: address tcp/6237: unknown port W: 2019/07/05 01:25:16 core.go:116: Unable to read history: open /boot/config/plugins/unbalance/unbalance.hist: no such file or directory I: 2019/07/05 01:25:16 app.go:73: Press Ctrl+C to stop ...

As an update, I have migrated 23 drives from Reiser to XFS using UnBalance. As far as I can tell there have been no issues and no data loss. Thank you!

Thanks @Squid. I'll take a closer look. You are almost certainly right, I bet that my docker appdata location is problematic.

I'm not sure how the newperms command works. The ones I provided only change the directories/files with bad permissions, rather than resetting everything. I was mainly trying to avoid running Fix Common Problems permissions fix because it hits everything everywhere and takes forever.

Great work. Looking forward to using it. 2.0x is been working great. I've migrated two 4TB and two 3TB drives to XFS without an issue. I do have a suggestion, rather than relying on that steamroller Fix Common Problems to reset permissions (slow, locks array up, etc). Its much faster to take a scalpel to it: Just change directory to the disk with the problems: cd /mnt/diskXX If ownership problems - chmod -R nobody:user If file permission problems - find \! -perm 666 -type f -print0 | xargs -0 -I {} chmod 666 {} If directory permission problems - find \! -perm 777 -type d -print0 | xargs -0 -I {} chmod 777 {} These commands only replace file permissions as needed on the bad files/directory. Takes seconds.

I am grateful for this plugin. I just installed it and am giving it a test run moving all the files off of one drive to another. If it works as intended, this may be much easier for me to manage converting 24 drives from ReiserFS to XFS. Use unbalance to empty a drive. Re-format empty drive as XFS. Rinse and repeat. Does anyone know if there is a problem with this approach?