yukij

I’ve removed it now and triggered the mover again. Let’s see if anything happens. And it's works. Thx everyone/

Yes, I saw it, I just didn’t figure it out right away. I set it to "10GB", which seems to be correct. Thanks.

What values am I supposed to use here? "10" - does this mean 10 MB? "10Mb" - does this mean 10 MB? "10Gb" - does this mean 10 GB? I’m not quite sure what format these values are expected to be in.

homenas-diagnostics-20260110-0133.zip

Hello everyone. I’ve run into an issue and would appreciate some help. I have a share accessible via SMB. The primary storage is set to cache, with array as secondary storage, and I’m facing two problems: 1.When the cache disk becomes full, writes stop completely with a “not enough space” error. Logically, I would expect the data to continue writing to the array instead of the cache. 2.When I try to start the mover manually, it completely ignores the command, nothing happens at all. Any insights would be appreciated. Unraid version 7.2.3

Now everything works. Thank you very much.

Hi everyone, I’m having an issue with my Unraid server and hope someone can help me figure this out. Setup: .Unraid server running the latest stable version. .Plex is installed in Docker and assigned to a static IP via br0 interface: 192.168.1.30 .Other Docker containers (e.g., Jellyfin, qBittorrent, etc.) are on the bridge network with the host IP 192.168.1.25 .I have port forwarding set up on my router (Mikrotik AX3) to expose 192.168.1.30 to the internet — Plex is accessible externally and works fine. .Nginx is installed on the Unraid server (host or Docker, I've tried both) and is meant to reverse proxy traffic to Plex using a domain name. Port forwarding is set up on my Mikrotik AX3 router, and Plex is accessible from the internet. However, Nginx running on Unraid can’t reach 192.168.1.30, so reverse proxying via domain fails (502 Bad Gateway or timeout). From Unraid’s terminal, ping 192.168.1.30 doesn’t work, though the IP is accessible from other devices on the LAN. It feels like Unraid treats the br 0 container as a separate physical device. Do I need to enable some kind of multicast or proxy ARP, or use a different approach to make internal communication possible between the host and the container on br0?

I did according to this instruction, yes. After rebuilding parity (after 8 hours), I will check all the files. I think everything will be OK. Thanks

"rebuild on top" - is it to restore from parity to the same "broken" disk? I changed the sata cable, reconnected the disk and started recovery from parity (checked the emulated files, everything is fine). Is that right?

A problem with the hard drive. The disk is new, it worked for about a month, after which a small number of UDMA CRC errors appeared (10-15 within 2-3 days). After that, unraid reported: Disk 1 - ST8000NM017B-2TJ103_WWZ17Z1T (sd) (errors 513). The question is what should I do, since according to the analysis the smart disk is in excellent condition. How can I correctly determine the cause of this error? homenas-smart-20231101-1330.zip