Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,504

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    I don't know why but it is this command, ran it on a pool device and it immediately spun up and started showing the bogus temp in the GUI:
  2. JorgeB
    Unraid doesn't support Infiniband, can't help with the other question but it shouldn't be difficult to find an answer by googling it.
  3. JorgeB
    Thanks, but those tests are also here, I keep updating the original post as I test new controllers.
  4. JorgeB
    I would start by replacing/swapping all cables connected to the LSI attached devices, SATA and power, to rule those out first.
  5. JorgeB
    Start here.
  6. JorgeB
    It is, just remove one of the devices, see here.
  7. JorgeB
    It aborted because there was a read error, i.e. bad sector.
  8. JorgeB
    Most likely, but this is getting OT, you can start a general support thread and please include diags.
  9. JorgeB
    Yes, /mnt/user0 is the same content as /mnt/user except cache.
  10. JorgeB
    fstrim runs on a mounted filesystem, not on the device, e.g. use fstrim -v /mnt/cache Edit to add: if you want to do a full trim on a device you can use: blkdiscard /dev/sdX Note that it will completely wiped.
  11. JorgeB
    The symptoms look more like a hardware problem, but you can try running in safe mode without any dockers/VMs for a couple of days to rule out most other issues, if it's not stable as a basic NAS it's most likely hardware problem.
  12. JorgeB
    Sorry, misread the post.
  13. JorgeB
    Yep.
  14. JorgeB
    IIRC it's not done at mount time, it's done at decryption time, and Unraid already does that, look for the luksopen command in the syslog, it should include "--allow-discards"
  15. JorgeB
    Did you see this?
  16. JorgeB
    I don't use encryption but pretty sure it already does that. Also mkfs already does a full device trim, with both btrfs and xfs.
  17. JorgeB
    Not that I recall, can you move the file manually, if not maybe there will be a more detailed error.
  18. JorgeB
    Both times errors only happened on devices connected to the LSI, could be cables, could be power, could be the controller, though the controller would be my last suspect, unless there are doubts if it's be a chinese fake or if it's overheating. As for disk1, saw that a few times, with power but mostly with the SATA plug, sometimes you can reuse the existing cables, with the broken part inside, not ideal but don't known of another way to fix it, bet would be to replace the disk.
  19. JorgeB
    Should be OK, don't remember reading anything against that, though doubt you'll notice much performance difference, if any.
  20. JorgeB
    I've now confirmed this plugin is interfering with pool device spin down, when possible please take a look at this: https://forums.unraid.net/bug-reports/prereleases/690-beta22-no-spin-down-of-pool-hdds-r976/?do=findComment&comment=10202
  21. JorgeB
    Changed Status to Solved
  22. JorgeB
    Color me embarrassed , just recently I was reprimanding a user by making a bug report without testing in safe mode first, and I did the same, so pool spin down works correctly in safe mode, I need to test which plugin is causing the issue but if I had to guess probably the IPMI plugin.
  23. JorgeB
    It shouldn't need regular balancing on current kernel, since kernel 4.15 IIRC
  24. JorgeB
    Please post new diags.
  25. JorgeB
    Yes. Those attributes are not cable related, and likely no indication of any issue, but if you want post the diags once the SMART test and rebuild finish.
×
×
  • Create New...