Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Enable the syslog server and post that after a crash.
  2. JorgeB
    Since that's a RAID controller you likely need to create a JBOD/RAID0 volume for each device, but note that it's not recommended, and if later you change controllers you are likely going to run into problems.
  3. JorgeB
    Post output of: fdisk -l /dev/nvme0n1
  4. JorgeB
    Try this: https://forums.unraid.net/topic/87409-kworker-100-cpu/?do=findComment&comment=861527
  5. JorgeB
    You can enable turbo write for better arrays speeds at the expanse of all disks spinning up for writes.
  6. JorgeB
    This happens when the fs runs out of space for a new metadata chunk, much less likely to happen with newer kernels, one way to get around this is to freu up some space, pre-allocate some metadata, then delete that when it's getting full, I can post detailed instructions if you want, but first you'd need to free up some space, like 100 or 200GB should be enough.
  7. JorgeB
    No link being detected on either port of the Mellanox NIC, check cables/transceivers, could also be a bad NIC.
  8. JorgeB
    Oct 12 17:42:49 ZACAV-UNRAID kernel: ata3: SATA link down (SStatus 0 SControl 300) Oct 12 17:42:49 ZACAV-UNRAID kernel: ata1: SATA link down (SStatus 0 SControl 300) Oct 12 17:42:49 ZACAV-UNRAID kernel: ata2: SATA link down (SStatus 0 SControl 300) Oct 12 17:42:49 ZACAV-UNRAID kernel: ata4: SATA link down (SStatus 0 SControl 300) According to this there are no devices connected to these ports, are the disks spinning up? P.S. Intel onboard controller is set to IDE, change to AHCI in the BIOS.
  9. JorgeB
    Enable the syslog server and post that after a crash.
  10. JorgeB
    Diags are from v6.9.2? Where's the permanent log?
  11. JorgeB
    There's something else reading from disk2.
  12. JorgeB
    Pool is showing issues with both devices, run a correcting scrub and post the output.
  13. JorgeB
    It should work as two 14TB hard drives.
  14. JorgeB
    Do a manual update.
  15. JorgeB
    Devices names changed, this can happen with some controllers and/or using an old firmware, do a new config, assign all devices to their original slots and check "parity is already valid" before array start.
  16. JorgeB
    Please post the diagnostics.
  17. JorgeB
    Depends on if the errors are from the device you're going to remove, best to post new diags.
  18. JorgeB
    Please post the diagnostics after running the command on a fresh boot.
  19. JorgeB
    You just create a new pool and assign the device there, then need to adjust all the mappings, e.g. /mnt/disks/ud_name/appdata becomes /mnt/pool_name/appdata
  20. JorgeB
    Try updating to v6.11.1
  21. JorgeB
    I'm not so sure it's a plugin issue, especially considering that most in the list are some of the most used ones, e.g., if CA or UD were the problem I would expect many more cases, not the half a dozen reported (at least so far), I guess it could be an interaction between two different plugins, but have my doubts, still since it's easy to rule them out we should do that first.
  22. JorgeB
    Oct 12 01:48:17 PlexServer kernel: ata6: limiting SATA link speed to 3.0 Gbps Oct 12 01:48:22 PlexServer kernel: ata6: COMRESET failed (errno=-16) Oct 12 01:48:22 PlexServer kernel: ata6: reset failed, giving up Oct 12 01:48:22 PlexServer kernel: ata6.00: disable device One of the cache devices dropped offline again, did you check/replace cables? Both power and SATA.
  23. JorgeB
    Upgrade first since that functionally is broken on v6.9, then see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419
  24. JorgeB
    Does it make a difference if you connect the Seagate drives to the LSI? You can swap with two disks there to the onboard SATA.
  25. JorgeB
    It's already included with Unraid 6.11
×
×
  • Create New...