Jump to content

trurl

Moderators
  • Posts

    44,363
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. Have you done memtest?
  2. It doesn't want. Only moving is in accordance with the Use cache setting of each user share. Yes I always recommend only adding drives as needed for capacity. Each additional drive is an additional point of failure, requires more ports and power, and at some point, more license. Be sure to install cache before enabling dockers/VMs so those get created on cache where they belong. Let us know if you have any problems.
  3. Also, your appdata and system shares have files on the array instead of all on cache. This often happens when you enable dockers/VMs before installing cache. Parity updates will affect docker/VM performance, and dockers/VMs will keep array disk spunup since they will have open files in system and appdata. You can't move open files so you would have to disable docker and VM services in Settings before you could move those to cache, or get mover to move them since they are cache-prefer.
  4. That screenshot is what I was looking at in your diagnostics when I said If you open up that file that you have circled in red you will see it says it exists on no drives. Did you have any other problems before you posted that you tried to fix yourself, perhaps the wrong way?
  5. There is a checkbox to anonymize the diagnostics. You can examine the diagnostics yourself since they are just text files. In fact, I encourage everyone to take a look at their diagnostics.
  6. Change your cache Minimum Free in Global Share Settings. If you just give it a number without specifying MB or GB I think it uses KB which makes it larger than you expect.
  7. Looks like all your disks together have 960GB + 142G on Unassigned. Looks like disk2,3 has little if anything on them. Doesn't look like you had a share named media, but there was a share that might have been name Media and it doesn't exist anymore. Can you tell us anything more about what you might have done?
  8. I don't see disk4 in the SMART but it is emulated and mounted so rebuilding it should be fine. As for disk1, are those diagnostics you posted the most recent? As I said It is showing some connection problems in syslog though. You might be best to wait until you get the new SATA card to try to fix anything.
  9. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  10. Please post screenshots instead of photos when possible, and I see you did post a screenshot at first so I don't know why these others are photos. According to your diagnostics disk1 is mounted and has 9.6TB of files on it.
  11. I don't use this but I assume you would have to go to the command line inside the container. Click on the icon for the container and select Console
  12. I'm not entirely sure why cache is a disk share. I recommend not sharing any disks on the network. Stop the array then go to Global Share Settings and post a screenshot.
  13. Didn't notice that. Win-win with more capacity.
  14. I think the reason you didn't have any user shares at all is because your array disks couldn't be read due to encryption. If any array or cache disks are unreadable it will sometimes break user shares completely. If those folders exist at the top level of cache, they should show up in your user shares because cache is part of user shares. Post new diagnostics.
  15. Since you have a replacement disk, rebuild to the replacement and keep the original in case there is a problem rebuilding. You could try to rebuild to the original if you want instead if you would rather return the new disk, for example. In either case, you should rebuild the data and not parity.
  16. I apologize for not asking for diagnostics at the outset. It might have at least helped with communication.
  17. I don't see a missing disk in that screenshot, nor do I see a disabled disk. A missing or disabled disk would not be green, it would have a red X instead. So, parity is not emulating anything. You just have an unmountable disk, which usually means a corrupted filesystem.
  18. This is a bit confusing and makes me question your use of "emulated" again. Maybe a screenshot would clarify.
  19. Jul 31 00:41:04 Shark-Dive emhttpd: Opening encrypted volumes... Jul 31 00:41:04 Shark-Dive emhttpd: Missing encryption key You seem to indicate you can see files on cache. Can you actually access any of the array disks?
  20. According to your diagnostics you don't have any user shares. I don't use encryption so I don't know what is going wrong with your encryption that is preventing user shares from working. Have you actually unlocked your disks?
  21. No data disk can be larger than any parity disk. Since your parity disk is 8TB, you can only use data disks up to 8TB, unless you replace parity with a larger disk first.
  22. Possibly this was due to some problem other than an actual failed disk. Connection issues are far more common than bad disks. Perhaps it wasn't even necessary to buy another disk. Disk4 isn't showing up in SMART in those diagnostics. Often when mucking about inside the case, such as when replacing a disk, the connections of other disks will be disturbed. Possibly this is what has happened here. Shutdown, check all connections, all disks, SATA and power, both ends, including any splitters. Reboot and post new diagnostics.
×
×
  • Create New...