Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,647

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Always assumed this was the intended behavior.
  2. JorgeB
    You need to unmount the filesystem first: umount /x
  3. JorgeB
    This setting also applies to the cache drive when it's part of a share, the higher value of the two is the one which will kick in first.
  4. JorgeB
    None of the NICs is detecting a link: Link detected: no
  5. JorgeB
    Yep. See reply above.
  6. JorgeB
    You'd need to change it back and run the mover.
  7. JorgeB
    Mover won't move files that already exist on destination.
  8. JorgeB
    Try also the above, if it doesn't help not much more you can do, other then using different hardware.
  9. JorgeB
    Enable mover logging, run the mover, post diags.
  10. JorgeB
    I linked you a specific post: append initrd=/bzroot pci=nommconfto
  11. JorgeB
  12. JorgeB
    Those are normal with Seagate drives.
  13. JorgeB
    No, that's SAS1, 92xx models are SAS2, 93xx models are SAS3.
  14. JorgeB
    I never used it, compare with the configuration in the link.
  15. JorgeB
    That's not unheard of if it is a disk, though unless it keeps happening practically impossible to find the culprit.
  16. JorgeB
    Not always clear to see if anything was fixed with xfs_repair, unless you check the exit code, see if it makes any difference.
  17. JorgeB
    Forgot to mention, you need to run a filesystem check on the cache device.
  18. JorgeB
    Yep, that rules out the unclean shutdown and makes the sync errors much more important, since RAM is ECC and the second check found the same errors that's unlikely the reason, first suspect would be a disk.
  19. JorgeB
    May 4 19:20:31 unRAID emhttpd: unclean shutdown detected A few sync errors are normal after this.
  20. JorgeB
    Yes, you can also use raid0 (if the devices are all of the same capacity). Yes, pool will just be rebalanced as you add one or more devices.
  21. JorgeB
    Known issue with that Marvell controller, this works for some: https://forums.unraid.net/bug-reports/stable-releases/disks-missing-after-upgrading-to-670-r536/?do=findComment&comment=4583
  22. JorgeB
    LSI controllers only trim SSDs with deterministic read after trim, and with recent firmwares SAS2 models can't trim any devices with Linux, SAS3 can (on the supported models).
  23. JorgeB
    https://lime-technology.com/forums/topic/72837-error-log-filled-to-100-in-1day-47min-with-this/?do=findComment&comment=669775
  24. JorgeB
    Yes, you can use for example the UD plugin.
  25. JorgeB
    There's no SMART report for disk1 on the diags, see if you can get one manually.
×
×
  • Create New...