WubbaLubbaDubDub

Ah understood. Thank you for clarifying. Unfortunately, in my case, the drive that was being replaced was dead. I do have a couple more to replace so I will keep the old drives for a while in the event I need to recover from them. I was initially hesitant about running the parity check for that exact reason you listed of introducing errors. If the data were more important, I would recommend verifying or correcting errors before doing the parity check. In this case, the data being recovered is on my media server. The importance of the server running in my specific situation was more crucial to me than the need to repair or remove bad data later. I am now performing scans and log checks to identify any potentially damaged data. Thank you @trurl for mentioning those key points.

It has been a couple more days now. Looks like the solution was simpler than expected. For those who may encounter a similar issue in the future: After restarting the server and placing it in maintenance mode, it allowed Data Rebuild to begin. I let this complete. Before taking it out of maintenance mode, I ran a Parity Check just in case. I then restarted the server and started the array. It has now finally started, and everything is working properly. Thank you, @JorgeB , for your assistance and for pointing out the syslog server option that I was previously unaware of. I now have my logs being collected on another server, just in case.

Correct. However, the data is actually being rebuilt now which was also not occurring before. The hope is that once the data is rebuilt, the disks will mount. This has become a one thing at a time kind of process. Too easy, I will do that right after the data rebuild completes and post. About halfway there now.

UPDATE: And possible solution. After more troubleshooting and just trying things, I could not get the array to start using the "Start" button. I was, however, able to put it in maintenance mode (which i was not able to do before and i believe that was an issue related to my failing USB) and then sync to begin the data rebuild. As the array was not actually started, I am not sure if this is fixed yet. I will return when the data is rebuilt with an update as to whether this solves the issue.

When I click start it still gets stuck mounting drives and then I'm not able to pull the syslog. It's like it locks me out completely. I had to hard reboot and pulled some new logs (attached). The only thing that was different this time was that the cache and VM pools were missing disks and were showing not mounted. I was able to mount them. After the hard reboot, the drives were showing back correctly in their pools. jarvis-diagnostics-20260108-1957.zip syslog20250108.txt jarvis-syslog-20260109-0206.zip

So, I will try to keep it brief, but also provide all of the info because I am now on day 3 of reading through forums and trying to repair the issue. I had a drive (drive 8) finally fail on me. I decided to get 10 brand new 6TB WD drives, Merry Christmas to myself. I removed the failed drive, inserted the new drive and let the parity begin to rebuild the new 6TB drive. Since I wanted to make sure this drive was fully restored, I did not worry about the other couple drives with SMART errors until after this one rebuilt. The rebuild of this one drive was taking a long time (like we were on day 4 of it rebuilding) but I let it go because it was still moving along and I was not in any hurry for it to finish. On day 4, there was a power outage during the rebuild. I of course, have yet to get a UPS (yes I know, I know..). When I rebooted the system everything looked ok, but when I tried to start the array the disk were stuck "mounting" for several hours. I tried to soft reboot, but after clicking the button nothing ever happened so I had to hard restart it. This time, to keep it short, the flash drive was bad. Thankfully, I was able to pull the /config and create a new flash drive, however, that did not solve my issues with the system never actually mounting the drives. It still was stuck "mounting" the drives for hours. I, like most people, would love to not lose the TBs of data in this media server. And have scoured the forums. I have found similar issues and tried those suggestions, but I am still stuck. Please help this is day 3 of trying things without breaking it more. jarvis-diagnostics-20260107-2153.zip syslog.txt

Went to setup flaresolverr for prowlarr. Received this error and log section. Seems like a straight forward install. Double checked everything input correctly. Removed and reinstalled. The rest of the 'arr' suite is up and running great, just having issues here. Any ideas? 2024-12-13 14:30:57.7|Warn|ProwlarrErrorPipeline|Invalid request Validation failed: -- Host: Unable to connect to proxy: HTTP request failed: [503:ServiceUnavailable] [POST] at [http://192.168.1.64:8191/v1]. Check the log surrounding this error for details 2024-12-13 14:30:57.7|Debug|Api|[POST] /api/v1/indexerProxy/test: 400.BadRequest (30116 ms) 2024-12-13 14:31:04.0|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated. 2024-12-13 14:31:04.0|Debug|FlareSolverr|Cloudflare Detected, Applying FlareSolverr Proxy FlareSolverr to request https://prowlarr.servarr.com/v1/ping 2024-12-13 14:31:34.0|Warn|HttpClient|HTTP Error - Res: HTTP/1.1 [POST] http://192.168.1.64:8191/v1: 503.ServiceUnavailable (6571 bytes) 2024-12-13 14:31:34.0|Error|FlareSolverr|Proxy validation failed [v1.27.0.4852] NzbDrone.Common.Http.HttpException: HTTP request failed: [503:ServiceUnavailable] [POST] at [http://192.168.1.64:8191/v1] at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 128 at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 137 at NzbDrone.Core.IndexerProxies.FlareSolverr.FlareSolverr.Test() in ./Prowlarr.Core/IndexerProxies/FlareSolverr/FlareSolverr.cs:line 189 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> Flaresolver logs show this. 2024-12-13 14:28:38,025 DEBG 'flaresolverr' stdout output: 2024-12-13 14:28:38 INFO Test successful! 2024-12-13 14:28:38,030 DEBG 'flaresolverr' stdout output: 2024-12-13 14:28:38 INFO Serving on http://0.0.0.0:8191

A year later and now I have this same issue. Wanted to see if there was ever a tried and true solution. I've pruned and completely removed/reinstalled the Plex container and am still receiving the same error. Please help. Also receive about:blank#blocked in the WebUI Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-12-06 20:08:30.483231 [info] Host is running unRAID 2024-12-06 20:08:30.498084 [info] System information: Linux 83a87e322070 6.1.118-Unraid #1 SMP PREEMPT_DYNAMIC Thu Nov 21 15:54:38 PST 2024 x86_64 GNU/Linux 2024-12-06 20:08:30.512669 [info] Image tags: BASE_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=1.41.2.9200-1-01 2024-12-06 20:08:30.528945 [info] PUID defined as '99' 2024-12-06 20:08:30.547265 [info] PGID defined as '100' 2024-12-06 20:08:30.579060 [info] UMASK defined as '000' 2024-12-06 20:08:30.595537 [info] Permissions already set for '/config' 2024-12-06 20:08:30.612819 [info] Deleting files in /tmp (non recursive)... 2024-12-06 20:08:30.630834 [info] TRANS_DIR defined as '/config/transcode' 2024-12-06 20:08:30.650004 [info] SHARED_NETWORK defined as 'no' 2024-12-06 20:08:30.665220 [info] Starting Supervisor... 2024-12-06 20:08:30,767 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2024-12-06 20:08:30,767 INFO Set uid to user 0 succeeded 2024-12-06 20:08:30,769 INFO supervisord started with pid 7 2024-12-06 20:08:31,771 INFO spawned: 'plexmediaserver' with pid 65 2024-12-06 20:08:31,771 INFO reaped unknown pid 8 (exit status 0) 2024-12-06 20:08:32,772 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-12-06 20:08:44,398 DEBG 'plexmediaserver' stdout output: Critical: libusb_init failed

Hey, noob here. Have everything setup except I am receiving this error: Error: The pgvecto.rs extension is not available in this Postgres instance. If using a container image, ensure the image has the extension installed. at /app/immich/server/dist/services/database.service.js:73:23 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /app/immich/server/dist/repositories/database.repository.js:197:23 api worker exited with code 1 I am unsure how to get this extension installed. Please help.