Jump to content

trott

Members
  • Posts

    140
  • Joined

  • Last visited

Everything posted by trott

  1. I'm on X470D4U-2T + 3700x, no issue so far except ECC is not working in Kernel 5.3 yet
  2. thanks, I got information from below link, I'm not serach for those patch myself as I don't know how to patch it https://www.reddit.com/r/ASUS/comments/cw74rl/asus_pro_ws_x570ace_ecc_compability/
  3. are you running QB in vm, I notice same issue when I write data from windows VM to cache, the vm is complete hang after write 100-200M data, the cpu usage of qemu-system-x86 is extreamly high
  4. try to change the Power Supply Idle Control in bios to typical current idle, I'm fine with that using x470+3700x
  5. actully you can download the latest one from github, it is just a perl script
  6. might be samba issue, I remember I have a strange issue after update to RC1, I copy a file from PC to share and try to rename the file, it told me the file is already open and cannot rename the file
  7. I don't think RC2 to RC4 changes that much enough to cause all your issues, it must be something else here
  8. thanks, I think I might try later; what this plugin will modify the system when active the tunnle? like iptables ...
  9. ok, I add a peer with remote to Lan access, the tunnel can be activated(with mobile data connection), but I cannot connect the server by IP; I disconnect the tunnel, now I cannot even connect to server on the laptop in the same lan, enven ping cannot be reached; now I totally lost connection to the sever(web or ssh)
  10. 1. will plex corrupt if it is the only docker running? 2. what's your plex path mapping?
  11. it will be great if this plugin support running custom scripts before and after the mover, so we can have script to stop vm/docker before mover running and restart them after mover is finished
  12. Bios is hte newest, it is the EDAC bug for ryzen 2, there are some patch in kernel 5.4, I think I have to wait
  13. I just updated to 6.8-RC1, with ryzen 3700x and ECC ram, I got following error in log, it suppose to be a kernel issue root@Tower:~# dmesg | grep EDAC [ 0.505230] EDAC MC: Ver: 3.0.0 [ 21.472853] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.473283] EDAC amd64: F17h detected (node 0). [ 21.473715] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.474154] EDAC amd64: Error: Error probing instance: 0 [ 21.496227] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.496659] EDAC amd64: F17h detected (node 0). [ 21.497100] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.497537] EDAC amd64: Error: Error probing instance: 0 [ 21.517185] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.517620] EDAC amd64: F17h detected (node 0). [ 21.518067] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.518504] EDAC amd64: Error: Error probing instance: 0 [ 21.537210] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.537643] EDAC amd64: F17h detected (node 0). [ 21.538090] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.538527] EDAC amd64: Error: Error probing instance: 0 [ 21.558282] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.558716] EDAC amd64: F17h detected (node 0). [ 21.559166] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.559603] EDAC amd64: Error: Error probing instance: 0 [ 21.579233] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.579666] EDAC amd64: F17h detected (node 0). [ 21.580114] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.580552] EDAC amd64: Error: Error probing instance: 0
  14. Yes, the error is corrected, but you need to find out why there is error at the first place; Corrected error with report turn off does not means there is no issue
  15. turn off the AER did actully not fix the issue, if I were you, I will change the HBA card, once the error cannot be automatically corrected, you might lose your data
  16. I also have HBA card with only 4 SATA connected, no such issue. what's firmware version
  17. frandkly, I don't know what's the issue you get, I never see ping return system error
  18. so it seems no issue on your network connectivity, try dig github.com or ping github.com to see what's result, it mignt be your DNS issue
  19. youmight wait for 3950x, which supposed to release at beginning of Oct
  20. can you first just let DHCP assign the IP to unraid
  21. downgrade to 6.67 to see if the issue is still there, 6.72 has the performance issue might lead to this .
×
×
  • Create New...