Jump to content

Max

Members
  • Posts

    262
  • Joined

  • Last visited

Everything posted by Max

  1. @johnnie.black could it because of some bad sata ports of my motherboard cause my new setup is like this -- disk which was earlier disk1 is now disk2 and the disk which earlier disk2 is now disk1 so i ran extended self test on both the drives, so the disk2 which was earlier disk1 the one which was showing those ata error passed the extended self test but the disk1 which was earlier disk2 the one which wasn't showing any errors suddenly gone missing in the middle of extended self test. So the reason behind me thinking it could be bad sata ports of motherboard is that i also interchanged the powercables and sata ports.
  2. okay btw did u find any error for disk2 or its irrelevant to ask cause their is no data on it.
  3. @trurl @johnnie.black So after a reboot somehow docker page loaded fine but after still dockers were not working properly so i had to delete the docker image again. I just ran scrub test on disk and now its showing this error.
  4. okay set it to "no" now, what's next how am i going to use dockers after disabling it. As for docker image being so large, Actually earlier when my docker image got corrupted fix common problem plugin reported that it could be docker image is full, so at that time when i created a new image i also increased the size of it for just in case. But after that i kept an eye on it so now i know i never used more than 5.5 gigabyte, so yeah im not doing something crazy.
  5. that's the docker page. Actually earlier in docker settings page delete option was not appearing, so thought maybe they appear after stopping the array. i dont know why the status says its stopped.
  6. @johnnie.black Just now i was trying to delete docker image so i order to delete docker image it tried to stop the unraid array but then it got stuck at unmounting disks so i had to hard reboot. So now after deleting docker isn't loading properly. Its like this.
  7. i guess i did change the power cable, don't remember for which one disk1 or disk2. Could you please tell me where to look for that error.
  8. i guess you forgot who i am. So let me remind you i am that same person that was a couple of days back was having some trouble with unraid so you suggested me to replace the cable so i did. So is their any way to make sure that its a bad disk
  9. So i was installing that rutorrent docker from @Capt.Insano but the docker run command failed at the end and now dashboard and docker page is showing that their are no docker installed to show but still i can access all my dockers. their is also a warning that is appearing on both dashboard and docker page. Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 673 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 853 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 673 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 853 i will be attaching the diagnostics with this post. if anyone knows how to fix this then in that case in any kind of help will be appreciated. unraid-diagnostics-20170506-1515.zip So guys i just ran scrub test and its showing one uncorrectable error.
  10. @trurl Hey guys could it be all because of some corrupted torrent file cause i noticed that after restarting docker every time, it would start the rechecking process and at somewhere around 20-25 % that error poops in for every single time. So what i did was deleted some of files it was checking when it was around that 20-25 % mark and voila no more error and now its like 4-5 hours since its running perfectly. So could it be all because of some file that got corrupted somehow.
  11. here goes the log. Brought to you by linuxserver.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 20-config: executing...'access-swap.sh' -> '/config/rutorrent/settings/access-swap.sh''access.ini' -> '/config/rutorrent/settings/access.ini''access_no' -> '/config/rutorrent/settings/access_no''access_yes' -> '/config/rutorrent/settings/access_yes''config.php' -> '/config/rutorrent/settings/config.php''plugins.ini' -> '/config/rutorrent/settings/plugins.ini'[cont-init.d] 20-config: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.==> /config/log/rtorrent/rtorrent.log <==tail: cannot open '268' for reading: No such file or directory- And Here Goes the Docker run command. Pulling image: linuxserver/rutorrent:latest IMAGE ID [latest]: Pulling from linuxserver/rutorrent. Status: Image is up to date for linuxserver/rutorrent:latest TOTAL DATA PULLED: 0 B Stopping container: rutorrent Successfully stopped container 'rutorrent' Removing container: rutorrent Successfully removed container 'rutorrent' Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="rutorrent" --net="bridge" -e TZ="Asia/Calcutta" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 84:80/tcp -p 51413:51413/tcp -p 6881:6881/udp -v "/mnt/user/Window share/rutorrent/":"/downloads":rw -v "/mnt/user/appdata/rutorrent":"/config":rw linuxserver/rutorrent f7d1d7c9fb033c1edb8431116f72622d67e714034f53a445c461f80d9cd95c7b The command finished successfully!
  12. I can't believe this. I guess i had tried 4-5 different different paths and i guess that was the only one that i didn't tried. why this has to be the one that works. Thanks Man, you rocks.
  13. hey guys i need some help, i keep getting this error. Here goes the log If i restart the docker it will work some seconds and then it just stops working and start showing error.
  14. okay, i know that was stupid but i was just giving it a try cause with that at least it was downloading for a couple of seconds but with this i.e. "/root/downloads/down/" torrents just enters in error state in an instant no waiting.
  15. Hey guys i need some help im getting permission denied error
  16. Okay will do that, thanks for suggestions and everything.
  17. okay that means i took too long before grabbing diagnostics. ohh okay will be careful next time i guess i will give BTRFS one last chance, lets hope their will be no next time.
  18. okay but even this time i grabbed them before rebooting, infact i didn't rebooted my unraid server until you told me to.
  19. Do have any idea what could be those other problems might be. Cause as i said this will be the third time i will be strting all over again but this time i would love to not face these problems again
  20. that was the very first thing that i did so already copied all that data that was important to me. So basically u mean i have to reformat my drives and start all over again, so if that's what u meant then in that case would u recommend me to switch to xfs cause this will be the third time i will be starting all over in 15 days of trial period.
  21. So when i tried to stop the unraid array it was stuck at unmounting disks, so i hard rebooted the system but still everything is same. scrub status for 3a966616-a38f-43fc-992b-b99d7ae0b686 scrub started at Mon May 1 13:56:25 2017 and was aborted after 00:00:00 total bytes scrubbed: 0.00B with 0 errors It just aborts itself on its won.
  22. Okay i already tried running scrub but it aborts on its own after 3 secs. scrub status for 3a966616-a38f-43fc-992b-b99d7ae0b686 scrub started at Mon May 1 08:43:22 2017 and was aborted after 00:00:03 total bytes scrubbed: 291.64MiB with 0 errors And now just to be sure i just tried it again and now whenever i click on scub button it just reloads the page.
  23. So today morning when i woke up i realized that plex wasn't working properly so restated the plex docker but after that it is showing this read only file system error. so i restarted my unraid array and now fix common problem plugin in showing these errors. Just forget about the filebotui error part, cause i did it on my own and it was working fine. here goes the diagnostics. I really need some help cause now im starting to feel that unraid might not work out for me cause after every 3-4 days im here, crying out for help or could it be all because of BTRFS. unraid-diagnostics-20170501-1127.zip
  24. @coppit hey i finally fixed it. As you told me earlier that 3389 port is not what it should be, it should be 8080. So here's what i did. and now the ui is working.
×
×
  • Create New...