• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by trurl

  1. cache doesn't seem to have much data on it. You must have reformatted it.
  2. Disable Docker and VM Manager in Settings until all your files are back on the server.
  3. You shouldn't even attempt to run any computer unless memory is working perfectly. Everything goes through RAM, the OS and other executable code, your data, everything. The CPU can't do anything with anything until it is loaded into RAM. Go to, Test your memory before doing anything else with this computer.
  4. attach diagnostics to your NEXT post in this thread
  5. Linux is case sensitive, so these are different paths to different shares. Or, said another way, these are different shares specified by different paths. Check all your docker host paths to make sure you have consistently specified the share you want with the upper/lower case you want. If you have any other processes such as scripts that might specify user share paths, check those also.
  6. Well, the "answer" is to reboot. That will clear log. But why does it fill? Lots of possible explanations. Your diagnostics are after reboot, so your log is already cleared. Would need to see diagnostics when you have the problem.
  7. You seemed to be having connection problems on disks 2, 6. Check those and try again with another non-correcting parity check.
  8. The diagnostics show you have dockers now. How did you recreate them?
  9. This is just doing a normal New Config/Parity Rebuild. The only thing that matters is the disk to be removed is not assigned when you rebuild parity. A formatted disk is not a clear disk. A formatted disk contains an empty filesystem. Only a clear disk can be removed without invalidating parity. A clear disk is all zeros so has no effect on the parity results.
  10. Those are I/O errors, often a bad connection. Much more common than bad disks. Attach diagnostics to your NEXT post in this thread
  11. What path were you using as output? Any path that is not a disk, pool, or user share, is in RAM.
  12. Probably you renamed the share, but didn't fix all references to the old share name. In your dockers, for example. So those references recreated the share with the old name when files were written to that path.
  13. A small number of sync errors is typical from unclean shutdown. Post new diagnostics so we can see if there is something else to consider.
  14. Attach Diagnostics to your NEXT post in this thread
  15. Could still be corrupt even if it copies. Check each to see if it is at least valid XML
  16. Something wrong with its template on the flash drive? Docker templates are in config/plugins/dockerMan/templates-user
  17. Standard syslog (included in diagnostics) is in RAM, so doesn't survive reboot. Diagnostics can't tell us anything that happened before reboot. Do you have an UPS? Setup syslog server.
  18. You don't want automatic parity checks to change parity if there is some other problem that might be causing the sync errors. After you get sync errors from a non-correcting check, you can try to determine the cause and then decide on the correct course of action for the sync errors.
  19. Doesn't seem to be a problem with FCP plugin
  20. Typically, you would let parity check run during idle hours, such as at night. Parity check will affect performance of any other access, and any other access will affect performance of parity check. My 8TB parity check is scheduled monthly, runs from midnight to 6am, and finishes on the third night. Scheduled parity checks should be non-correcting. Noticed early in the thread you mentioned hot swap. Hot swap with Unraid is not useful except perhaps for unassigned devices. You can't replace a drive with hot swap, because Unraid won't do anything with the new drive until you assign it, and you can't assign a drive with the array started. So best to power down to replace drives.
  21. This seems to be about the Unassigned Devices plugin. Plugin issues do not belong in bug reports. You can go directly to the correct support thread for any of your plugins by clicking its Support link on the Plugins page of your Unraid webUI. Go to the Unassigned Devices plugin thread, explain your problem, and include your diagnostics in your post there.