akhisyahmi
-
Posts
82 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by akhisyahmi
-
-
Hi, I got this error when I unplug my 2.5 NIC card that connected LAN with my PC (I plan to not use that card anymore)
My 2.5G card use isolated network which is 192.168.1.200 and my network for router use 192.168.0.136
I got this when pinging 8.8.8.8
Unraid network settings might be wrong here as it's using 1.0 gateway. Any idea how to fix this?
Solution I tried :
✅restart unraid api
-
20 hours ago, itimpi said:
What is the IP you have set for the PC end on the Ethernet port that is directly wired to the Unraid server.
nevermind I fixed it. I just need to manual put different IP address into my PC setting.
this video helps me :
-
-
8 minutes ago, itimpi said:
Not clear how everything is set up from a network perceptive? How do you have the rest of the network configured? If your PC is wired directly to Unraid, does the Unraid server have a wired link to a router (and if so what address is that using)?
My router connect directly to both of my PC and unraid via LAN (Motherboard built-in port)
I got 2 2.5GB network card, both are inside PC and unraid and directly connected with LAN.
My unraid server use 192.168.0.136 as static IP from router.
I choose to do 192.168.1.200 directly from both card (it's within their own network)
My router support only 1Gbps LAN connection so I use that card to get 2.5Gbps before.
-
-
I set my PC to DHCP yesterday and only now have free time to check. But my IP 192.168.1.200 won't connect.
-
2 hours ago, itimpi said:
You cannot have 200 as the last byte of the IP address on both the PC and Unraid - they need to be different values.
If you used DHCP to get the addresses assigned by your router then that would automatically have given them different values. If you want fixed IP addresses normally best to leave the server and PC set to use DHCP, and then set the fixed addresses for each of them within the router settings.
I will set my PC to use DHCP. Sorry for asking but is there any need to set up router here? Because I use LAN and directly plug it into both my PC and Unraid Network card.
-
Should I set this to automatically?
-
The picture above (unraid screenshot) is my old setting. It works and I didn't touch it at all yet. So the wrong thing I did is in my Windows settings but I don't which one is it.
-
38 minutes ago, trurl said:
You can't use the same IP address for your Unraid and for your Windows computer.
Sorry I don't understand. Where should I clear it?
-
Hi, I use windows PC and I do reset my network, uninstall and install ipv4 back and etc. Now the network card which directly connect from my PC to Unraid card won't even responding.
Here's some screenshot of the setting and etc. Hope someone can point out, it might be some wrong configuration on my PC.
-
[14.02.2024 17:56:20][ℹ️][radarr-nime] Starting radarr-nime is being ignored, because it was not started before (or should not be started).
[14.02.2024 17:56:20][ℹ️][radarr] No stopping needed for radarr: Not started!
[14.02.2024 17:56:20][ℹ️][radarr] Should NOT backup external volumes, sanitizing them...
[14.02.2024 17:56:20][ℹ️][radarr] Calculated volumes to back up: /mnt/user/appdata/radarr
[14.02.2024 17:56:20][ℹ️][radarr] Backing up radarr...
[14.02.2024 17:56:37][❌][radarr] tar creation failed! Tar said: tar: /mnt/user/appdata/radarr/logs/radarr.24.txt: File shrank by 995287 bytes; padding with zeros; tar: /mnt/user/appdata/radarr/logs/radarr.21.txt: File shrank by 1011456 bytes; padding with zeros; tar: /mnt/user/appdata/radarr/MediaCover/128/fanart.jpg: Read error at byte 20480, while reading 10240 bytes: Input/output error; tar: /mnt/user/appdata/radarr/MediaCover/154/fanart-180.jpg: Read error at byte 0, while reading 6656 bytes: Input/output error; tar: /mnt/user/appdata/radarr/MediaCover/166/fanart-360.jpg: File shrank by 62211 bytes; padding with zeros; tar: /mnt/user/appdata/radarr/MediaCover/169/fanart.jpg: File shrank by 803138 bytes; padding with zeros; tar: /mnt/user/appdata/radarr/MediaCover/172/poster.jpg: File shrank by 1513292 bytes; padding with zeros; tar: /mnt/user/appdata/radarr/MediaCover/321/poster-500.jpg: File shrank by 66810 bytes; padding with zeros; tar: Exiting with failure status due to previous errors
[14.02.2024 17:56:38][ℹ️][radarr] Starting radarr is being ignored, because it was not started before (or should not be started).i keep getting this error and want to restore from this failed backup appdata. is there any problem will occur later?
-
debug log : cb64bd87-0009-4ba1-a622-3387bd9d866f
I keep getting this error while backing up my docker. Any idea how to fix this?
-
5 minutes ago, JorgeB said:
The test passed, but those still look like device errors to me, you can try backing up anything import and re-formatting the pool, if after that it keeps having errors I would replace the NVMe device.
Alright thanks for your respond. I will try that later on. Have a nice day sir.
-
3 hours ago, JorgeB said:
Run an extended SMART test on the NVMe device.
Here's the SMART test
-
2 minutes ago, JorgeB said:
Run an extended SMART test on the NVMe device.
Okay, I will run it and share with you later. Thank you both of you for responding.
-
2 minutes ago, itimpi said:
If the docker.img file is corrupt then you should assume that you need to reinstall all of them. Easy enough to do via Apps->Previous Apps which puts back the binaries with previous settings intact. However you will first need to put back the 'appdata' share contents if you want any of them to remember their state.
So first of all I will need to copy all my appdata and remove all of my dockers and then recreate the docker back, pull new image and then paste old appdata content into it so that it will be back with the same settings and etc.
Is this right? And about my nvme, is it going bad? Do I need to change to other nvme or not?
-
5 minutes ago, itimpi said:
Your syslog is full of messages along the lines of:
Feb 7 18:24:17 Paradyne kernel: critical medium error, dev nvme0n1, sector 193991280 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 7 18:24:17 Paradyne kernel: I/O error, dev loop2, sector 33488120 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2
where the first line suggests a problem with your nvme drive, and the second one that docker.img (which is on the nvme drive) is corrupt so any docker will probably fail.
Can you check which docker is corrupted? Or I need to reinstall all of them after swapping with new nvme?
-
16 hours ago, JorgeB said:
It would be better to see the diags first, but based on the screenshots it looks like a failing NVMe device.
Got the diagnostics. Here it is. I tried stopping dockers one by one and found that scrunity docker making this log fills up. After removing it, my log still climb up but at a slow rate. Might be a bad nvme.
-
Hi, I don't know what's happening anymore. i tried googling around, some post say that my nvme broke down and etc but I can just use my docker as usual without any problem (dockers are in my nvme). I forgot where to copy diagnostics so I just screenshot all that i tried.
My CPU won't idle when this log happen.
Got this from reddit and I tried it (don't know what does it say about it)
I check this every few minutes and can confirm syslog keep climbing up
Appreciate if someone can help me. Is it my docker got corrupted or my nvme broke down?
-
Hi binhex, I have google and etc and even try this before but I can't make it works except only when I change my network type to custom network. Im running unraid OS.
I tried to duplicate qbittorrent and I want to use 2 qbittorrent. One is for seeding and another for personal stuff. Both are connected to the same PIA VPN account and I will always get this error. Any idea how to bypass this except changing network type? I want to use jackett/autobrr/cross-seed all of them connected to both qbit docker.
-
-
I saw this https://github.com/pia-foss/manual-connections/blob/master/connect_to_wireguard_with_token.sh but don't know how to use it and where did the config file will go later. Anyone can help?
-
i tried following this setup : https://github.com/pia-foss/manual-connections
The connection got connected but I can't access my server webui and all my dockers. Restarting it fixed it. Is there any way for me to connect this PIA VPN and bind it to qbit docker?
I login into PIAVPN and even contact support but they can't help it. The only way to Port Forwarding using this VPN is via Wireguard setup and there's not even download button in their website to download WG config file which frustrate me.
API KEY: NETWORK_ERRORNETWORK
in General Support
Posted
Deleting network.cfg in flash drive fixed it! But my server reset to DHCP back so you guys will need to set to static back and connect server to monitor to check which IP unraid is using after deleting and rebooting network.cfg.