Jump to content

JorgeB

Moderators
  • Posts

    67,893
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. And you can at least disconnect and reconnect the cables.
  2. If you leave it unassigned it should not be a problem, but fist reboot anyway to clear the failed rebuild.
  3. Above I mentioned to replace the cables first.
  4. According to those you didn't reboot yet, and still lots of errors on disk3, check/replace cables for disk3 and post new diags after array start.
  5. Usually not unless the superblocks are damaged, if they are it will scan the complete disk looking for a backup, post new diags in the meantime.
  6. Are you using the GUI or running the command manually?
  7. Why do you say that? HBA is being detect and initialized by Unraid, so apparently it's working, like mentioned above try connecting a disk directly to the HBA bypassing the backplane, if it still doesn't work you could be using the wrong cables.
  8. Try with a new flash drive with a stock Unraid install, no key needed, if the issue persists it's likely browser related, if not it's config related so recreate the flash drive and restore only the minimum config files.
  9. Without shutting down the VM service libvirt.img would not be moved, do you have a backup or the old cache device still untouched?
  10. That looks harmless, you can ignore.
  11. Ryzen with overclocked RAM like you have is know to corrupt data, and btrfs is detecting a lot of data corruption, correct that and also a good idea to run memtest after.
  12. Some strange errors in the end, try booting in safe mode, if that doesn't help suggest redoing the flash drive.
  13. Enable the syslog server and post that after a crash.
  14. Multiple crashes occurring, try with just one of the RAM sticks at a time, with XMP disabled.
  15. Disk dropped offline and reconnected again, this is usually a power/connection problem, also a good idea to update the LSI firmware to latest.
  16. 50MB/s is about normal for the default write mode, unless SMR limitations quick in, I see <5MB/s every few minutes with some if my SMR drives, if you enable turbo write you'll get faster writes at the expense of all drives spinning up.
  17. Not really, I don't use XFS, but wouldn't really worry about that, probably normal.
  18. Problem with disk3 looks power/cable related, check/replace the cables for that disk, then start the array and before rebuilding check filesystem on the emulated disk3.
  19. These disks are SMR, so lower write performance is expected, especially with medium/small files, transfer to cache should be much faster, not familiar with rclone but it might not be the fastest option, can you do a large file transfer from a wired desktop over SMB direct to cache? Also, getting btrfs corruption errors immediately suggests a hardware problem
  20. Probably there's a comment in the kernel to why the quirk was added, but sorry, no idea how to find that.
  21. Yes, no need to run the mover, pool can be in use during the upgrade, of course anything important should still be backed up.
  22. Something is still causing the errors, so try and reduce some more, or try running just some services at a time to try and find the culprit.
×
×
  • Create New...