Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,582

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's logged as a disk problem, though these can sometimes be intermittent, run an extended test on disk4 and if it passes keep an eye on this attribute: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1 It it continues to increase there will likely be more errors.
  2. JorgeB
    Several places already exist with info, easily found with google, e.g.: https://ma.juii.net/blog/interpret-smart-attributes
  3. JorgeB
    Run a filesystem check (without -n) on those drives, if the emulated disk5 is not fixable or is severely corrupt it could be better to re-sync parity with the old disk then upgrade again.
  4. JorgeB
    Please use the exiting plugin support thread:
  5. JorgeB
    Do you mean it's working now or not? If not please post new diags.
  6. JorgeB
    That looks like a very corrupt filesystem, but basically you can only attempt to repair it without -n, is that an emulated disk or actual disk?
  7. JorgeB
    No problem, I would recommend getting rid of those controllers though, or you'll likely run into trouble again, see here for as list of recommended ones:
  8. JorgeB
    There's no such button, you just do a new config, keep all assignments, changes the ones you want and start the array to begin the parity sync.
  9. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  10. JorgeB
    It is, you might not need a new cooler, just to clean, re-apply thermal paste and make sure the current one is correctly installed.
  11. JorgeB
    Errors are logged as an actual disk problem, you should run an extended SMART test.
  12. JorgeB
    It started rebuilding disk2, but then there were errors on disk1 and then disk2, disks look fine, and multiple disk errors suggest a power, controller or connection problem.
  13. JorgeB
    The other way is also not risky if the array is set to not autostart and you unassign that device before array start.
  14. JorgeB
    Yes, if you stop the array and refresh main that device will likely be unassigned, if yes you just need to start the array again, or stop and power down and physically remove the device, then just start the array.
  15. JorgeB
    Cache device dropped offline, this is usually a power/connection problem, but yes that link is correct to remove a device (after it comes back online).
  16. JorgeB
    And if you now start the array that disk is still unmountable?
  17. JorgeB
    Reboot or re-start the array.
  18. JorgeB
    Yes, normal with xfs.
  19. JorgeB
    Cache errors don't appear on the GUI: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
  20. JorgeB
    No, unrelated.
  21. JorgeB
    Recent xfs filesystem use always a few GB for metadata, etc, the larger the disk the larger the usage, you can see the same in disk4.
  22. JorgeB
    It's an elusive issue, and not easy to reproduce, but those kind of dockers that directly manipulate files seem to be the ones that are more likely to cause this problem, but unless you can use disk shares for that (that would limit it to one disk or pool) don't known much else you can do.
  23. JorgeB
    Run a filesystem check on disk1, but before that replace its cables, there are several ATA errors.
  24. JorgeB
    Do you know why you have this in the go file? ### Fix plugins cp -r /usr/local/emhttp/plugins/webGui/phaze.page /usr/local/emhttp/plugins/dynamix If unrelated try redoing your flash drive, backup current one, redo it, restore only super.dat (disk assignments) and the key, if it works reconfigure the server or restore older config part by part until you find the problem.
  25. JorgeB
    Cache device is full.
×
×
  • Create New...