abeksis

Members
  • Posts

    130
  • Joined

  • Last visited

Everything posted by abeksis

  1. I can not pre-formatted. I purchased the disk I added to the system. And I chose the Clear. If there is an option to format it before I'll be happy to explain. So I did all the discs that I have.
  2. Hello, i added a new disk, I click the Clear option to continue the process, but it stops after a few percent. Why? I am attaching the log. It seems that after 10 percent (not always) it just restarts (no server restart, only option). Syslog.txt
  3. Can I get an explanation of how to install the plugin? I installed under the old explanation, when I reboot the server, the config off the plugin gong
  4. It's located at /usr/local/emhttp/plugins/dockerMan/assets/images/banners . If you have a banner to include, you can post it here; I'll gladly include it on the plugin. My contribution Soon I will prepare more ...
  5. What's this? Why am I getting these messages? Sep 3 19:38:22 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 941879777 expected csum 3038475726 Sep 3 19:38:24 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1828596017 expected csum 3038475726 Sep 3 19:38:25 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2832518305 expected csum 3038475726 Sep 3 19:38:26 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 6883105 expected csum 3038475726 Sep 3 19:38:27 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2157543843 expected csum 3038475726 Sep 3 19:38:29 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2729550668 expected csum 3038475726 Sep 3 19:38:30 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1193941000 expected csum 3038475726 Sep 3 19:38:31 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2172697789 expected csum 3038475726 Sep 3 19:38:32 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2485259712 expected csum 3038475726 Sep 3 19:38:33 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1908356721 expected csum 3038475726 Sep 3 19:38:34 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 921021548 expected csum 3038475726 Sep 3 19:38:36 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1218586503 expected csum 3038475726 Sep 3 19:38:37 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 312398306 expected csum 3038475726 Sep 3 19:38:38 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4186015190 expected csum 3038475726 Sep 3 19:38:39 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2435752438 expected csum 3038475726 Sep 3 19:38:40 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2540469548 expected csum 3038475726 Sep 3 19:38:41 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2267664642 expected csum 3038475726 Sep 3 19:38:43 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1529972118 expected csum 3038475726 Sep 3 19:38:44 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3851408705 expected csum 3038475726 Sep 3 19:38:45 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3583886127 expected csum 3038475726 Sep 3 19:38:46 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3908626968 expected csum 3038475726 Sep 3 19:38:47 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1623424418 expected csum 3038475726 Sep 3 19:38:48 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3497563586 expected csum 3038475726 Sep 3 19:38:49 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3192442981 expected csum 3038475726 Sep 3 19:38:51 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2544940046 expected csum 3038475726 Sep 3 19:38:52 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1692009821 expected csum 3038475726 Sep 3 19:38:53 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2926946907 expected csum 3038475726 Sep 3 19:38:54 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 208950530 expected csum 3038475726 Sep 3 19:38:55 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1875966847 expected csum 3038475726 Sep 3 19:38:56 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 822495346 expected csum 3038475726 Sep 3 19:38:58 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1976928265 expected csum 3038475726 Sep 3 19:38:59 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1527979514 expected csum 3038475726 Sep 3 19:39:00 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3827120606 expected csum 3038475726 Sep 3 19:39:01 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4241077043 expected csum 3038475726 Sep 3 19:39:03 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2257142250 expected csum 3038475726 Sep 3 19:39:04 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3728326295 expected csum 3038475726 Sep 3 19:39:05 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1574203534 expected csum 3038475726 Sep 3 19:39:06 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1111781376 expected csum 3038475726 Sep 3 19:39:07 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1629342684 expected csum 3038475726 Sep 3 19:39:08 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 838176165 expected csum 3038475726 Sep 3 19:39:10 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3240675638 expected csum 3038475726 Sep 3 19:39:11 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3436946781 expected csum 3038475726 Sep 3 19:39:12 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2091816005 expected csum 3038475726 Sep 3 19:39:13 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 190336128 expected csum 3038475726 Sep 3 19:39:14 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4280345388 expected csum 3038475726 Sep 3 19:39:15 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2664147010 expected csum 3038475726 Sep 3 19:39:17 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2788966781 expected csum 3038475726 Sep 3 19:39:18 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1854302262 expected csum 3038475726 Sep 3 19:39:19 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2907888508 expected csum 3038475726 Sep 3 19:39:20 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1531916232 expected csum 3038475726 Sep 3 19:39:21 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3367006042 expected csum 3038475726 Sep 3 19:39:22 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4075711400 expected csum 3038475726 Sep 3 19:39:23 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4032204269 expected csum 3038475726 Sep 3 19:39:25 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 744115501 expected csum 3038475726 Sep 3 19:39:26 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3457223072 expected csum 3038475726 Sep 3 19:39:27 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2626928494 expected csum 3038475726 Sep 3 19:39:28 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2541581988 expected csum 3038475726 Sep 3 19:39:30 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2092652876 expected csum 3038475726 Sep 3 19:39:31 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3742300931 expected csum 3038475726 Sep 3 19:39:32 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 661185822 expected csum 3038475726 Sep 3 19:39:33 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2584543821 expected csum 3038475726 Sep 3 19:39:34 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3465722361 expected csum 3038475726 Sep 3 19:39:36 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 882030517 expected csum 3038475726 Sep 3 19:39:37 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4207958048 expected csum 3038475726 Sep 3 19:39:38 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2979258028 expected csum 3038475726 Sep 3 19:39:39 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1339476662 expected csum 3038475726 Sep 3 19:39:40 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2426288737 expected csum 3038475726 Sep 3 19:39:41 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1998475403 expected csum 3038475726 Sep 3 19:39:42 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2101493216 expected csum 3038475726 Sep 3 19:39:44 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3162668184 expected csum 3038475726 Sep 3 19:39:45 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1178236686 expected csum 3038475726 Sep 3 19:39:46 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4198409984 expected csum 3038475726 Sep 3 19:39:47 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1396331646 expected csum 3038475726 Sep 3 19:39:48 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3602559496 expected csum 3038475726 Sep 3 19:39:49 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1129340030 expected csum 3038475726 Sep 3 19:39:51 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1520628242 expected csum 3038475726 Sep 3 19:39:52 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3811934344 expected csum 3038475726 Sep 3 19:39:53 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1422485324 expected csum 3038475726 Sep 3 19:39:54 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 178974169 expected csum 3038475726 Sep 3 19:39:55 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3404343779 expected csum 3038475726 Sep 3 19:39:56 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 507039058 expected csum 3038475726 Sep 3 19:39:58 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4064631500 expected csum 3038475726 Sep 3 19:39:59 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1667668024 expected csum 3038475726 Sep 3 19:40:00 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4133590599 expected csum 3038475726 Sep 3 19:40:01 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2969333643 expected csum 3038475726 Sep 3 19:40:03 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 543778692 expected csum 3038475726 Sep 3 19:40:04 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2354671325 expected csum 3038475726 Sep 3 19:40:05 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2116785903 expected csum 3038475726 Sep 3 19:40:06 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4208957750 expected csum 3038475726
  6. I installed the plugin And according to the picture shown here http://i.imgur.com/kqQsyJV.png plugin does not sit under its correct location Why? Another way, how do I change the icons of what I have installed? For me it does not show any icons. http://i.imgur.com/TE58Qp3.png - My Photo
  7. Where to install the plugin? Under, /boot/config/plugins/dockerMan.plg Or at another location?
  8. After I run the server again it worked It is not clear why.
  9. Yes I did it, the file is not there (img). Here are some pictures and a last attempt to log session. Sep 1 10:52:27 HomeServer php: /etc/rc.d/rc.docker start Sep 1 10:52:27 HomeServer php: Not starting Docker: /mnt/disk1/docker/ is not a file Sep 1 10:52:27 HomeServer php:
  10. Sep 1 10:29:38 HomeServer php: /etc/rc.d/rc.docker start Sep 1 10:29:38 HomeServer php: Creating new image file for Docker: size: G Sep 1 10:29:38 HomeServer php: Not starting Docker: failed to create image file Sep 1 10:29:38 HomeServer php: Sep 1 10:30:28 HomeServer vsftpd[2653]: connect from 79.182.137.180 (79.182.137.180) Sep 1 10:30:29 HomeServer vsftpd[2653]: [root] OK LOGIN: Client "79.182.137.180" Sep 1 10:30:48 HomeServer vsftpd[2656]: [root] OK MKDIR: Client "79.182.137.180", "/mnt/disk1/untitled folder" Sep 1 10:30:56 HomeServer vsftpd[2656]: [root] OK RENAME: Client "79.182.137.180", "/mnt/disk1/untitled folder /mnt/disk1/docker" Sep 1 10:31:09 HomeServer vsftpd[2656]: [root] OK UPLOAD: Client "79.182.137.180", "/mnt/disk1/docker/untitled file", 0.00Kbyte/sec Sep 1 10:31:21 HomeServer vsftpd[2656]: [root] OK RENAME: Client "79.182.137.180", "/mnt/disk1/docker/untitled file /mnt/disk1/docker/docker.img" Sep 1 10:31:42 HomeServer php: /etc/rc.d/rc.docker start Sep 1 10:31:42 HomeServer php: Maybe expand image file Sep 1 10:31:54 HomeServer php: Not starting Docker: mount error Sep 1 10:31:54 HomeServer php: Sep 1 10:33:32 HomeServer vsftpd[2656]: [root] OK DELETE: Client "79.182.137.180", "/mnt/disk1/docker/docker.img" Sep 1 10:33:44 HomeServer php: /etc/rc.d/rc.docker start Sep 1 10:33:44 HomeServer php: Not starting Docker: /mnt/disk1/docker/ is not a file Sep 1 10:33:44 HomeServer php: Sep 1 10:37:35 HomeServer vsftpd[2816]: connect from 79.182.137.180 (79.182.137.180) Sep 1 10:37:35 HomeServer vsftpd[2816]: [root] OK LOGIN: Client "79.182.137.180" Here are some of the important log
  11. I do not know what is wrong. I created a folder under /mnt/disk1/docker and a file named docker.img Extensions under the path I took on a new path (as shown) and it does not work. What am I doing wrong?
  12. Thanks for the answer. I just download bluray movies, DTS quality. All downloaded some mkv movies without the need to unrar. what movie release.quality, 1:1 bluray rip? transmission eating up all your ram? it getting eaten up during unrar? etc.. i dont think this has anything to do with unraid specifically... but just configuration of apps.. prob best to hollar at cp/transmission once you know where the issue is...
  13. Hello, I'm using the latest version of the 6.0-beta7 unRIAD and it installed a number of plugins under docker. the plugins are: Couchpotato | HTPC-Manager | Transmission course. When a server at rest and reasonable memory is the use of 1289 from 6 GHz As shown in the first picture. When the transmission kicks (Download Movie) quickly ran out of memory, as shown in the second picture. I'd love to help and solve the problem. To release the memory (after download), I use this command. sudo sysctl -w vm.drop_caches = 3
  14. Transmission eats the server's memory Hello, I'm using the latest version of the 6.0-beta7 unRIAD and it installed a number of plugins under docker. the plugins are: Couchpotato | HTPC-Manager | Transmission course. When a server at rest and reasonable memory is the use of 1289 from 6 GHz As shown in the first picture. When the transmission kicks (Download Movie) quickly ran out of memory, as shown in the second picture. I'd love to help and solve the problem. To release the memory I'm using the following command. sudo sysctl -w vm.drop_caches = 3
  15. I found a solution that works. https://registry.hub.docker.com/u/coppit/no-ip/
  16. Hello, I am looking for an option for Dynamic DNS Docker Does anyone know of such a possibility?
  17. Thanks for the reply, If there is a manager that can transfer an entire thread that would be great. The actual problem? Currently you have restarted the computer and is holding up .. but it happens from time to time it just hangs Interface (GUI)
  18. Thanks for the reply, I wrote the first post which operating system I run (6.0-beta7). Plug-ins that I run through Dockers | Couchpotato | HTPC-Manager | Transmission. That means there could be memory runs out and drops the service emhttp to free the memory? Right now I only have 4 GB of memory, is worth adding more memory? Here's a picture of the disks that run on the system. Photo
  19. I did not understand, Reboot the server? Or the internal network? What idea to reboot the server every time the webgui interface does not work? And it relatively frequently.
  20. Thanks for the reply, As I wrote, webGUI interface stopped working and I had bo access to the browser, I have tried all sorts of options until I got some instructions to make a killing at the solutions. And i try to restart the webGUI. root@HomeServer:~# killall emhttp root@HomeServer:~# nohup / user / local / sbin / emhttp & But all actions have not yielded results. My problem is that after a few hours once in 24 hours, once after 10 hours, the webGUI interface via the browser does not respond.
  21. Hello, I have a problem after a few hours (from time to time after a day or two, but after 8 hours a day), I have a problem with usb so I changed the usb and after obtaining a new license. I tried all sorts of solutions to what I found at the wonderful and nothing helps. I enclose the commands and system log, I'd be happy to help and find a solution to the problem repeats itself. I enclose the details of the system = v6.0-beta7 64bit killall emhttp root@HomeServer:~# nohup: ignoring input and appending output to ‘nohup.out’ nohup: failed to run command ‘/user/local/sbin/emhttp’: No such file or directory root@HomeServer:/var/log# tail -f /var/log/syslog Aug 29 19:21:03 HomeServer kernel: UDP: bad checksum. From 46.246.19.19:51916 to 10.0.0.3:1024 ulen 1410 Aug 29 19:21:18 HomeServer last message repeated 3 times Aug 29 19:21:22 HomeServer kernel: UDP: bad checksum. From 24.203.177.241:50100 to 10.0.0.3:1024 ulen 1427 Aug 29 19:21:35 HomeServer last message repeated 7 times Aug 29 19:22:05 HomeServer kernel: UDP: bad checksum. From 46.246.19.19:51916 to 10.0.0.3:1024 ulen 1410 Aug 29 19:22:05 HomeServer last message repeated 9 times Aug 29 19:22:13 HomeServer kernel: net_ratelimit: 7 callbacks suppressed Aug 29 19:22:13 HomeServer kernel: UDP: bad checksum. From 46.246.19.19:51916 to 10.0.0.3:1024 ulen 1410 Aug 29 19:23:11 HomeServer last message repeated 2 times Aug 29 19:24:25 HomeServer last message repeated 5 times root@HomeServer:/usr/local/sbin# emhttp Segmentation fault (core dumped) root@HomeServer:/usr/local/sbin# tail -f /var/log/syslog Aug 29 19:42:33 HomeServer emhttp: shcmd (5): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Aug 29 19:42:33 HomeServer avahi-daemon[1747]: Files changed, reloading. Aug 29 19:42:33 HomeServer avahi-daemon[1747]: Service group file /etc/avahi/services/smb.service changed, reloading. Aug 29 19:42:33 HomeServer emhttp: shcmd (6): ps axc | grep -q rpc.mountd Aug 29 19:42:33 HomeServer emhttp: _shcmd: shcmd (6): exit status: 1 Aug 29 19:42:33 HomeServer emhttp: shcmd (7): /usr/local/sbin/emhttp_event svcs_restarted Aug 29 19:42:33 HomeServer emhttp_event: svcs_restarted Aug 29 19:42:33 HomeServer emhttp: startArray not found Aug 29 19:42:33 HomeServer kernel: emhttp[7601]: segfault at 0 ip 00002adbb910c057 sp 00007fff4bac1628 error 4 in libc-2.17.so[2adbb8fd6000+1bf000] Aug 29 19:42:34 HomeServer avahi-daemon[1747]: Service "HomeServer" (/etc/avahi/services/smb.service) successfully established. Aug 29 19:43:23 HomeServer kernel: UDP: bad checksum. From 24.203.177.241:50100 to 10.0.0.3:1024 ulen 1426 Aug 29 19:43:36 HomeServer last message repeated 6 times Aug 29 19:43:46 HomeServer kernel: UDP: bad checksum. From 46.246.19.19:51916 to 10.0.0.3:1024 ulen 1410 I would appreciate help and guidance, every time I turn on the system in the wrong way and it could ruin my server