David13858

Issue has magically resolved its self... I haven't touched anything so I have no idea why it is fixed.

I have been having some issues with the container over the past few weeks (it has been running fine for years) so I decided to give it a reinstall. I have set it up exactly the same way as before and everything works fine until I try to import existing media. I have tried the following commands but none have worked. ```docker exec -it binhex-radarr /bin/bash``` ```chown -R nobody:nobody media``` ```chmod -R 777 /media/``` When I run ls -la on the media folder every file returns drwxrwxrwx 1 nobody nobody <size> <date> <folder name>

Knew I was in the wrong place. I will post there, thanks.

Hi All, I have been having some issues with the binhex-radarr docker container over the past few weeks so I decided to give it a reinstall. I have set it up exactly the same way as before and everything works fine until I try to import existing media. This is above my understanding so I am a bit lost about what to do. I have tried the following commands but none have worked. ```docker exec -it binhex-radarr /bin/bash``` ```chown -R nobody:nobody media``` ```chmod -R 777 /media/``` When I run ls -la on the media folder every file returns drwxrwxrwx 1 nobody nobody <size> <date> <folder name> See below for the docker container setup

Ah, that works. I had no idea the device name changed. It looks like that is me up and running again, Thank you.

Ok so I guess you guys were right, both the drives I tried appeared to be DOA (Inherited from a few old machines). Inserted another new drive and rebuilt the data. I am now back to 23 drives all functional. The part I still don't understand is the responses I get when I type the below command. I know Defragging doesn't matter that much (if at all) but It's still something that makes me think there are some issues. Is this something irrelevant or should I be worried about it ? I have attached the most recent diagnostics. plex-diagnostics-20230827-1957.zip

I forgot to include more information that is probably important. Yesterday I ran into an LZMA error, data is corrupted. I followed a forum post reinstalling UNRAID and copying the config files. That got the server back up and running again. The drive you mentioned above ending in 45 is the drive that has just been put in the server. That should be in full working order. When I stop the array and try to select the drive the option suddenly disappears (As seen in the screenshot). This is the second drive I have tried as well so it is unlikely that both ‘new’ drives would be failing. (That said they are technically used so it is possible)

Hi All, I'm not quite sure what issues I am having but my system isn't behaving as it should, I think it could be an issue with a drive or the file system. A few weeks ago I had a drive failure, did the standard procedure and replaced the failed drive. No issues from what I could see. This week I had another failure. Stopped the array and replaced the drive. When I turn the server on the array automatically starts and the array says I am missing disk 11 (The failed drive) I cannot stop the array as it will just error out indefinitely. When I enter the command : xfs_db /dev/md1 I get the response /dev/md1: No such file or directory fatal error -- couldn't initialize XFS library I tried to run the xfs_repair command today and the only response I got back was something like "no secondary super blocks found" I forgot to note down the exact message... Diagnostics are attached below. plex-diagnostics-20230826-1925.zip

Thanks Jorge, That seems to be solving the issue.

plex-diagnostics-20230308-0929.zip Hi All, I'm was having some issues with a docker container setup last night and thought It would be a good idea to give the server a restart. When It came back online docker had not loaded. I have tried to have a look through the diagnostics but I am not sure what I am looking for and if I am looking in the correct place.

plex-diagnostics-20230224-1456.zip Development: Tried to reseat the drive for the 5th time and this time it appears everything has fired up correctly. Going to replace the drive anyway but it would be interesting to see what went wrong.

Reseated the drive and it failed again, this time failing to find the device... I will attempt a few more times but realistically all the signs are pointing to a failed drive, bit of a bummer the drive is only 277 days old.

plex-diagnostics-20230218-1340.zip It appears that has mostly worked. The docker containers are back online but the docker tab in the UI is looking different.

plex-diagnostics-20230218-1138.zip

Hi All, Interesting issue has developed over the past few days. I have been unable to access my server due to an Error 500 code, inconvenient but not the end of the world so I just left it. Today it appeared that the docker containers failed (Plex stopped working). I decided to try the good old turn it off and on again, in hindsight this was not the best idea. Server booted up and went into Unraid as normal, drives automatically re-mounted themselves and I thought we were back up and running. Then I looked and noticed docker is no longer running and a grey dot has appeared next to the 'cache' label instead of the usual green and now the drive has a reported capacity of 0 B (It should be 2 TB) My first instinct tells me that the drive has failed, although it is a reasonably new drive (6 months old). I thought It was worth a post here to see if anyone has any ideas on how to proceed.