Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,737

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Check this: https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-disabling-summary-fix/?do=getNewComment
  2. JorgeB
    If you don't need graphics use the x16 slot, x4 used with a PCIe 3.0 HBA still has plenty of bandwidth for 8 drives, just keep in mind that slot goes thought the DMI, so bandwidth is shared with the remaining SATA ports, etc.
  3. JorgeB
    Please don't crosspost, continue below:
  4. JorgeB
    Changed Status to Closed Changed Priority to Other
  5. JorgeB
    Not surprisingly GUI is showing the correct usage, btrfs reports around 165GiB used (or 177GB), and that is the actual used space, like mentioned du isn't reliable with btrfs.
  6. JorgeB
    There's clearly a hardware issue there, start by running memtest, if that doesn't find any issues board/controller would be my next suspect.
  7. JorgeB
    Unlikely, GUI should be reporting what btrfs is reporting being used, but please post the diagnostics to confirm.
  8. JorgeB
    Yes, they can make Unraid crash.
  9. JorgeB
    That's a good sign. Yep.
  10. JorgeB
    Yes. Don't see much point in doing that instead.
  11. JorgeB
    Yes, for disk3 make sure contents look correct, also look for a lost+found folder, before rebuilding on top of the old disk.
  12. JorgeB
    Only things you care for now are the emulated disks, emulated disk3 is mounting now so it can be rebuilt. Use -L and post output.
  13. JorgeB
    IIRC that was about enabling TRIM support for the array, at this time and since TRIM is not supported you can use any SSD, well except the V300 due to unrelated issues, AFAIK it's the only model that should be avoided and it's been discontinued for years now so likely not a problem anyway.
  14. JorgeB
    I see that later in the diags disk3 shows is mounted, since you mentioned it didn't and the diags showed that initially I didn't check until the end, in that case post the output of xfs_repair just for disk4.
  15. JorgeB
    Which is it?
  16. JorgeB
    Not because of that.
  17. JorgeB
    Btrfs check --repair should be used with much care, it might make things even worse, a btrfs filesystem can quickly go bad with RAM issues, Ryzen with overclocked RAM is known to corrupt data, you should fix data and if it were me I would then backup and recreate that filesystem.
  18. JorgeB
    First check was non correct, so seconds one was expect to find errors, though Ryzen with above spec RAM is known to corrupt data, fix that and run another correcting check, if it finds errors run a non correcting check without rebooting and post new diags.
  19. JorgeB
    You don't even need to do a new config, just unassign parity and start the array.
  20. JorgeB
    This is a hardware issue, diagnostics might give more clues.
  21. JorgeB
    Start by running memtest, also good to post the complete diagnostics.
  22. JorgeB
    Start the array in maintenance and post the output of: xfs_repair -v /dev/md3 xfs_repair -v /dev/md4
  23. JorgeB
    GUI will show the actual used space, except for some pool configurations, like a pool with an odd number of devices in RAID1, also du isn't reliable with btrfs, which I assume is what the pool is using, see if this helps get the space back: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
  24. JorgeB
    Like mentioned it doesn't look like the devices are the problem.
  25. JorgeB
    Problem is not just the SSD, there are multiple timeout errors with various devices, also some read errors with e.g. disk3, this is usually a power/connection problem, could also be an enclosure/backplane issue.
×
×
  • Create New...