motoxnate

Thanks for the replies guys, I don't think a file is in use, because the disks do initially all spin down and then the one in question will spin back up in the next 1-15 minutes usually from what I've seen. I do have some plugins, but the only one disk related I believe is Disk Location which I discussed seeming to find a (temporary) fix for. I can try looking at the diagnostics, maybe that will help. I'm not very familiar with them.

I've spent a couple of days trying to pin down what is keeping my disks spinning all the time. I've done all the basic troubleshooting - dockers off, no VMs, etc. I did pin most of the issue on the Disk Location plugin (see post here). However after manually updating /etc/cron.d/root without those jobs, I still see something almost immediately wake up my main array disk after I spin it down. I have one main disk and one parity disk, and only the main array disk gets spun back up. Cache probably too, but I don't care about the SSDs. Using my little chatGPT script to trace back PIDs and PPIDs from lsof, I see the below repeatedly waking the disk at irregular intervals. The trace just brings me back to /usr/libexec/unraid/emhttpd and I don't know enough about the inner workings of Unraid to pull this thread further. I hope somebody may be able to help! \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete --- \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete --- \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete --- \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete --- \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete --- \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete --- \n--- Disk Activity Detected (Tracing PID 1905290) --- \nPID: 1905290 ============================= UID PID PPID C STIME TTY TIME CMD root 1905290 1905286 0 10:48 ? 00:00:00 /usr/sbin/smartctl -A /dev/sdb \nPID: 1905286 ============================= UID PID PPID C STIME TTY TIME CMD root 1905286 5058 0 10:48 ? 00:00:00 /usr/bin/php -q /usr/local/sbin/smartctl_type disk1 -A \nPID: 5058 ============================= UID PID PPID C STIME TTY TIME CMD root 5058 1 0 Aug20 ? 05:27:39 /usr/libexec/unraid/emhttpd \n--- Trace Complete ---

Hi, I have been having an issue recently where none of my Unraid HDDs will sleep anymore, adding ~25W of power draw at all times. I've been trying to monitor what is causing this and after disabling all Dockers, I've traced it back at least partially to the Disk Location plugin. I am using a small one-line script to trace PIDs and PPIDs after lsof -r 1 /dev/sd<xx> sees some disk activity. Here is an example trace back to a Disk Location cron job. \n--- Disk Activity Detected (Tracing PID 1839742) --- \nPID: 1839742 ============================= UID PID PPID C STIME TTY TIME CMD root 1839742 1836960 0 10:30 ? 00:00:00 smartctl -x --json --quietmode=silent /dev/sdb \nPID: 1836960 ============================= UID PID PPID C STIME TTY TIME CMD root 1836960 1836958 0 10:30 ? 00:00:00 php -f /usr/local/emhttp/plugins/disklocation/pages/cronjob.php start syslogread silent \nPID: 1836958 ============================= UID PID PPID C STIME TTY TIME CMD root 1836958 3685427 0 10:30 ? 00:00:00 /bin/sh -c php -f /usr/local/emhttp/plugins/disklocation/pages/cronjob.php start syslogread silent &> /dev/null \nPID: 3685427 ============================= UID PID PPID C STIME TTY TIME CMD root 3685427 1 0 Nov03 ? 00:00:01 /usr/sbin/crond \n--- Trace Complete ---I've tried manually editing /etc/cron.d/root to change the frequency of syslog reads and smartctl status commands, but the plugin seems to auto-revert these back to every 5 minutes... */5 * * * * Can we pretty please add something in the plugin configuration to change the frequency of these jobs so my disks can sleep? I appreciate any input or if anybody has found a workaround. Otherwise I may need to just remove the plugin.

This should be a very simple task but I have not been able to figure it out for the life of me. I have Immich, PostgreSQL_Immich, and Redis running on my Unraid server, all using Bridge mode for network. When I run like this and use the machine IP (lets say 10.0.0.xx for example) everything talks fine. Now I ran docker network create dockernet to create a docker only network for these to communicate, without using the host adapter and to keep things a little more secure. So using hosnames, I can see that the hostnames are resolved properly (lets say these are 172.0.0.xx) and the ports have not changed. But now Immich just CANT REACH POSTGRES??? Put it back to bridge and use the host IPs, no problem. I created the dockernet from the spaceinvader tutorial but it just won't work for me. Is there like one tiny detail I am missing here? I really appreciate any help at all.

SMB worked fine for quite a while and now I have no idea what is happening. Completely freezes Finder on my MacBook Pro and I can't access data in my shares. Any ideas would be greatly appreciated. Unraid System Log: Jan 3 03:40:01 Server root: Starting Mover Jan 3 03:40:01 Server root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.004803, 0] ../../lib/util/fault.c:173(smb_panic_log) Jan 3 07:49:29 Server smbd[20362]: =============================================================== Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.004841, 0] ../../lib/util/fault.c:174(smb_panic_log) Jan 3 07:49:29 Server smbd[20362]: INTERNAL ERROR: Signal 11: Segmentation fault in pid 20362 (4.17.12) Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.004855, 0] ../../lib/util/fault.c:178(smb_panic_log) Jan 3 07:49:29 Server smbd[20362]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.004867, 0] ../../lib/util/fault.c:183(smb_panic_log) Jan 3 07:49:29 Server smbd[20362]: =============================================================== Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.004880, 0] ../../lib/util/fault.c:184(smb_panic_log) Jan 3 07:49:29 Server smbd[20362]: PANIC (pid 20362): Signal 11: Segmentation fault in 4.17.12 Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.005160, 0] ../../lib/util/fault.c:292(log_stack_trace) Jan 3 07:49:29 Server smbd[20362]: BACKTRACE: 30 stack frames: Jan 3 07:49:29 Server smbd[20362]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x1474e727064e] Jan 3 07:49:29 Server smbd[20362]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x1474e72708a9] Jan 3 07:49:29 Server smbd[20362]: #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x1474e7270937] Jan 3 07:49:29 Server smbd[20362]: #3 /lib64/libc.so.6(+0x3ae20) [0x1474e7051e20] Jan 3 07:49:29 Server smbd[20362]: #4 /usr/lib64/libsmbd-base-samba4.so(+0xc16dc) [0x1474e76c66dc] Jan 3 07:49:29 Server smbd[20362]: #5 /usr/lib64/libtalloc.so.2(+0x44df) [0x1474e721f4df] Jan 3 07:49:29 Server smbd[20362]: #6 /usr/lib64/libtalloc.so.2(+0x413e) [0x1474e721f13e] Jan 3 07:49:29 Server smbd[20362]: #7 /usr/lib64/libtalloc.so.2(+0x413e) [0x1474e721f13e] Jan 3 07:49:29 Server smbd[20362]: #8 /usr/lib64/libsmbd-base-samba4.so(+0xdcc45) [0x1474e76e1c45] Jan 3 07:49:29 Server smbd[20362]: #9 /usr/lib64/libsmbd-base-samba4.so(smbd_reinit_after_fork+0) [0x1474e76e2070] Jan 3 07:49:29 Server smbd[20362]: #10 /usr/lib64/libsmbd-shim-samba4.so(exit_server_cleanly+0x14) [0x1474e7275284] Jan 3 07:49:29 Server smbd[20362]: #11 /usr/lib64/libsmbd-base-samba4.so(smbd_server_connection_terminate_ex+0x4d6) [0x1474e76b7326] Jan 3 07:49:29 Server smbd[20362]: #12 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x1474e72328c1] Jan 3 07:49:29 Server smbd[20362]: #13 /usr/lib64/libtevent.so.0(+0xee07) [0x1474e7238e07] Jan 3 07:49:29 Server smbd[20362]: #14 /usr/lib64/libtevent.so.0(+0xcef7) [0x1474e7236ef7] Jan 3 07:49:29 Server smbd[20362]: #15 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x1474e7231ba1] Jan 3 07:49:29 Server smbd[20362]: #16 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x1474e7231e7b] Jan 3 07:49:29 Server smbd[20362]: #17 /usr/lib64/libtevent.so.0(+0xce97) [0x1474e7236e97] Jan 3 07:49:29 Server smbd[20362]: #18 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x1474e76a8be7] Jan 3 07:49:29 Server smbd[20362]: #19 /usr/sbin/smbd(+0xb090) [0x55fccc150090] Jan 3 07:49:29 Server smbd[20362]: #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x1474e72328c1] Jan 3 07:49:29 Server smbd[20362]: #21 /usr/lib64/libtevent.so.0(+0xee07) [0x1474e7238e07] Jan 3 07:49:29 Server smbd[20362]: #22 /usr/lib64/libtevent.so.0(+0xcef7) [0x1474e7236ef7] Jan 3 07:49:29 Server smbd[20362]: #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x1474e7231ba1] Jan 3 07:49:29 Server smbd[20362]: #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x1474e7231e7b] Jan 3 07:49:29 Server smbd[20362]: #25 /usr/lib64/libtevent.so.0(+0xce97) [0x1474e7236e97] Jan 3 07:49:29 Server smbd[20362]: #26 /usr/sbin/smbd(main+0x1489) [0x55fccc14d259] Jan 3 07:49:29 Server smbd[20362]: #27 /lib64/libc.so.6(+0x236b7) [0x1474e703a6b7] Jan 3 07:49:29 Server smbd[20362]: #28 /lib64/libc.so.6(__libc_start_main+0x85) [0x1474e703a775] Jan 3 07:49:29 Server smbd[20362]: #29 /usr/sbin/smbd(_start+0x21) [0x55fccc14db31] Jan 3 07:49:29 Server smbd[20362]: [2025/01/03 07:49:29.005370, 0] ../../source3/lib/dumpcore.c:315(dump_core) Jan 3 07:49:29 Server smbd[20362]: dumping core in /var/log/samba/cores/smbd Jan 3 07:49:29 Server smbd[20362]: Jan 3 07:49:30 Server emhttpd: read SMART /dev/sdb Jan 3 07:49:50 Server emhttpd: read SMART /dev/sdc There is nothing in /var/log/samba/cores/smbd, just an empty directory. On the Mac, after rebooting the Unraid server I ran: % smbutil statshares -a ================================================================================================== SHARE ATTRIBUTE TYPE VALUE ================================================================================================== Storage SERVER_NAME Server._smb._tcp.local USER_ID 501 SMB_NEGOTIATE SMBV_NEG_SMB2_ENABLED SMB_NEGOTIATE SMBV_NEG_SMB3_ENABLED SMB_VERSION SMB_3.1.1 SMB_ENCRYPT_ALGORITHMS AES_128_CCM_ENABLED SMB_ENCRYPT_ALGORITHMS AES_128_GCM_ENABLED SMB_ENCRYPT_ALGORITHMS AES_256_CCM_ENABLED SMB_ENCRYPT_ALGORITHMS AES_256_GCM_ENABLED SMB_CURR_ENCRYPT_ALGORITHM OFF SMB_SIGN_ALGORITHMS AES_128_CMAC_ENABLED SMB_SIGN_ALGORITHMS AES_128_GMAC_ENABLED SMB_CURR_SIGN_ALGORITHM AES_128_GMAC SMB_SHARE_TYPE DISK SIGNING_SUPPORTED TRUE EXTENDED_SECURITY_SUPPORTED TRUE UNIX_SUPPORT TRUE LARGE_FILE_SUPPORTED TRUE OS_X_SERVER TRUE FILE_LEASING_SUPPORTED TRUE MULTI_CREDIT_SUPPORTED TRUE SESSION_RECONNECT_TIME 0:0 SESSION_RECONNECT_COUNT 0 --------------------------------------------------------------------------------------------------

I am running 6.12.13 and I am pretty new to Unraid. I have had basically no speed issues and have populated ~3-4TB from my Macs so far... until today. For whatever reason my MacBook Pro running MacOS Sonoma 14.7.2 has slowed significantly. Certain folders are taking forever to populate in Finder while others load pretty quickly. Copying data seems to have slowed quite a bit as well and has actually completely stopped and failed to transfer a couple of times. If there are any logs or anything that would help, let me know and I will supply them.

Hey @djismgaming I am having an issue with this on Unraid 6.12.14 where on shutdown, the /var/run/mbpfan.pid file is not being removed, and the docker container fails to start when I bring Unraid back up. Not sure if you are able to look into this? Otherwise I can try but I don't know much about it yet.

Is anybody up to date with getting search working on Mac currently? I followed through this whole thread and I was able to get fscrawler installed and talking to elasticsearch 7.17.26 The problem I am having now is as soon as fscrawler starts to try to index, it fails looking for a folder that seems to be named after my job. I named my job "unraid_data_spotlight" as mentioned earlier in the thread, and the error says: 09:45:35,256 INFO [f.p.e.c.f.FsCrawlerImpl] Starting FS crawler 09:45:35,257 INFO [f.p.e.c.f.FsCrawlerImpl] FS crawler started in watch mode. It will run unless you stop it with CTRL+C. 09:45:35,479 INFO [f.p.e.c.f.c.ElasticsearchClient] Elasticsearch Client connected to a node running version 7.17.26 09:45:35,500 INFO [f.p.e.c.f.c.ElasticsearchClient] Elasticsearch Client connected to a node running version 7.17.26 09:45:36,095 INFO [f.p.e.c.f.FsParserAbstract] FS crawler started for [unraid_data_spotlight] for [/mnt/user] every [15m] 09:45:36,130 WARN [f.p.e.c.f.FsParserAbstract] Error while crawling /mnt/user: index unraid_data_spotlight_folder does not exist. 09:45:36,130 INFO [f.p.e.c.f.FsParserAbstract] Closing FS crawler file abstractor [FileAbstractorFile]. I am not sure where it thinks it is getting "unraid_data_spotlight_folder" from as there is no such share in /mnt/user Any help would be appreciated and maybe then we could put together a proper guide if it works. Thanks!