Jump to content

trurl

Moderators
  • Content Count

    25653
  • Joined

  • Last visited

  • Days Won

    82

Everything posted by trurl

  1. It is very easy to reinstall your dockers as explained in the Docker FAQ linked several posts above.
  2. Looks OK. Disk3 rebuilding.
  3. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  4. No, your cache drive is unmountable. Totally different thing than an empty drive. And since cache is corrupt and unmountable, all the things associated with dockers and VMs were recreated from scratch on disk10. You will want to get rid of all that and see if you can get cache going again. Go to Settings - Docker and disable then delete docker.img. Do the same for Settings - VM Manager. Leave them disabled until we see if cache can be recovered. Go to Unraid command line and post output of this lsblk
  5. Why do you have SSDs in the parity array? Do you know they can't be written any faster than HDD parity, and they cannot be trimmed?
  6. You only need one or more data drive to start the array, parity is not required. All other features you want are still available with that configuration
  7. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread
  8. If you only have parity and one data disk then it is RAID1. One advantage of Unraid is when you add more data disks they don't have to be all the same size.
  9. On the other hand, if you don't format them, then you have an extra copy. Keep things straight by the disk serial number, that is how Unraid does it. However you might reuse an old disk, it isn't necessary to format it before using it in Unraid. If you use a disk, whether old or new, to rebuild another disk, the rebuild will completely overwrite every bit of the disk, so it doesn't matter what was already on the disk. If you add a disk, whether old or new, to a new slot in an array that already has valid parity, then Unraid will clear that disk so parity remains valid. A clear disk (different than an empty disk) is all zeros and so has no effect on existing parity. After clearing, then Unraid will make you format the disk (at which point it becomes an empty disk) so it can be used. And finally, if you do format a disk (thus making it an empty disk) before adding it to a new slot in an array that already has valid parity, Unraid will clear that disk so parity remains valid, then make you format it so it can be used.
  10. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  11. And I just noticed your latest diagnostics is showing corruption on disk4 and disk7, though they do seem to be mounted. I think you must have some hardware problem that still hasn't been fixed. Bad cables, bad power, bad controller, something. Have you done memtest?
  12. As mentioned, it was a parity rebuild, not a parity check. Not sure what you mean about the New Config not taking very long. It doesn't take any time at all except what time you take in assigning disks. Starting the array is where the New Config takes effect, and at that point it has already begun rebuilding parity. If there was some additional time then that makes me suspect you formatted disk3 again. Format does take a few minutes. Upgrading might help at least get things off to a better new start. Just thought I would comment on something you said earlier. There is no need to format anything when you start over. Parity doesn't even have a format since it has no filesystem. When you setup your disks again, parity will rebuild, completely overwriting anything that is already on parity. Doesn't matter if the disk has old parity information, doesn't matter if you have formatted it to some filesystem, doesn't matter if it is full of files. If a disk is assigned as parity it is completely overwritten with parity. And empty disk 3 is already formatted. You don't want to format anything else or you will lose that data too. You seem to still have some incorrect idea of what "format" does.
  13. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  14. Disk3 disabled, emulated drive is mounted so your data should be OK. Can't see SMART for the disk since it is disconnected. Shut down, check all connections, all disks, both ends, power and SATA, including splitters. Then reboot and post new diagnostics.
  15. Do you mean you did New Config and didn't check the box saying parity was already valid? As I mentioned, your appdata is all on cache. I was just concerned that cache didn't seem to have much data on it. But it looks like appdata is the only thing on cache, so if it is all there then good. Normally you also want system share on cache instead of on disk2 as you have it. Since docker and VM services will always have those files open they will always keep array disks spinning and dockers won't perform as well due to slower array.
  16. Like all linux, Unraid uses RAM for I/O buffer.
  17. Looks like you are rebuilding parity, which you didn't mention. Not related to your problems though. Your system share (docker.img and libvirt.img) is on disk2. Perhaps you moved it there because of cache problem. But it looks like docker.img is corrupt. Not really a problem since it is easily recreated and your containers can be reinstalled just as they were with Previous Apps on the Apps page. More concerning is your appdata is all on cache, which is mostly empty, so I guess you lost that, unless you copied it to into another share or somewhere. You don't have CA Backup plugin installed so I assume you don't have backups of appdata, libvirt, or flash. Or perhaps you were not following conventions and didn't really use appdata user share for your dockers. Anything else you can tell us that might clarify some of this?
  18. Don't know if this is something that might help or not