Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,460

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Nothing jumps out, most likely it's related to the earlier parity swap, for some yet unknown reason some users then have sync errors in the extra parity section, run a correcting check, then a non correcting one, as long as no more errors are detected you should be fine.
  2. JorgeB
    Just the SATA cable.
  3. JorgeB
    Possibly, if you post the diagnostics.
  4. JorgeB
    Unraid can't protect against filesystem corruption, if corruption keeps happening always on the same disk it might be a good idea to re-format and create a new filesystem, but you'd need to backup all data there first, if corruption is happening on multiple disks without an apparent reason there's likely some hardware problem, like bad RAM, controller, etc.
  5. JorgeB
    raid1c3/c4 will only work on the v.6.9 betas.
  6. JorgeB
    You can try this.
  7. JorgeB
    Lots of UDMA_CRC errors, replace the SATA cable and rebuild on top, assuming the emulated disk shows the correct data.
  8. JorgeB
    Disk looks OK but it's not good that it can't complete a SMART test, if it's in warranty replace it, if not run a parity check or preclear read test to see if there are any read errors.
  9. JorgeB
    There's no risk trying to mount the emulated disk, and whatever is there is what there will be on the rebuilt disk, parity was already updated during the filesystem check to reflect that.
  10. JorgeB
    This means you have more connected devices than your license allows.
  11. JorgeB
    You don't have any share set to cache="yes", only those will be moved to the array, see the GUI help.
  12. JorgeB
    You need to use -L, usually it's mostly OK. You can still rebuild with current controllers, better than having the array unprotected, but if you can leave the server off then wait for the new controllers.
  13. JorgeB
    If that's one hour of usage after the change it still wrote about 30GB, that's 720GB per day. Edited to correct values, had misplaced a 0 before.
  14. JorgeB
    You forgot the diagnostics: Tools -> Diagnostics
  15. JorgeB
    That's fine, they are x8, and they are plug'n'play and use the sames cables.
  16. JorgeB
  17. JorgeB
    Disk17 is really failing, still with a good controller it would just get disable instead of bringing all the other disks down with it, you should replace them with and LSI controllers when possible. Check filesystem on disk17 and if all OK then replace it. https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  18. JorgeB
    Changed Status to Closed Changed Priority to Other
  19. JorgeB
    This is a general support issue, please start a thread in the general support forum and don't forget to add the diagnostics: Tools - Diagnostics
  20. JorgeB
    Looks like the one of the typical SASLP problems, reboot and post new diags so we can check the SMART reports.
  21. JorgeB
    It is the docker image.
  22. JorgeB
    It usually is, but we'd need the full diags to confirm, and if it is it needs to be recreated.
  23. JorgeB
    Not necessarily, a failing PSU can cause stability issues.
  24. JorgeB
    Not me but there are some post of users with 4TB parity, IIRC there's one with like 16 4TB SSDs. For parity you want an SSD with good performance and high endurance, since parity can never be trimmed, even when LT adds trim support for the array, also it will have to endure much more writes than the array devices, I would recommend a good NVMe device or an enterprise level SSD.
  25. JorgeB
    smartctl -t long /dev/sdX Should be.
×
×
  • Create New...