Niklas
Members
-
Joined
Everything posted by Niklas
-
Do you mean you don't have the datasets created using SpaceInader1's script? Only that? I guess you'll have to destroy the datasets (using zfs destroy) from when docker created them. Deleting the folder/share won't do it. But I'm fairly new to zfs myself. You can use destroy to do it recursively but don't destroy the wrong one. 😅
-
Looks like when you have docker set to directory and the dir is on zfs formatted drive. Docker will use the built in zfs driver and create the layers as datasets. It will also create lots of snapshots. Just hide it. Edit You can hide them by entering the dir as exclusion in plugin settings, like this (i have it set to a share named docker on zfs cache only)
-
I removed that line and now I can open the log window without Chrome freezing the Unraid tab and showing blank log window. Logs show as they should so I would like to make this change more permanent. Related? Edit: Oops, talking about Chrome for Android. The tab with Unraid open freezed as soon as I tried to open the log. Log window opens but no text. This change fixes it.
-
Having two containers with network type set to "None" becase they route via another container. For both containers I have deleted all port mapprings and set network type to none. I have added --net=container:containername to extra config. When opening Docker tab and looking at my two specially routed countainers i expect the field for PORT MAPPINGS should be blank. They are not blank. Showing radom data that comes from my stopped mariadb-instance (for now, it can be something else tomorrow, ports and mappings from another container having nothing to do with it could just show as belonging to my routed containers. I expect the part below to just be empty. Just like other containers not using the network. :3306 = port for MariaDB (stopped) Port 3306 has never been used by the containers in question so I don't know why that info shows up for them
-
I find this almost unusable. The old system worked great. I just ignore the bell icon. If I have notifications of different types I have to click multiple times to open all of them just to see what they say and to ack them. Using the system from my mobile devices (Chrome) is very hard so it's easier to just ignore the icon and risk missing something. But there is more just not working using my phone like the log windows. It opens but just a black empty window. Unraid gui just freezes in the background so I have to close and reopen the tab.. but this is just another problem. 😊 This new notification system is not good UX.
-
Please read back just a couple of posts before yours in this thread. Like this one
-
Could be the plugin ZFS Master.
-
Normal here.
-
I just changed the numbers in the url https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.9.2-x86_64.zip
-
I used macvlan for years with Unraid. Now it just crashes and make my system unstable (tried it out for a couple of hours, bad mistake. CKSUM errors on cache while downloading and writing to cache, problems with docker disk img). What changed? Ipvlan works fine but I can't see the individual containers and usage in the router with that.
-
Check this out
-
Added 1TB drive June 24. Disk-clear in parity check log. All ok. Monthly parity check ran at midnight until early morning today. Everything ok but the notification in GUI and Join show the stats from the disk-clear. The check before this one. Wrong duration here too Shows up correct in log/history/gui I don't know if this has happened before because I haven't added any drive in years and all parity checks have been ok so I might not have noticed if the stats was from the check before the one just ran. parity-checks.log
-
Checking on windows took time and generated lots of chunks in FOUND.000 on the drive. I didn't do much more with it. Restored backup to old drive I had at home for like 10+ years so I have to replace it again soon. Only strange thing I see now is that the write/read led on the USB-stick is always on. It shouldn't be. The old one didn't have any leds so can't compare. Had trouble accessing the drive and had to reboot. I don't know if it's hardware or software..
-
I didn't notice any differences in memory usage.
-
So my flash drive apperently decided to die when upgrading. Oh well.. 🥲
-
Yes. It's very hard to see and handle notifications from mobile devices. Also, see
-
Sorry to ask again but can I do something myself to stop microsocks from filling the log and supervisord file with domains connected to using socks? I don't need it logged.
-
v1.4 of this script will not play nice with 6.12.0-rc6 (and later?). My docker share (on zfs pool) with docker-xfs.img would not allow it to unmount the docker mount (busy) when rebooting the server or stopping the docker service. Ends up with unclean shutdown when unraid forces the reboot (starts parity check when rebooted).
-
I have used your script for some time, thanks! It saves much but I still have several GBs written to cache pool every day (like 30+GB). Not counting any stuff affected by mover but I also have appdata on cache of course, but nothing that should write that amount every day.
-
Would it be complicated to copy/move the docker-xfs.img to pool or array at shutdown and back again to ram at power up? I have lots of unused ram so I have been thinking of this for a while. It will save lots on wear on the SSD pools.
-
Is it possible to turn this off from the logging? I have lots of rotated logfiles filled with just info like this (for everything using socks, no logging to terminal for privoxy). It's not really needed for me. 🙂 Also, not good for privacy with everything logged. 2023-03-26 20:23:28,168 DEBG 'watchdog-script' stderr output: client[5] 192.168.1.5: connected to dl2.cdn.filezilla-project.org:443
-
The warnings cleared after the new update.
-
Getting this: I don't understand. They are all set to "Only : Cache" so files/folders should exist there? I have two pools (named cache and temp_hdd), 3 devices in total.
-
Got the same warning. Invalid Certificate 1. Server.lan vs server.lan.
-
Something changed with permissions when Unraid got updated a while back.
