Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61,692

  • Joined

  • Last visited

  • Days Won

    650

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Something is still causing the errors, so try and reduce some more, or try running just some services at a time to try and find the culprit.
  2. JorgeB
    I don't know, but if it was added likely there's a good reason, could be for example due to data corruption or other serious problem.
  3. JorgeB
    If the tree log is the only problem it should be fixable with: btrfs rescue zero-log /dev/nvme1n1p1 Then try to mount again, if it still doesn't mount post new diags.
  4. JorgeB
    Yes, if they are in raid1. Nope.
  5. JorgeB
    Possibly some quirks added to the kernel for the USB bridge: usb-storage 1-5.3.3:1.0: Quirks match for vid 174c pid 55aa: 400000 It might be downgrading the speed to USB 2.0, we really don't recommend USB for array/pool devices.
  6. JorgeB
    HBA BIOS is still independent and it should be upgradable.
  7. JorgeB
    Like mentioned for enterprise SSDs it's not usually a problem.
  8. JorgeB
    Yes, that's what it looks like, HBA should not be the problrem, suspect cable/enclosure problem, I would start with a different cable since it's the easiest and cheapest to replace.
  9. JorgeB
    If they are assigned to the array they cannot be trimmed, even if there's no parity.
  10. JorgeB
    This is likely a general support issue, not a bug, start with the HBA which is constantly resetting: Nov 21 07:45:51 NAS kernel: mpt2sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready Nov 21 07:45:51 NAS kernel: mpt2sas_cm0: fault_state(0x265d)! Nov 21 07:45:51 NAS kernel: mpt2sas_cm0: sending diag reset !! Nov 21 07:45:53 NAS kernel: mpt2sas_cm0: diag reset: SUCCESS Update to latest firmware, then make sure it's well seated, sufficiently cooled and/or try a different PCIe slot if available.
  11. JorgeB
    Array doesn't support trim for SSDs, but that is much less important with enterprise models, both for performance and durability.
  12. JorgeB
    You can, or like mentioned you can add the new device to the same pool, by default Unraid will create a raid1 pool, then remove the old device.
  13. JorgeB
    That would be the main suspect, test read speed over SMB for those drives.
  14. JorgeB
    Run the diskpeed controller benchmark, to rule out any bottlenecks there.
  15. JorgeB
    It was wiped, but the select-super command restored a backup superblock, if you assign it to a pool it should mount, you can then add the new device to the pool and once that's done, remove the old one.
  16. JorgeB
    I meant is it still going at 20MB/s? It could have been a slower zone on one of the disks.
  17. JorgeB
    Various out of memory errors, limit RAM setting for the various services.
  18. JorgeB
    Intel support page is where it should be, if one exists.
  19. JorgeB
    Look for a firmware update for the NIC.
  20. JorgeB
    Grab diags, reboot, grab new diags and post both.
  21. JorgeB
    The syslog in the diags starts over after every boot, and if the server shuts down on its own it's most likely hardware and probably there won't be anything relevant logged anyway, but you can enable the syslog server and post that after the next crash.
  22. JorgeB
    Could have just dropped offline, in that case a reboot will bring it back, also make sure you are using a USB 2.0 port. Difficult to guess, and any config changes won't be saved.
  23. JorgeB
    No btrfs filesystem exists on old cache, possibly it's been wiped, try this: btrfs-select-super -s 1 /dev/sdb1 If the command is successful post again the output of btrfs fi show
  24. JorgeB
    Similar issue as before, on the same controller, note that unless the IDs changed it's the Asmedia controller dropping the drives.
  25. JorgeB
    I'm used to see those Plex Media scan segfaults on various diags, so probably normal, other errors are also harmless.
×
×
  • Create New...