Jump to content

JorgeB

Moderators
  • Posts

    67,594
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. For gigabit this one is a good choice: https://www.amazon.com/-/es/Adaptador-Intel-Gigabit-PCI-EXPI9301CTBLK/dp/B001CY0P7G/ref=sr_1_3?__mk_es_US=ÅMÅŽÕÑ&dchild=1&keywords=intel+gigabit+nic&qid=1615476200&sr=8-3
  2. Based on the trans id the docker image is practically new, see here for ho to restore your dockers: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  3. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  4. Assuming loop2 is the docker image, if you're not sure post the complete diagnostics, delete and recreate.
  5. Try replacing or swapping both cables, if still issues please post the complete diags: Tools -> Diasgnostics
  6. Try it in a different PCIe slot if available, or another computer just to make sure it's working, until it's detected in the system devices it will never work.
  7. It's a problem with the SAS2LP, you're not the first with issues after upgrading, you can try this to see if it helps but if it's an option I would recommend replacing it with an LSI, since those controllers have several known issues.
  8. Pools are always mounted at //mnt/name_of_pool, you can also access the share in /mnt/user/name_of share (or /mnt/name_of_pool/name_of_share if disk shares are enable).
  9. SMART test failed, so it should be replaced.
  10. Please post the diagnostics: Tools -> Diagnostics
  11. btrfs check --repair should be use with much care, there's even a warning about it when you use it, and it can make things even worse, probably best to try and recover the data and then re-format, if still possible.
  12. If these are Seagate drives it's normal, if you still need help post the complete diagnostics.
  13. There's a format button next to array start/stop. Should be OK, but I've never used it. https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  14. According to the syslog after booting and when you started the procedure there was only one cache device assigned, so you didn't start like the instruction, i.e., unassign one of the devices and start the array, this will erase the unassigned device, since you didn't do this it wasn't erased, and looks to me like that was what caused the problems later, not sure if or how you can recover the pool now.
  15. Devices connected to the HBA are constantly re-setting, check all connections, could also be a power or backplane problem.
  16. Yes. It's OK if you use a pool, and you can have a single device pool if caches slots are set to >1.
  17. There's nothing logged, so no idea what's causing the problem, doubt it's MyServers, but try uninstallling it.
  18. According to wiki max Reiser FS volume size is 16TiB, so likely why you're running into trouble, best to upgrade to Unraid V6 and convert to XFS.
  19. You can try this to capture the complete crash.
  20. Filesystem corruption is most usually caused by an unclean shutdown or hardware problem, like bad RAM.
  21. Make sure you're booting using legacy BIOS/CSM, memtest doesn't support UEFI boot.
  22. This is one way: https://forums.unraid.net/topic/93846-btrfs-error-with-new-system-m2-ssd/?tab=comments#comment-867992
×
×
  • Create New...