deviousx

anyone?

I'll attach the previous log i posted and the new one till emby freezes. I don't know how to get the log after crash and reboot. I did notice a mono runtime error but didn't understand what meant after googling it embylog.txt emby2.txt

Ok i fixed every other problem but the freezes are still on going. I posted on emby forum and received no replies. If I leave the emby docker on I'm unable to access the web UI or any docker page and tower stop showing up on my network. I'm unsure how to pull the log files while it's in this state. And I'm sure hard rebooting damaging my drives. Any insight how to resolve this would be greatly appreciated.

I just got the docker from app i see no option to update

I posted on both just wanted to make sure I've haven't messed up anything docker end as it was working fine till updated and all fell apart and fresh install wasn't fixing it. Probably not relevant to the freezing issue, but you need to fix your mapping. You have /mnt listed along with /mnt/user paths. I suggest you read the docker FAQ's on path mapping. A good start would probably be to remove the /mnt that is by itself. You neglected to post what the host paths were mapped to inside the container, so it's not possible to tell what other issues the duplicate host mapping may be causing. Anime and Tv shows was added recently because I thought might be the /mnt path causing an issue. Those are the host paths on the container. I just wanted to get how everyone else set up so could eliminate the docker as issue, which hurricanehrndz already mentioned it's Emby itself freezing the system.

I've tried fixing every other issue but my emby still causing my unraid to freeze. I seet it up as: /mnt/cache/app/emby /mnt /mnt/user/Anime/ /mnt/user/Tv Shows/ I also attached docker log before the last freeze. embylog.txt

Ok so my issue is: 6tb free 1.77 TB 2tb free 768 MB 2tb free 14.7 GB 2tb free 84.1 GB I was concerned the 768 MB free was causing the issues on the drive. I'm not sure if it was issue before added 6tb or on going one due to setup

That's why you never change the port on the container side, nor in the webui. Only ever on the host side. I was unware of that till i used FCP. Thanks both you and Squid for all the help

That was it. I actually skipped the first 25 and copied everything else. I think was issue with port not changing in the config file causing it not to load. All good now container on 5050 and host using 8082 like before

I asked same time we trying to fix it. Trying to figure out why i can't fix the container port. What happens with a fresh install using new appdata? [/quote Works take you to wizard but of course loose all settings

So is it better to use the most fill with drives of diffeerent size?

I asked same time we trying to fix it. Trying to figure out why i can't fix the container port.

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="couchpotato" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 5050:5050/tcp -v "/mnt/cache/app/couchpotato/":"/config":rw -v "/mnt/cache/app/sabnzbd/Downloads/complete/":"/downloads":rw -v "/mnt/user/":"/movies":rw linuxserver/couchpotato 01e9905128509e39749d4f268ecb3458160d05395c290c5acd849bf5373ca520 The command finished successfully! [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-install: executing... Cloning into '/app/couchpotato'... [cont-init.d] 30-install: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. that's the information you requested

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

Hey guys, I recently changed my container port back to 5050 due to fix common problems telling me i used wrong thing but now I can't access webui. I've tried reinstalling using the same paths but keeping everything else the same but no luk

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?

Installed it but seems having same error trying to acess webpage installed evereything left it as default expcept the paths

FCP shows as all good. When you say remove container it gives the option to also remove image?

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

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?

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 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

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 It been about few years since setup unraid I'm unsure where to go to fix allocation

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:

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

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