Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Try changing your DNS server to 208.67.222.222 and 208.67.220.220 instead of using your router. Settings - Network Settings
  2. I reported this issue to LT, hopefully something can be done, it's strange because it works for most people, but there are at least 3 cases I know of that where it is not working.
  3. https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
  4. Looks like it, at least for now, still a good idea to check cables.
  5. Note that rsync creates all the folders before the transfer, so they will all be in the first available disk, and depending on the split level all data can go there.
  6. These are normal mostly during initialization with controllers based on this chip, it's the same with the SAS2LP.
  7. I expect Unraid to report the same as df, you can try googlling to see if you find similar issues with xfs, sparse files and df.
  8. Start with memtest, it's a boot option in the Unraid boot menu
  9. Same strange crashing going on, please reboot and post new diags after array start.
  10. Enable the syslog server and post that after a crash.
  11. Try connecting those the the onboard SATA controller to see if there's any difference.
  12. If you don't mind please share what the issue was, it might help someone else in the future.
  13. Those errors won't make the server stop working for now, they might cause some delays while the connection is resetting.
  14. Since btrfs was detecting some data corruption before this it's a good idea to run memtest first, then backup and re-format the pool.
  15. Looks more like a power/SATA cable issue but if the issue persists after replacing them it could be the device.
  16. Yes, just removing the *.plg files will prevent them from loading, but you can also delete the respective folders if you don't care about the settings for those plugins.
  17. Please uninstall these and see if there's any difference: docker.folder.plg - 2021.08.20 (Up to date) (Incompatible) NerdPack.plg - 2021.08.11 (Up to date) (Incompatible)
  18. Looks OK, but that won't fix the current libvirt.img issue, only if you restore a backup, or need to re-create the VM(s), can still point to the same vdisk(s).
  19. XML files for all VMs are stored in libvirt.img, you should always have a backup of that file.
  20. https://forums.unraid.net/topic/50698-monthly-5-parity-errors/?do=findComment&comment=499236
×
×
  • Create New...