Jump to content

JorgeB

Moderators
  • Posts

    67,884
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Try lowering the RAM cache size, you can do that with the tips and tweaks plugin, using a disk share instead of user share whenever possible should also help.
  2. Share cache full doesn't mean cache is full, that will be logged as "cache disk full", share cache full means a share is hitting the minimum free space set and it's now copying directly to the array. Make sure there's nothing open on a disk, ssh session will be enough.
  3. Reboot to clear the errors and then run a non correcting parity check.
  4. That's normal SMART overall-health self-assessment only fails if there's a "failing NOW" attribute, and that's why it's basically meaningless.
  5. This usually means the same devices are being detected twice, make sure there's only one cable from the HBA to the NetApp enclosure, Unraid doesn't support SAS multipath.
  6. I'm going to close the bug, but the thread will remain unlocked if anyone still wants to add any info.
  7. Yes, thank you @Altwazar, everyone having this specific call trace with Unraid is using Qbittorrent or is there anyone not using it and still having this issue?
  8. There's no Unraid SMART test, SMART tests are done by the disk, Unraid only starts a test and shows the results.
  9. Try booting in safe mode to rule out any plugin issues.
  10. Yes, you need a file sync tool, like Syncback free, or if the D drives on the PCs are shared over SMB you can have for example an rsync script on Unraid doing the sync.
  11. Not really since the log starts over, all looks OK in the second ones, if you continue to have issues enable the syslog server.
  12. Make sure there's no Android device with a browser window opened on the WebGUI, it can cause issues when the device is sleeping, and to clear the log you can reboot.
  13. Ahh, sorry, misunderstood, in the first diags the go scrip was not executed, no idea why, if it happens again try booting in safe mode.
  14. Those diags are also just after a reboot.
  15. Start by posting the diagnostics.
  16. Double check that C-States are disabled, call traces look related to CPU idle issues, also look for a BIOS update for the board.
  17. It may take a few minutes, if it doesn't finish after 15 min or so reboot.
  18. Please post the diagnostics
  19. You basically just send an email describing the problem with the log, before doing it I would recommend running a file system check directly on the disk to rule out any md driver issues, unlikely it will make a difference but better to be sure xfs_repair -v /dev/sdX1 Replace X with the correct disk letter and note the 1 in the end.
  20. Doubt this is Unraid related but you can try downgrading to last known good release to confirm.
×
×
  • Create New...