Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,557

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Run a single stream iperf test.
  2. JorgeB
    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.
  3. JorgeB
    If there are no errors you could rebuild knowing for sure parity was 100% valid.
  4. JorgeB
    See here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  5. JorgeB
    Nothing to lose if you try a non correcting check.
  6. JorgeB
    It should.
  7. JorgeB
    Please post diags after the mover fails to move the file (mover logging should be enable).
  8. JorgeB
    If it's the issue I'm thinking it can happens with any of the onboard SATA ports.
  9. JorgeB
    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.
  10. JorgeB
    No, but best to disable trim for now. Devices are tracked by serial, Unraid won't notice any difference.
  11. JorgeB
    Still better to have SSDs even without trim.
  12. JorgeB
    This is one of the most common scenarios, replacing an existing disk with a larger one.
  13. JorgeB

    Disk error

    JorgeB replied to dheg's topic in General Support

    Looks more like a power/connection problem, replace/swap cables.
  14. JorgeB
    Looks like it.
  15. JorgeB
    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
  16. JorgeB
    Don't remember seeing anyone using it so far, probably a recent model, but should be OK.
  17. JorgeB
    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.
  18. JorgeB
    Dashboard CPU load includes I/O wait.
  19. JorgeB
    LSISAS2308: FWVersion(20.00.00.00) Upgrade the firmware to 20.00.07.00, previous p20 releases have known issues, including generating CRC errors.
  20. JorgeB
    By the screenshot I can't tell if that's a disk share or user share, you can name them whatever you want.
  21. JorgeB
    iperf looks OK, if you haven't yet try copying from a disk share instead of user share.
  22. JorgeB
    You need v6.9.rc1 for the NIC on that board to be supported.
  23. JorgeB
    You can do this: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  24. JorgeB
    Because the disk wasn't disabled, any write error Unraid would disable the disk. Just do a standard replacement, as long as no more errors on a different disk it should be rebuilt correctly.
  25. JorgeB
    Diags are after rebooting so we can't see what happened, but the disk looks fine, so replace/swap cables to rule them out and rebuild on top.
×
×
  • Create New...