trurl

Moderators
  • Posts

    31334
  • Joined

  • Last visited

  • Days Won

    103

Everything posted by trurl

  1. USB not recommended for array or pool disks for several reasons. Port multipliers will impact performance on multidisk operations such as parity check and rebuilds.
  2. Mover won't move duplicates (file already exists at destination), and nothing can move open files.
  3. Have you tried booting in SAFE mode?
  4. The page you linked says: which is not what you did. You set them to cache=yes
  5. Also noticed in syslog that you have CA Backup configured to backup /mnt/cache/appdata. But your appdata setting has moved some of appdata to the array so those won't be included in the backup.
  6. Why do you have appdata, domains, system shares set to be moved to the array? If these are on the array, dockers/VMs won't perform as well due to slower parity array, and they will keep array disks spunup since they always have open files.
  7. I seem to recall there might be a bug if you have an empty pool, such as cache, and then another pool after that.
  8. The most common way to lose data is probably user error. And, of course, parity won't help with that either.
  9. Haven't looked at diagnostics yet. My guess is there was never anything wrong with the original disk or this one. Bad connections or controller issues are much more common than bad disks.
  10. Why did you remove cache? I thought the idea was to add another pool for docker/VM. If you only want one pool it might as well be "cache".
  11. It's difficult to make much sense of the shares folder in your diagnostics, because you have a lot of .cfg files that probably don't correspond to any user share. Perhaps you accidentally created some of those shares at some time. Plus, since it appears that user shares are broken, many if not all of them say they don't exist. I haven't checked them all since there are 149 of them. Take a look at the config/shares folder on your flash drive and you will see what I mean. Another thing I noticed is that you seem to be sharing disks on the network. I don't recommend that and it is usually not necessary, though it might be useful for some things if you don't know how to work with files directly on the server instead of over the network. Just be sure you know not to work with disk and user shares at the same time.
  12. https://wiki.unraid.net/Manual/Storage_Management#Parity_Swap
  13. I wouldn't have chosen that name since the word already has a meaning in Unraid, but maybe it will be OK. Your user shares seem broken, no /mnt/user0. Post a screenshot of the User Shares page.
  14. Parity swap copies parity to the new larger disk, then rebuilds the disabled data disk to the old parity disk. After that rebuild completes it won't be disabled anymore, but you could replace it and rebuild to that other new disk if you want.
  15. Syslog is in RAM just like the rest of the OS. You can setup syslog server to get those stored somewhere. Those do look like disk problems though maybe not critical. Since the disk is so old I would consider replacing it.
  16. That seems right but I have never done it. @JorgeB may not be available for several hours if you want to wait.
  17. Actually I do have parity and cache in my backup server. But they are not required by Unraid so nothing preventing you from not having them.
  18. assuming the controller is giving that information correctly. That is one of the reasons RAID controllers and USB connections aren't recommended. Looks like your hardware is good for that.
  19. You can't upgrade disk3 to 4TB until you have a parity disk at least that large. You can't upgrade parity when you already have a disabled data disk. This is exactly the situation the parity swap procedure was designed for.