MarshallU

Members
  • Posts

    18
  • Joined

  • Last visited

MarshallU's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Saiba, I'm having the same issue. I backed up my world and reset all the non-relevant chunks using the MCA editor program. Now I'm trying to move my server to 1.17 in MineOS and it will not start. I have seen other instances of this happening - looks like it could be some incompatibility with the old version of java.. Need some help to get this resolved though - just wanted to let you know you are not alone
  2. Hey all, I have an issue with my cache drives - they are showing up as read only which is causing all dockers to act up. I have tried a few common fixes seen on the forums like rebalancing the cache but haven't seen any success yet. Wondering if someone can look at the diagnostics file and see if there are any other thing I can try. I also got this error that I've never seen when I tried to write the diagnostic file. Thanks! usreymedia-diagnostics-20210306-1330.zip
  3. Hey Jorge - wanted to let you know it looks like this solution worked. I changed the RAM speed to 2400 MHz in the BIOS (updated BIOS while I was at it) Then ran 2 back to back parity checks. The first still found and corrected about 1000 errors, the second was completely clean. Thanks so much for your help!
  4. Thanks, Jorge, appreciate the tip. Just to make sure - I am running a 2nd gen Ryzen with 2 of 4 DIMS (dual channel) populated, so I should set my mem frequency to 2400 MHz in BIOS? Would you suggest running any more tests other memtest if that doesn't help?
  5. Small numbers of parity sync errors were corrected starting about a month ago - now I have ran a few within the last week with several thousand errors being "corrected". If they're being corrected, shouldn't they not appear on the next scan? Unless there is a hardware issue that is causing this. Posted my diagnostic file if anyone wants to take a look and can figure out what might be causing this. I'm having trouble starting VMs and wondering if the drive space for them might be corrupted? Thanks in advance! usreymedia-diagnostics-20210224-1050.zip
  6. Thank you, I will try that! The disk has a three year warranty of which only 1 year is used - so if worse comes to worse I am covered for a replacement. Thanks for looking over the data!
  7. I had this same issue happen to me today - one drive shows up as disabled - contents emulated. I'm attaching the SMART report here so someone can review it. It shows "Passed" on the overall health assessment. Parity check was performed 3 days ago with 0 errors. Any help would be appreciated! This is the first time I have come across this situation in Unraid. ST4000VN008-2DR166_ZDH7GQYQ-20200830-1326.txt
  8. Okay so I opened the terminal for Unraid on my system and did the Ifconfig command again and here are the results: Linux 4.18.20-unRAID. root@UsreyMedia:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 inet6 fe80::6d4:c4ff:fe57:4e55 prefixlen 64 scopeid 0x20<link> ether 04:d4:c4:57:4e:55 txqueuelen 1000 (Ethernet) RX packets 72344418 bytes 54455395648 (50.7 GiB) RX errors 0 dropped 0 overruns 235 frame 0 TX packets 65535197 bytes 42700854453 (39.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.8 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::20de:c2ff:feca:eeb1 prefixlen 64 scopeid 0x20<link> ether 04:d4:c4:57:4e:55 txqueuelen 1000 (Ethernet) RX packets 57499139 bytes 53057311704 (49.4 GiB) RX errors 0 dropped 288 overruns 0 frame 0 TX packets 60361649 bytes 42367326612 (39.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:bff:fef7:e2bf prefixlen 64 scopeid 0x20<link> ether 02:42:0b:f7:e2:bf txqueuelen 0 (Ethernet) RX packets 52046581 bytes 29530460190 (27.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 68956108 bytes 53570993784 (49.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 04:d4:c4:57:4e:55 txqueuelen 1000 (Ethernet) RX packets 72344422 bytes 54455396220 (50.7 GiB) RX errors 0 dropped 0 overruns 235 frame 0 TX packets 65535203 bytes 42700859352 (39.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xf6500000-f651ffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 4644616 bytes 5287958283 (4.9 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4644616 bytes 5287958283 (4.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth1114cec: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::e4ad:1eff:fefc:1397 prefixlen 64 scopeid 0x20<link> ether e6:ad:1e:fc:13:97 txqueuelen 0 (Ethernet) RX packets 104377 bytes 13762126 (13.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 79196 bytes 19082322 (18.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth24170d5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::d9:89ff:fe69:6c9 prefixlen 64 scopeid 0x20<link> ether 02:d9:89:69:06:c9 txqueuelen 0 (Ethernet) RX packets 68243 bytes 596845800 (569.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 161491 bytes 407691023 (388.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth8130a5e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::1487:90ff:fe6f:bb13 prefixlen 64 scopeid 0x20<link> ether 16:87:90:6f:bb:13 txqueuelen 0 (Ethernet) RX packets 188914 bytes 27153799 (25.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 217239 bytes 82407082 (78.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth832a600: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::6830:79ff:fe5b:85a5 prefixlen 64 scopeid 0x20<link> ether 6a:30:79:5b:85:a5 txqueuelen 0 (Ethernet) RX packets 45441742 bytes 27341002496 (25.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 48489479 bytes 36406310841 (33.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth8680b10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::5cde:b5ff:fee9:c77f prefixlen 64 scopeid 0x20<link> ether 5e:de:b5:e9:c7:7f txqueuelen 0 (Ethernet) RX packets 996 bytes 1503463 (1.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1365 bytes 715255 (698.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth91db3b1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::458:d9ff:fece:12b1 prefixlen 64 scopeid 0x20<link> ether 06:58:d9:ce:12:b1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2288 bytes 389239 (380.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb3876c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::546e:86ff:feef:e038 prefixlen 64 scopeid 0x20<link> ether 56:6e:86:ef:e0:38 txqueuelen 0 (Ethernet) RX packets 93193 bytes 20790815 (19.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 77287 bytes 50350863 (48.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:46:9e:b9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
  9. I opened the console for the docker in Unraid, ran the ifconfig. See attached. Couldn't copy/paste for some reason so took a screenshot of it. It's reporting eth0 inet of 172.17.0.2 Even though when I set it up, I specied LAN network 192.168.1.0/24 as the LAN_NETWORK variable. I'm not sure if this is causing the discrepancy.. Let me know what you think. Thanks!
  10. Here's my supervisord.log file from today after setting debug to "true" and restarting the docker. Very long so uploading instead of copy/pasting. I changed my PIA username and password to "username" and "password" for this version of the log file just in case Thanks in advance! supervisord log 1.8.2020.txt
  11. Currently going to: /data/Incomplete for my downloading files and /data/Completed when they are finished.
  12. Using unraid! I guess that would have been important to mention.
  13. Hey everyone! I'm working on getting my DelugeVPN container set up (used SpaceInvaderOne YT video for reference for initial setup). I'm using PIA for the VPN. After getting everything set up, I got my first torrent started and saw reasonable speeds (~5MB/s download) but after 30s to 1 min of these good downloads, my download speed drops to 0 kb/s and never recovers. I can delete the torrent and restart the docker and try again but see the same pattern every time I try to restart a torrent (have tried using a few different connection points and toggling port forwarding on/off. Wondering if anyone can help with further setup to get stable downloads. Let me know what data I need to attach! Thanks! Marshall