Jump to content

JorgeB

Moderators
  • Posts

    67,647
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. There are multiple threads and bug reports about that, you can look at them for any ideas.
  2. It's a known btrfs bug, raid1 pools with an odd number of devices or raid10 pools with non multiple of 4 devices will display the wrong free space, but all the pool space can be used and the free space will be less incorrect as the pool fills up.
  3. That is from an Intel SSD, the other one is having similar issues, probably just noise but if nothing else is spamming the log, try connecting them on a different controller, ideally the onboard Intel SATA ports.
  4. Not a mac user but IIRC there was an issue with osx that treated SMB writes as sync writes, google "osx smb strict sync".
  5. That's not a stock Unraid file, it's created by CA backup IIRC.
  6. There are many different crashes, some network related, see if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  7. Still seems related to these: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  8. See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  9. Still looks like a power/connection issue.
  10. Disk5 is failing and should be replaced.
  11. It's possible, but it's still overclocking, if you start getting unexpected sync errors after a parity check start looking there, various examples of that happening here on the forum.
  12. Disk dropped again, so there's no SMART report, you're using a Marvell controller with port multipliers, these are a known problem separately, even worse together, there's also another controller with port multipliers, you should really get rid of those. Connect the disk to a different port/controller and post new diags so we can see SMART.
  13. Yep, everything looks normal to me, post new ones if there are issues in the future.
  14. What is the problem? Diags only show array stopped, no attempt I can see to start it.
  15. Make sure you respect the max officially supported speeds depending on the config, or still risk stability issues or even data corruption.
  16. Nope, and if with a single cable you get that it's likely some enclosure specif issue, but I don't know that model.
  17. Do you mean there was only one cable or there is one cable now? If there was only one cable it's not the problem I suspected.
  18. Don't understand the question, just make sure only one cable (from one HBA) goes to the IBM disk array.
  19. Please don't start multiple threads for the same thing, there's no reason for a SED to not work with Unraid unless it's locked, please continue discussion on your other thread:
×
×
  • Create New...