Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,480

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    A few sync errors are normal, even expected, after an unclean shutdown.
  2. JorgeB
    Try this, also look at the SMART to calculate the GBs written per day, number of writes in the GUI doesn't mean much.
  3. JorgeB
    If the preclear read was successful they should be OK and the pending sectors can be "false positives", but you can also run an extended SMART test to confirm.
  4. JorgeB
    Diags are after rebooting so not much to see, wait for the error and post new ones.
  5. JorgeB
    Since the diags are after rebooting you can't see which drive and what type of errors, I assume disk3 since it appears to be failing, you can run and extended SMART test to config, then copy all the data you can or use ddrescue.
  6. JorgeB
    Correct.
  7. JorgeB
    Duplicate of
  8. JorgeB
    Like @trurlmentioned this is the result of having shares set to "most free" allocation method, parity writes will overlap making the performance considerably slower, note also that since v6.8.x "turbo write" will be disable once multiple array disk activity is detected making performance even worse, you'll see the same behavior with v6.8, I never recommend using most free as an allocation method precisely because of this performance issue, it can be a little better if used with some split level that avoids the constant disk switching for any new file.
  9. JorgeB
    If you mean multiple arrays, no it's not possible, not yet at least.
  10. JorgeB
    Changed Priority to Other
  11. JorgeB
    Please add diagnostics.
  12. JorgeB
    It is using RAID5 but due to a bug you'll need to manually subtract the parity size to know the correct free space, this is expected to be be fixed on next v6.9-beta release.
  13. JorgeB
    I guess you could copy the MBR of a working disk with dd and write it back to one of the new ones, if you feel comfortable with dd, after correcting the partition start size, I never tried that but it should work.
  14. JorgeB
    It won't, it needs a special signature.
  15. JorgeB
    Yep, that disk needs to be replaced.
  16. JorgeB
    Yep
  17. JorgeB
    Disk is failing, you need to replace it. P.S, You just post the diagnostics zip like before, it includes everything we need.
  18. JorgeB
    Initial error is logged as a disk problem, but it then dropped offline so there's no SMART report, power down, check/replace cables on that disk, power back on and post new diags.
  19. JorgeB
    Unlikely.
  20. JorgeB
    If that's the case then it shouldn't be a RAM problem, could still be a hardware problem, like controller or actual device.
  21. JorgeB
    If you mean the link to re-enable a drive it's below, but make sure the drive is healthy and the emulated disk is mounting correctly and contents look correct before rebuilding on top. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  22. JorgeB
    LSI controller is bound to vfio:
  23. JorgeB
    Checksum errors suggest a hardware problem, like bad RAM.
  24. JorgeB
    Just out of curiosity were the errors still happening on the Intel controller or you didn't test?
  25. JorgeB
    It passed the short test, you should run a long one, but if Seatools passed it should also pass, it did fail a long test before, so there were issues before.
×
×
  • Create New...