jbrodriguez Posted July 3, 2019 Author Share Posted July 3, 2019 Hi, checked the logs, there are several successful gathers, and towards the end of the log, some attempts that get flagged due to flag:(rsync: failed to set times on "/mnt/disk11/Media2": Operation not permitted (1)) Not sure what's the issue with that share (Media2), but for some reason rsync can't set times on it 🤷🏼♂️ Quote Link to comment
derekos Posted July 5, 2019 Share Posted July 5, 2019 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 ... Quote Link to comment
jbrodriguez Posted July 5, 2019 Author Share Posted July 5, 2019 3 hours ago, derekos said: F: 2019/07/05 01:24:22 server.go:149: Unable to start on http: listen tcp: address tcp/6237: unknown port This is the issue. It doesn't say that the port is in use, but that might be an option. Try lsof -i :6237 to find out if there's any process currently using the port. Other than that, is it possible that you're running ONLY ipv6 (no ipv4) ? Quote Link to comment
derekos Posted July 5, 2019 Share Posted July 5, 2019 (edited) Not using ipv6, only ipv4. Port not in use: root@tower:~# lsof -i :6237 root@tower~# Edited July 5, 2019 by derekos Quote Link to comment
derekos Posted July 5, 2019 Share Posted July 5, 2019 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. Quote Link to comment
jbrodriguez Posted July 5, 2019 Author Share Posted July 5, 2019 Glad to know you got it working ! You can set the port from the Settings page, so you don't have to run the plugin manually each time. Not sure what the issue is with the unknown port error. I looked it up but nothing really came up. Quote Link to comment
jbrodriguez Posted July 5, 2019 Author Share Posted July 5, 2019 On 7/3/2019 at 1:19 PM, jbrodriguez said: Hi, checked the logs, there are several successful gathers, and towards the end of the log, some attempts that get flagged due to flag:(rsync: failed to set times on "/mnt/disk11/Media2": Operation not permitted (1)) Not sure what's the issue with that share (Media2), but for some reason rsync can't set times on it 🤷🏼♂️ I got a similar error today and it was due to permission issues: trying to write to a folder for which the user didn't have permissions. Quote Link to comment
titon Posted July 5, 2019 Share Posted July 5, 2019 Hey Folks, I really enjoyed using Unbalance. I was able to leverage the plugin to consolidate some drives. I got a new drive, and was planning on doing the consolidation again, but the plugin doesn't want to function properly. I did uninstall the plugin and reinstalled. I am currently running: unBALANCE v5.5.0-1104-b9678b5-v2019.02.12b, on Unraid 6.6.5 After going into the webui, I select the "From" and "To". When I hit the "Plan" button I see the rainbow worms on the top right growing and shrinking. The problem is that it never stops. I first thought I picked a folder that was too large. I tried again with a much smaller folder ~ 100mb. It still never finish "Planning" I went into the log file and got the following lines: Quote I: 2019/07/05 11:15:15 app.go:51: unbalance v5.5.0-1104-b9678b5-v2019.02.12b starting ... I: 2019/07/05 11:15:15 app.go:59: No config file specified. Using app defaults ... I: 2019/07/05 11:15:15 server.go:77: Starting service Server ... I: 2019/07/05 11:15:15 server.go:94: Serving files from /usr/local/emhttp/plugins/unbalance I: 2019/07/05 11:15:15 array.go:46: starting service Array ... I: 2019/07/05 11:15:15 server.go:145: Server started listening http on :6237 I: 2019/07/05 11:15:15 server.go:155: Server started listening https on :6238 I: 2019/07/05 11:15:15 planner.go:52: starting service Planner ... I: 2019/07/05 11:15:15 core.go:101: starting service Core ... W: 2019/07/05 11:15:15 core.go:116: Unable to read history: open /boot/config/plugins/unbalance/unbalance.hist: no such file or directory I: 2019/07/05 11:15:15 app.go:73: Press Ctrl+C to stop ... I: 2019/07/05 11:15:38 core.go:175: Sending config I: 2019/07/05 11:15:38 core.go:180: Sending state I: 2019/07/05 11:15:38 core.go:190: Sending storage Any thoughts? Do i need to manually create the unbalance.hist file / folder? - TiTON Quote Link to comment
jbrodriguez Posted July 5, 2019 Author Share Posted July 5, 2019 2 hours ago, titon said: Any thoughts? Do i need to manually create the unbalance.hist file / folder? You don't need to create the history file. It's (re)created if not present. It seems to me like a bug ... can you open DevTools in your browser (Tools > Web Developer > Web Console in Firefox, View > Developer > Javascript Console in Chrome) and check for any errors (red messages) ? Send a screenshot of the console if you want. Quote Link to comment
bouis Posted July 6, 2019 Share Posted July 6, 2019 Bug report: it seems that unbalance won't move files with ` (that's that upper-left key) in the name. Quote Link to comment
jbrodriguez Posted July 6, 2019 Author Share Posted July 6, 2019 10 hours ago, bouis said: Bug report: it seems that unbalance won't move files with ` (that's that upper-left key) in the name. Weird. I'll do some tests. Quote Link to comment
bouis Posted July 6, 2019 Share Posted July 6, 2019 I guess I should have been more clear---it didn't delete the old files after moving, so I ended up with duplicates. Sorry for the lack of clarity; it was late and I was busy. Quote Link to comment
RGauld Posted July 7, 2019 Share Posted July 7, 2019 In regards to unbalance not working, this was your response: "Hi, checked the logs, there are several successful gathers, and towards the end of the log, some attempts that get flagged due to flag:(rsync: failed to set times on "/mnt/disk11/Media2": Operation not permitted (1)) Not sure what's the issue with that share (Media2), but for some reason rsync can't set times on it." I added the -O switch to the settings, Custom RSYNC Flags, and it appears to have solved the problem... Also, I've had an issue where the setup for unbalance specifies port 6237, but I can't get the plugin to work unless the web page I open uses ********:6238.... not a big deal, just weird.... Quote Link to comment
titon Posted July 8, 2019 Share Posted July 8, 2019 (edited) On 7/5/2019 at 1:29 PM, jbrodriguez said: You don't need to create the history file. It's (re)created if not present. It seems to me like a bug ... can you open DevTools in your browser (Tools > Web Developer > Web Console in Firefox, View > Developer > Javascript Console in Chrome) and check for any errors (red messages) ? Send a screenshot of the console if you want. Thanks for your response. I found the problem. Actually I do not know the exact reason, but its probably one of my extension in Chrome. Unbalance ran just fine in Firefox. I then tried it in Chrome under Incognito, and it worked. It didn't work on my normal Chrome, so I figure it may be one of my extension causing the problem. Thanks again for the help. Time to migrate data from the old drive to the new drive. Edited July 10, 2019 by titon typo Quote Link to comment
meep Posted July 21, 2019 Share Posted July 21, 2019 (edited) Would be grateful if someone could advise what I'm doing wrong here as I cannot quite grasp how unbalance is dealing with folders.... My Cache drive is failing and I want to move off a number of files/folders resident there. My docker share is set to all disks with cache preferred. so the files are scattered across several disks, but mainly on cache. I want to consolidate them to a single disk, swap out the cache, and move the dockers folder back. I changed my dockers share to disk 4 only and set cache to no. The share has about 2GB of data in it. I selected the Dockers share folder in unBalance for a Gather operation. After a period of thinking, it offered top move only 14kB of data. On checking, I see that my docker share contains 2x items, an Appdata folder and an OSX .DS_store file. unBalance seems to want to move the file , and ignores the folder. I proceeded to try again, selecting only the Appdata folder this time. Again, it offered to move any files inside this top level folder, but was ignoring the sub folders. Is this how it works? I went ahead and selected each folder inside Appdata individually and executed the move. Now, what its done is moved some folders entirely, some folders are partially moved (contents now on either disk 4 or remaining on cache) or some folders were not moved at all. No permissions or other errors were displayed in unValance and there's TBs of space on disk 4. Do I have a fundamental misunderstanding of how unBalance is supposed to work? The OP says it can be used to move files or folders, but it seems to be very selective about what folders it's willing to move. Why would it not move everything inside a selected parent folder? Here's what I've ended up with after asking unBalance to gather all the appdata folders to Disk4; Edited July 21, 2019 by meep Quote Link to comment
jbrodriguez Posted July 21, 2019 Author Share Posted July 21, 2019 Hi, I'm not really sure what the issue might have been. If you want to send the log (/boot/logs/unbalance.log), I'll take a look at it. Quote Link to comment
JonathanM Posted July 21, 2019 Share Posted July 21, 2019 4 hours ago, meep said: My Cache drive is failing and I want to move off a number of files/folders resident there. My docker share is set to all disks with cache preferred. so the files are scattered across several disks, but mainly on cache. I want to consolidate them to a single disk, swap out the cache, and move the dockers folder back. Unbalance is probably not the correct tool for the immediate issue of the failing cache drive. I would disable dockers and vm's in settings, set any shares with data on the cache drive to cache:yes, run the mover, then check the cache drive for any remaining files. Cache: no is definitely the incorrect option here, as mover won't touch shares with that option set. 1 Quote Link to comment
JBanner Posted July 24, 2019 Share Posted July 24, 2019 Hi, I've used Unbalance a few times successfully, but now when I try to open the webUI, I get the usual certificate alert, but it still refuses to open the WebUI.... I get chrome-error://chromewebdata/# I've uninstalled and reinstalled and no change, any ideas? Quote Link to comment
meep Posted July 24, 2019 Share Posted July 24, 2019 On 7/21/2019 at 1:17 PM, jbrodriguez said: Hi, I'm not really sure what the issue might have been. If you want to send the log (/boot/logs/unbalance.log), I'll take a look at it. Heres the log. Though I did follow @jonathanm's advice and that cleared the remaining files off. Maybe you'll spot something in the log. Am I correct to assume that selecting a directory should move any files and sub-directories therein? unbalance.log Quote Link to comment
jbrodriguez Posted July 25, 2019 Author Share Posted July 25, 2019 On 7/24/2019 at 2:28 AM, JBanner said: Hi, I've used Unbalance a few times successfully, but now when I try to open the webUI, I get the usual certificate alert, but it still refuses to open the WebUI.... I get chrome-error://chromewebdata/# I've uninstalled and reinstalled and no change, any ideas? I haven't published any changes to the plugin in a while, so I lean towards some change in your environment/browser ? Did you install any chrome extension lately ? Disabled javascript ? Changed SSL settings in Unraid ? Try looking in Chrome Dev Tools console for any possible errors. Quote Link to comment
jbrodriguez Posted July 25, 2019 Author Share Posted July 25, 2019 11 hours ago, meep said: Am I correct to assume that selecting a directory should move any files and sub-directories therein? It should move all files/sub-folders that fit into the target disks you choose. If some files/folders don't fit, it won't move them and send an email informing about this (if you have notifications on). Not sure what you attached, but that's not the log file. Quote Link to comment
Hennie Posted July 26, 2019 Share Posted July 26, 2019 (edited) Hi, I am new to this plugin. I have 2 small questions regarding my setup: 6x 1tb with 1 parity. I replaced the parity with a 4tb disk, I replaced one 1tb with a 4tb disk (rebuild from parity) and I added one 4tb disk. this last move was a mistake Now I want to move the data away from the 1tb disks and Yesterday I chose to copy instead of move. Questions 1: Is this going to be a problem? Do I have to move it again? (same source and destination) This takes ages so I would not prefer it. second question: I chose move but I don't see the files being removed from the disk when I check the content with Krusader or WinSCP. Is this normal behaviour? The move is not finished yet, So I will be patient I get around 32.63 MB/s on a xeon e5-2520 with 48gb of ram. Edited July 26, 2019 by Hennie Quote Link to comment
jbrodriguez Posted July 26, 2019 Author Share Posted July 26, 2019 2 hours ago, Hennie said: Yesterday I chose to copy instead of move. Questions 1: Is this going to be a problem? Your issue will be that once the copy is finished, the data will exist in both the target and the source disk. You'll need to remove data from the source disk manually (please note I'm referring to disks, not user shares). 2 hours ago, Hennie said: I chose move but I don't see the files being removed from the disk Move is implemented by a copy then delete, to protect your source data in case the copy fails for whatever reason. This is normal behaviour. 1 Quote Link to comment
Hennie Posted July 27, 2019 Share Posted July 27, 2019 14 hours ago, jbrodriguez said: Your issue will be that once the copy is finished, the data will exist in both the target and the source disk. You'll need to remove data from the source disk manually (please note I'm referring to disks, not user shares). Move is implemented by a copy then delete, to protect your source data in case the copy fails for whatever reason. This is normal behaviour. Thanks for the quick reply. It worked out very nice. Regarding the copy, I did a move from the same source to the same destination as where I did a copy before and that was finished in seconds. So I am very happy about that. Quote Link to comment
jpotrz Posted July 30, 2019 Share Posted July 30, 2019 If you stop unBalance midway through it's process, you end up with duplicates of those files it's already moved, correct? I queued up 4TB of data to move and that was a mistake. It's been running now for 24hrs and I want to stop it, but it's already copied nearly 2TB of data. If I kill it now, that data is going to be duplicated on 2 drives, right? Quote Link to comment
Recommended Posts
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.