October 25, 20241 yr Big Issue: Last night when I came home I wanted to finally set up paperless nxg (i had the container deploied and running for couple of days now but didn't do much more than Access it and look around) But unfortunately my Server had sever Dockers that just didn't work anymore - i couldn't connect to them. No Web GUI seemed to work as there was no Connection. So i checked the logs (fortunately Dozzle still works): Guacamole: sed: can't create temp file '/config/guacamole/logback.xmlXXXXXX': No space left on device Using existing properties file. Copying MySQL extension. cp: can't create '/config/guacamole/extensions/guacamole-auth-jdbc-mysql-1.5.4.jar': No space left on device cp: can't create '/config/guacamole/lib/mysql-connector-j-8.0.33.jar': No space left on device mkdir: can't create directory '/config/mysql-schema': File exists cp: can't create '/config/mysql-schema/001-create-schema.sql': No space left on device cp: can't create '/config/mysql-schema/002-create-admin-user.sql': No space left on device cp: can't create directory '/config/mysql-schema/upgrade': No space left on device Updating user permissions. Database exists. Database upgrade not needed. 2024-10-25 07:37:20,054 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2024-10-25 07:37:20,055 INFO Set uid to user 0 succeeded 2024-10-25 07:37:20,058 INFO supervisord started with pid 28 2024-10-25 07:37:21,061 INFO spawned: 'guacd' with pid 29 2024-10-25 07:37:21,066 INFO spawned: 'mariadb' with pid 30 2024-10-25 07:37:21,071 INFO spawned: 'tomcat' with pid 31 guacd[29]: INFO: Guacamole proxy daemon (guacd) version 1.5.4 started guacd[29]: INFO: Listening on host 0.0.0.0, port 4822 2024-10-25 07:37:22,103 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:22,103 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:22,104 INFO success: tomcat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:22,104 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:23,109 INFO spawned: 'mariadb' with pid 94 2024-10-25 07:37:24,148 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:24,149 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:25,152 INFO spawned: 'mariadb' with pid 118 2024-10-25 07:37:26,195 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:26,196 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:27,199 INFO spawned: 'mariadb' with pid 120 2024-10-25 07:37:28,237 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:28,242 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:29,246 INFO spawned: 'mariadb' with pid 122 2024-10-25 07:37:30,285 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:30,286 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:31,293 INFO spawned: 'mariadb' with pid 124 2024-10-25 07:37:32,327 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:32,327 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:33,332 INFO spawned: 'mariadb' with pid 126 2024-10-25 07:37:34,367 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:34,368 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:35,372 INFO spawned: 'mariadb' with pid 128 2024-10-25 07:37:36,407 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:36,407 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:37,411 INFO spawned: 'mariadb' with pid 130 2024-10-25 07:37:38,444 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-10-25 07:37:38,444 WARN exited: mariadb (exit status 1; not expected) 2024-10-25 07:37:39,449 INFO spawned: 'mariadb' with pid 132 frigate: 09:39:31 Container started s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service certsync-log: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service certsync-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting 2024-10-25 09:39:30.564283350 [INFO] Preparing Frigate... 2024-10-25 09:39:30.565502524 [INFO] Starting NGINX... 2024-10-25 09:39:30.572395568 [INFO] Preparing new go2rtc config... 2024-10-25 09:39:30.585011475 [INFO] Starting Frigate... 2024-10-25 09:39:31.021672688 [INFO] Starting go2rtc... 2024-10-25 09:39:31.121223774 09:39:31.121 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2024-10-25 09:39:31.121551964 09:39:31.121 INF config path=/dev/shm/go2rtc.yaml 2024-10-25 09:39:31.121975043 09:39:31.121 INF [rtsp] listen addr=:8554 2024-10-25 09:39:31.121989851 09:39:31.121 INF [api] listen addr=:1984 2024-10-25 09:39:31.122142489 09:39:31.122 INF [webrtc] listen addr=:8555/tcp s6-rc: info: service nginx successfully started s6-rc: info: service certsync: starting s6-rc: info: service certsync successfully started s6-rc: info: service legacy-services: starting 2024-10-25 09:39:31.679263063 [INFO] Starting certsync... s6-rc: info: service legacy-services successfully started 2024-10-25 09:39:32.169381120 [2024-10-25 09:39:32] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa) 2024-10-25 09:39:32.169696485 [2024-10-25 09:39:32] frigate.util.config INFO : Checking if frigate config needs migration... 2024-10-25 09:39:32.246821047 [2024-10-25 09:39:32] frigate.util.config INFO : frigate config does not need migration... 2024-10-25 09:39:33.462777719 [2024-10-25 09:39:33] frigate.util.services WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended 2024-10-25 09:39:33.508119300 unable to open database file 2024-10-25 09:39:34.851963246 [INFO] Service Frigate exited with code 1 (by signal 0) s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service certsync: stopping 2024-10-25 09:39:34.868031075 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) s6-rc: info: service go2rtc-healthcheck successfully stopped 2024-10-25 09:39:34.870489020 [INFO] Service CERTSYNC exited with code 256 (by signal 15) s6-rc: info: service certsync successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service certsync-log: stopping s6-rc: info: service certsync-log successfully stopped 2024-10-25 09:39:34.933597028 [INFO] Service NGINX exited with code 0 (by signal 0) s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped 2024-10-25 09:39:34.938215384 exit with signal: terminated s6-rc: info: service frigate-log successfully stopped 2024-10-25 09:39:34.945634933 [INFO] The go2rtc service exited with code 0 (by signal 0) s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped MariaDB: 25.10.2024 09:42:06 Container started [migrations] started [migrations] no migrations found usermod: no changes ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── [custom-init] No custom files found, skipping... 241025 09:42:05 mysqld_safe Logging to '/config/databases/2133f311f16b.err'. 241025 09:42:06 mysqld_safe Starting mariadbd daemon with databases from /config/databases /usr/bin/mariadbd-safe-helper: Can't create/write to file '/config/databases/2133f311f16b.err' (Errcode: 28 "No space left on device") Caught SIGTERM signal! cat: /var/run/mysqld/mysqld.pid: No such file or directory 241025 09:42:07 mysqld_safe Logging to '/config/databases/2133f311f16b.err'. 241025 09:42:07 mysqld_safe Starting mariadbd daemon with databases from /config/databases /usr/bin/mariadbd-safe-helper: Can't create/write to file '/config/databases/2133f311f16b.err' (Errcode: 28 "No space left on device") Caught SIGTERM signal! cat: /var/run/mysqld/mysqld.pid: No such file or directory 241025 09:42:08 mysqld_safe Logging to '/config/databases/2133f311f16b.err'. 241025 09:42:08 mysqld_safe Starting mariadbd daemon with databases from /config/databases /usr/bin/mariadbd-safe-helper: Can't create/write to file '/config/databases/2133f311f16b.err' (Errcode: 28 "No space left on device") Caught SIGTERM signal! cat: /var/run/mysqld/mysqld.pid: No such file or directory 241025 09:42:09 mysqld_safe Logging to '/config/databases/2133f311f16b.err'. 241025 09:42:09 mysqld_safe Starting mariadbd daemon with databases from /config/databases /usr/bin/mariadbd-safe-helper: Can't create/write to file '/config/databases/2133f311f16b.err' (Errcode: 28 "No space left on device") Caught SIGTERM signal! cat: /var/run/mysqld/mysqld.pid: No such file or directory 241025 09:42:10 mysqld_safe Logging to '/config/databases/2133f311f16b.err'. 241025 09:42:10 mysqld_safe Starting mariadbd daemon with databases from /config/databases /usr/bin/mariadbd-safe-helper: Can't create/write to file '/config/databases/2133f311f16b.err' (Errcode: 28 "No space left on device") Caught SIGTERM signal! cat: /var/run/mysqld/mysqld.pid: No such file or directory 241025 09:42:11 mysqld_safe Logging to '/config/databases/2133f311f16b.err'. 241025 09:42:12 mysqld_safe Starting mariadbd daemon with databases from /config/databases Nextcloud: 25.10.2024 09:43:00 Container started [migrations] started [migrations] 01-nginx-site-confs-default: skipped [migrations] 02-default-location: skipped [migrations] done usermod: no changes ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── Linuxserver.io version: 30.0.1-ls347 Build-date: 2024-10-22T11:52:26+00:00 ─────────────────────────────────────── cp: cannot create regular file '/config/nginx/nginx.conf.sample': No space left on device cp: cannot create regular file '/config/nginx/ssl.conf.sample': No space left on device cp: cannot create regular file '/config/nginx/site-confs/default.conf.sample': No space left on device sed: can't create temp file '/config/nginx/nginx.confXXXXXX': No space left on device using keys found in /config/keys After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations. Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html sed: can't create temp file '/config/www/nextcloud/config/config.phpXXXXXX': No space left on device **** The following site-confs have extensions other than .conf **** **** This may be due to user customization. **** **** You should review the files and rename them to use the .conf extension or remove them. **** **** nginx.conf will only include site-confs with the .conf extension. **** /config/nginx/site-confs/default.conf.bak [custom-init] No custom files found, skipping... [ls.io-init] done. nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:13 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:14 Nginx: 25.10.2024 09:45:35 Container started ❯ Configuring npm user ... 0 usermod: no changes ❯ Configuring npm group ... ❯ Checking paths ... ❯ Setting ownership ... ❯ Dynamic resolvers ... ❯ IPv6 ... Enabling IPV6 in hosts in: /etc/nginx/conf.d - /etc/nginx/conf.d/default.conf - /etc/nginx/conf.d/include/assets.conf - /etc/nginx/conf.d/include/block-exploits.conf - /etc/nginx/conf.d/include/force-ssl.conf - /etc/nginx/conf.d/include/ip_ranges.conf - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf - /etc/nginx/conf.d/include/log.conf - /etc/nginx/conf.d/include/proxy.conf - /etc/nginx/conf.d/include/ssl-ciphers.conf - /etc/nginx/conf.d/include/resolvers.conf - /etc/nginx/conf.d/production.conf Enabling IPV6 in hosts in: /data/nginx - /data/nginx/default_host/site.conf - /data/nginx/proxy_host/4.conf - /data/nginx/proxy_host/5.conf - /data/nginx/proxy_host/2.conf - /data/nginx/proxy_host/3.conf - /data/nginx/proxy_host/1.conf - /data/nginx/proxy_host/6.conf - /data/nginx/proxy_host/7.conf ❯ Docker secrets ... ------------------------------------- _ _ ____ __ __ | \ | | _ \| \/ | | \| | |_) | |\/| | | |\ | __/| | | | |_| \_|_| |_| |_| ------------------------------------- User: npm PUID:0 ID:0 GROUP:0 Group: npm PGID:0 ID:0 ------------------------------------- ❯ Starting backend ... ❯ Starting nginx ... nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/2.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/2.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/4.conf:14 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/4.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/4.conf:15 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/4.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/5.conf:14 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/5.conf:15 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/6.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/6.conf:20 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/7.conf:19 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/7.conf:20 [10/25/2024] [7:45:35 AM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [10/25/2024] [7:45:36 AM] [Migrate ] › ℹ info Current database version: none Can't take lock to run migrations: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file If you are sure migrations are not running you can release the lock manually by running 'knex migrate:unlock' [10/25/2024] [7:45:36 AM] [Global ] › ✖ error update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file MigrationLocked: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file at /app/node_modules/knex/lib/migrations/migrate/Migrator.js:342:13 at async Migrator._runBatch (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:358:7) [10/25/2024] [7:45:37 AM] [Migrate ] › ℹ info Current database version: none Can't take lock to run migrations: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file If you are sure migrations are not running you can release the lock manually by running 'knex migrate:unlock' [10/25/2024] [7:45:37 AM] [Global ] › ✖ error update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file MigrationLocked: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file at /app/node_modules/knex/lib/migrations/migrate/Migrator.js:342:13 at async Migrator._runBatch (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:358:7) \6 Einträge übersprungen [10/25/2024] [7:45:43 AM] [Migrate ] › ℹ info Current database version: none Can't take lock to run migrations: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file If you are sure migrations are not running you can release the lock manually by running 'knex migrate:unlock' [10/25/2024] [7:45:43 AM] [Global ] › ✖ error update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file MigrationLocked: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file at /app/node_modules/knex/lib/migrations/migrate/Migrator.js:342:13 at async Migrator._runBatch (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:358:7) [10/25/2024] [7:45:44 AM] [Migrate ] › ℹ info Current database version: none Can't take lock to run migrations: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file If you are sure migrations are not running you can release the lock manually by running 'knex migrate:unlock' [10/25/2024] [7:45:44 AM] [Global ] › ✖ error update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file MigrationLocked: update `migrations_lock` set `is_locked` = 1 where `is_locked` = 0 - SQLITE_CANTOPEN: unable to open database file at /app/node_modules/knex/lib/migrations/migrate/Migrator.js:342:13 at async Migrator._runBatch (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:358:7) Bitwarden: /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.32.2 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://github.com/dani-garcia/vaultwarden/discussions or | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] Using saved config from `data/config.json` for configuration. [WARNING] The following environment variables are being overridden by the config.json file. [WARNING] Please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN [DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead. [NOTICE] You are using a plain text `ADMIN_TOKEN` which is insecure. Please generate a secure Argon2 PHC string by using `vaultwarden hash` or `argon2`. See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token [2024-10-25 09:46:28.501][panic][ERROR] thread 'main' panicked at 'Failed to turn on WAL: DatabaseError(Unknown, "unable to open database file")': src/db/mod.rs:455 0: vaultwarden::init_logging::{{closure}} 1: std::panicking::rust_panic_with_hook 2: std::panicking::begin_panic_handler::{{closure}} 3: std::sys::backtrace::__rust_end_short_backtrace 4: rust_begin_unwind 5: core::panicking::panic_fmt 6: core::result::unwrap_failed 7: vaultwarden::db::DbPool::from_config 8: vaultwarden::main::{{closure}} 9: vaultwarden::main 10: std::sys::backtrace::__rust_begin_short_backtrace 11: main 12: <unknown> 13: __libc_start_main 14: _start 25.10.2024 09:46:36 Container stopped SO I checked the drives: Filesystem Size Used Avail Use% Mounted on rootfs 63G 2.8G 61G 5% / tmpfs 128M 8.0M 121M 7% /run /dev/sda1 15G 1.7G 13G 12% /boot overlay 63G 2.8G 61G 5% /lib overlay 63G 2.8G 61G 5% /usr devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 63G 0 63G 0% /dev/shm tmpfs 128M 5.5M 123M 5% /var/log tmpfs 1.0M 1.0M 0 100% /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 9.1T 8.0T 1.2T 88% /mnt/disk1 /dev/md2p1 9.1T 8.0T 1.2T 88% /mnt/disk2 /dev/md3p1 9.1T 8.0T 1.2T 88% /mnt/disk3 /dev/md4p1 9.1T 8.0T 1.2T 88% /mnt/disk4 /dev/md5p1 9.1T 7.8T 1.4T 86% /mnt/disk5 /dev/nvme1n1p1 1.9T 1.8T 105G 95% /mnt/cache /dev/nvme0n1p1 1.9T 215G 1.7T 12% /mnt/speicher shfs 46T 40T 5.9T 88% /mnt/user0 shfs 46T 40T 5.9T 88% /mnt/user /dev/loop2 200G 77G 121G 39% /var/lib/docker tmpfs 1.0M 1.0M 0 100% /mnt/disks concerns me.... but I don't really know what to do about it EDIT.... ok my cache was apparently full... so yeah... that fixed everything Edited October 25, 20241 yr by Zeze21
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.