BKS

The parity check shows 10k+ errors. SMART test running now.

Sorry, I should have posted it in the original post along with logs. See SMART Logs below: ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 22776 hours (949 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 ff ff ff 4f 00 27d+15:23:24.705 READ FPDMA QUEUED 60 00 20 ff ff ff 4f 00 27d+15:23:24.704 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 27d+15:23:24.704 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 27d+15:23:24.704 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 27d+15:23:24.704 READ FPDMA QUEUED

Tried filesystem check and got the following output. I'm not sure whether I should attempt repair of the filesystem, disable the drive and emulate for now, or something else. The logs are redacted to some extent to make them smaller, but its representative of the types of logs. log.txt

I've attached my diagnostic files. I noticed a SMART error that appears to be a bad sector on Disk 1. I have a dual parity setup, BLAKE3 hash of all files, and a remote backup with backblaze, so I think I am well equipped to handle a bad sector. However, I'm not certain on next steps. Bad sector to me means potential lost files, so I'd want to restore. However, does unraid auto restore/emulate impacted files from parity when this happens? If not, is looking at the hash the only way to determine which files to restore? Second, I'm reading that a single bad sector may not mean an imminently failing drive, so my plan is to just watch that drive for now and see if more start to occur. Please correct me if I'm wrong in that assumption. server-diagnostics-20260426-0857.zip

Disabling docker did not fix it. I ran the filesystem check and repaired the corruption, now the issue has resolved. Thank you. Does presence of corruption indicate an issue with the HDD? All smart checks short/long passed without error. Wondering if I should consider replacing this drive or not. Thanks

I'm unable to delete an empty directory. I've tried restarting server, starting/stopping array, and the below. ls -l #within directory shows nothing rm -rf #as root rm: cannot remove 'restored_appdata_11-13-23/appdatarestore/photoprism/cache/thumbnails/3/f/a': Directory not empty I've also attempted to rm from the /mnt/disk# directly with no success. lsof shows no processes in use. Docker stopped doesn't fix it. Any guidance appreciated. Diagnostics attached. server-diagnostics-20260319-2146.zip

Yeah, it started happening with HA for me as well. This problem was the final straw that pushed me away from unraid as a homelab server. Strange problem that I could never figure out and community support from here and reddit/discord didn't help.

I've had this happen on several instances, but twice with my Immich container over the past week. Container is present and working fine, then overnight it seems to disappear. Containers are getting started/stopped by CA Backup plugin but otherwise should not be changing. Any thoughts on where to look for troubleshooting this? Unraid Pro 6.11.5

I've provisioned a new esphome device using USB and https://web.esphome.io, able to connect to the device directly with HTTP. After it is provisioned, I think it should be detected with ESPHome at that point, correct? No config installed on the device itself yet.

Trying to get ESPHome separated from my HA pi box. I installed the container through CA store, get to the web UI and no devices are shown. I'm able to get into the container console and ping the relevant devices and get a response, seems like network connectivity is there. Not sure if it should be bridge networking or host, have tried both, but can't get the (working in HA) esphome devices to show in the dashboard through the esphome unraid image. Any thoughts?

Attempting to use db-backup container to back up a mariadb server, both running as bridge mode in an unraid host. On running the backup command, I get an error that the MySQL/MariaDB server is not accessible. I can ping the IP address from the shell of that container though. Seems to be a networking issue but can't figure it out. Any tips here?

I use your node-red container, thank you for maintaining it. A few node plugins I'd like to use give me errors when I try to add to the node-red palette. Logs show (excerpt): today at 1:54:50 PMnpm ERR! npm ERR! Please make sure you are using a supported platform and node version. If you today at 1:54:50 PMnpm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your today at 1:54:50 PMnpm ERR! npm ERR! build environment-- today at 1:54:50 PMnpm ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp today at 1:54:50 PMnpm ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` today at 1:54:50 PMnpm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` today at 1:54:50 PMnpm ERR! today at 1:54:50 PMnpm ERR! npm ERR! A complete log of this run can be found in: today at 1:54:50 PMnpm ERR! npm ERR! /data/.npm/_logs/2022-08-14T17_54_38_092Z-debug-0.log Looks like I need to get some packages installed for compiling python code. Is this not included in the container by default? Any recommendations on best way for me to add it? Thanks!

Actually, nevermind. Device is less than a month old, I'm just going to take the easy way out and replace it while it's within the window!

I got an error randomly a couple of days ago: Tower: Warning [TOWER] - Cache pool BTRFS missing device(s) Unraid Cache disk message Warning [TOWER] - Cache pool BTRFS missing device(s) 1657356301 Samsung_SSD_970_EVO_Plus_1TB_S6S1Nxxx (nvme0n1) warning. I logged into web UI and all lights were green, thought it may have been a momentary issue. I then noticed that my /var/log was at 100% and dug into why. I had tons of BRTFS errors related to that drive. I restarted the server and now am getting the message that that drive is missing. Diagnostics attached. It's an M2 slot device, no replacing cables. What other steps can I try? The drive is less than 1 month old.

6.10.3 -- Removing that parameter worked! Thanks