zkvvoob

So, I followed @JorgeB's advice and initiated a new data-rebuild process. That was 4 days ago. Three days in, the server started behaving weirdly, as in no sound from the drives reading/writing, even though the process was supposed to be under way. Then I lost external access to all the services I was running (Docker containers). I couldn't even reboot the server, neither from the button on the Dashboard, nor from terminal. That lead me to force a shutdown. Afterwards, I mounted the array and let the data-rebuild process to start again. I can hear the drives running now and when I last checked 3 hours ago, it showed 25.1% completing. However, at this point, 3 hours in, the numbers haven't changed (even though the disks are being written to/read from). Furthermore, I can't even download the diagnostics report: the process is stuck at sed -ri 's/^(share(Comment|ReadList|WriteList)=")[^"]+/\1.../' '/valinor-diagnostics-20231218-1420/shares/appdata.cfg' 2>/dev/null sed -ri 's/^(share(Comment|ReadList|WriteList)=")[^"]+/\1.../' '/valinor-diagnostics-20231218-1420/shares/b-----s.cfg' 2>/dev/null sed -ri 's/^(share(Comment|ReadList|WriteList)=")[^"]+/\1.../' '/valinor-diagnostics-20231218-1420/shares/d----r.cfg' 2>/dev/null I've replaced all SATA cables. What should I do here, please? Thank you! EDIT: the problems with the docker services began again – the drives stopped making a sound and all of my external applications are no longer accessible, the error being 504 gateway timeout.

All right, I'll come back in a couple of days... 😔 EDIT: Wait, I'm fairly certain I didn't reboot the server after the drive failed this morning. Here's what I did: last night I waited for the rebuild process to complete, rebooted then, made sure all Docker containers were up an running and went to sleep. This morning I noticed the drive had failed and stopped Nextcloud, then initiated a SMART test...

Hello all, A bit of background: I've been using Unraid (6.12.6) on my server with 3 16 TB Seagate drives in an array, with one of them used as parity, for the past 2-3 months. The drives are all formated to ZFS. One of the drives is used solely for storing Nextcloud data (Nextcloud itself is running in Docker, using the LinuxServer image, updated regularly). There is a bash script that is run every night that uses `rclone` to sync the contents of the individual users' folders to a remote NAS server. A couple of days ago, I woke up to an email from the server saying I asked on Discord and was told to try to rebuild the drive on itself, which I promptly did. Last night, a day and a half later, the process completed, I rebooted the server and everything looked in order once again. This morning I was greeted with the exact same email. The drive is marked with a red X and it says its contents are emulated. Here's an exerpt from the System log, which I thought might be relevant: https://pastebin.com/YSWCfj6F. I'm also attaching a diagnostics archive. For the time being, I've stopped Nextcloud altogether, so that nothing writes to the drive and I've left it to perfrom a long SMART test (results pending). Could someone please help me understand what's causing this problem and how to avoid it in the future? If you need additional information, I'd be happy to provide it. Thank you! valinor-diagnostics-20231214-1345.zip

Thank you very much, @scolcipitato for opening my eyes. The issue, for whatever reason, turned out to be the Invidious container (which I had created manually, if memory servers). Removing it from the terminal solved the Unraid indicator problem.

Here's a screenshot of the Firefox console. Does this help?

Hi guys, I really love the Folder View plugin. I've been using it for the past month or so and up until the latest version it worked all right. However, now the Docker page keeps showing the animated Unraid logo constantly and all the buttons are disabled. I've tested this in two browsers (Firefox and Brave), with and without cache and the result is the same. Do you know what's causing this and how to sort it out, please? Screen Recording 2023-11-04 at 10.15.11.mov EDIT: Rebooting the server didn't fix the issue.

Hello all, I'm new to Unraid, been testing it on my brand new server for the past 3 days. Last night I left Syncthing (installed from the CA) to copy files from my old server (both are at home, connected to the same network via cable). This morning, all attempts to access the web GUI failed with the message "Unable to connect". When I plugged in the monitor and keyboard, I could type in the console, so I managed to get some diagnostics (attaching here). I'm not an expert, but a quick glance at the syslog file showed me the following recurring error: Sep 22 21:15:30 VALINOR ntpd[13059]: bind(19) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use Sep 22 21:15:30 VALINOR ntpd[13059]: unable to create socket on lo (126) for 127.0.0.1#123 Sep 22 21:15:30 VALINOR ntpd[13059]: failed to init interface for address 127.0.0.1 and this Sep 22 21:20:30 VALINOR ntpd[13059]: bind(19) AF_INET 10.0.0.77#123 flags 0x19 failed: Address already in use Sep 22 21:20:30 VALINOR ntpd[13059]: unable to create socket on br0 (129) for 10.0.0.77#123 Sep 22 21:20:30 VALINOR ntpd[13059]: failed to init interface for address 10.0.0.77 I checked, even though I was sure, but there was no other device using this IP - it was assigned to the Unraid server. Could you help me understand what caused all this, so that I could avoid it happening in the future, please? Thank you! valinor-diagnostics-20230923-0920.zip