Jump to content

JorgeB

Moderators
  • Posts

    67,871
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Where does it stop in the boot process?
  2. If the old disk is expected to be good you can use, if it's known bad don't.
  3. Usually no, but make sure you are using both channels.
  4. There's no procedure, you just swap the cables physically, noting is done in Unraid.
  5. This would be much better than using USB, assuming that m.2 slot supports PCIe.
  6. I suspect more a compatibility problem, especially since there's another user with what look like issues with an identical AMD board SATA controller and an Ironwolf drive, 12TB in that case. I'm not suggesting you get new disks for now, just connect both parity drives to the HBA swapping other disks to the SATA controller, just not disk1 since it's the same model, connect for example disks 2 and 3 to the onboard SATA and both parity disks to the HBA in their place.
  7. Yes same size or larger, initially and to get the emulated disk you can even use a known bad disk in that slot, as long as it's detected, still needs to be same size or larger, but then you need a good one to rebuild.
  8. Reboot and get diags/syslog right after array start to see if there's any difference.
  9. Suspicious that there are issues with two of the same model disk connected to the onboard controller, disk1 on the other hand is the same model but connected to the HBA and no issues there, if you have free ports connect one or both parity disks to the HBA, if you don't swap with other disks (except disk1 in case it cause problems to that one).
  10. Nothing relevant logged, if the server was stable and started crashing recently without any change it suggests a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  11. Once that's done run a correcting parity check since parity is not 100% valid, you might want to replace/swap cables on disk6 to rule that out if there are more errors.
  12. Copy the syslog to a share you can access over the network then attach it here, e.g.: cp /var/log/syslog /mnt/user/share_name/syslog.txt
  13. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 Also check that there's no other device with the same name in the network.
  14. Just restore the config folder to the flash drive, overwrite any existing files.
  15. Did some more testing, diags work correctly until v6.11.0-beta3, they don't starting with -beta4, so it's some change in that release that introduced this problem.
  16. Enable the syslog server and post that after a crash together with the complete diagnostics.
  17. Good thinking but it's not that, tried it on a test server, basically empty with just the default system and appdata shares, tried with both shares on disk1 one with shares set to use cache=no and both shares on cache with shares set to cache=prefer, either way the diags don't show which disk(s) they are using.
  18. 99.99% is good, do you also already have a replacement for disk4?
  19. Update to v6.10.3 or v6.11.0, you can update manually, the array not working is not a problem.
  20. Now that I think more about I'm not sure that the "parity is already valid" option worked with v6.1.x, I believe there was a bug with that, @Kevin Tmake sure you update first.
  21. JorgeB

    Which 10g NIC?

    Yes. Not sure those are standard modules but they are not removable anyway.
  22. It will rebuild the disk you unassign in this part:
×
×
  • Create New...