fazrul

Members
  • Posts

    8
  • Joined

  • Last visited

fazrul's Achievements

Noob

Noob (1/14)

1

Reputation

2

Community Answers

  1. managed to solve it as it look like the time and date is out of sync
  2. This past week or so my unraid server has not been able to contact to the internet at all. I noticed this when I attempted to go in and check apps for updates, and got the error: recently i change RAM and after that the system did not work. ========= Download of appfeed failed. Community Applications requires your server to have internet access. The most common cause of this failure is a failure to resolve DNS addresses. You can try and reset your modem and router to fix this issue, or set static DNS addresses (Settings - Network Settings) of 208.67.222.222 and 208.67.220.220 and try again. Alternatively, there is also a chance that the server handling the application feed is temporarily down. Last JSON error Recorded: Syntax error ========= Tried different cables, no change Tried Changing DNS to 208.67.222.222 208.67.220.220 8.8.8.8 1.1.1.1 i do not use any pfsense. reboot router and switch doest work as well. logged into console to ping IP addresses, get back host reachable. root@Waklu:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=30.9 ms ^C --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 30.901/30.901/30.901/0.000 ms root@Waklu:~# ping 208.67.222.222 PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data. 64 bytes from 208.67.222.222: icmp_seq=1 ttl=54 time=32.0 ms 64 bytes from 208.67.222.222: icmp_seq=2 ttl=54 time=30.5 ms ^C --- 208.67.222.222 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 30.547/31.297/32.047/0.750 ms root@Waklu:~# ping 208.67.220.220 PING 208.67.220.220 (208.67.220.220) 56(84) bytes of data. 64 bytes from 208.67.220.220: icmp_seq=1 ttl=54 time=30.2 ms 64 bytes from 208.67.220.220: icmp_seq=2 ttl=54 time=28.9 ms ^C --- 208.67.220.220 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 28.906/29.575/30.245/0.669 ms root@Waklu:~# not sure what is going wrong here, or what else to try to fix it. Any help you could suggest would be great.
  3. seems like global issue as i having the same problem, any eta on the fixed?
  4. i fixed the issue it is due to bad RAM slot evendo the memtest that i did on slot 12 are working fine. Thanks everyone for the assistance.
  5. Seems doesn't solve the issue even the memory result has passed. I saw this message and change the date and time on BIOS but it still hang Line 3913: Jun 24 02:48:30 Tower ntpd[1561]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Line 3929: Jun 24 02:50:04 Tower nginx: 2022/06/24 02:50:04 [error] 1895#1895: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. syslog MemTest86-Report-20220623-150250.html
  6. Thanks for clarification. I've notice the error about RAM but a doubt that could be the issue since it was running fine under Truenas and previous unraid setup. I've remove all ECC RAM and just use 16GB for now. After 5 hours later the result PASSED. Hence I will only use one RAM to perform parity sync and awaiting next 2 hours to complete and will update the outcome. Yep got it thanks for that information. Did use this setup few years back with Unraid but didnt encouter any issue. It's seems reusing the setup with new config shows there an issue with RAM. Thanks, there was a typo as what i meant was using cache as SSD. Anyway will update the result
  7. Hello everyone, I been stuck for several days and been checking the net to find solution and seems the issue still persist. How to reproduce: using SATA cable add one parity with 1 disk 2TB (same size) and 512GB SSD - no go (hang at 2%) add one parity with 3 disk 512GB SSD - no go (hang at 1%) Internal Mini SAS 36p SFF-8087 M Latch to 4X SATA 7p F Breakout Cable one parity with 1 disk 2TB and hang at 10% during parity sync One Parity with SSD connected and 3 SATA connected hang around 5% during parity sync One parity with 3 SATA 2TB, hang at 7$ parity sync Expected results: parity Sync completed Actual results: parity Sync hang Other information: perform memtest for 6 hours and not seeing any issue notice while using Mini SAS to SATA the parity sync speed drop from 180MB+ to 14MB before freeze using safe mode the parity sync will take approx 1 days plus with 17MB speed. feedback_diagnostics_1655979140.zip syslog