Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,492

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Best bet is to backup cache data and re-format the pool.
  2. JorgeB
    Parity can't usually help with filesystem corruption, and it won't if it's 100% in sync, but because of the HBA problem it might not be, so you can try, stop the array, unassign disk5, start the array, if disk5 is still unmountable run xfs_repair on the emulated disk (it's also md5), if that doesn't work best bet is to ask for help on the xfs mailing list or to use a data recovery program like UFS explorer.
  3. JorgeB
    You assume right. WD Helium models are all CMR, also any WD 8TB or larger model is also always CMR, at least for now.
  4. JorgeB
    Make sure the BIOS is up to date, the option is called "power supply idle control" or similar, if you can't find it disable C-States globally. You're also overclocking the RAM, respect the max officially supported speeds for your config.
  5. JorgeB
    Possibly a bug, unless the enable cache setting is now also on another place, edit /boot/config/shares.cfg and change: shareCacheEnabled="no" to "yes"
  6. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  7. JorgeB
    That setting is no longer there, it's set on a share by share basis:
  8. JorgeB
    You should disable the mover logging so it doesn't spam the syslog.
  9. JorgeB
    Disk looks fine, most likely an issue with the SASLP, since they are known to drop drives without a reason, could also be a cable/connection issue.
  10. JorgeB
    Update UD and reboot.
  11. JorgeB
    Can't find them, either missed them or they are not there since there are several hours missing because of all the log spam, disk looks healthy, would recommend replacing/swapping cables to rule them out and rebuild on top.
  12. JorgeB
    First thing you need to do is to make your server not internet facing, now let me see if I can find the disk errors in the middle of all those login attempts.
  13. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421
  14. JorgeB
    Try it on a different controller if possible, like the onboard SATA ports.
  15. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  16. JorgeB
    Yes if the filesystem was fixed, you can also reboot to see if there aren't any more errors.
  17. JorgeB
    Problem first starts with the cache filesystem, then the docker because it's on cache. Possibly there's something using the cache at that time, like the mover.
  18. JorgeB
    Check filesystem on disk3.
  19. JorgeB
    There's filesystem corruption on the cache pool, best bet is to backup any important data there and re-format the pool.
  20. JorgeB
    That would be a BIOS bug, look for a BIOS update or contact ASUS support, or just get a cheap keyboard and leave it connected. Make sure UEFI boot is enable in Unraid, you can easily check by looking at the EFI folder on the flash drive, if it's named EFI- rename to EFI.
  21. JorgeB
    Please use the existing docker support thread:
  22. JorgeB
    Cache pool is completely full, you need to move some data, it also has dual data profiles and it's not redundant, after you free up some space run a balance to raid1.
  23. JorgeB
    Yep. Old age? 9 Power_On_Hours -O--CK 013 013 000 - 63895 That's over 7 years, not bad.
  24. JorgeB
    e.g., this is how it looks on the Asus board I'm working now, but it's not the same on all, some have more advanced options where you can chose on what errors it halts or not, and some might not have any option:
  25. JorgeB
    That is a board issue, some boards have the option to not halt on that error, look for that option in the BIOS. That also looks like a board issue, if you are booting CSM try UEFI, or vice-versa.
×
×
  • Create New...