Niklas

Members
  • Posts

    237
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Niklas

  1. Something changed with permissions when Unraid got updated a while back.
  2. You could try setting both PUID and GUID to 0. Please note that this will give the container full access to the file system (everything).
  3. fstrim -av /mnt/cache: 111.9 GiB (120167636992 bytes) trimmed on /dev/mapper/sdb1 /var/lib/docker show same size as /mnt/cache/system/docker I use far from 78G. Before the change to directory my docker.img was 30G with about 50% used. I have just ignored this discrepancy. I have a lot less writes to my ssds now and with ssds rated at over 400TBW it feels ok. What worries me is that the different size reports could cause problems in the future, or not.
  4. No change here. Running trim every night. du for /mnt/cache say 89GB used but df say only 21GB used (df is probably correct)
  5. I still see problems with how much space the docker folder use as I noted in this thread before. The Unraid gui does not show the same space used as if you check the docker folder size in the terminal.
  6. Set both "Container Variable: PUID" and "Container Variable: PGID" to 0
  7. latest is v3 for me. I changed from preview to latest a couple of minutes after the docker build and page was updated. Sonarr was on version 3.0.5.1143 for preview and upgraded to 3.0.5.1144 when changed to latest. I did not remove the tag, I changed linuxserver/sonarr:preview to linuxserver/sonarr:latest and updated.
  8. Strange. I switched from preview to latest without any problems.
  9. When using directory I see this: "Compute..." from the GUI. Stats show 10% usage for my cache drive (not correct if the system share is 83,4GB) My dockerdata-dir (on cache) show 77G used. My cache drive show 20G used. What's wrong here? My docker.img was 30GB with about 50% used. Could the cache drive become full without Unraid noticing it?
  10. It's fixed now. Update the container.
  11. There must be some problem here. My /mnt/cache/system/docker/dockerdata (docker in folder) is about 72-79GB if I check with du. My old docker.img had a max size of 30GB and was near half full. If I check using the unraid gui and click calculate for the system share I get about 80GB used but when I use df -h i see that my cache drive only has 19GB used.
  12. My docker dir show 72-79GB (using du) but my cache drive only show 19GB (df -h) used. Edit: Using "Compute..." in the gui for the "system" share in unraid show 85,1 GB used. Cache only.
  13. I just changed to directory, added my docker containers back and deleted docker.img when all looked good.
  14. Not using MQTT (yet). I think it has something to do with networking. I don't know if this bug report could help
  15. Far easier, yes. I knew I had that information somewhere locked away in my brain. Thanks for pointing that out! I just moved from docker.img to directory and added my 20 containers back using the add container button. Wasted some time there.
  16. Also running home assistant. The most abuse I saw was writing to the home-assistant_v2.db (recorder/history). I moved home-assistant_v2.db from the btrfs cache to my unassigned hdd in 6.8.3. With the multiple cache pool support in 6.9, I removed unassigned devices and added the hdd as a second cache pool formatted as XFS. Just for use with stuff that writes lots of data to save some ssd life. No critical stuff.
  17. Same time-zone as me. Yes, that what I said. You can try the "add container" button now before upgrading and you will probably see what I mean. Your dockers with settings will be in the "Template:" dropdown list (under "User templates").
  18. 57 days uptime without any problems. I just moved from docker.img to directory like three hours ago, running fine. As i understand, that command is not needed anymore with the 6.9-rc2. It only mitigates some of the writing amplifications but it's a start.
  19. You don't need the solution mentioned there if running 6.9-rc2. In 6.9 you can select a dir to store your docker data instead of the docker.img (in the gui). You will lose all of your dockers but you can easily add them back with all your settings intact by using the "ADD CONTAINER" button. Select your docker from the "Template:" dropdown box and click apply.
  20. I have one ttyUSB0 also Edit And three ttyACMx
  21. Same here. Broke all connections to my USB devices. You could try doing chmod 777 /dev/ttyACM0 in the server terminal and restart Domoticz. If it works, add the command to your go file.
  22. Wondering the same thing, The version is getting quite old.
  23. Working fine here (marthoc/deconz). Recent update to the deconz software has changed how to talk to the device. Previliged mode need to be activated and check the path of the device.