Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid-arr

Members
  • Joined

Everything posted by Unraid-arr

  1. Having the same issue, everything was stable past few years. I'll look into the solutions above. For me the image goes up close to 40Gb. crazy!
  2. So, this happened again today and I narrowed it down to Plex. I have to see what's going on. Plex has had same configuration since ages and nothing has changed except the new updates. Today the Docker image bloated up to 78GB and when I force recreated the container using the force update command in WebUI. The image went down to 40-ish GB. So, that is narrowed down. I am waiting for plex to bloat up again, so I can investigate inside the container what's going on. In case anyone wanders here, I am using the linuxserver/plex image. Cheers!
  3. @jj9987 - Any implications of this for regular users? https://hub.docker.com/r/bitnami/redis/#%EF%B8%8F-important-notice-upcoming-changes-to-the-bitnami-catalog GitHubUpcoming changes to the Bitnami catalog (effective August...ImportantAfter evaluating the impact and community feedback, the Bitnami team has postponed the deletion of the Bitnami public catalog (docker.io/bitnami) until September 29th to give users more ti...Specifically this -> https://github.com/bitnami/containers/issues/83267#issuecomment-3296097823 Thanks
  4. @JorgeB - so the first thing I did was to force update (force recreate) all the containers and the docker image size dropped from 80 GiB to 41.1GiB. Exactly what I hoped for, I will check the difference in container sizes next and report on it.
  5. @JorgeB This is the syslog-previous file until restart after the last notification I received that Docker image disk utilization is 80%. Looks like the docker system crashed around 20 mins after that notification. Upon restart some containers are not starting. Sep 16 12:27:04 Zeus sSMTP[3904962]: Sent mail for [email protected] (221 2.0.0 closing connection ca18e2360f4ac-88f2d69e080sm534111439f.8 - gsmtp) uid=0 username=root outbytes=840 Sep 16 12:28:54 Zeus smbd[3912693]: [2025/09/16 12:28:54.445304, 0] ../../lib/param/loadparm.c:1960(lpcfg_do_service_parameter) Sep 16 12:28:54 Zeus smbd[3912693]: Global parameter ntlm auth found in service section! Sep 16 12:28:54 Zeus smbd[3912693]: [2025/09/16 12:28:54.569304, 0] ../../lib/param/loadparm.c:1960(lpcfg_do_service_parameter) Sep 16 12:28:54 Zeus smbd[3912693]: Global parameter ntlm auth found in service section! Sep 16 12:30:16 Zeus emhttpd: read SMART /dev/sdt Sep 16 12:30:16 Zeus emhttpd: read SMART /dev/sdu Sep 16 12:30:16 Zeus emhttpd: read SMART /dev/sdr Sep 16 12:30:16 Zeus emhttpd: read SMART /dev/sds Sep 16 12:32:23 Zeus emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/temp/script Sep 16 12:35:41 Zeus flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdm Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdk Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdy Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdw Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdz Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdx Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdf Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdv Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdn Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdq Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdo Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdl Sep 16 12:42:19 Zeus emhttpd: read SMART /dev/sdi Sep 16 12:44:11 Zeus kernel: br-3a0cd0aea84a: port 26(veth7d53c42) entered disabled state Sep 16 12:44:12 Zeus kernel: veth3f05c46: renamed from eth0 Sep 16 12:44:12 Zeus kernel: br-3a0cd0aea84a: port 26(veth7d53c42) entered disabled state Sep 16 12:44:12 Zeus kernel: veth7d53c42 (unregistering): left allmulticast mode Sep 16 12:44:12 Zeus kernel: veth7d53c42 (unregistering): left promiscuous mode Sep 16 12:44:12 Zeus kernel: br-3a0cd0aea84a: port 26(veth7d53c42) entered disabled state Sep 16 12:44:13 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered blocking state Sep 16 12:44:13 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered disabled state Sep 16 12:44:13 Zeus kernel: vethaecb6a6: entered allmulticast mode Sep 16 12:44:13 Zeus kernel: vethaecb6a6: entered promiscuous mode Sep 16 12:44:16 Zeus kernel: eth0: renamed from veth7bd4bac Sep 16 12:44:16 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered blocking state Sep 16 12:44:16 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered forwarding state Sep 16 12:49:56 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered disabled state Sep 16 12:49:56 Zeus kernel: veth7bd4bac: renamed from eth0 Sep 16 12:49:56 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered disabled state Sep 16 12:49:56 Zeus kernel: vethaecb6a6 (unregistering): left allmulticast mode Sep 16 12:49:56 Zeus kernel: vethaecb6a6 (unregistering): left promiscuous mode Sep 16 12:49:56 Zeus kernel: br-3a0cd0aea84a: port 26(vethaecb6a6) entered disabled state Sep 16 12:49:57 Zeus kernel: br-3a0cd0aea84a: port 26(vethd281101) entered blocking state Sep 16 12:49:57 Zeus kernel: br-3a0cd0aea84a: port 26(vethd281101) entered disabled state Sep 16 12:49:57 Zeus kernel: vethd281101: entered allmulticast mode Sep 16 12:49:57 Zeus kernel: vethd281101: entered promiscuous mode Sep 16 12:49:59 Zeus kernel: eth0: renamed from veth484891a Sep 16 12:49:59 Zeus kernel: br-3a0cd0aea84a: port 26(vethd281101) entered blocking state Sep 16 12:49:59 Zeus kernel: br-3a0cd0aea84a: port 26(vethd281101) entered forwarding state Sep 16 12:50:33 Zeus monitor_nchan: Stop running nchan processes Sep 16 12:51:01 Zeus php-fpm[18063]: [WARNING] [pool www] child 4006070 exited on signal 9 (SIGKILL) after 16.275179 seconds from start Sep 16 12:51:03 Zeus php-fpm[18063]: [WARNING] [pool www] child 4006071 exited on signal 9 (SIGKILL) after 18.721749 seconds from start Sep 16 12:51:04 Zeus php-fpm[18063]: [WARNING] [pool www] child 4006118 exited on signal 9 (SIGKILL) after 16.517430 seconds from start Sep 16 12:51:07 Zeus kernel: ------------[ cut here ]------------ Sep 16 12:51:07 Zeus kernel: BTRFS: Transaction aborted (error -28) Sep 16 12:51:07 Zeus kernel: WARNING: CPU: 29 PID: 3794453 at fs/btrfs/free-space-tree.c:865 remove_from_free_space_tree+0x2b2/0x300 Sep 16 12:51:07 Zeus kernel: Modules linked in: cmac cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver xt_connmark xt_comment iptable_raw xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net vhost vhost_iotlb tap nf_conntrack_netlink xt_nat veth ipvlan xt_conntrack xfrm_user xt_addrtype nvidia_uvm(PO) md_mod xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat ntfs3 tcp_diag inet_diag ipmi_devintf iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc ixgbe xfrm_algo mdio igb zfs(PO) spl(O) ses enclosure nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif nvidia(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_ttm_helper sha256_ssse3 ttm sha1_ssse3 mgag200 Sep 16 12:51:07 Zeus kernel: aesni_intel video drm_shmem_helper crypto_simd drm_kms_helper cryptd rapl intel_cstate drm mpt3sas intel_uncore raid_class nvme scsi_transport_sas sr_mod cdrom mei_me agpgart backlight i2c_algo_bit input_leds nvme_core joydev led_class mei i2c_core ipmi_si wmi acpi_power_meter acpi_pad acpi_ipmi button [last unloaded: xfrm_algo] Sep 16 12:51:07 Zeus kernel: CPU: 29 UID: 0 PID: 3794453 Comm: kworker/u193:0 Tainted: P O 6.12.24-Unraid #1 Sep 16 12:51:07 Zeus kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Sep 16 12:51:07 Zeus kernel: Hardware name: Dell Inc. PowerEdge R720xd/0X3D66, BIOS 2.9.0 12/06/2019 Sep 16 12:51:07 Zeus kernel: Workqueue: events_unbound btrfs_async_reclaim_metadata_space Sep 16 12:51:07 Zeus kernel: RIP: 0010:remove_from_free_space_tree+0x2b2/0x300 Sep 16 12:51:07 Zeus kernel: Code: c0 75 18 48 8b 7d 60 44 89 f2 48 c7 c6 cb 8d 2d 82 e8 d2 98 5d 00 41 b0 01 eb 13 44 89 f6 48 c7 c7 ec 8d 2d 82 e8 7e e8 b2 ff <0f> 0b eb e8 41 83 e0 01 44 89 f1 ba 61 03 00 00 48 c7 c6 90 36 e5 Sep 16 12:51:07 Zeus kernel: RSP: 0000:ffffc90031947a48 EFLAGS: 00010282 Sep 16 12:51:07 Zeus kernel: RAX: 0000000000000000 RBX: ffff88981ba05a80 RCX: 0000000000000027 Sep 16 12:51:07 Zeus kernel: RDX: 0000000000000002 RSI: ffffffff823430e7 RDI: 00000000ffffffff Sep 16 12:51:07 Zeus kernel: RBP: ffff8881cf3127e0 R08: 0000000000000000 R09: ffffffff82da6e70 Sep 16 12:51:07 Zeus kernel: R10: 00001fffffffffff R11: 000000000000002e R12: 00000021736cc000 Sep 16 12:51:07 Zeus kernel: R13: ffff8894272b2c00 R14: 00000000ffffffe4 R15: 00000021736c8000 Sep 16 12:51:07 Zeus kernel: FS: 0000000000000000(0000) GS:ffff889fffb80000(0000) knlGS:0000000000000000 Sep 16 12:51:07 Zeus kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 16 12:51:07 Zeus kernel: CR2: 0000147f085988c8 CR3: 0000000002418001 CR4: 00000000001726f0 Sep 16 12:51:07 Zeus kernel: Call Trace: Sep 16 12:51:07 Zeus kernel: <TASK> Sep 16 12:51:07 Zeus kernel: alloc_reserved_extent+0x1f/0xb0 Sep 16 12:51:07 Zeus kernel: __btrfs_run_delayed_refs+0x589/0xc90 Sep 16 12:51:07 Zeus kernel: ? __traceiter_sched_cpu_capacity_tp+0x11/0x40 Sep 16 12:51:07 Zeus kernel: btrfs_run_delayed_refs+0x4e/0x110 Sep 16 12:51:07 Zeus kernel: btrfs_write_dirty_block_groups+0x11e/0x300 Sep 16 12:51:07 Zeus kernel: ? preempt_latency_start+0x2b/0x50 Sep 16 12:51:07 Zeus kernel: ? _raw_spin_lock+0x13/0x20 Sep 16 12:51:07 Zeus kernel: ? _raw_spin_unlock+0x14/0x30 Sep 16 12:51:07 Zeus kernel: commit_cowonly_roots+0x1ca/0x240 Sep 16 12:51:07 Zeus kernel: btrfs_commit_transaction+0x486/0xae0 Sep 16 12:51:07 Zeus kernel: flush_space+0x9d/0x460 Sep 16 12:51:07 Zeus kernel: ? _raw_spin_lock+0x13/0x20 Sep 16 12:51:07 Zeus kernel: ? _raw_spin_unlock+0x14/0x30 Sep 16 12:51:07 Zeus kernel: ? btrfs_get_alloc_profile+0xdf/0x180 Sep 16 12:51:07 Zeus kernel: ? calc_effective_data_chunk_size+0x13/0x50 Sep 16 12:51:07 Zeus kernel: ? calc_available_free_space.isra.0+0x54/0x80 Sep 16 12:51:07 Zeus kernel: btrfs_async_reclaim_metadata_space+0x89/0x180 Sep 16 12:51:07 Zeus kernel: process_scheduled_works+0x19c/0x2c0 Sep 16 12:51:07 Zeus kernel: worker_thread+0x13b/0x1c0 Sep 16 12:51:07 Zeus kernel: ? __pfx_worker_thread+0x10/0x10 Sep 16 12:51:07 Zeus kernel: kthread+0xef/0x100 Sep 16 12:51:07 Zeus kernel: ? __pfx_kthread+0x10/0x10 Sep 16 12:51:07 Zeus kernel: ret_from_fork+0x24/0x40 Sep 16 12:51:07 Zeus kernel: ? __pfx_kthread+0x10/0x10 Sep 16 12:51:07 Zeus kernel: ret_from_fork_asm+0x1a/0x30 Sep 16 12:51:07 Zeus kernel: </TASK> Sep 16 12:51:07 Zeus kernel: ---[ end trace 0000000000000000 ]--- Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): dumping space info: Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): space_info DATA has 21736722432 free, is not full Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): space_info total=67654123520, used=45917364224, pinned=8192, reserved=0, may_use=28672, readonly=0 zone_unusable=0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): space_info METADATA has 0 free, is full Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): space_info total=19825950720, used=19608027136, pinned=208863232, reserved=8994816, may_use=0, readonly=65536 zone_unusable=0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): space_info SYSTEM has 33538048 free, is not full Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): space_info total=33554432, used=16384, pinned=0, reserved=0, may_use=0, readonly=0 zone_unusable=0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): global_block_rsv: size 204816384 reserved 0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): trans_block_rsv: size 0 reserved 0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): chunk_block_rsv: size 0 reserved 0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): delayed_block_rsv: size 0 reserved 0 Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state A): delayed_refs_rsv: size 326238208 reserved 0 Sep 16 12:51:07 Zeus kernel: BTRFS: error (device loop2 state A) in remove_from_free_space_tree:865: errno=-28 No space left Sep 16 12:51:07 Zeus kernel: BTRFS info (device loop2 state EA): forced readonly Sep 16 12:51:07 Zeus kernel: BTRFS error (device loop2 state EA): failed to run delayed ref for logical 143670411264 num_bytes 16384 type 176 action 1 ref_mod 1: -28 Sep 16 12:51:07 Zeus kernel: BTRFS: error (device loop2 state EA) in btrfs_run_delayed_refs:2215: errno=-28 No space left Sep 16 12:51:07 Zeus kernel: BTRFS warning (device loop2 state EA): Skipping commit of aborted transaction. Sep 16 12:51:07 Zeus kernel: BTRFS: error (device loop2 state EA) in cleanup_transaction:2025: errno=-28 No space left Sep 16 12:51:13 Zeus emhttpd: read SMART /dev/sdh Sep 16 12:51:13 Zeus emhttpd: read SMART /dev/sdd Sep 16 12:51:13 Zeus emhttpd: read SMART /dev/sde
  6. I cant figure out what container is causing this.
  7. Yes as I mentioned before, before the crash happens the docker image starts filling up. I know this because I get notifications. I got them today as well. trying to login from kvm is not possible. I was not in safe mode because the server was started just before I created this thread.
  8. So, the server crashed today. I am restarting now. Here, is the screen stuck at the error. I will try to get syslog from flash drive once it boots up.
  9. While the verify_install issue has been considered and a potential fix pushed. GitHubfix: false positive on verify_install script being extern...Introduced a new test script for shell detection logic in verify_install.sh. Updated the package.json to include a new test command for shell detection. Enhanced the verify_install.sh script to acc...I am still not sure why NZB360 is unable to pull docker containers without errors. There has been no instability since I started this post. Surprised myself and will continue to monitor. I have to wait and see the performance overall. Thanks
  10. I see this update was pushed today.https://github.com/unraid/api/pull/1704 We will see the performance and report again. Thanks
  11. Further updates are in this post if anyone comes in the future. Thanks
  12. @Kameleon83 — Are you willing to provide a link to the FOSS GitHub repo for this project? I think many folks here have asked for it. Thanks
  13. Why is the script telling me it is the default after naming itself as default. I am confused here. root@Tower:~# grep -rnI "verify_install" /boot /boot/config/plugins/dynamix.unraid.net.plg:465:if [ -x "$SCRIPTS_DIR/verify_install.sh" ]; then /boot/config/plugins/dynamix.unraid.net.plg:467: echo "Running verify_install.sh" /boot/config/plugins/dynamix.unraid.net.plg:469: "$SCRIPTS_DIR/verify_install.sh" /boot/config/plugins/dynamix.unraid.net.plg:471: echo "ERROR: verify_install.sh not found or not executable" /boot/config/plugins/dynamix.unraid.net.plg:472: echo "ERROR: verify_install.sh not found or not executable"Here is the script location - /usr/local/share/dynamix.unraid.net/install/scripts/verify_install.sh (attached) [Line 17 onwards] verify_install.sh root@Tower:~# find / -path /mnt -prune -o -type f -iname "*verify_install*" /usr/local/share/dynamix.unraid.net/install/scripts/verify_install.sh
  14. Same for me root@Tower:~# grep -rnI "verify_install" /boot /boot/config/plugins/dynamix.unraid.net.plg:465:if [ -x "$SCRIPTS_DIR/verify_install.sh" ]; then /boot/config/plugins/dynamix.unraid.net.plg:467: echo "Running verify_install.sh" /boot/config/plugins/dynamix.unraid.net.plg:469: "$SCRIPTS_DIR/verify_install.sh" /boot/config/plugins/dynamix.unraid.net.plg:471: echo "ERROR: verify_install.sh not found or not executable" /boot/config/plugins/dynamix.unraid.net.plg:472: echo "ERROR: verify_install.sh not found or not executable"Here is the script location - /usr/local/share/dynamix.unraid.net/install/scripts/verify_install.sh (attached) [Line 17 onwards] verify_install.sh
  15. @JorgeB - thanks for the recommendation. I couldn't get anything in the logs because server would freeze and had to be restarted. Last notifications I would get before that happens is that docker image is like 79% full. Which is nowhere near completely full. I increased the size of docker image from 80 GB to 100 GB, and it has not filled up more. Now it is at 69%, but the system still freezes and has to be cold reset. Additionally, I have since enabled syslog to mirror on flash and that is working. But it is NOT saving a copy on the selected local folder (downloads). If it happens again, I will post logs as you mentioned. I have had major issues with API in the past. Where Web-UI would just refuse to work after cold server boot. I just deleted the connect plugin to resolve that. I had to reinstall the plugin because of NZB360 app. The API is still bad and an unoptimized mess. Takes ages to load containers/VMs and shows no UPS info from NUT plugin. Giving the error on boot with no explanation for which I made this post. Have to keep restarting the api via unraid-api restart command in the terminal every time after server start and after some time just to keep it available. Thanks.
  16. Following for a clarification from staff. There is nothing on the web to figure this out. Thanks
  17. My server keeps freezing and I have to hard restart. Not sure what is going on. It's a nightmare.
  18. Need help fixing this issue. If someone knows from UnRaid team. My system has been unresponsive every 12 hours or so. I do have multiple user scripts that run frequently. I restarted the system for Nth time and realized this. Maybe it is connected to the situation at hand. Unsupported shell detected: verify _ install . Unraid scripts require bash but your systen is configured to use verify _ install. for scripts. This can cause infinite loops or unexpected behavior uhen Unraid scripts execute. Please configure verify _ install. to only activate for interactive shells. Add this check to your ~/.bachrc or /etc/profile before starting verify_install. : [[ $- ==*i* ]] & exec verify _ install. This ensures verify _ install. only starts for interactive sessions, not scripts .Picture taken from iDRAC, sorry for quality. Here are the packages installing from /boot/extra folder on boot. Using un-get for these. root@Tower:/boot/extra# ls -lsah total 55M 8.0K drwx------ 2 root root 8.0K Sep 9 14:31 ./ 8.0K drwx------ 12 root root 8.0K Dec 31 1969 ../ 1.5M -rw------- 1 root root 1.5M May 19 09:33 7zip-24.09-x86_64-1_SBo.tgz 5.2M -rw------- 1 root root 5.2M Apr 29 12:08 exiftool-13.29-x86_64-1cf.txz 1.2M -rw------- 1 root root 1.2M May 19 09:35 fastfetch-2.34.0-x86_64-1_SBo.tgz 40K -rw------- 1 root root 40K May 3 2024 iftop-1.0pre4-x86_64-5.txz 2.5M -rw------- 1 root root 2.5M May 23 21:25 ipmitool-1.8.19-x86_64-2_SBo.tgz 1.3M -rw------- 1 root root 1.3M Oct 3 2022 p7zip-16.02-x86_64-1sl.txz 120K -rw------- 1 root root 119K Apr 19 14:09 python-packaging-25.0-x86_64-1.txz 2.3M -rw------- 1 root root 2.3M May 3 14:42 python-pip-25.1.1-x86_64-1.txz 1.7M -rw------- 1 root root 1.7M May 16 13:24 python-setuptools-80.7.1-x86_64-1.txz 13M -rw------- 1 root root 13M Oct 3 2022 python2-2.7.18-x86_64-4.txz 25M -rw------- 1 root root 25M Apr 9 14:27 python3-3.12.10-x86_64-1.txz 16K -rw------- 1 root root 13K May 19 09:41 python3-pkgconfig-1.5.5-x86_64-1_SBo.tgz 384K -rw------- 1 root root 380K May 19 09:44 rar-5.5.0-x86_64-1_SBo.tgz 1.7M -rw------- 1 root root 1.7M Oct 3 2022 sg3_utils-1.47.tgz 264K -rw------- 1 root root 262K Mar 24 08:40 unrar-7.1.6-x86_64-1cf.txz Thanks in advance!
  19. @ich777 - Thanks for your awesome work on this plugin. Quick question - I am using P2000 for Plex and Immich dockers. What branch should I remain on - it is very confusing and after reading a few comments above I am more confused by legacy and proprietary drivers. Cheers!
  20. Thanks this helped me today. Clear and concise answer in the comment by @skywalker6705. Helped me today when I was scratching my head trying to remember the UMASK thing from a while back. Thanks a bunch internet stranger.
  21. Thanks @elibosley , I appreciate the response. However, I'm not brave enough to tinker with my production server on a daily. I need it to be stable. I will encourage others to do that, as I unfortunately don't have a replica server to test this on. The only feature I was taking advantage of, albeit somewhat was flash backup. I still use a local app that does it for me on a secondary NAS, so it's not really critical for me. Thanks and have a good day!
  22. Hello everyone, thanks for keeping this thread alive. For some reason there has been no definite answer from Limetech on a fix. In the meanwhile I have just removed the plugin since this happened. I see no benefit myself using this benefit. It was a nice to have plugin with automatic backups and stuff, however the anxiety of server crashing on reboot is a no-go for me. If someone needs this personally. You can also try to nudge Unraid team :) Thanks
  23. Thanks @Frank1940 for the response, much appreciated. I was not sure where you wanted me to post. It was confusing for me. I like this explanation, and thanks for the details.
  24. @Mainfrezzer — I liked the read-check scheduling, I am not sure why this functionality is removed. It gives me a choice to schedule the read checks per my schedule. I am not sure if you are trying to be snarky but, It is not obvious as parity check doubled as read-checks if parity drive is not present. I don't need a parity drive for my pool, so I don't have it. Also, if unraid doesn't want people to do a read-check on a schedule remove the colored history section on main page which turns red if you don't do parity/read-check for 90 days. @itimpi — thanks for the response, you worded it better than me. I agree with everything you said. @MowMdown — yes, FCP can be updated to have a better language. But importantly I would like this functionality back to do scheduled read-checks. Thanks everyone!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.