hermy65
-
Posts
273 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by hermy65
-
-
Tuesday i started to hear a sound from my server that sounded like a fan going bad then about 5 minutes later i got notification that some drives were hot so i pulled the lid off to check the fan and it was good. Put things back together then went back to the dashboard and was missing 4 drives from one backplane. Shut down, reseated the 4 drives and powered back on, 2 came back and 2 were marked as missing. Thought maybe a backplane went bad so i powered down, swapped a new one in and then the 2 missing drives showed back up but were disabled so i kicked off a rebuild on the first one. Today the rebuild finished but now it says its unmountable, same with the other drive that was missing.
What do i do now? Diagnostics are attached
-
I just added another USB device to passthru into a VM today and now im getting all kinds of issues with USB devices and an error saying No free USB ports. I found another post saying to bump the USB controller to 3.0 (qemu XHCI) and that would fix the issue but it did not. I have 4 devices im trying to pass thru to a Home Assistant VM.
Diagnostics are attached
Thanks for the assistance!
-
I just added another USB device to passthru into a VM today and now im getting all kinds of issues with USB devices and an error saying No free USB ports. I found another post saying to bump the USB controller to 3.0 (qemu XHCI) and that would fix the issue but it did not. I have 4 devices im trying to pass thru to a Home Assistant VM.
This is what i see in syslog: Jul 7 15:51:58 Storage usb_manager: Info: virsh called HomeAssistant 003 021 error: Failed to attach device from /tmp/libvirthotplugusbbybusHomeAssistant-003-021.xml error: internal error: No free USB ports
Diagnostics are attached
Thanks for the assistance!
-
27 minutes ago, yayitazale said:
Ok now the error is different. Are you sure you did the chmod +x to the file in /mnt/user/Backup/tensorrt models/ ??
@yayitazale well, not sure what happened here but i did a wget again on the script and did a chmod+x again and now its working. Not sure why but it worked this time as there are 3 yolov models in the folder now.
-
1 hour ago, yayitazale said:
Can you try to put the script on the path of first entry "TRT-Models folder path", in the case of the image, "/mnt/user/Backup/TensorRT Models/" ??
I suspect that the second entry is not working but as I tested using the same folder for both I didn't notice it. If this works I would change the template and the steps on the description.
@yayitazale So unless i misunderstood you, i moved the script to the user/backup/tensorrt models folder, updated the paths, re-did the chmod +x and ran it but the same error happened.
Here is my current config
/opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Permission denied /opt/nvidia/nvidia_entrypoint.sh: line 49: exec: /tensorrt_models.sh: cannot execute: Permission denied /opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Permission denied /opt/nvidia/nvidia_entrypoint.sh: line 49: exec: /tensorrt_models.sh: cannot execute: Permission denied /opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory /opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success /opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory /opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success ===================== == NVIDIA TensorRT == ===================== NVIDIA Release 22.07 (build 40077977) NVIDIA TensorRT Version 8.4.1 Copyright (c) 2016-2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved. Container image Copyright (c) 2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved. https://developer.nvidia.com/tensorrt Various files include modifications (c) NVIDIA CORPORATION & AFFILIATES. All rights reserved. This container image and its contents are governed by the NVIDIA Deep Learning Container License. By pulling and using the container, you accept the terms and conditions of this license: https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license To install Python sample dependencies, run /opt/tensorrt/python/python_setup.sh To install the open-source samples corresponding to this TensorRT release version run /opt/tensorrt/install_opensource.sh. To build the open source parsers, plugins, and samples for current top-of-tree on master or a different branch, run /opt/tensorrt/install_opensource.sh -b <branch> See https://github.com/NVIDIA/TensorRT for more information.
-
6 hours ago, yayitazale said:
Can you show how are you launching the template?
I guess is something related with the path itself. Try to use the suggested path /mnt/user/appdata/trt-models/ and try again.
@yayitazale Below is how i have it currently setup, i tried changing the path to user/appdata but it still fails
This is what i see in the container logs
/opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory /opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success /opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory /opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success ===================== == NVIDIA TensorRT == ===================== NVIDIA Release 22.07 (build 40077977) NVIDIA TensorRT Version 8.4.1 Copyright (c) 2016-2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved. Container image Copyright (c) 2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved. https://developer.nvidia.com/tensorrt Various files include modifications (c) NVIDIA CORPORATION & AFFILIATES. All rights reserved. This container image and its contents are governed by the NVIDIA Deep Learning Container License. By pulling and using the container, you accept the terms and conditions of this license: https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license To install Python sample dependencies, run /opt/tensorrt/python/python_setup.sh To install the open-source samples corresponding to this TensorRT release version run /opt/tensorrt/install_opensource.sh. To build the open source parsers, plugins, and samples for current top-of-tree on master or a different branch, run /opt/tensorrt/install_opensource.sh -b <branch> See https://github.com/NVIDIA/TensorRT for more information.
-
Can anybody give me some guidance on the Tensorrt-models container? For the life of me i cannot get it to work. Ive installed the container, done the chmod +x but when i run it i get this in the logs and the container dies:
/opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory
/opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success -
@JorgeB i assume i run the xfs_repair on each disk individually? Anything else i should be looking for while running this?
-
Twice in the last week ive been using various applications on my server and all of a sudden everything would just hang and then nothing would be responsive until i hard powered the machine off. This time i managed to get diagnostics ran but i have no idea what is happening here. Can anyone shine some light on this? Thanks!
-
If i wanted to specify a static ip for the web container in this compose file what would i do?
Tried doing something like this but it didnt work. My compose file is attached as well. Thanks
networks: - spodcast ipv4_address: 192.168.0.206 ports: - 8099:80
-
Im attempting to use this for the first time to build out this: Spodcast Github but im struggling with getting it figured out. I assume i need to add mount points somehow in the compose file so it wont just fill my docker image up but i cannot for the life of me figure it out. Following an example i found in this thread yields a:
volumes.spodcast_data must be a mapping or null
If i add a /data directly after the spodcast_data: like throughout the rest of the compose file i get a:
yaml: line 38: mapping values are not allowed in this context
Attached is what i currently have for my compose file, can someone point me in the right direction on this? Thanks!
-
7 minutes ago, LeonStoldt said:
@hermy65 it looks like your connection to redis does not work properly. How did you setup redis and reference it in the ghostfolio container?
I could reproduce your issue without the REDIS_PORT variable in the ghostfolio container. I forgot to add the variable to the template and will do it soon. For now, please add a new variable to your ghostfolio template and call it "REDIS_PORT" (case sensitive). It should be 6379 by default or your custom port of your redis container.
The REDIS_HOST variable should be set to your Unraid IP or local hostname.
To check, you could run 'ping ${Unraid_IP}:6379' and check if redis is reachable from your ghostfolio console / container.
It sounds like you already did most of it, so maybe check your configurations, give the containers a restart in the correct order and check if it works.
I am able to ping the ip:port of redis through the container. I had already added the REDIS_PORT variable and mapped it to 6379. As for how i configured it, ive tried redis both through host mode and br0 with a custom ip and neither appear to work for me.
-
Managed to get this up and running after adding the redis_port variable and an account created, however, whenever i try to add anything i save it and at the bottom it says Oops, something went wrong, please try again.
In the container logs i see this
[32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [38;5;3m[NestApplication] [39m[32mNest application successfully started[39m[38;5;3m +319ms[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m ________ __ ____ ___[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m / ____/ /_ ____ _____/ /_/ __/___ / (_)___[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m / / __/ __ \/ __ \/ ___/ __/ /_/ __ \/ / / __ \[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m/ /_/ / / / / /_/ (__ ) /_/ __/ /_/ / / / /_/ /[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m\____/_/ /_/\____/____/\__/_/ \____/_/_/\____/ v1.150.0[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32mListening at http://localhost:3333[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [32m[39m [32m[Nest] 1 - [39m05/23/2022, 2:39:45 PM [32m LOG[39m [38;5;3m[DataGatheringService] [39m[32mData gathering has been reset.[39m [32m[Nest] 1 - [39m05/23/2022, 2:40:00 PM [32m LOG[39m [38;5;3m[DataGatheringService] [39m[32m7d data gathering has been started.[39m [31m[Nest] 1 - [39m05/23/2022, 2:42:23 PM [31m ERROR[39m [38;5;3m[ExceptionsHandler] [39m[31mConnection is closed.[39m Error: Connection is closed. at Redis.sendCommand (/ghostfolio/apps/api/node_modules/ioredis/built/redis/index.js:636:24) at Script.execute (/ghostfolio/apps/api/node_modules/ioredis/built/script.js:27:34) at Redis.addJob (/ghostfolio/apps/api/node_modules/ioredis/built/commander.js:158:27) at Object.addJob (/ghostfolio/apps/api/node_modules/bull/lib/scripts.js:49:19) at addJob (/ghostfolio/apps/api/node_modules/bull/lib/job.js:82:18) at /ghostfolio/apps/api/node_modules/bull/lib/job.js:95:14 [31m[Nest] 1 - [39m05/23/2022, 2:43:04 PM [31m ERROR[39m [38;5;3m[YahooFinanceService] [39m[31mBadRequestError: Missing required query parameter=symbols[39m [31m[Nest] 1 - [39m05/23/2022, 2:43:37 PM [31m ERROR[39m [38;5;3m[ExceptionsHandler] [39m[31mConnection is closed.[39m Error: Connection is closed. at Redis.sendCommand (/ghostfolio/apps/api/node_modules/ioredis/built/redis/index.js:636:24) at Script.execute (/ghostfolio/apps/api/node_modules/ioredis/built/script.js:27:34) at Redis.addJob (/ghostfolio/apps/api/node_modules/ioredis/built/commander.js:158:27) at Object.addJob (/ghostfolio/apps/api/node_modules/bull/lib/scripts.js:49:19) at addJob (/ghostfolio/apps/api/node_modules/bull/lib/job.js:82:18) at /ghostfolio/apps/api/node_modules/bull/lib/job.js:95:14
-
Any chance anyone can help me with some samesite/sameorigin issues im having with swag+organizr?
I was able to use the chrome flags when they were available to get things working, then they removed the flags so i resorted to a registry tweak but that no longer works for me either. I would like to get this fixed once and for all so i can continue to use things.
Right now i have everything going through swag using a name.domain.com format. If i use local ips for organizr + the organizr tabs use local ips i get the attached image when i inspect the tab. If i go through my reverse proxy with organizr.domain.com and all the tabs using service.domain.com i get the same thing. How do i resolve this once and for all?
-
Any chance anyone can help me with some samesite/sameorigin issues im having with swag+organizr?
I was able to use the chrome flags when they were available to get things working, then they removed the flags so i resorted to a registry tweak but that no longer works for me either. I would like to get this fixed once and for all so i can continue to use things.
Right now i have everything going through swag using a name.domain.com format. If i use local ips for organizr + the organizr tabs use local ips i get the attached image when i inspect the tab. If i go through my reverse proxy with organizr.domain.com and all the tabs using service.domain.com i get the same thing. How do i resolve this once and for all?
-
Either i have done a good job of not getting dupes/samples in my library OR i cannot figure out how to get this working. My UI looks exactly like the post below, ive disabled SSL with the variable of 1 but still get nothing. Logs do not show anything interesting either.
On 8/10/2021 at 8:44 PM, shaunbarrow said: -
My server hung up entirely today and i ended up having to hard power it off. When it came back it started a standard parity check and for the first time in like 5+ years it actually made a couple parity corrections which it never has before. My log looks strange and i cant really tell what's going on other than containers aren't working well and everything is super sluggish. Diagnostics attached
My log looks like this:
ErrorWarningSystemArrayLogin Jun 19 00:53:51 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:53:51 Storage kernel: tun: 38 00 00 00 03 00 00 00 c4 ce a5 05 00 00 00 00 8............... Jun 19 00:53:51 Storage kernel: tun: 38 00 00 00 03 00 00 00 c4 ce a5 05 00 00 00 00 8............... Jun 19 00:53:51 Storage kernel: tun: 5d f0 00 00 00 00 00 00 63 00 00 00 64 00 00 00 ].......c...d... Jun 19 00:53:51 Storage kernel: tun: 5d f0 00 00 00 00 00 00 63 00 00 00 64 00 00 00 ].......c...d... Jun 19 00:53:51 Storage kernel: tun: cc 95 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 7b 01 00 00 00 00 00 00 00 01 00 00 00 00 ad de {............... Jun 19 00:53:51 Storage kernel: tun: cc 95 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 7b 01 00 00 00 00 00 00 00 01 00 00 00 00 ad de {............... Jun 19 00:53:51 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:53:51 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 93 ff 01 20 20 00 00 00 00 00 00 00 00 00 00 00 ... ........... Jun 19 00:53:51 Storage kernel: tun: 01 00 00 00 00 00 00 00 69 9b 00 00 e0 6c bb f8 ........i....l.. Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 93 ff 01 20 20 00 00 00 00 00 00 00 00 00 00 00 ... ........... Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 01 00 00 00 00 00 00 00 69 9b 00 00 e0 6c bb f8 ........i....l.. Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 242, hdr_len 308 Jun 19 00:53:51 Storage kernel: tun: 00 20 e4 0c 86 88 ff ff 00 00 00 00 00 00 00 00 . .............. Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:53:51 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 214, hdr_len 280 Jun 19 00:53:51 Storage kernel: tun: 30 00 00 00 1b 00 00 00 3c 23 88 1b 00 00 00 00 0.......<#...... Jun 19 00:53:51 Storage kernel: tun: 55 ac 00 00 00 00 00 00 63 00 00 00 64 00 00 00 U.......c...d... Jun 19 00:53:51 Storage kernel: tun: 10 71 00 00 00 00 00 00 00 80 01 00 00 00 00 00 .q.............. Jun 19 00:53:51 Storage kernel: tun: 65 66 20 4a 75 6e 69 6f 72 00 2d 20 53 30 36 45 ef Junior.- S06E Jun 19 00:53:54 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 39, hdr_len 105 Jun 19 00:53:54 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 39, hdr_len 105 Jun 19 00:53:54 Storage kernel: tun: c0 73 15 31 00 ea ff ff 00 d0 00 00 00 00 00 00 .s.1............ Jun 19 00:53:54 Storage kernel: tun: c0 73 15 31 00 ea ff ff 00 d0 00 00 00 00 00 00 .s.1............ Jun 19 00:53:54 Storage kernel: tun: c0 86 15 31 00 ea ff ff 00 30 00 00 00 00 00 00 ...1.....0...... Jun 19 00:53:54 Storage kernel: tun: c0 86 15 31 00 ea ff ff 00 30 00 00 00 00 00 00 ...1.....0...... Jun 19 00:53:54 Storage kernel: tun: 80 63 ce 2f 00 ea ff ff 00 10 00 00 00 00 00 00 .c./............ Jun 19 00:53:54 Storage kernel: tun: c0 d8 d6 2f 00 ea ff ff 00 10 00 00 00 00 00 00 .../............ Jun 19 00:53:54 Storage kernel: tun: 80 63 ce 2f 00 ea ff ff 00 10 00 00 00 00 00 00 .c./............ Jun 19 00:53:54 Storage kernel: tun: c0 d8 d6 2f 00 ea ff ff 00 10 00 00 00 00 00 00 .../............ Jun 19 00:54:00 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1433, hdr_len 1499 Jun 19 00:54:00 Storage kernel: tun: 6f 00 73 00 2f 00 6c 00 6f 00 67 00 62 00 61 00 o.s./.l.o.g.b.a. Jun 19 00:54:00 Storage kernel: tun: 63 00 6b 00 2f 00 63 00 6c 00 61 00 73 00 73 00 c.k./.c.l.a.s.s. Jun 19 00:54:00 Storage kernel: tun: 69 00 63 00 2f 00 70 00 61 00 74 00 74 00 65 00 i.c./.p.a.t.t.e. Jun 19 00:54:00 Storage kernel: tun: 72 00 6e 00 2f 00 6d 00 61 00 72 00 6b 00 65 00 r.n./.m.a.r.k.e. Jun 19 00:54:00 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1378, hdr_len 1444 Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1378, hdr_len 1444 Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:00 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:54:02 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:54:02 Storage kernel: tun: 38 00 00 00 03 00 00 00 00 1e a2 18 00 00 00 00 8............... Jun 19 00:54:02 Storage kernel: tun: 38 00 00 00 03 00 00 00 00 1e a2 18 00 00 00 00 8............... Jun 19 00:54:02 Storage kernel: tun: 5d f0 00 00 00 00 00 00 63 00 00 00 64 00 00 00 ].......c...d... Jun 19 00:54:02 Storage kernel: tun: 5d f0 00 00 00 00 00 00 63 00 00 00 64 00 00 00 ].......c...d... Jun 19 00:54:02 Storage kernel: tun: cc 95 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: cc 95 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: d4 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: d4 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:54:02 Storage kernel: tun: 21 29 1e c3 4e ee 54 91 17 fd 79 c4 9d 9d 47 62 !)..N.T...y...Gb Jun 19 00:54:02 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:54:02 Storage kernel: tun: 21 29 1e c3 4e ee 54 91 17 fd 79 c4 9d 9d 47 62 !)..N.T...y...Gb Jun 19 00:54:02 Storage kernel: tun: b7 8b da f2 ac e6 d1 84 82 cb 3c 2e b2 9a e3 6e ..........<....n Jun 19 00:54:02 Storage kernel: tun: 19 7b 64 7c c8 82 dc 7f d8 fe 2f 89 7f 00 fb ac .{d|....../..... Jun 19 00:54:02 Storage kernel: tun: b7 8b da f2 ac e6 d1 84 82 cb 3c 2e b2 9a e3 6e ..........<....n Jun 19 00:54:02 Storage kernel: tun: 74 09 d3 a4 8b 98 7e 09 c5 5c 26 5c 44 c9 45 38 t.....~..\&\D.E8 Jun 19 00:54:02 Storage kernel: tun: 19 7b 64 7c c8 82 dc 7f d8 fe 2f 89 7f 00 fb ac .{d|....../..... Jun 19 00:54:02 Storage kernel: tun: 74 09 d3 a4 8b 98 7e 09 c5 5c 26 5c 44 c9 45 38 t.....~..\&\D.E8 Jun 19 00:54:02 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:54:02 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 fe 01 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: 80 db 9b 12 00 ea ff ff 63 00 00 00 64 00 00 00 ........c...d... Jun 19 00:54:02 Storage kernel: tun: cc 95 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 Jun 19 00:54:02 Storage kernel: tun: 00 00 00 00 00 00 00 00 20 2d 20 4e 6f 74 68 69 ........ - Nothi Jun 19 00:54:02 Storage kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 fe 01 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: 80 db 9b 12 00 ea ff ff 63 00 00 00 64 00 00 00 ........c...d... Jun 19 00:54:02 Storage kernel: tun: cc 95 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 19 00:54:02 Storage kernel: tun: 00 00 00 00 00 00 00 00 20 2d 20 4e 6f 74 68 69 ........ - Nothi
-
3 hours ago, Roxedus said:
Radarrsync is pretty pointless, as radarr has the functionality built in now, IL remove it when I get to a computer@Roxedus it has that functionality built in now? Can you give me some more info on it as i must have missed that?
-
Can anybody point me in the right direction with radarrsync? I have been using it for maybe a year and it has been working without issue and then all of a sudden today i notice that there are things that should have been synced but were not. I opened up the logs and see this:
Traceback (most recent call last): File "/RadarrSync.py", line 86, in <module> searchid.append(int(r.json()['id'])) TypeError: list indices must be integers or slices, not str
From what i can tell is that its a profile ID issue but for the life of me i cannot figure out how to determine the profile ID. I assumed i just counted the profiles but for some reason in my config i have 5 whereas in radarr(s) my 4k is the 6th one listed, if i change the config to 6 i no longer get an error but nothing syncs over either. Nothing in the radarrsync logs or radarr logs that i can find either.
Any insight?
-
Just now, GilbN said:
Yeah you missed the instructions
dammit...i read those like 11 times before i made any posts because i didnt want to be that guy. My apologies
- 1
-
-
Just now, GilbN said:
And in the 'show more settings'?
Nothing under Show More Settings
-
-
2 minutes ago, GilbN said:
What do you have in the post arguments for telegraf?
/bin/sh -c 'apk update && apk upgrade && apk add ipmitool && apk add smartmontools && telegraf'
Drive issues?
in General Support
Posted
@JorgeB im getting this on both
Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.