Jump to content

trurl

Moderators
 View Profile  See their activity

  • Posts

    44,363

  • Joined

  • Last visited

  • Days Won

    137

 Content Type 

Everything posted by trurl

  1. trurl
    Remove it, reboot, and see if the problem improves.
  2. trurl
    Mover can't move open files. Disable docker and VM services in Settings, run mover, when it completes post new diagnostics.
  3. trurl
    Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.
  4. trurl
  5. trurl
    Do you have Notifications setup so Unraid can notify you immediately by email or other agent if a problem is detected?
  6. trurl
    That's OK, but there really wasn't anything there. The Diagnostics are still anonymized, but the mover logging part of the syslog isn't. That part only had a few lines in it that didn't seem very important for privacy in this case.
  7. trurl
    Split Level is the likely cause. Did you leave that at default also?
  8. trurl
    Logs indicate it moved and appdata is all on cache now. Not sure why it didn't finish before. You should turn off mover logging now since those aren't anonymized.
  9. trurl
    appdata still has some files on the array. Go to Settings - Scheduler - Mover Settings and enable Mover Logging, then run mover again and post new diagnostics so we can see why those aren't getting moved.
  10. trurl
    And why are your docker icons missing?
  11. trurl
    Be sure to get diagnostics in case the non-correcting check still has errors. By comparing the logs of the parity checks sometimes it can help troubleshoot the problem.
  12. trurl
    Your system share still has files on disk1. Did you actually disable the docker and VM services in Settings?
  13. trurl
    Your appdata, domains, and system shares are all on the array. Did you restore appdata? Not sure how that works since I have never needed to do it. I would have thought it would restore it to cache since appdata is cache-only. Ideally you want those shares all on cache and staying on cache so docker/VM performance will not be affected by the slower array, and so docker/VMs won't keep array disks spinning. Set those shares to cache-prefer, run mover, when it completes post new diagnostics.
  14. trurl
    Make sure you make a backup plan. You don't have to backup everything, but
  15. trurl
    How much RAM do you have?
  16. trurl
    That would be simplest. Disable dockers and VMs for now since there may be some additional cleanup needed. Just get appdata restored to cache and post new diagnostics. ***EDIT*** If you had anything else besides appdata backed up from cache, then go ahead and restore it too. But leave dockers,VMs disabled.
  17. trurl
    Shut down, fix your cooling problems, check all connections, power and SATA, both ends, including any power splitters. I see you have Marvell controller, possibly on the motherboard, and Intel SATA controller as well. You might try not using the Marvell ports, or disabling IOMMU (vt-d in Intel) in the BIOS, I know some have had better success with Marvell if they don't have IOMMU enabled. After exploring all that, boot up again and post new diagnostics.
  18. trurl
    You must always have another copy of anything important and irreplaceable. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.
  19. trurl
    Nothing obvious. Many of your disks are very full, more importantly your cache is very full. You typically want to avoid filling cache especially. Also your docker and VM related shares (appdata,domains,system) aren't configured ideally (should all be on cache). We can deal with all that later. Since Diagnostics (as well as current syslog) don't contain anything from before reboot, you might setup Syslog Server to store syslog somewhere you can retrieve it after you are forced to reboot again.
  20. trurl
    Do you have a backup of cache? These may be newly created on the array since cache isn't mounting. Or they will be only partial contents missing anything that was on cache. Do you have a backup of appdata from the CA Backup plugin?
  21. trurl
    Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.
  22. trurl
    He means you have VMs disabled in Settings - VM Manager.
  23. trurl
    Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. Diagnostics includes syslog and a lot of other things that give a more complete understanding of your configuration and situation.
  24. trurl
    Your cache is corrupt and you should forget about getting dockers going again until you fix that. Post a screenshot of Main - Cache Devices
  25. trurl
    If the correcting check doesn't fix all parity errors there is no point in another correcting check since you have some other problem to diagnose. So you follow a correcting check with a non-correcting check to verify the correcting check fixed all parity errors.
×
×
  • Create New...