Jump to content

trurl

Moderators
  • Posts

    44,362
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. Did you create a user account there? Your screenshots suggest that SpaceInvaderOne is logged in to the website, but you are not.
  2. This suggests a problem with your flash drive and the upgrade, which could be the cause of all other symptoms. Do you have a current backup of flash?
  3. Setup syslog server anyway. If it happens again start a new support thread in General Support.
  4. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Also, setup Syslog Server so you can save your syslog for retrieval after reboot: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
  5. You should still post diagnostics even if you have to do that after reboot. And setup syslog server so you can save syslog for later retrieval: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
  6. If that works then I would say that is optimal. Why not make that application use its own login?
  7. Also, your report doesn't exactly follow the guidelines here: https://forums.unraid.net/bug-reports/prereleases/how-to-install-prereleases-and-report-bugs-r8/ In particular: Some people have reported lockups when trying to get their BOINC docker tuned just right. Does it lockup if you don't run that docker?
  8. That sounds like you must be working from an old V5 wiki or something, since the Utils tab is called Tools on V6. That is still basically the idea, except it will now let you keep your assignments when doing New Config. So keep all your assignments, and then just unassign the single disk you want to remove before starting the array and rebuilding parity.
  9. Are you sure you are looking in the right place? This would be in your Download share in the pdf/output folder. Maybe that is where you looked, but since you are new I thought maybe you don't understand how to use dockers.
  10. Have you read the Docker FAQ? I suspect you must have read at least some of it since you posted your docker run command. People are often confused by "mappings". All it means is a correspondence. Just as a place on a road map corresponds to a place in the world, a docker volume mapping is simply a correspondence between a path inside the container, and a path on the host computer. Your Unassigned Device has a host path that begins with /mnt/disks/... When mapping an Unassigned Device, be sure to select slave mode.
  11. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.
  12. I think you left out a step between 4 and 5. Move data from one of those 14TB drives to those drives formatted in step 5, so you can use that 14TB drive as parity. Do you have another copy of anything important and irreplaceable?
  13. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.
  14. On mobile now so can't look at Diagnostics yet. Have you done memtest?
  15. Post your docker run command as explained in this very first link in the Docker FAQ:
  16. Unraid keeps track of disk assignments using the serial number of the disks, so it doesn't matter where they are plugged in. The only thing that sometimes gets people in trouble is if they use a controller that doesn't report the drive serial numbers correctly. As long as you don't use a RAID card you should be OK.
  17. The reason I said they weren't interchangeable, which you said you knew even though you thought they were the same, is because the parity on parity1 is not valid for the parity2 slot, and the parity on parity2 is not valid for the parity1 slot.
  18. Parity2 wouldn't really provide any extra redundancy if it were the same. If parity and parity2 were the same, then if one parity failed you would still have the other and could recover the data for a single data disk. But if 2 data disks failed at the same time, then you wouldn't have enough parity information to recover both data disks. If both parity were the same they wouldn't have any more information than a single parity disk and could only recover a single data disk.
  19. But are you writing to a cached user share?
  20. Post your docker run command for plex as explained here:
  21. Probably makes more sense to let docker handle it like @testdasi explained. Not sure BOINC will really know all it needs to know about the rest of the system when it is running in the virtual environment of a container. I have run BOINC for many years on many systems and my settings from my "project" account probably work best when running it on a PC.
  22. I can see now what you mean. Never noticed since it never caused any lag for me.
×
×
  • Create New...