Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,457

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    See below for officially supported RAM speeds with Ryzen depending on CPU and config: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  2. JorgeB
    This can sometimes help with those NVMe errors: Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append" nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.
  3. JorgeB
    Please delete all those attachments and attach the single diagnostics.zip to a new post.
  4. JorgeB
    These means there's an NTFS UD device with filesystem issues, run chkdsk.
  5. JorgeB
    Macvlan call traces are usually related to having dockers with a custom IP address:
  6. JorgeB
    That's a RAID controller (though it might be flashable to IT mode) better to use any of the recommended LSI HBAs instead. Yes, but only SAS devices support 12Gb/s, SATA is still 6Gb/s max.
  7. JorgeB
    It shouldn't make any other drives link at lower then supported speeds, also note that you shouldn't have any performance issues because of that, SATA2 is enough for spinners, SSDs are a different story.
  8. JorgeB
    If they are mounting correctly they should be fine but it's also OK to run xfs_repair again to make sure.
  9. JorgeB
    There was an shfs segfault, rebooting should fix it.
  10. JorgeB
    You should post the diagnostics, they might provide some clues.
  11. JorgeB
    That's not a good idea, one SATA port should be split in two max, SATA plug is only ratted for 4.5A, a single disk can use 2.5A during startup.
  12. JorgeB
    The damage (if any) is already done, you'll need to run xfs_repair once it finishes, you can also cancel and run xfs_repair now then start rebuilding again from the start, this way you know if it's worth rebuilding and can also access the data during it. There's something else using the array, in the screenshot you can see extra reads on disk6, and on the diags there extra reads on disk3.
  13. JorgeB
    Also look for an available expander firmware update.
  14. JorgeB
    Possibly a backplane issue, you could try connecting a drive directly to the miniSAS cable to see if it makes any difference, also next time please post the complete diags: tools -> diagnostics.
  15. JorgeB
    You need to use --rebuild-tree, it will take several hours.
  16. JorgeB
    Note that because of the old firmware you might need to do a new config since all disks identifier string will likely change, this you be easier to do with all disks enable, if you can get them like that.
  17. JorgeB
    HBA is running a very old firmware (p05), first thing to try is to update it to current one (p16).
  18. JorgeB
    Check filesystem on disk3: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  19. JorgeB
    Don't mess with the disks/filesystem for now, not until the problem is fixed. That would be my next step, start with the one easier/cheaper to replace/swap, then run another read check.
  20. JorgeB
    It's affecting multiple devices, start by checking/replacing all cables, both SAS/SATA and power.
  21. JorgeB
    Constant ATA errors on both disk3 and parity, check cables.
  22. JorgeB
    Media share is set to split level 1, so if the folder where you're trying to copy to already exists on disk2 all new files will go there, split level overrides allocation method.
  23. JorgeB
    Changed Status to Closed Changed Priority to Other
  24. JorgeB
    This is likely a general support issue. most likely split level related, please start a thread on the general support forum, enable mover logging, run the mover and then download the diagnostics and attached them to your post.
  25. JorgeB
    It should be fine to remove as long as "power supply idle control" is correctly set in the BIOS, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
×
×
  • Create New...