Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,765

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Run a read test with the diskspeed docker to see if all disks are performing normally.
  2. JorgeB
    Looks to me like the disk is not being "released" to Unraid, try preclearing the disk manually or using the UD preclear plugin to see if it's any different.
  3. JorgeB
    Test also failed, they should still be under warranty.
  4. JorgeB
    There's nothing visible in the diags, if you suspect issues with the cache filesystem you can see if the array starts without it, stop the array, if cache is used for docker/VMs disable those services, unassign cache device, start array.
  5. JorgeB
    That's not the point, point is if any data was written to the emulated disk parity will no longer be valid if we use actual disk instead. In that case and IMHO best way forward would be to do a new config with the new disk2 and the remaining disks and re-sync parity.
  6. JorgeB
    SSD failed the SMART test so it should be replaced now, UDMA CRC errors are a connection issue, if the attribute keeps rising start by replacing that SATA cable.
  7. JorgeB
    You just need to assign the devices as they were, or copy super.dat form the flash drive, pools will still need to be re-assigned.
  8. JorgeB
    That's not what the link says to do, follow the steps below to test with one of the disks: stop array unassign one of the data disks start array post new diags.
  9. JorgeB
    Not sure, you can try, or restore to a different path.
  10. JorgeB
    Tested them one a time to see if you can find the culprit.
  11. JorgeB
    Make sure the correct Power Supply Idle Control is set, this way you can still have C-States enable to improve power consumption.
  12. JorgeB
    It should, does it work if you connect disks directly to that HBA port? Yes, even on the same HBA, one connected to each port, or by cascading them, but cascading is worst for performance.
  13. JorgeB
    That's still above max supported speed and known to corrupt data in some cases, see here, for that config it's 2133 or 1866MT/s depending on the number of ranks.
  14. JorgeB
    For backups it would be much better, assuming the sync is done frequently enough.
  15. JorgeB
    Mirror is for redundancy, it won't help with filesystem corruption which is the problem here, there are some recovery options here, see if you can backup anything important then re-format the pool and restore the data.
  16. JorgeB
    Cache filesystem is going read-only, btrfs is also detecting data corruption on both devices, this is usually a RAM problem, start by running memtest.
  17. JorgeB
    Please post the diagnostics.
  18. JorgeB
    That's basically impossible, data should be all fine except if there was any data being written at the time of the server reset.
  19. JorgeB
    The syslog will say "parity incorrect" or "parity corrected" for those errors, if it's incorrect it was the auto check and you need to run a correcting check.
  20. JorgeB
    Btrfs raid5 has some known issues, it can be used, and I do, but I also have good backups.
  21. JorgeB
    Are you sure? Auto parity check after an unclean shutdown is non correct, or post the diags so we can check.
  22. JorgeB
    No, based on the number of parity drives. No, never format, read the link above.
  23. JorgeB
    That's it, and both backups you did should have the same data.
  24. JorgeB
    Expander is an Intel RES2SV240 with the latest firmware, which is known to work great, unless it's failing.
  25. JorgeB
    Both are logged as disk issues and both disks have non zero number elements in grown defect list, which is never a good sign with SAS disks, you can run SMART long tests to confirm.
×
×
  • Create New...