Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,616

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
  2. JorgeB
    Try a different port/controller, but SATA cable is still the most likely culprit.
  3. JorgeB
    Enable this then post that log after a crash.
  4. JorgeB
    Looks like a power/connection problem.
  5. JorgeB
    You can remove all the SSH stuff form the GO file: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0#SSH_Improvements
  6. JorgeB
    I wanted the diags showing disk4 failing to mount, to see what the issue was.
  7. JorgeB
    Since they are on different controllers, errors on two different disks at the same time suggest a power/connection issue.
  8. JorgeB
    Likely related to this: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/?do=findComment&comment=10972
  9. JorgeB
    Replace the SATA cable, Samsung SSDs are very picky with cable quality.
  10. JorgeB
    Even more strange if it's intermittent, didn't notice any issues so far with the LSI 9300-8i.
  11. JorgeB
    Not with high water allocation method: https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
  12. JorgeB
    After replacing the wrong disk you either needed to let the rebuild finish or reassign both original disks, re-sync parity then start over.
  13. JorgeB
    No, but you can just create one.
  14. JorgeB
    Yeah, looks share.cfg is not there by default, note that split level overrides allocation method, so for the TV share if the folders already exist on disk1 all new data will go there, that should not happen with the Photos shares, can you confirm if you copy files there they go to disk1?
  15. JorgeB
    I don't know if this is an easy fix, or even possible to fix if it's related to FUSE, I did what I can, which is to create a bug report.
  16. JorgeB
    There's no share.cfg on the diags, does that file exist in the config folder?
  17. JorgeB
    New config is not used to rebuild disks: Also, parity can't help with a formatted disk, since it's updated in real time, and trying to rebuild a disk after a format will just rebuild the formatted disk, you'll need to try UFS explorer or a similar data recovery program.
  18. JorgeB
    Disk dropped offline, if it's not connections look at the PSU, it might be starting to fail.
  19. JorgeB
    This could be a filesystem issue, diags would show.
  20. JorgeB
    That screenshot shows that cache is still mounted, array can't be stopped.
  21. JorgeB
    This would completely wipe the device, without diags can't see why it didn't work, another option would be to use wipefs.
  22. JorgeB
    If the UD NVMe device was formatted with a relatively recent version of UD you can assign it to a new pool, start the array, then add the other NVMe device.
  23. JorgeB
    Syslog starts over after every reboot, enable this then post that log after a crash.
  24. JorgeB
    Sorry, no more ideas, likely some hardware bottleneck, CPU is kind of old and SMB is single threaded, but still should be faster than that.
  25. JorgeB
    It doesn't. You can take a look here for some performance numbers: https://forums.unraid.net/topic/41340-satasas-controllers-tested-real-world-max-throughput-during-parity-check/
×
×
  • Create New...