Everything posted by maddog
-
[SOLVED] Cannot unmount /mnt/cache to Stop array
running into same problem. its been more than hr or so now. version: 6.12.6, can attach diagnostics if needed. i keep getting: Logs Nov 8 09:16:49 Beta root: umount: /mnt/cache: target is busy. Nov 8 09:16:49 Beta emhttpd: shcmd (30293350): exit status: 32 Nov 8 09:16:49 Beta emhttpd: Retry unmounting disk share(s)... i checked lsof and losetup and nothing shows up. so i just went ahead and tried to un-mount it directly using umount -l /dev/loop2 and now i see this in my logs. Logs again Nov 8 10:19:56 Beta kernel: sd 5:0:0:0: [sdf] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Nov 8 10:19:56 Beta kernel: sd 5:0:0:0: [sdf] tag#10 CDB: opcode=0x28 28 00 00 72 fd a0 00 00 20 00 Nov 8 10:19:56 Beta kernel: I/O error, dev sdf, sector 7536032 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Nov 8 10:19:56 Beta kernel: BTRFS error (device sdf1: state EA): bdev /dev/sdf1 errs: wr 99, rd 160091136, flush 0, corrupt 0, gen 0 any suggestions ?
-
Stopping array takes forever
running into same problem. its been more than hr or so now. version: 6.12.6, can attach diagnostics if needed. i keep getting: Nov 8 09:16:49 Beta root: umount: /mnt/cache: target is busy. Nov 8 09:16:49 Beta emhttpd: shcmd (30293350): exit status: 32 Nov 8 09:16:49 Beta emhttpd: Retry unmounting disk share(s)...
-
[Support] MattFaz Repo
i was trying to move to docker compose version: '3.3' services: app: image: fireflyiii/core:latest hostname: app container_name: firefly_iii_core networks: - firefly restart: always volumes: - firefly_iii_upload:/var/www/html/storage/upload env_file: .env ports: - '7500:8080' depends_on: - db2 db2: image: mariadb:lts hostname: db2 container_name: firefly_iii_db networks: - firefly restart: always env_file: .env volumes: - firefly_iii_db:/var/lib/mysql cron: # # To make this work, set STATIC_CRON_TOKEN in your .env file or as an environment variable and replace REPLACEME below # The STATIC_CRON_TOKEN must be *exactly* 32 characters long # image: alpine container_name: firefly_iii_cron restart: always command: sh -c "echo \"0 3 * * * wget -qO- http://app:7500/api/v1/cron/STATIC_CRON_TOKEN\" | crontab - && crond -f -L /dev/stdout" networks: - firefly volumes: firefly_iii_upload: firefly_iii_db: networks: firefly: driver: bridge env file APP_ENV=local APP_DEBUG=true APP_KEY=<key> TZ=America/Los_Angeles MARIADB_RANDOM_ROOT_PASSWORD=true MYSQL_RANDOM_ROOT_PASSWORD=true DB_CONNECTION=mysql DB_HOST=db DB_PORT=3306 DB_DATABASE=firefly2 DB_USERNAME=firefly_user DB_PASSWORD=<pwd> STATIC_CRON_TOKEN=<token> but still getting this error on UI page: Could not poll the database: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed: Name or service not known (Connection: mysql, SQL: select `id`, `name`, `data` from `configuration` where `name` = is_demo_site and `configuration`.`deleted_at` is null limit 1) in logs (multilple similar errors) [previous exception] [object] (PDOException(code: 0): PDO::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:65) DB pod is running, can log into it. what am i missing?
-
[Support] MattFaz Repo
I am having similar issue with a new setup: This is the error: But during the setup the database has timeout and then show "DB is up" wait-for-it.sh: timeout occurred after waiting 60 seconds for fireflydb:3306
-
[BUIILD HELP] Choosing right CPU and RAM
The other system will not just have plex but other docker services as well. That is why checking options if it makes sense to just do one system or two.
-
[BUIILD HELP] Choosing right CPU and RAM
I am planning to build a NAS with unraid which will have 2x14, 2x8 TB, for now. This NAS will be a standalone and act as NAS without Plex or any other services. I want to have another system working as the main server. I currently have few optoins at my disposal and was wondering what would be the best use of current resources. Some are already built systems and some need to be built. Expand-ability: slowly but not sure to what storage. Power consumption: Preferred low, as it might be idle 70% at least for the first year. Option1 (Preferred option): i5-2400, 8GB (not expandable) ram as NAS and i5-8500T, 16GB as the main server Option2: i3-10105F, xGB (need to be built) and i5-8500T, 16GB - either can be used for either purpose Option3: i7-6700, xGB (need to be built) and i5-8500T, 16GB - either can be used for either purpose Option4: Use either of the above systems to do the whole server in one massive system, which has all the HDD's and the main server. Also, have a 1060, 6GB nvidia if that can be leveraged. As mentioned would prefer to use the existing builds but wondering if 2nd gen would be sufficient enough.