Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,880

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    This was before the parity sync correct?
  2. JorgeB
    That would be OK for now, as long as an extended SMART test or parity check completes without any errors.
  3. JorgeB
    Are you using xfs or btrfs?
  4. JorgeB
    Nope, run a non correcting parity check after the sync.
  5. JorgeB
    It it still showing pending sectors? It should have gone to zero after the sync.
  6. JorgeB
    Up to you, should be OK for now, I would give a 2nd chance but if any more errors appear then replace it.
  7. JorgeB
    Please post the diagnostics.
  8. JorgeB
    I would just install it in Unraid and sync parity, then run a non correcting check to confirm all is good.
  9. JorgeB
    See where? There were no errors on the previous diags, but disk9 has pending sectors so it's likely failing, but since there's only one parity drive not much you can do about it, replace it after the other disk finishes rebuilding, but there could be some data loss.
  10. JorgeB
    Same issue reported here, unfortunately still not clear what the cause is.
  11. JorgeB
    Nothing obvious logged, try booting in safe mode to rule out any plugin issues.
  12. JorgeB
    Test passed, if the emulated disk is mounting and contents look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself Before doing it it might be a good idea to replace/swap cables/slot to rule that out if it happens again to the same disk.
  13. JorgeB
    Please use the existing plugin support thread:
  14. JorgeB
    You can run memtest for 24H, but that mostly tests RAM and it's only conclusive if it finds errors.
  15. JorgeB
    You'll have to force a reboot if needed, then choose safe mode in the boot menu options.
  16. JorgeB
    That's has info, but not much to see since it's right after rebooting, only can see that the array is not stopping because something is still using it.
  17. JorgeB
    Install the Dynamix File Manager plugin.
  18. JorgeB
    That points to a different issue, and likely a hardware problem if it persists after downgrading to a previously known good release.
  19. JorgeB
  20. JorgeB
    All empty also, all files are 0Kb
  21. JorgeB
    If it doesn't enable the syslog server and post that after a crash.
  22. JorgeB
    This is usually a BIOS/hardware issue, try this first: https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009 if it doesn't help see here to at least try and suppress the error: https://forums.unraid.net/topic/111161-pcie-errors/?do=findComment&comment=1013378
  23. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  24. JorgeB
    For non encrypted devices wiped with wipefs you just type: btrfs-select-super -s 1 /dev/sdX1 or btrfs-select-super -s 1 /dev/nvmeXn1 and usually that everything you need, encryption add another layer, you'd need to first restore the LUKS headers from a backup (if available) then run: btrfs-select-super -s 1 /dev/mapper/sdX1 or btrfs-select-super -s 1 /dev/mapper/nvmeXn1
  25. JorgeB
    Looks like the NVMe device was wiped with wipefs, if it wasn't encrypted it's usually easy to recover, but with encryption I don't know how, first the device would need to be decrypted but now it's not being likely because the LUKS heaters were also wiped.
×
×
  • Create New...