-
Parity-Check log entries
So should I reboot and do the check again? Or is it enough to do the check again without rebooting? Do these 5 errors cause data loss or wrong written data?
-
Parity-Check log entries
Oh, yes… On the main page, 5 errors found. Why I need these notifications, when they can be wrong? And what should I do now? EDIT: Could it be because I connected an HDD from the array to my SATA PCIE ASM1166 card for a day or so? To see if the controller is working? It was about a week ago. So now the HDD is connected normally.
-
I/O error BTRFS info (device sdh1): read error
Booth SSDs were defect.
-
Parity-Check log entries
Hello, tonight the Parity-Check ran, and it finished with 0 errors. But why I have these entries in my log? Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565768 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565776 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565784 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565792 Jan 5 04:46:08 SauerRaid kernel: md: recovery thread: P incorrect, sector=1565565800 Jan 5 05:26:05 SauerRaid emhttpd: spinning down /dev/sdb Jan 5 09:16:56 SauerRaid kernel: md: sync done. time=22615sec Jan 5 09:16:56 SauerRaid kernel: md: recovery thread: exit status: 0 Unraid Parity-Check: 05-01-2025 03:01 Notice [SAUERRAID] - Parity-Check started Size: 3 TB Unraid Parity-Check: 05-01-2025 09:17 Notice [SAUERRAID] - Parity-Check finished (0 errors) Duration: 5 hours, 46 minutes, 42 seconds. Average speed: 144.2 MB/s
-
Slow Apps and Docker Tab
I prepared a new usb stick with UNRAID and transfered some essential config files and plugins. The problem is now fixed. It takes about 5 minutes to check for docker updates, but it works now and not fails with 500 error
-
Slow Apps and Docker Tab
I have some from LinuxServer, but all containers start with linuxserver/. And I have some from GitHub Packages they all start with ghcr.io/. Would it be wrong when it starts with lscr.io/linuxserver/?
-
I/O error BTRFS info (device sdh1): read error
Unfortunately, I don't have any free SATA ports on the mainboard 🥲 Which SATA PCIe card you can suggest? I would try to switch it.
-
I/O error BTRFS info (device sdh1): read error
sauerraid-diagnostics-20240703-1158.zip
-
Slow Apps and Docker Tab
I use Cloudflare DNS. But when I redo the flash drive what is about this problem?
-
Slow Apps and Docker Tab
The slow apps tab randomly disappeared after an Unraid update, but the DockerUpdate check still does not work. For this I have opened a new topic but forgot to close the old one.
-
Slow Apps and Docker Tab
But if no hard disc configuration is selected, the array will not run. And therefore neither will the Docker. Or am I misunderstanding this? And so I can't even check whether the Docker update service is working.
-
Slow Apps and Docker Tab
Okay thx, but when I will start the Unraid server with a new stick. Nothing get messed up? Like the drive configuration?
-
Slow Apps and Docker Tab
How I should do that? I understand that I should install a new Unraid image on the stick. But which files I should save, so that nothing gets broken?
-
DockerUpdate Check fails
When I search for docker updates, it spins endlessly and at Chrome developer tools you see that it fails with 500 error.
-
I/O error BTRFS info (device sdh1): read error
Hello since several months my logs get flooded by I/O errors. The errors coming from the two cache drives (sdh, sdg), which are connected to a SATA PCIE ASM1166 controller. I already changed the drives, cables and ports. I also deleted and reconfigured the cache and upgraded the firmware of the ASM1166 controller. It would be nice if anyone could please help me because I don't understand from what the errors are caused. parts_of_log.txt