Jump to content

Stannis33

Members
 View Profile  See their activity

  • Posts

    25

  • Joined

  • Last visited

 Content Type 

Posts posted by Stannis33

    Unraid 6.9.2 - parity disk in error state as soon as parity check started

    in General Support

    Posted

    How do I actually make it work again right now though, even if it happening again is likely? I don't actually know how to get my system out of the current disabled state.

     

    If I just re enable the disk, will my parity actually be working or do I have to do "Getting it back on would require checking, unassigning, reassigning and rebuilding"?
    And if the latter, what does that actually mean?

    Unraid 6.9.2 - parity disk in error state as soon as parity check started

    in General Support

    Posted

    Oh. Ummm. So that suggests I cannot just re-enable the disk and have everything working again, correct?
    I see someone says "Getting it back on would require checking, unassigning, reassigning and rebuilding" - I don't actually know how to do that - can someone please elaborate?

     

    I am very scared of upgrading - I seldom succeed at upgrading anything without strange things happening. I really don't know what I am doing with Unraid in general and if anything goes wrong I won't have the faintest idea how to fix it. :/

    I know there are instructions for upgrading, but I got rather lost rather quickly. Does anything along the lines of "upgrading Unraid for dummies" exist anywhere?

     

    I'm sorry if I am asking silly questions :/ 

    Unraid 6.9.2 - parity disk in error state as soon as parity check started

    in General Support

    Posted

    I just tried running the extended test again, and progress completely vanished after about 20 miinutes

     

    I don't know if it means anything but this was in the file I got via the download report button

     

    "SMART Extended Self-test Log Version: 1 (1 sectors)
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Extended offline    Aborted by host               90%     18216         -
    # 2  Short offline       Completed without error       00%     18216         -
    # 3  Extended offline    Aborted by host               90%     18207         -
    # 4  Extended offline    Aborted by host               90%     18206         -"

    Unraid 6.9.2 - parity disk in error state as soon as parity check started

    in General Support

    Posted · Edited by Stannis33
    Additional info

    My monthly parity check started at 04:00 and when I checked on the server when I woke up I was greeted by these messages

    image.png.5821b587144871c169b8f1f52e03da65.png

     

    And this is what Array Devices shows
    image.thumb.png.69b5bc8f1d6df8a3bdb616169c2204a1.png

     

    I attach the diagnostics zip

     

    Can someone please help and tell me what to do next?
    I am very new to this and at a complete loss 😕

     

    Update: I read somewhere that is it often suggested to run and extended SMART test, so that is now running.

     

    But in the meantime is it safe to eg watch things on Plex? Or should I use the server at little as possible?

    bob-diagnostics-20230901-0813.zip

    [Plugin] CA Appdata Backup / Restore v2.5

    in Plugin Support

    Posted

    @KluthR just thought you might like to know, since you spent so long trying to help me, that my weird "sonarr" issue *might* finally have been identified

    It seems there was an rclone related user script which looks like it was supposed to stop and start the containers and involved a dropbox and other credentials which aren't mine. Theory being these credentials are no longer valid and so things were failing somewhere. Looks like it stopped the container but never got round to starting it again

    That script was set to run every 10 minutes.....hence the max run I ever got was 10 minutes and usually only around 5.

    With the script disabled, my "sonarr" container has now been running for 2 hours. I am a little reluctant to actually believe it.....but maybe....just maybe.....

    Where else might I get help?

    in General Support

    Posted

    I have a very strange problem with a docker container. I am desperately searching for help, I've asked everywhere I can think of and have been unsuccessful
    I'm wondering if anyone knows of anywhere else I can try asking?

     

    I've tried:

    This Unraid forum in Genral Support, Docker engine and on an app thread (which might have been the issue - it wasn't)
    The Unraid discord

    The Unraid Reddit
    the discord for the markers of the container
    the discourse for the makers of the container
    the discord for Sonarr (the app in question, although the app itself works fine)
    The support forum for Sonarr
    The docker support forum

     

    Anywhere else I could possibly try?

    DOCKER CONTAINER OF SPECIFIC NAME KEEPS STOPPING

    in Docker Engine

    Posted

    I really hope someone can help me as this is very strange

     

    I had a sonarr docker container which was working fine, but then suddenly would only run for 5 minutes without stopping.

    I don't think that the issue is actually with sonarr itself though. It seems to be the name of the container causing the issue, not what is in it.

     

    My original container was called "sonarr". I recreated an identical copy of the container with a different name - "sonarr2" - and it ran for several hours. I then stopped the container, deleted the old "sonarr" container and renamed the new one to "sonarr". The container stopped after ~5 minutes. I changed it to "sonarr2" again and it ran for several hours again. I repeated this name change several times with the same result - "sonarr" always stops after ~5 minutes, "sonarr2" never stopped. It ran as "sonarr2" for nearly a week (before I stopped it myself). 

     

    Also, the "sonarr" container does actually work perfectly for the 5 minutes it actually remains running.

     

    What can possibly have happened? Can I somehow "clear" the seemingly wonky "sonarr" name so I can use it again?

     

    This is a chunk of server logs from when I was renaming containers
    https://pastebin.com/DYajFwp8 

     

    This is my Docker run command

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='sonarr2' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8989:8989/tcp' -v '/dev/rtc':'/dev/rtc':'ro' -v '/mnt/user/Videos/':'/tv':'rw' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/mount_rclone/dropbox/To Mum & Dad/':'/export':'rw' -v '/mnt/user/Downloads/Scripts/':'/scripts':'rw' -v '/mnt/user/appdata/sonarr':'/config':'rw' --security-opt seccomp=unconfined 'linuxserver/sonarr'
    704bcfa29e947831767a7c3970cd6591abfe529faa326049f7fbd7cf4c176f37

     

    I have been told on the sonarr forum that there is nothing amiss in the sonarr logs - they just stop logging when the container stops, but these are some debug logs from a stopping incident
    https://pastebin.com/16Xb15FV 

    [Plugin] CA Appdata Backup / Restore v2.5

    in Plugin Support

    Posted · Edited by Stannis33
    update

    Weird is definitely the word to use!

     

    Ok so I have:
    docker inspect for the container while named sonarr (while running)

    https://pastebin.com/KLA32xvc

     

    docker inspect for the container while named sonarr2
    https://pastebin.com/9hJ2UgrT

     

    And this is what appeared in the system log for the rename (from sonarr2 to sonarr) and subsequent stop

    https://pastebin.com/ywgRKBS9

     

     

    2 hours ago, KluthR said:

    Or maybe something inside /var/log/docker.log?

    Ummm.......I don't seem to have that. At least I can't find it, but I didn't build the server so I don't really know where anything is. Where should I be looking for that? Or is it possible that docker has been set to not log? I couldn't find any kind of option for that but I may have been in the wrong place😕 

    Never mind, I hadn't Googled hard enough 
    Docker logs:
    https://pastebin.com/56MdDy2Z

    [Plugin] CA Appdata Backup / Restore v2.5

    in Plugin Support

    Posted · Edited by Stannis33
    typos

    So I rebooted my server, changed the container name back to sonarr......and it stopped again. I named it sonarr2 again and it's been running again for 5 hours....

     

    15 hours ago, KluthR said:

    Unraid stores all docker related infos directly inside the docker container meta infos (using labels). So, if you remove a container, there is nothing left from it (maybe the image but thats ok). What does a "docker ps -a" say? What does the container logs say?

     

    "docker ps -a" gives
    image.thumb.png.bee49d23440291fda77305f8ed746eb0.png

    After the "wonky" version had stopped (I can try to get it while still running if that  might help)

    and I get this for the "working" version

    image.thumb.png.994594adff70373be39feba1070ed076.png

     

    When you  say the container logs do you mean the sonarr logs or some actual docker logs? The sonarr logs say nothing, even in debug mode, they just stop logging - even the sonarr forum says there's nothing weird in them.

     

    Where might I find the "meta infos"? I tried looking in the sonarr appdata folder but there was no obvious candidate, at least to my very untrained eyes.

     

    15 hours ago, KluthR said:

    Do you have the seperate AutoUpdate plugin installed as well?

    It seems I do.....it is set to run at 02:47 (I don't know why that time, I didn't set it up) and my appdata backup is set to run at 04:00 so it feels like they shouldn't collide. Although it did go wrong the day clocks went forward so I guess there could have been some timezone related screwup.

     

    [Plugin] CA Appdata Backup / Restore v2.5

    in Plugin Support

    Posted

    On 3/27/2023 at 5:07 AM, ctrlaltd1337 said:

     

    I have had my appdata backup run on Mondays at 4am for years, even with the recently deprecated plugin. It hadn't been giving me issues until recently and I had read that v2.5 was giving people errors so I stuck with the v2 until last week, but my issue still occurred with v2.5. The issue seems to only be affecting the Plex container, as all other containers backup properly and restart without issue. This obviously makes me think it's an issue with the container, but I've tried to completely re-install it and the same thing keeps happening.

     

    The issue is that after the appdata backup, Plex does not restart, and whenever I try to start it I get greeted with "Error: Server Error" with no other information. I cannot start the container, delete the container, I can hardly do anything to it. The one thing I was able to do one time was rename it (I changed it from plex to plex2). I have tried turning the Docker service off and on, but I was unable to unmount my unassigned disk (appdata), so something was stuck. I still could not update, delete, anything. My solve was to set the container to not autostart, restart the server, and then all works as expected when I start it up manually.

    I am having a very similar issue to this and have tried asking just about everywhere else, maybe someone here can help....

     

    I have been running the appdata backup for several months without issue, but after my last backup, on 2nd April, my sonarr container just stops after 5 minutes. It is not set to auto-start. I start it, it works perfectly (as far as I can tell) for around 5 minutes then just stops. I've rebooted my server numerous times and it didn't help.

     

    But eventually I realised that if I rename the container to "sonarr2", it was called "sonarr", it runs for days and never stops. Rename it to "sonarr" again and it stops after 5ish minutes every time.

     

    Does anyone have any suggestions as to how I can get my container back to being called "sonarr"? (I have just realised that I have not rebooted the server since I renamed the container, might that be enough to "clear out" any wonky usages of the "sonarr" name?)

    And how I might prevent this from happening again at the next backup?

    Unraid 6.9.2 - Docker container of specific name keeps stopping

    in General Support

    Posted

    I really hope someone can help me as this is very strange

     

    I had a sonarr docker container which was working fine, but then suddenly would only run for 5 minutes without stopping.

    I don't think that sonarr itself is actually the issue though. It seems to be the name of the container, not what is in it.

     

    My original container was called "sonarr". I recreated an identical copy of the container with a different name - "sonarr2" - and it ran for several hours. I then stopped the container, deleted the old "sonarr" container and renamed the new one to "sonarr". The container stopped after ~5 minutes. I changed it to "sonarr2" again and it ran for several hours again. I repeated this name change several times with the same result - "sonarr" stops, "sonarr2" never stopped. It has now been running as sonarr2 for 20 hours. 

     

    What can possibly have happened? Can I somehow "clear" the seemingly wonky "sonarr" name so I can use it again?

     

    This is a chunk of server logs from when I was renaming containers
    https://pastebin.com/DYajFwp8 

     

    This is my Docker run command

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='sonarr2' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8989:8989/tcp' -v '/dev/rtc':'/dev/rtc':'ro' -v '/mnt/user/Videos/':'/tv':'rw' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/mount_rclone/dropbox/To Mum & Dad/':'/export':'rw' -v '/mnt/user/Downloads/Scripts/':'/scripts':'rw' -v '/mnt/user/appdata/sonarr':'/config':'rw' --security-opt seccomp=unconfined 'linuxserver/sonarr'
    704bcfa29e947831767a7c3970cd6591abfe529faa326049f7fbd7cf4c176f37

     

    I have been told on the sonarr forum that there is nothing amiss in the sonarr logs - they just stop logging when the container stops, but these are some debug logs from a stopping incident
    https://pastebin.com/16Xb15FV

    Sonarr docker container stops several minutes after starting

    in General Support

    Posted

    Oh, I see....sorry.....

     

    Docker run command
    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='sonarr' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8989:8989/tcp' -v '/dev/rtc':'/dev/rtc':'ro' -v '/mnt/user/Videos/':'/tv':'rw' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/mount_rclone/dropbox/To Mum & Dad/':'/export':'rw' -v '/mnt/user/Downloads/Scripts/':'/scripts':'rw' -v '/mnt/user/appdata/sonarr':'/config':'rw' 'linuxserver/sonarr'
    b7a38edf4ae0cea94d0149398c82360d9b91ba1234457007e04a3c11e1320065

     

    I have been told that the Sonarr logs themselves are basically useless - they don't say anything about a crash/shutdown, they just stop logging

     

    The Unraid logs with the start and subsequent stopping of Sonarr right at the end

    https://pastebin.com/jY76equ6

    Sonarr docker container stops several minutes after starting

    in General Support

    Posted

    I’ve tried asking support for the docker container itself, but they are stumped. I am very out of my depth and don't know where else to turn

     

    I have an inherited Unraid server (6.9.2) and it has a Sonarr docker container which was (as far as I am aware) working fine until sometime overnight. Now it will only run for about 5 minutes before shutting down

     

    I have tried rebooting the server and that didn’t help and my other docker containers seem to be working fine.

     

    As far as I know the only thing that happened overnight was an automatic backup by CA Appdata Backup/Restore - but this has run several times before without causing a problem

     

    Can anyone help me figure out what might have happened and help me fix it?

    Dockers not quite right after installing new router

    in General Support

    Posted

    I am a complete newbie in need of help - and when I say newbie I really mean it. I inherited an Unraid media server, I didn't set it up, so I know virtually nothing about Unraid. I've just about muddled through so far, but now I have a problem...and I am in over my head. 😕

     

    I have an Orbi mesh system "running" my network. And everything relating to my media server - dockers, external access etc was fine.
    This morning I had to install a new router. I put it into Modem mode, hooked it back up to my Orbi and everything else seems fine, except something on the media server.

     

    Initially I could not access Plex from outside the network, but after restarting the router, Orbi and server about 3 times that does now seem to be working.

    But all of my docker containers are showing "not available" for the versions, this was not the case yesterday.
    Nothing, as far as I can tell, is not actively working (sonarr, deluge etc seem to be running fine) but this is clearly not the correct state of things.

     

    I have found a few articles which mention this problem - one mentioned an issue fixed in 6.9.2, but I have 6.9.2 and I only understood every 3rd word or so in most of the rest. 
    Could anyone offer an explanation in the smallest and simplest words possible what might be wrong and how I might fix it?

     

    Thanks

×
×
  • Create New...