Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Are you sure? It's working for me. NIC drive does appear to be missing, was it present in rc3 or did you upgrade from v6.10?
  2. Delete key.key from the flash drive config folder and reboot.
  3. Nothing obvious I can see, try rebooting in safe mode and/or leave all docker containers off and if server is normal then enable one by one.
  4. That is just the syslog and too big to open, please post the complete diagnostics.
  5. Forgot to mention, you can see how the next disk would turnout by unassigning the disk and starting the array and letting Unraid emulate the disk, if it doesn't mount check filesystem on the emulated disk, and if you are happy with the results then rebuild.
  6. It does look like a cable problem, but there were also issues when connected to the HBA with different cables, did you also replaced/swapped the power cable?
  7. Sorry, I don't use either, probably best to do another post with a title about that.
  8. Don't see how that could be the problem when you were getting low speeds with iperf, iperf only tests network speed, it has nothing to do with actual write speeds.
  9. You'd need to manually move everything back. You'd need to rebuild each disk one at a time, but because of the filesystem corruption that occurred with disk1 it makes me think that the HBA damaged more than just the MBR, so there might be some Dara loss, this is one of the reasons we don't recommend using RAID controllers with Unraid.
  10. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  11. Please post the diagnostics from v6.11
  12. Some strange crashing going on that might be affecting that, please reboot it the disks still don't mount post new diags.
  13. There's no standard max number of PCIe devices, depends on the board, check the manual to see if any PCIe slots are shared with other devices, if not you can have as many devices as there are slots.
  14. SMART shows them logged as disk problems, but with LBA 0 which is strange, since the SMART tests passed I would keep it for now.
  15. El disco se puede identificar por el número de serie.
  16. This, any sectors that have never been written are known by the firmware, so the disk returns zeros directly from the controller, it doesn't read the disk surface, hence the higher speeds.
  17. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
×
×
  • Create New...