Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,771

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Cache filesystem is fully allocated so you need to re-balance to free up some unallocated space for new metadata chunks to be created, more info below: https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551 On a side note there's a very high metadata usage compared to data, not that this is necessarily bad, just unusual, do you have a lot small of files up to 2KB?
  2. JorgeB
    You can add parity first, but there will be read errors from disk2 during the sync, so Unraid won't be able to then correctly rebuild it.
  3. JorgeB
    Without parity Unraid does a read check, the errors are no sync errors, but read errors, from disk2 which is failing, since there's no parity best way to try and recover as much data as possible is to use ddrescue, then you can sync parity with the cloned disk.
  4. JorgeB
    The bad RAM corrupted the filesystem, best way forward is to backup the pool, reformat then restore the data.
  5. JorgeB
    That's a SMART warning, might or note be serious, need the SMART report. That's from the UD plugin, you can remove them from there, or toggle the historical devices button to not show then.
  6. JorgeB
    Since the emulated disk is mounting the partition was successfully recreated, now: -stop the array -re-assign disk4 -start array to begin rebuild Once that's done you need to repeat the process for all the other data disks, one at a time or two at a time since you have dual parity, also recommend replacing those controllers with recommended LSI HBAs ASAP.
  7. JorgeB
    Run a read test with the diskspeed docker to see if all disks are performing normally.
  8. 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.
  9. JorgeB
    Test also failed, they should still be under warranty.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. JorgeB
    Not sure, you can try, or restore to a different path.
  16. JorgeB
    Tested them one a time to see if you can find the culprit.
  17. JorgeB
    Make sure the correct Power Supply Idle Control is set, this way you can still have C-States enable to improve power consumption.
  18. 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.
  19. 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.
  20. JorgeB
    For backups it would be much better, assuming the sync is done frequently enough.
  21. 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.
  22. 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.
  23. JorgeB
    Please post the diagnostics.
  24. 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.
  25. 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.
×
×
  • Create New...