sasbro97

@trurl Filesystem Size Used Avail Use% Mounted on rootfs 32G 532M 31G 2% / tmpfs 32M 5.9M 27M 19% /run /dev/sda 7.5G 1.1G 6.5G 14% /boot overlay 32G 532M 31G 2% /lib overlay 32G 532M 31G 2% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 32G 0 32G 0% /dev/shm tmpfs 4.0G 856K 4.0G 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1p1 17T 14T 2.6T 85% /mnt/disk1 /dev/md2p1 5.5T 2.9T 2.6T 53% /mnt/disk2 cache 710G 384K 710G 1% /mnt/cache safety 2.5T 31G 2.4T 2% /mnt/safety cache/domains 720G 11G 710G 2% /mnt/cache/domains cache/domains/Ubuntu-File-Transfer 710G 128K 710G 1% /mnt/cache/domains/Ubuntu-File-Transfer cache/appdata 711G 1.6G 710G 1% /mnt/cache/appdata cache/system 710G 319M 710G 1% /mnt/cache/system cache/development 710G 7.3M 710G 1% /mnt/cache/development cache/appdata/sablier 710G 128K 710G 1% /mnt/cache/appdata/sablier cache/appdata/remotely 710G 512K 710G 1% /mnt/cache/appdata/remotely cache/appdata/redis 710G 3.0M 710G 1% /mnt/cache/appdata/redis cache/appdata/nginx-proxy-manager 710G 16M 710G 1% /mnt/cache/appdata/nginx-proxy-manager cache/appdata/adguardhome 711G 753M 710G 1% /mnt/cache/appdata/adguardhome cache/appdata/semaphore 710G 256K 710G 1% /mnt/cache/appdata/semaphore cache/appdata/duplicati 710G 86M 710G 1% /mnt/cache/appdata/duplicati cache/appdata/homepage 710G 1.4M 710G 1% /mnt/cache/appdata/homepage cache/appdata/changedetection.io 710G 1.5M 710G 1% /mnt/cache/appdata/changedetection.io cache/appdata/onedev 710G 375M 710G 1% /mnt/cache/appdata/onedev cache/appdata/smart-home 714G 4.2G 710G 1% /mnt/cache/appdata/smart-home cache/appdata/n8n 710G 68M 710G 1% /mnt/cache/appdata/n8n cache/appdata/portainer 710G 18M 710G 1% /mnt/cache/appdata/portainer cache/appdata/ldap 710G 50M 710G 1% /mnt/cache/appdata/ldap cache/appdata/unmanic 710G 128K 710G 1% /mnt/cache/appdata/unmanic cache/appdata/hrconvert2 710G 128K 710G 1% /mnt/cache/appdata/hrconvert2 cache/appdata/mediaserver 766G 57G 710G 8% /mnt/cache/appdata/mediaserver cache/appdata/monitoring 716G 6.0G 710G 1% /mnt/cache/appdata/monitoring cache/appdata/website 711G 962M 710G 1% /mnt/cache/appdata/website cache/appdata/wiki 710G 258M 710G 1% /mnt/cache/appdata/wiki cache/appdata/endlessh 710G 128K 710G 1% /mnt/cache/appdata/endlessh cache/appdata/finance 710G 27M 710G 1% /mnt/cache/appdata/finance cache/appdata/snippet-box 710G 128K 710G 1% /mnt/cache/appdata/snippet-box cache/appdata/code-server 710G 6.3M 710G 1% /mnt/cache/appdata/code-server cache/appdata/ddclient 710G 128K 710G 1% /mnt/cache/appdata/ddclient cache/appdata/authelia 710G 6.0M 710G 1% /mnt/cache/appdata/authelia cache/appdata/downloader 710G 308M 710G 1% /mnt/cache/appdata/downloader cache/appdata/speedtest-tracker-db 710G 46M 710G 1% /mnt/cache/appdata/speedtest-tracker-db cache/appdata/cloud 712G 2.4G 710G 1% /mnt/cache/appdata/cloud cache/appdata/deprecated 710G 238M 710G 1% /mnt/cache/appdata/deprecated cache/appdata/speedtest-tracker 710G 128K 710G 1% /mnt/cache/appdata/speedtest-tracker cache/appdata/healthchecks 710G 896K 710G 1% /mnt/cache/appdata/healthchecks cache/appdata/dms 710G 152M 710G 1% /mnt/cache/appdata/dms cache/appdata/urbackup 710G 212M 710G 1% /mnt/cache/appdata/urbackup cache/appdata/traggo 710G 128K 710G 1% /mnt/cache/appdata/traggo cache/appdata/deprecated/bookstack 710G 128K 710G 1% /mnt/cache/appdata/deprecated/bookstack cache/appdata/deprecated/bookstack-db 710G 128K 710G 1% /mnt/cache/appdata/deprecated/bookstack-db safety/cloud 2.5T 125G 2.4T 5% /mnt/safety/cloud safety/Sascha 3.2T 768G 2.4T 25% /mnt/safety/Sascha safety/backup 2.4T 2.3G 2.4T 1% /mnt/safety/backup safety/Musik 2.5T 60G 2.4T 3% /mnt/safety/Musik shfs 22T 17T 5.2T 77% /mnt/user0 shfs 22T 17T 5.2T 77% /mnt/user /dev/loop2 1.0G 4.6M 904M 1% /etc/libvirt cache/system/e8a1eefe454230f065bf35c4359f9eff44a4ebe8325e75a4db9a50d813468cf6 712G 2.1G 710G 1% /var/lib/docker/zfs/graph/e8a1eefe454230f065bf35c4359f9eff44a4ebe8325e75a4db9a50d813468cf6 cache/system/1be623491e2f0e171707e79c7d26a89e094ddcb27a6d669ac02d0f6446f2ff3d 711G 1.1G 710G 1% /var/lib/docker/zfs/graph/1be623491e2f0e171707e79c7d26a89e094ddcb27a6d669ac02d0f6446f2ff3d cache/system/a4d7cfe504453602e7264c76c2c83227e137c005df472e4404d57089d3cc3278 712G 1.8G 710G 1% /var/lib/docker/zfs/graph/a4d7cfe504453602e7264c76c2c83227e137c005df472e4404d57089d3cc3278 cache/system/59fbd4fdc2fce9311d3020c592abe3d97139ab4415ec28a586e6b885f98c0671 710G 498M 710G 1% /var/lib/docker/zfs/graph/59fbd4fdc2fce9311d3020c592abe3d97139ab4415ec28a586e6b885f98c0671 cache/system/92a90aeec7a97f4640229eea72a376db732b9678879e83ac1441fbd535f76bd1 710G 16M 710G 1% /var/lib/docker/zfs/graph/92a90aeec7a97f4640229eea72a376db732b9678879e83ac1441fbd535f76bd1 cache/system/5769a7086692bed5aa2248a9eedafab558d8f0bcc175ee8fbaff8ac66938b8b8 710G 239M 710G 1% /var/lib/docker/zfs/graph/5769a7086692bed5aa2248a9eedafab558d8f0bcc175ee8fbaff8ac66938b8b8 cache/system/e5dbccff166d24bff3024b4385317c8da5d3e38788625c3bbf704765483f073e 710G 112M 710G 1% /var/lib/docker/zfs/graph/e5dbccff166d24bff3024b4385317c8da5d3e38788625c3bbf704765483f073e cache/system/9e33d8b61635798d0856e0686ff349d86102c9366991a65e1460cc65b3d7afc7 710G 41M 710G 1% /var/lib/docker/zfs/graph/9e33d8b61635798d0856e0686ff349d86102c9366991a65e1460cc65b3d7afc7 cache/system/d50c80bd567b183b5024742c02388e9110e3841e9782600b94e2f360563b4e4c 711G 979M 710G 1% /var/lib/docker/zfs/graph/d50c80bd567b183b5024742c02388e9110e3841e9782600b94e2f360563b4e4c cache/system/ae6820b44cab95f60829264253b76f7832faea57780022b7595bd95a0b73acb7 710G 427M 710G 1% /var/lib/docker/zfs/graph/ae6820b44cab95f60829264253b76f7832faea57780022b7595bd95a0b73acb7 cache/system/e3834f9dbeb365ee65c1c71111dd0b4920400896c9b8ef145460c04dc9a36d39 710G 242M 710G 1% /var/lib/docker/zfs/graph/e3834f9dbeb365ee65c1c71111dd0b4920400896c9b8ef145460c04dc9a36d39 cache/system/ab373807429b49d2e9e6f17b493b2066f59acb5eae42874aa8a1c403bee7e4ca 710G 427M 710G 1% /var/lib/docker/zfs/graph/ab373807429b49d2e9e6f17b493b2066f59acb5eae42874aa8a1c403bee7e4ca cache/system/2b2f711c33bb7e97a3895c8bd1474c54d1a7c0e007e7d532f34f9258548a90a9 710G 156M 710G 1% /var/lib/docker/zfs/graph/2b2f711c33bb7e97a3895c8bd1474c54d1a7c0e007e7d532f34f9258548a90a9 cache/system/88373cdbfa1707d0e58e99b0325c4aedff3e1145092cb4f03779f8bbf137fa32 710G 12M 710G 1% /var/lib/docker/zfs/graph/88373cdbfa1707d0e58e99b0325c4aedff3e1145092cb4f03779f8bbf137fa32 cache/system/bf07c2720311d0ab417da4852319fd034d382d1630344ab049ab5ce454c061f7 710G 620M 710G 1% /var/lib/docker/zfs/graph/bf07c2720311d0ab417da4852319fd034d382d1630344ab049ab5ce454c061f7 cache/system/ee9365e2e6e922e3c41b5bd7218df5dc931c3153bf5ae2809567a6c9d44616c5 710G 192M 710G 1% /var/lib/docker/zfs/graph/ee9365e2e6e922e3c41b5bd7218df5dc931c3153bf5ae2809567a6c9d44616c5 cache/system/d58c024bc4048c6119c96bbd5baf5abf7a153fba84101db95e0f1647d0f2ed91 710G 198M 710G 1% /var/lib/docker/zfs/graph/d58c024bc4048c6119c96bbd5baf5abf7a153fba84101db95e0f1647d0f2ed91 cache/system/ca1d75b92dee570be7443918c3236847fdaf09979989734dc2dffe143d15451f 710G 118M 710G 1% /var/lib/docker/zfs/graph/ca1d75b92dee570be7443918c3236847fdaf09979989734dc2dffe143d15451f cache/system/76699a3fd3defb8c93f22c6cb740450c6f7759c98f12605cc64edb05a67db706 710G 262M 710G 1% /var/lib/docker/zfs/graph/76699a3fd3defb8c93f22c6cb740450c6f7759c98f12605cc64edb05a67db706 cache/system/a0c5888e582921b424027faed60a900ff60c4d1a4769925ef1b7a68e28328a85 710G 236M 710G 1% /var/lib/docker/zfs/graph/a0c5888e582921b424027faed60a900ff60c4d1a4769925ef1b7a68e28328a85 cache/system/68d1a52cde55b6e15e13cb06b146273b0b2c52376bbcd800d59066cb72577ab6 711G 843M 710G 1% /var/lib/docker/zfs/graph/68d1a52cde55b6e15e13cb06b146273b0b2c52376bbcd800d59066cb72577ab6 cache/system/0d5b366eba8642ecb836cd33ba3aa01b2e87ebc324f74cd3523336239a93df0d 710G 117M 710G 1% /var/lib/docker/zfs/graph/0d5b366eba8642ecb836cd33ba3aa01b2e87ebc324f74cd3523336239a93df0d cache/system/2fe6ae13c96d20a6a9de6c8a492eecd9b7fa733d19e6fb56a4203709e2d00918 710G 49M 710G 1% /var/lib/docker/zfs/graph/2fe6ae13c96d20a6a9de6c8a492eecd9b7fa733d19e6fb56a4203709e2d00918 cache/system/0cc2d7dbd265cfaf78628bf7c02c58355949db483e6e06a49902110e8cc443ce 710G 515M 710G 1% /var/lib/docker/zfs/graph/0cc2d7dbd265cfaf78628bf7c02c58355949db483e6e06a49902110e8cc443ce cache/system/0f150e957c5055f35e48c6daa388a950902a1345ca775908625e8f550c73472d 710G 25M 710G 1% /var/lib/docker/zfs/graph/0f150e957c5055f35e48c6daa388a950902a1345ca775908625e8f550c73472d cache/system/cb9e020fc90aabc8649d72645709b7aa5685d648465f5bfd0d3d65aeee54715d 710G 409M 710G 1% /var/lib/docker/zfs/graph/cb9e020fc90aabc8649d72645709b7aa5685d648465f5bfd0d3d65aeee54715d cache/system/f5437360d7b9733f18f7ee64b6ce70f7b31de389d0cd898a287a010274dc354f 710G 89M 710G 1% /var/lib/docker/zfs/graph/f5437360d7b9733f18f7ee64b6ce70f7b31de389d0cd898a287a010274dc354f cache/system/426900ef5cf827ad2f3a3324a57dc3383cf61df78d73d91a08f3035c924daccf 710G 22M 710G 1% /var/lib/docker/zfs/graph/426900ef5cf827ad2f3a3324a57dc3383cf61df78d73d91a08f3035c924daccf cache/system/1232c42eb15a2edec0f1c755688ce944be61df5729a29b86a4eb426c078356d4 710G 138M 710G 1% /var/lib/docker/zfs/graph/1232c42eb15a2edec0f1c755688ce944be61df5729a29b86a4eb426c078356d4 cache/system/f2a3fc6e18dd2b1c92e9b541dee8acf044128d244bb1ef7cde789808a9982760 710G 206M 710G 1% /var/lib/docker/zfs/graph/f2a3fc6e18dd2b1c92e9b541dee8acf044128d244bb1ef7cde789808a9982760 cache/system/318aafd0d654fe8aeac089c8a8b48ada56cb228508dbb0d673faecbef4d283d9 710G 147M 710G 1% /var/lib/docker/zfs/graph/318aafd0d654fe8aeac089c8a8b48ada56cb228508dbb0d673faecbef4d283d9 cache/system/31e24ae7cc7fbeb4d2e155ef053ff39826763ee73dc485a988af1eca2a9a4f9c 710G 113M 710G 1% /var/lib/docker/zfs/graph/31e24ae7cc7fbeb4d2e155ef053ff39826763ee73dc485a988af1eca2a9a4f9c cache/system/cc8d88bfcf31ede6da1daa58ce57cc38d8033ddbc42cc7a881c864130ab24ddf 710G 84M 710G 1% /var/lib/docker/zfs/graph/cc8d88bfcf31ede6da1daa58ce57cc38d8033ddbc42cc7a881c864130ab24ddf cache/system/5f23404bdb8171b1bac01ba0251561c819cdbdc1cc6e1c157a8e0d813ae8ee54 710G 293M 710G 1% /var/lib/docker/zfs/graph/5f23404bdb8171b1bac01ba0251561c819cdbdc1cc6e1c157a8e0d813ae8ee54 cache/system/f644c904d6ffb22b799256109b17d38f6d8956bf2a4dba45c649a8b4e816cd10 710G 75M 710G 1% /var/lib/docker/zfs/graph/f644c904d6ffb22b799256109b17d38f6d8956bf2a4dba45c649a8b4e816cd10 cache/system/ab509feb7fdc8db986f4fc77503854a2a193ba076332f34fab699423185efc99 710G 32M 710G 1% /var/lib/docker/zfs/graph/ab509feb7fdc8db986f4fc77503854a2a193ba076332f34fab699423185efc99 cache/system/1f32e5abee5938a1ca836f933322f63093d15dfc431ba9650b92bb987f607243 710G 179M 710G 1% /var/lib/docker/zfs/graph/1f32e5abee5938a1ca836f933322f63093d15dfc431ba9650b92bb987f607243 cache/system/b1c5c1461a5c836b3bd1ff239957c573a110639b12aa177b0b147e4e7b60ee3d 711G 1013M 710G 1% /var/lib/docker/zfs/graph/b1c5c1461a5c836b3bd1ff239957c573a110639b12aa177b0b147e4e7b60ee3d cache/system/0b16d0d52de3f72e3123ff5b82b5f64993956985a5d021b6e248b85abc6f90eb 711G 971M 710G 1% /var/lib/docker/zfs/graph/0b16d0d52de3f72e3123ff5b82b5f64993956985a5d021b6e248b85abc6f90eb cache/system/c7289e222a0b9b990b35ee9744a03a6b1af16daf160ef19592eee874bd75d99f 710G 9.8M 710G 1% /var/lib/docker/zfs/graph/c7289e222a0b9b990b35ee9744a03a6b1af16daf160ef19592eee874bd75d99f cache/system/056cf475f09055b5d35b58b48e5d9b51d91cd6c0d0859868b160d8c9d6787276 711G 1009M 710G 1% /var/lib/docker/zfs/graph/056cf475f09055b5d35b58b48e5d9b51d91cd6c0d0859868b160d8c9d6787276 cache/system/8ebc1fdd867c73f796e2d539963e54f0d4005300d50640403694da0ffc08dce8 710G 535M 710G 1% /var/lib/docker/zfs/graph/8ebc1fdd867c73f796e2d539963e54f0d4005300d50640403694da0ffc08dce8 cache/system/4302abed5ea57ea1c2bce0f3e86ad84fc3630215903d9223eeffc21f0e075f49 710G 198M 710G 1% /var/lib/docker/zfs/graph/4302abed5ea57ea1c2bce0f3e86ad84fc3630215903d9223eeffc21f0e075f49 cache/system/704d69dd6da682ef0e7a93422abb8215b6db30993c81b7adde6dcc8f8bbcb877 710G 198M 710G 1% /var/lib/docker/zfs/graph/704d69dd6da682ef0e7a93422abb8215b6db30993c81b7adde6dcc8f8bbcb877 cache/system/84919403db27c2e0e7f4e7c86efe91c083649ed65b29aa0eb77c21ae830c6833 710G 459M 710G 1% /var/lib/docker/zfs/graph/84919403db27c2e0e7f4e7c86efe91c083649ed65b29aa0eb77c21ae830c6833 cache/system/82a03784cd53ba8689f21501c292fd50ad316ba3521541f09c1d2af11fea1ad0 711G 1.3G 710G 1% /var/lib/docker/zfs/graph/82a03784cd53ba8689f21501c292fd50ad316ba3521541f09c1d2af11fea1ad0 cache/system/ed4806db10584dd0515222b648816fb6e98ad3b7be446054e261153920074ffe 710G 352M 710G 1% /var/lib/docker/zfs/graph/ed4806db10584dd0515222b648816fb6e98ad3b7be446054e261153920074ffe cache/system/9492c03d3a793b567d76e4b2b17df6e2ca40c3b1659fa048fbf319312c36e4d6 710G 198M 710G 1% /var/lib/docker/zfs/graph/9492c03d3a793b567d76e4b2b17df6e2ca40c3b1659fa048fbf319312c36e4d6 cache/system/3af3c1cd4545da5686dfaa6fa1c0d21c1e4fe344258bfc76f93a56d8d66ddb32 710G 12M 710G 1% /var/lib/docker/zfs/graph/3af3c1cd4545da5686dfaa6fa1c0d21c1e4fe344258bfc76f93a56d8d66ddb32 cache/system/6c4ad09a4c2d03f2699943970aef0f3f99d7435890dbb164894eb09444825ad2 710G 30M 710G 1% /var/lib/docker/zfs/graph/6c4ad09a4c2d03f2699943970aef0f3f99d7435890dbb164894eb09444825ad2 cache/system/2088778e022a8b024c0fabcd4a40ad1797c02ffe6ffca1ed7b87828868e4aa4e 710G 36M 710G 1% /var/lib/docker/zfs/graph/2088778e022a8b024c0fabcd4a40ad1797c02ffe6ffca1ed7b87828868e4aa4e cache/system/3620a65dddc28d26cf1a101de70d53738aee10729d3eca3571135d93d993c324 710G 242M 710G 1% /var/lib/docker/zfs/graph/3620a65dddc28d26cf1a101de70d53738aee10729d3eca3571135d93d993c324 cache/system/9844935ec93f882121700e0389609e6fad7ccf2e8a1d0113763a19d7654fe829 711G 811M 710G 1% /var/lib/docker/zfs/graph/9844935ec93f882121700e0389609e6fad7ccf2e8a1d0113763a19d7654fe829 cache/system/fff7fe343cd0f6ff0c454599a5fc86612a48ec8a5bfd75830e83fcf52875ef04 710G 356M 710G 1% /var/lib/docker/zfs/graph/fff7fe343cd0f6ff0c454599a5fc86612a48ec8a5bfd75830e83fcf52875ef04 cache/system/8d7de36e597549ca1c32700383e3727c99fce5b7a0d1d6b00c91096d1896a8cc 711G 995M 710G 1% /var/lib/docker/zfs/graph/8d7de36e597549ca1c32700383e3727c99fce5b7a0d1d6b00c91096d1896a8cc cache/system/d66e8ad26ef673cb3279019d543adfa569197ace7d24737ed946b843ce0e84d2 710G 222M 710G 1% /var/lib/docker/zfs/graph/d66e8ad26ef673cb3279019d543adfa569197ace7d24737ed946b843ce0e84d2 cache/system/a160a867bb39c7d00ce3bbd1f9db3b79df0cc9250ec0db99238c0a7eaca78e59 710G 242M 710G 1% /var/lib/docker/zfs/graph/a160a867bb39c7d00ce3bbd1f9db3b79df0cc9250ec0db99238c0a7eaca78e59 cache/system/ba916a663d93c88c00a204e58230b9b9066605853c5a4341edbe074b687b8704 711G 1.1G 710G 1% /var/lib/docker/zfs/graph/ba916a663d93c88c00a204e58230b9b9066605853c5a4341edbe074b687b8704 cache/system/10e0752573c69fbaf92a94986ca6f6fdbddfddd0f48fcad33e52b11d848e98c9 710G 224M 710G 1% /var/lib/docker/zfs/graph/10e0752573c69fbaf92a94986ca6f6fdbddfddd0f48fcad33e52b11d848e98c9 cache/system/934f49aba3ca787ebcd58d96449f0bc243340350dc808be1742361faa69b9ba1 710G 150M 710G 1% /var/lib/docker/zfs/graph/934f49aba3ca787ebcd58d96449f0bc243340350dc808be1742361faa69b9ba1 cache/system/70694c661997b8425cfe0262f9f7c313e37354f443c0727a51ef7de57258cf60 710G 308M 710G 1% /var/lib/docker/zfs/graph/70694c661997b8425cfe0262f9f7c313e37354f443c0727a51ef7de57258cf60 cache/system/9da8a9ffdb60ac4a58c3b87f51658a85d4bc04d80ccde59ed10041d731f27338 710G 255M 710G 1% /var/lib/docker/zfs/graph/9da8a9ffdb60ac4a58c3b87f51658a85d4bc04d80ccde59ed10041d731f27338 cache/system/3d14e51e421519360ad7573dbf93963ac3ec22276901bf17062dd9f1a665dd6c 710G 262M 710G 1% /var/lib/docker/zfs/graph/3d14e51e421519360ad7573dbf93963ac3ec22276901bf17062dd9f1a665dd6c cache/system/1fc939cb4a60c443d56b03949f1ad9f53e4c6e1a60d2be30b03e5bf029f991be 711G 1.2G 710G 1% /var/lib/docker/zfs/graph/1fc939cb4a60c443d56b03949f1ad9f53e4c6e1a60d2be30b03e5bf029f991be cache/system/39198428065fe4898f589b12475be5d64906dbb9b5c470efeb98aac9dd1f14f6 710G 177M 710G 1% /var/lib/docker/zfs/graph/39198428065fe4898f589b12475be5d64906dbb9b5c470efeb98aac9dd1f14f6 cache/system/315fd6f273a61bb43ea3c7da1c02cecf9ed625e28a8d2c86b93b7df3e7a8c3ca 710G 231M 710G 1% /var/lib/docker/zfs/graph/315fd6f273a61bb43ea3c7da1c02cecf9ed625e28a8d2c86b93b7df3e7a8c3ca cache/system/fc020e963725fb4b5ff1d80eb9964d60b5d48205f6f47ba61af6f4ed34478dc8 710G 109M 710G 1% /var/lib/docker/zfs/graph/fc020e963725fb4b5ff1d80eb9964d60b5d48205f6f47ba61af6f4ed34478dc8 cache/system/76568fd71ecabb1be3c2bd856fa5aabd05567a74952a46ece4ee24cf6bf10ad1 710G 517M 710G 1% /var/lib/docker/zfs/graph/76568fd71ecabb1be3c2bd856fa5aabd05567a74952a46ece4ee24cf6bf10ad1 cache/system/40c09ea2f3f0211739419f86d4950e41b63e387db7d32effa3a974c2f74bfb8d 710G 510M 710G 1% /var/lib/docker/zfs/graph/40c09ea2f3f0211739419f86d4950e41b63e387db7d32effa3a974c2f74bfb8d cache/system/e823eb420d51743083c278b0c50548b4c0d6a28caa51ed4c285203f758380ec7 710G 251M 710G 1% /var/lib/docker/zfs/graph/e823eb420d51743083c278b0c50548b4c0d6a28caa51ed4c285203f758380ec7 cache/system/89ab6f4fb0545f02cd1ee305d706c8f885f9fd46f3b5f9e8ea35ec9ddf87f18a 710G 490M 710G 1% /var/lib/docker/zfs/graph/89ab6f4fb0545f02cd1ee305d706c8f885f9fd46f3b5f9e8ea35ec9ddf87f18a cache/system/2dcd863d9ba6f2e7691a2dc27de65eaf9654b6f0dc8c3e911d362976ed6cba69 711G 766M 710G 1% /var/lib/docker/zfs/graph/2dcd863d9ba6f2e7691a2dc27de65eaf9654b6f0dc8c3e911d362976ed6cba69 cache/system/344fa30fbc91e4a9789cab6736bb5b88df740e8201b2052b7bfbf6da984a3606 710G 639M 710G 1% /var/lib/docker/zfs/graph/344fa30fbc91e4a9789cab6736bb5b88df740e8201b2052b7bfbf6da984a3606 cache/system/7c7de960343a6bb558ca27765fd3027706817495cbd463b58a42ac8263377e2c 710G 277M 710G 1% /var/lib/docker/zfs/graph/7c7de960343a6bb558ca27765fd3027706817495cbd463b58a42ac8263377e2c cache/system/27efacc1298d8cbd821abf2d892aea35300fadad6634de7387dafa482c24fca0 710G 9.2M 710G 1% /var/lib/docker/zfs/graph/27efacc1298d8cbd821abf2d892aea35300fadad6634de7387dafa482c24fca0 cache/system/faaf3b59904aabd5fa6031d1939f35a5187cca844aa78988bd09d222ec8fbdbc 710G 13M 710G 1% /var/lib/docker/zfs/graph/faaf3b59904aabd5fa6031d1939f35a5187cca844aa78988bd09d222ec8fbdbc cache/system/fbf993becba2893c2b4b5ee066e5aeb1d003f3c0bef5174eee850a38fb2e9e48 710G 198M 710G 1% /var/lib/docker/zfs/graph/fbf993becba2893c2b4b5ee066e5aeb1d003f3c0bef5174eee850a38fb2e9e48 cache/system/4f2bab8ebc9b56f04b6067d25def02128bae2fc7ca07ac39323afb6a864c8be6 710G 11M 710G 1% /var/lib/docker/zfs/graph/4f2bab8ebc9b56f04b6067d25def02128bae2fc7ca07ac39323afb6a864c8be6 cache/system/603733c80a97d8fe778feb8f9a7662e3ba0cdf71a4262c0cc120436b65bd798d 710G 224M 710G 1% /var/lib/docker/zfs/graph/603733c80a97d8fe778feb8f9a7662e3ba0cdf71a4262c0cc120436b65bd798d cache/system/197538007e358844d75174831ffe0b13e1a62d2de775e7a189ca6c893d1cc3b1 710G 223M 710G 1% /var/lib/docker/zfs/graph/197538007e358844d75174831ffe0b13e1a62d2de775e7a189ca6c893d1cc3b1 cache/system/b24f39da76b5da16b6e8d4010aea115049c560d26ce5eeb85c0171f2cdd9bd56 710G 405M 710G 1% /var/lib/docker/zfs/graph/b24f39da76b5da16b6e8d4010aea115049c560d26ce5eeb85c0171f2cdd9bd56 cache/system/a9dbbbe8afcedfb2591b50eb0eddab322194b0cb3623ab64183526e14d6e6ca4 710G 62M 710G 1% /var/lib/docker/zfs/graph/a9dbbbe8afcedfb2591b50eb0eddab322194b0cb3623ab64183526e14d6e6ca4 cache/isos 710G 128K 710G 1% /mnt/cache/isos

I have no idea what is happening. Since a few days it's the second or third time that it happened. Nothing special was done. Earlier I thought it was because people were watching Plex on my server and killed my bandwidth and more (even though it makes no sense to get the problem that I have). It randomly appears and starts by some Docker containers getting unhealthy and restarting. And then the loop starts. If I want to go to the unRAID web UI it's loading 1 minute if I'm lucky. I was able to make a screenshot but I guess the high load occurs because all containers get unhealthy and the autoheal tool restarts them all and they never get healthy again. The only suspicous thing I also realized is that my Nextcloud Docker instance also starts to fail several times a day since a few days. The 200 status code turns into 503 and Nextcloud enables automatically the maintenance mode and I always have to set it to off again and everything is just fine. I was lucky to get the diagnostics before it was completly unusable and unresponsive. The only thing that helps is a restart. A parity check was finished today without errors. I have changed nothing on my hardware setup. Also the unRAID version 6.12.6 is installed since a while now. Temperatures are also okay with temps around 40 degree. I'm running nearly 100 Docker containers but that's all. No VM was running or anything else. I had a look into the diagnostics docker.log and you can also see what I described in the last 3 days because the logs are there: time="2024-01-31T01:02:31.586877851+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2024-01-31T01:02:31.586918839+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1 time="2024-01-31T01:02:31.586926061+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1 This repeats very often. I don't know what is causing this error. Is it some kind of memory leak? But look at the screenshot there still is enough RAM... please help me! unraid-server-diagnostics-20240201-0155.zip It's not even possible to restart. After clicking restart and waiting 10 minutes I can get back on the Dashboard after a while to see this: Edit: Another thing I realized now is that my Nextcloud for example runs so much faster after that reboot but will get slower from time to time. Must not have anything to do with Unraid but I realized it.

Yes but I understood now. As you guys mentioned. A share is responsible for all drives of pools and arrays. And that's the point then. At least I can disable the mover like these. Even if there is a warning.

It's okay now. I disabled the second location but I want to know why this warning appears. It makes no sense for me if I want it like this.

Is it maybe a bug? This is the share now. Fix Common Problem shows this warning. But this is not a cache drive. It's a separate pool.

Same problem here again. It's the second time in 7 days now and I need to restart before the log is full. Every goddamn second. Diagnostics attached. Jan 10 19:31:30 UNRAID-Server nginx: 2024/01/10 19:31:30 [crit] 18760#18760: ngx_slab_alloc() failed: no memory Jan 10 19:31:30 UNRAID-Server nginx: 2024/01/10 19:31:30 [error] 18760#18760: shpool alloc failed Jan 10 19:31:30 UNRAID-Server nginx: 2024/01/10 19:31:30 [error] 18760#18760: nchan: Out of shared memory while allocating message of size 15621. Increase nchan_max_reserved_memory. Jan 10 19:31:30 UNRAID-Server nginx: 2024/01/10 19:31:30 [error] 18760#18760: *1269271 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jan 10 19:31:30 UNRAID-Server nginx: 2024/01/10 19:31:30 [error] 18760#18760: MEMSTORE:00: can't create shared message for channel /disks Jan 10 19:31:32 UNRAID-Server nginx: 2024/01/10 19:31:32 [crit] 18760#18760: ngx_slab_alloc() failed: no memory Jan 10 19:31:32 UNRAID-Server nginx: 2024/01/10 19:31:32 [error] 18760#18760: shpool alloc failed Jan 10 19:31:32 UNRAID-Server nginx: 2024/01/10 19:31:32 [error] 18760#18760: nchan: Out of shared memory while allocating message of size 15621. Increase nchan_max_reserved_memory. Jan 10 19:31:32 UNRAID-Server nginx: 2024/01/10 19:31:32 [error] 18760#18760: *1269275 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jan 10 19:31:32 UNRAID-Server nginx: 2024/01/10 19:31:32 [error] 18760#18760: MEMSTORE:00: can't create shared message for channel /disks Jan 10 19:31:33 UNRAID-Server nginx: 2024/01/10 19:31:33 [crit] 18760#18760: ngx_slab_alloc() failed: no memory Jan 10 19:31:33 UNRAID-Server nginx: 2024/01/10 19:31:33 [error] 18760#18760: shpool alloc failed Jan 10 19:31:33 UNRAID-Server nginx: 2024/01/10 19:31:33 [error] 18760#18760: nchan: Out of shared memory while allocating message of size 15621. Increase nchan_max_reserved_memory. Jan 10 19:31:33 UNRAID-Server nginx: 2024/01/10 19:31:33 [error] 18760#18760: *1269279 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jan 10 19:31:33 UNRAID-Server nginx: 2024/01/10 19:31:33 [error] 18760#18760: MEMSTORE:00: can't create shared message for channel /disks Jan 10 19:31:34 UNRAID-Server nginx: 2024/01/10 19:31:34 [crit] 18760#18760: ngx_slab_alloc() failed: no memory Jan 10 19:31:34 UNRAID-Server nginx: 2024/01/10 19:31:34 [error] 18760#18760: shpool alloc failed Jan 10 19:31:34 UNRAID-Server nginx: 2024/01/10 19:31:34 [error] 18760#18760: nchan: Out of shared memory while allocating message of size 15621. Increase nchan_max_reserved_memory. Jan 10 19:31:34 UNRAID-Server nginx: 2024/01/10 19:31:34 [error] 18760#18760: *1269281 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jan 10 19:31:34 UNRAID-Server nginx: 2024/01/10 19:31:34 [error] 18760#18760: MEMSTORE:00: can't create shared message for channel /disks Jan 10 19:31:35 UNRAID-Server nginx: 2024/01/10 19:31:35 [crit] 18760#18760: ngx_slab_alloc() failed: no memory Jan 10 19:31:35 UNRAID-Server nginx: 2024/01/10 19:31:35 [error] 18760#18760: shpool alloc failed Jan 10 19:31:35 UNRAID-Server nginx: 2024/01/10 19:31:35 [error] 18760#18760: nchan: Out of shared memory while allocating message of size 15621. Increase nchan_max_reserved_memory. Jan 10 19:31:35 UNRAID-Server nginx: 2024/01/10 19:31:35 [error] 18760#18760: *1269285 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jan 10 19:31:35 UNRAID-Server nginx: 2024/01/10 19:31:35 [error] 18760#18760: MEMSTORE:00: can't create shared message for channel /disks I tried /etc/rc.d/rc.nginx restart in the webterminal which closes after some time and the unRAID web interface never came back. I guess it was because the terminal was closed and the command terminated. I logged in via SSH and saw that NGINX is not running and started it again with /etc/rc.d/rc.nginx start Now the error is gone for a while but this is no solution. unraid-server-diagnostics-20240110-1930.zip

Is there a reason that there isn't an exclusion option for specific shares like this?

I have a folder named backup on my array and also on a separate pool. I want that these backups stay on the pool because they are very important so I want them to be on RAID1. Now I also have a backup folder on my array (disk1) for less important things. The problem I got is that I cannot tell mover to don't move these files. It's handled as the same share. When I had no secondary storage it worked but I got the warning from fix common problems that there are files on cache (what makes no sense anyway) and that's not correct. Don't have the error message now. I guess you guys know what I mean. This typical message. How to handle it the best way?

Okay I found the reason. I don't know why but the unRAID Template for this container here creates the folder at the defined location with 755 permissions. That is why this error occurs. Just manually fix it by setting it recursively to 777 and it works.

Same question here. Trying to install it the first time. Elasticsearch 8. fatal exception while booting Elasticsearch | @timestamp=2024-01-06T04:28:38.229Z log.level=ERROR ecs.version=1.2.0 service.name=ES_ECS event.dataset=elasticsearch.server process.thread.name=main log.logger=org.elasticsearch.bootstrap.Elasticsearch elasticsearch.node.name=78dd8c70729b elasticsearch.cluster.name=docker-cluster error.type=java.lang.IllegalStateException error.message=failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path? error.stack_trace=java.lang.IllegalStateException: failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path? at [email protected]/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:294) at [email protected]/org.elasticsearch.node.Node.<init>(Node.java:499) at [email protected]/org.elasticsearch.node.Node.<init>(Node.java:344) at [email protected]/org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:236) at [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:236) at [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) Caused by: java.io.IOException: failed to obtain lock on /usr/share/elasticsearch/data at [email protected]/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:239) at [email protected]/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:206) at [email protected]/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:286) ... 5 more Caused by: java.nio.file.NoSuchFileException: /usr/share/elasticsearch/data/node.lock at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixPath.toRealPath(UnixPath.java:834) at [email protected]/org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:94) at [email protected]/org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:43) at [email protected]/org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:44) at [email protected]/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:232) ... 7 more Suppressed: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data/node.lock at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:90) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:261) at java.base/java.nio.file.Files.newByteChannel(Files.java:379) at java.base/java.nio.file.Files.createFile(Files.java:657) at [email protected]/org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:84) ... 10 more

I'm using the newest version but also seeing the message fopen /var/run/nut/upsd.pid: No such file or directory in my boot logs. It still seems to work. After that it tells it is listening to 0.0.0.0 port 3493 and that its connected to ups usbhid-ups-ups and found 1 defined in the ups.conf. Then at the last logs I see UPS:[email protected] (primary) (power value 1) and Using power down flag file /etc/nut/no_killpower But how to get rid of this fopen error?

Moin zusammen, ich habe die Nachricht ebenfalls (Screenshot letzte Zeile). Gott sei Dank hat sich mein Server deshalb aber nicht selbst neugestartet. Das kommt direkt bei Systemstart und ich habe keine Ahnung wieso. Die Logs sind in unRAID auf jeden Fall da. Also die normalen. Es ist richtig, dass die Logs, die man hier auf dem Screenshot sieht nicht im unRAID Log sieht, oder?

Hey guys. I guess somebody has probably answered already but the search function does not show me anything useful. I have the same error as this user: mv: cannot stat '/usr/local/bin/mover': No such file or directory I see it in the boot logs. It still boots but why is this error appearing? How to fix it?

Of course. Here the ups.conf [ups] driver = "usbhid-ups" port = "auto" vendorid = "0463" productid = "FFFF" product = "Eaton 3S" serial = "Blank" vendor = "EATON" bus = "001"

Is something wrong in my configuration or why is the load of my Eaton 3S 850 DIN UPS always 4%? No matter if something load intensive is running on my Unraid server or not. Unfortunately, the UPS is not really smart and I have to manually specify VA with 850 and W with 510, but he would calculate everything so. At least that was the thought. But brings nothing, as long as the load is always at 4%.

How can I add the logs of the script in the notification of Unraid. Currently I'm just sending a notification if something has failed like this: if [ $? -eq 0 ]; then echo "Script succeeded" else echo "Script failed" /usr/local/emhttp/webGui/scripts/notify -i "alert" -s "Auto-Archiving" -d "Something went wrong" -l "http://192.168.178.39:86/Main/Userscripts" fi It would be awesome if I could send the logs directly in the notification because I get a mail for that. I always have to log in and download the ZIP because the show logs window does never work.

Thank you for your help @dlandon! Und natürlich vielen Dank @hawihoney. Dachte das muss per Device Script sein. So per User Script ist mir das auch lieber

Can I attach it via a script again then? My script looks like this: #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # DEVICE - partition device, e.g. /dev/sda1 # UD_DEVICE - unassigned devX designation # SERIAL - disk serial number # LABEL - partition label # LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1 # FSTYPE - partition filesystem # MOUNTPOINT - where the partition is mounted # OWNER - "udev" if executed by UDEV, otherwise "user" # PROG_NAME - program name of this script # LOGFILE - log file for this script case $ACTION in 'REMOVE' ) # do your stuff here # Spin down disk - uncomment this if you want the disk to be spun down after the disk is unmounted /usr/local/sbin/rc.unassigned spindown $DEVICE # Detach the disk - uncomment this if you want the USB disk to be detached after it is unmounted /usr/local/sbin/rc.unassigned detach $DEVICE /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Device unmounted" -i "normal" ;; esac

This doesn't work for me. Am I doing it right? It shows the following error logs: /tmp/unassigned.devices/scripts/SanDisk_Ultra.sh: line 1: syntax error near unexpected token `)' /tmp/unassigned.devices/scripts/SanDisk_Ultra.sh: line 1: ` 'REMOVE' )' Okay got it working with the template now. The device completely disappeared from Unassigened Devices. Should this happen? It's now a historial device. I cannot mount it anymore. Command show true but nothing is mounted.

Yes. Klappt. Command ist nur wie in Linux umount und nicht unmount. This is perfect!

In Anlehnung an mein Thema frage ich mich, ob und wenn ja, wie es geht, dass ich einen angeschlossenen USB-Stick automatisch bspw. jeden 01. des Monats um 02:00 mounten lasse und dann eben ein Backup Skript laufen lasse und wieder unmounte. Wäre das dann ein Device Script und wie würde es aussehen? Hab noch keinen Beitrag mit diesen Anforderungen gesehen.

I had these problems in 6.11.x as well. Chrome and Unraid GUI just don't seem to go well together. But I can say when NGINX is crashed for me it is everywhere. The whole GUI is broken then. Every websocket fetch fails. I can see the GUI and get into settings and stuff but don't see the main page or the Docker page.

Ok it didnt helped. 2 days and logs are shown as 100%. I try to pull out the bluetooth adapter but I don't think it is the only reason.

I have activated it. I'm using Chrome. Is there an option to exclude some URLs? I guess this should help then. I will google it.

@JorgeBI will try. So nothing obvious in the logs? Does the logs get filled just because the tab is somewhere opened in my browser?