January 3, 20179 yr I posted this in emby support problem but more i look into it might be the unraid. When i switch on emby docker unable to aceess unraid webui or any other dockers and takes hard reboot to get it working. As docker doesn't automatically run i tried the server with it off and it works fine. Trying t o resolve this i noticed one my disks is amost completly full when terrabytes on other disks available. I tried to use unbalance but it give me message about errors and to use fix ommon problems plugin. Now fix common problems has brought up bunch problems i don't understand but the one stand outtome is 500 disk error on the drive that's almost full. I'm unsure if drive failing or error caused by lack of space. tower-diagnostics-20170103-0142.zip
January 3, 20179 yr Community Expert Disk2 is having a lot of read errors. Might be a bad connection, but it also has 2 offline uncorrectable so it might be going. Since it's almost full maybe a good time to replace it with a larger disk. Not sure about your docker problem, maybe this disk is having some effect, maybe not.
January 3, 20179 yr Author I think might be right all the attributes read pre-fail and old age. Wondering there a way to check why disk 3 was getting so full? I thought unbalanced would redistribute files between the raid but seems to just offload file of one disk onto others or am i using it wrong
January 3, 20179 yr Community Expert Disk2 needs to be replaced: Model Family: Western Digital Green Device Model: WDC WD20EARX-00PASB0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 33
January 13, 20179 yr Author So I replaced disk 2 but still don't know why its being filled when space elsewhere. Is there a way to rebalance the drives as unbalance just moves folders. Also have this error I don't understand or know how to fix: same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:5050]/ and the webUI you are using is http://[iP]:[PORT:8082]/. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. You can fix this problem here:
January 13, 20179 yr Community Expert So I replaced disk 2 but still don't know why its being filled when space elsewhere. Is there a way to rebalance the drives as unbalance just moves folders. Also have this error I don't understand or know how to fix: same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:5050]/ and the webUI you are using is http://[iP]:[PORT:8082]/. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. You can fix this problem here: That message is from Fix Common Problems. Go to the Settings for Fix Common Problems and you can find out more about what it is talking about. What docker is it referring to?
January 13, 20179 yr 2 things that come to mind re allocation. (1) you set the share to either just include disk 2 or exclude other disks. (2) allocation method is set to fill.
January 13, 20179 yr Author So I replaced disk 2 but still don't know why its being filled when space elsewhere. Is there a way to rebalance the drives as unbalance just moves folders. Also have this error I don't understand or know how to fix: same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:5050]/ and the webUI you are using is http://[iP]:[PORT:8082]/. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. You can fix this problem here: That message is from Fix Common Problems. Go to the Settings for Fix Common Problems and you can find out more about what it is talking about. What docker is it referring to? Sonarr and couchpotato 2 things that come to mind re allocation. (1) you set the share to either just include disk 2 or exclude other disks. (2) allocation method is set to fill. It been about few years since setup unraid I'm unsure where to go to fix allocation
January 13, 20179 yr Community Expert Sonarr and couchpotato I don't use either of those. You might check on their support threads.
January 13, 20179 yr So I replaced disk 2 but still don't know why its being filled when space elsewhere. Is there a way to rebalance the drives as unbalance just moves folders. Also have this error I don't understand or know how to fix: same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:5050]/ and the webUI you are using is http://[iP]:[PORT:8082]/. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. You can fix this problem here: That message is from Fix Common Problems. Go to the Settings for Fix Common Problems and you can find out more about what it is talking about. What docker is it referring to? Sonarr and couchpotato 2 things that come to mind re allocation. (1) you set the share to either just include disk 2 or exclude other disks. (2) allocation method is set to fill. It been about few years since setup unraid I'm unsure where to go to fix allocation The message is from FCP is quite simple. You've changed the container port number when all you should ever do is change the host port and leave the container port (in CP's case set to 5050) You will have issues getting containers to talk to each other, possibly getting to the UI, etc. Not that its impossible with changing the host port, but you really have to jump through a ton of hoops when you change the container port. A ton easier to merely change the host port (in the case of port conflicts) and let docker do what its designed to do.
January 14, 20179 yr Author So I replaced disk 2 but still don't know why its being filled when space elsewhere. Is there a way to rebalance the drives as unbalance just moves folders. Also have this error I don't understand or know how to fix: same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:5050]/ and the webUI you are using is http://[iP]:[PORT:8082]/. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. You can fix this problem here: That message is from Fix Common Problems. Go to the Settings for Fix Common Problems and you can find out more about what it is talking about. What docker is it referring to? Sonarr and couchpotato 2 things that come to mind re allocation. (1) you set the share to either just include disk 2 or exclude other disks. (2) allocation method is set to fill. It been about few years since setup unraid I'm unsure where to go to fix allocation The message is from FCP is quite simple. You've changed the container port number when all you should ever do is change the host port and leave the container port (in CP's case set to 5050) You will have issues getting containers to talk to each other, possibly getting to the UI, etc. Not that its impossible with changing the host port, but you really have to jump through a ton of hoops when you change the container port. A ton easier to merely change the host port (in the case of port conflicts) and let docker do what its designed to do. Wow thanks i didn't even realise I was doing that. Gonna check others just to make sure. I think i fixed it but its still showing up in fix common problems
January 14, 20179 yr So I replaced disk 2 but still don't know why its being filled when space elsewhere. Is there a way to rebalance the drives as unbalance just moves folders. Also have this error I don't understand or know how to fix: same webUI interface as what the template author specified The webUI the author specified is http://[iP]:[PORT:5050]/ and the webUI you are using is http://[iP]:[PORT:8082]/. If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the Container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the application. You can fix this problem here: That message is from Fix Common Problems. Go to the Settings for Fix Common Problems and you can find out more about what it is talking about. What docker is it referring to? Sonarr and couchpotato 2 things that come to mind re allocation. (1) you set the share to either just include disk 2 or exclude other disks. (2) allocation method is set to fill. It been about few years since setup unraid I'm unsure where to go to fix allocation The message is from FCP is quite simple. You've changed the container port number when all you should ever do is change the host port and leave the container port (in CP's case set to 5050) You will have issues getting containers to talk to each other, possibly getting to the UI, etc. Not that its impossible with changing the host port, but you really have to jump through a ton of hoops when you change the container port. A ton easier to merely change the host port (in the case of port conflicts) and let docker do what its designed to do. Wow thanks i didn't even realise I was doing that. Gonna check others just to make sure. I think i fixed it but its still showing up in fix common problems Hit rescan Sent from my LG-D852 using Tapatalk
January 15, 20179 yr Author Ok so I thought I fixed it by changing the web UI once open advanced. I then realised it was host port 1. I added and a new path thinking it was host and deleted the old one and now the docker has gone missing. Anyway to get it back without reinstalling and loosing my data?
January 15, 20179 yr Ok so I thought I fixed it by changing the web UI once open advanced. I then realised it was host port 1. I added and a new path thinking it was host and deleted the old one and now the docker has gone missing. Anyway to get it back without reinstalling and loosing my data? Your appdata is still going to be there. See here http://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150 Images are messed up right now (at least for me), but I need to see the docker run command that appears when you try and add the app back in through the app tab (previous apps section)
January 15, 20179 yr Author Oh Ok I didn't know I could retrieve it back like that. I fixed what I broke but now the webpage won't open once I changed the container port
January 15, 20179 yr Oh Ok I didn't know I could retrieve it back like that. I fixed what I broke but now the webpage won't open once I changed the container port FCP and a rescan might tell you if you did something wrong on the webUI entry. Worst comes to worst, stop and remove the container, then re-add it via Apps, but use the Available apps section and add the volume mappings back in and make sure you point the /config to your appdata folder for the app
January 15, 20179 yr Author FCP shows as all good. When you say remove container it gives the option to also remove image?
January 15, 20179 yr FCP shows as all good. When you say remove container it gives the option to also remove image? Keep it checked
January 15, 20179 yr Author Installed it but seems having same error trying to acess webpage installed evereything left it as default expcept the paths
January 15, 20179 yr Author I don't understand what you mean by that. Everything was working i have correct docker settings the only thing that change is the container port. This stopped acessing the webui. Reinstalling it has made no difference i think the confi files in the folders hasnt changed so could it be using the old settings before port change?
January 15, 20179 yr I don't understand what you mean by that. Everything was working i have correct docker settings the only thing that change is the container port. This stopped acessing the webui. Reinstalling it has made no difference i think the confi files in the folders hasnt changed so could it be using the old settings before port change? ok. You changed the config files to handle the port changes also. No real need to have done that, but you can go back to what you did originally and ignore the error from fcp
January 15, 20179 yr Author ok well that working back to normal. I uninstalled sonarr and deleted the files and that seemed to fix reinstall issue so i think probably something in the config preventing it from working. Lastly Issue with disk 2 being filled up even though allocation is on high water all my shares
January 15, 20179 yr ok well that working back to normal. I uninstalled sonarr and deleted the files and that seemed to fix reinstall issue so i think probably something in the config preventing it from working. Lastly Issue with disk 2 being filled up even though allocation is on high water all my shares cool. Split levels override allocation method on shares. (And if you have mixed drive sizes then it does work how its supposed to (but not how people think its supposed to)
Archived
This topic is now archived and is closed to further replies.