Jump to content

JorgeB

Moderators
  • Posts

    67,565
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. This look like a device problem, is it faster if you transfer directly to the array with turbo write enable?
  2. It's possible, if the OP is not using the same power connector when connecting to the onboard SATA.
  3. That's not the problem, that causes the board not to post, or only detect part of the RAM, there's a tape mod to fix that.
  4. This means the HBA is not in IT mode or it's using an older firmware, you can do a new config with the disk using the SATA controller and check "parity is already valid" before array start.
  5. You can create a bug report, don't forget to include the diags.
  6. That confirms it's a lan problem, check if the desktop is linking at gigabit.
  7. If there are sync errors but no disk errors you can run a correcting check, if there are sync errors and disk errors, or just disk errors, replace the disk.
  8. If there are no errors you could rebuild knowing for sure parity was 100% valid.
  9. See here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  10. Nothing to lose if you try a non correcting check.
  11. Please post diags after the mover fails to move the file (mover logging should be enable).
  12. If it's the issue I'm thinking it can happens with any of the onboard SATA ports.
  13. Again lots of crashing but can't see the reason, one thing you can try it 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.
  14. No, but best to disable trim for now. Devices are tracked by serial, Unraid won't notice any difference.
  15. This is one of the most common scenarios, replacing an existing disk with a larger one.
  16. JorgeB

    Disk error

    Looks more like a power/connection problem, replace/swap cables.
  17. On second though pool names can't have spaces, so that must be a user share, try it on the disk share, you can enable disk shares on Settings -> Global Share Settings
  18. Don't remember seeing anyone using it so far, probably a recent model, but should be OK.
  19. You need to grab the diags before rebooting, but since both disabled disks are using the onboard SATA ports my first guess would be the rather common Ryzen SATA controller/IOMMU issue.
×
×
  • Create New...