Jump to content

trurl

Moderators
 View Profile  See their activity

  • Posts

    44,353

  • Joined

  • Last visited

  • Days Won

    137

 Content Type 

Everything posted by trurl

  1. trurl
    yes To get an idea of how Unraid parity is different than RAID, look in the bottom right corner of the webUI, there is a link to the manual.
  2. trurl
    That should be good for formatting. Just wanted to make sure it wasn't a very old version. Post new diagnostics.
  3. trurl
    Post new diagnostics
  4. trurl
    Were you using the current version of Unassigned Devices when you formatted the drive?
  5. trurl
    Newbie, Not likely the cause of your problem, but I see you are mapping an Unassigned Device in that docker run. You should use slave access mode when mapping Unassigned Devices. Click on the plex icon, select Edit to get to the Edit Container page, click on the Edit button for any path that specifies the Unassigned Device, and change access mode to slave.
  6. trurl
    Go to Tools - New Config and reassign your disks as parity and disk1. When you start the array it will build parity. When you only have one data disk then parity is a mirror of that disk, just because of how parity is calculated.
  7. trurl
    If you can't (or won't) get Syslog Server setup you could just tail syslog:
  8. trurl
    Nothing obvious. The only thing I see in syslog is a possible connection problem with an Unassigned Device that looks like isn't connected anymore. That shouldn't have any effect on parity check speed. Is anything reading or writing the server while it is checking parity?
  9. trurl
    You did New Config with the original disk3, correct? If so it was rebuilding parity, and it would not have changed anything on that original disk3. So you must have formatted the original disk3 at some point. But, there was some confusion earlier about which disk was the original disk3. At first you said you had formatted it, but then you said you found the disk and it had the files on it. Is the disk with serial ending 1pry the disk you assigned as disk3 when you did New Config? I will save further comment and wait for answers.
  10. trurl
    Let me start by bring some relevant quotes from the previous page I will comment further on my next post.
  11. trurl
    Do you think you have a good understanding of container volume mapping? Since you are mapping things at such a low level with all user shares as data and also as media, you may be experiencing scenario #2 as explained here: In other words, files get "repathed" to the same disk instead of getting moved.
  12. trurl
    Did you try to get diagnostics before rebooting?
  13. trurl
    Post new diagnostics
  14. trurl
    For future reference, you can go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support. However, since you are new, maybe you have some other problem and this is just a symptom. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. Also, post your docker run for plex as explained at this very first link in the Docker FAQ:
  15. trurl
    Do you already have any data on the array?
  16. trurl
    Unraid IS NOT RAID. However, if you only have a single parity drive and a single data drive, it is effectively a mirror. Just reassign that disk in slot2 to the parity slot instead.
  17. trurl
    There is already multiple pools for SSD storage in latest beta
  18. trurl
    You have to replace parity first since it can't be smaller than any data disk. To replace a disk, whether parity or data Stop array Shutdown Replace disk Reboot Assign new disk Start array to begin rebuild
  19. trurl
    Post a screenshot of Settings - SMB - SMB Extras
  20. trurl
    Don't know anything about that. Is that still installed on your Mac?
  21. trurl
    We could try fixing those permissions, but I don't understand how they are getting that way to begin with. None of those folders even exist when the array isn't started, and they get automatically created when you start the array. That is all as it should be, except yours have the wrong permissions. Was any of this working before? Can you tell us what you have done since it was working?
  22. trurl
    Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  23. trurl
    Start the array and post the results of the command again.
  24. trurl
    Stop the array then post the output of ls -lah /mnt
  25. trurl
    Disable docker service (Settings - Docker) and reboot.
×
×
  • Create New...