Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Looks more like a connection/power problem but wait for the SMART test to finish and check the results, or post new diags.
  2. JorgeB
    Please post new diags.
  3. JorgeB
    Please post the diagnostics.
  4. JorgeB
    Unlike the screenshot diags show that the disk is now rebuilding, if the rebuild fails post new diags before rebooting.
  5. JorgeB
    Nothing obvious in the logs, do you know the time in the log when it stopped working?
  6. JorgeB
    Unassign disk1, start array, post new diags.
  7. JorgeB
    This one might be recent, drive looks like it rotated that log, most use 16 bits to store this value which means 65,535 is the max value.
  8. JorgeB
    The instructions should still work fine with v6.1.9.
  9. JorgeB
    Lets see if @dlandonhas any ideas.
  10. JorgeB
    A new config will re-enable all disks.
  11. JorgeB
    Maybe, you can cancel the current run and see if both processes stop, if yes just resume, if not kill the other one then resume.
  12. JorgeB
    You need to wait for an Unraid release with kernel 6.0 for experimental support, production support is expected for kernel 6.1.
  13. JorgeB
    Oct 4 17:13:18 Tower kernel: XFS (sdl1): Corruption warning: Metadata has LSN (-977856008:384760175) ahead of current LSN (15:2420592). Please unmount and run xfs_repair (>= v4.3) to resolve. Check filesystem on that pool.
  14. JorgeB
    If you updated using the GUI go to Tools -> Update OS and click "Restore"
  15. JorgeB
    Please post the diagnostics.
  16. JorgeB
    That should work.
  17. JorgeB
    Run another check, if no more errors are found you are likely fine.
  18. JorgeB
    Unlikely that just NFS would crash, I've never used NFS so cannot really help with that but try updating to v6.11.0, newer kernel might help.
  19. JorgeB
    It does.
  20. JorgeB
    shfs crashed, rebooting should bring the shares back, if you are not using NFS disable it since it looks like the crash was related to that.
  21. JorgeB
    Like mentioned initially it didn't look like a disk problem, so most likely it's a power/connection issue, and if it has been happening with multiple disk the more likely that is.
  22. JorgeB
    You can still access the data in the other disks using the disk shares, if enabled.
  23. JorgeB
    It can affect the rest of the data since Unraid joins the contents from all the disks, so filesystem issues in one disk can affect the complete share.
  24. JorgeB
    Click on the flash drive and add it to the default boot option, like this: Then reboot. P.S. just noticed thy I linked the same post twice above, if you need to suppress the error it's here.
  25. JorgeB
    Correct. I guess it can be done under either one, since this one is also detecting the problem, it's not detecting at mount like v6.11, likely due to some extra checks in the newer kernel.
×
×
  • Create New...