• Posts

  • Joined

  • Last visited

About Saldash

  • Birthday 01/25/1989


  • Gender

Recent Profile Visitors

1121 profile views

Saldash's Achievements


Rookie (2/14)



  1. Hi all, I've started getting periodic systems halts that require a full hard reset to resolve. The system boots and appears to start normally until I get to entering my array password where after starting the array the UI appears to hang with the unraid logo pulse for a good minute at least before the UI becomes normally responsive again. I run weekly array health checks that have not reported any issues and after a fresh boot up, I cannot see anything in the system log that would indicate the source of the fault (not that I'd know what I was looking at to be honest). I've uploaded the diagnostic file in the hopes that someone might be able to point me in the right direction to getting this sorted. The box isn't highly critical but it is starting to get annoying having to hard reset the box and I've now gotten to the point where it's common enough that the server is on a smart plug that I can remotely turn off/on when this issue crops up. Thanks in advance for your help,
  2. Hmm.. I got updated today and now Sonarr won't start. I get a repeat of this block before it finally gives up and dies. 2021-03-09 21:08:59,097 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22543642412560 for <Subprocess at 22543642413328 with name sonarr in state STARTING> (stdout)> 2021-03-09 21:08:59,097 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22543642573312 for <Subprocess at 22543642413328 with name sonarr in state STARTING> (stderr)> 2021-03-09 21:08:59,097 INFO exited: sonarr (exit status 2; not expected) 2021-03-09 21:08:59,097 DEBG received SIGCHLD indicating a child quit 2021-03-09 21:09:02,101 INFO spawned: 'sonarr' with pid 68 2021-03-09 21:09:02,113 DEBG 'sonarr' stderr output: Cannot open assembly '/usr/lib/sonarr/NzbDrone.exe': No such file or directory. Forcing an update seems to have resolved this though. Might be useful for other people having the same issue.
  3. I'm unable to access VM's through the Unraid UI - Picking any of my running VM's and clicking VNC Remote just results in the new window showing me this error; I'm accessing the UI through: Google Chrome 88.0.4324.192 (Official Build) (x86_64) Running on MacOS 11.2.2 VNC Remote does work on Safari on the same machine.
  4. Has anyone been able to get the external (remote) client IP address to forward to the proxied server? I've skimmed a few pages and run a search over this topic but I can't find anything on getting the client's IP address to the server. For clarity I'm running a site using IIS on Windows Server 2016, with Nginx Proxy Manager fronting the public requests. My web server only ever sees the IP Address of the docker (my unraid server), which is problematic when my application has IP Address banning implemented for security - I've had to disable it incase someone cottoned on that they could effectively use my own security against me 😐
  5. So they do, weird I get the plugin and docker updates but I've never had an OS update notification though. I'll monitor for the next update. Request two though would still be nice
  6. Hey all, Just thought of a potential new feature this morning - had a power cut last night, signed into unraid to start the array this morning and discovered there's a new update available. Does unraid check for updates periodically and if it does, can a new notification option be added so that it sends a notification to configured clients? (I use Pushover which has been flawless so far). As an additional option to the above, could we have an option to let unraid automatically download (but not install) the update and let us know that (as well as it being available above), that it's now ready to install? Or disable the above all together as I'm guessing some people aren't too bothered. Edit: 1 and 3 already exist as pointed out.
  7. The last backup I have was taken while the USB device was in this state.
  8. Hi, Yes it's booting from a USB 2.0 port. I've run check disk, I got the message that there were errors and prompted to fix them, which I confirmed to do. This takes a few seconds before returning this message: I've gone into CMD prompt, into DISKPART and run to clear the readonly attribute from the drive but it never changes the current read only state from the disk.
  9. Hi all, Pretty sure I've seen this posted before but I couldn't find it. I've just tried to update my server to the latest version of Unraid but I received an error: plugin: run failed: /bin/bash retval: 1 Trying to update plugins errored out with either the same error or a general failure: plugin: updating: community.applications.plg Cleaning Up Old Versions plugin: downloading: ... failed (Generic error) plugin: wget: download failure (Generic error) I've then got a small notification that the USB drive was not read-write. The server was rebooted "just in case" and on loading, just before the final console login, it listed a bunch of dockers that couldn't open temp folders because of read-only. I'm a little nervous as this is the first time I've actually had anything "go wrong" with my server. The server booted up, has let me log into the WebGUI and has begun its usual parity check but the error saying USB was not read-write appeared again. As a precaution, I've downloaded a flash backup. The flash drive is only a few years old and is a Sandisk Cruzer Fit 16GB drive from Amazon. Background aside, is this indicative of a failing USB drive? Here's the disk log information: If this disk is failing, can I take the backup I've just made, get a new 32GB cruzer drive from Amazon, copy the contents of the zip over, re-licence the USB drive and carry on like nothing else happened? Thanks, S.
  10. This is a known issue in the current build and I believe a fix is going to be released on Tuesday for the main project. When this particular docker will be updated is another story. Hope that helps EDIT: While I know it's got nothing to do with this docker, this is why I wish unRaid would support an official API endpoint for dashboard information. For right now scraping the dashboard in C# and parsing the DOM using HTMLAgilityPack is having to suffice.. barely
  11. Sorry bud, I didn't even know you'd posted a response - I haven't had any notifications from the forum and only noticed when I popped on to ask a question about Grafana. I can't remember what is was that I had a problem with for this container, let me post this and I'll have a scroll back and edit this once I've remembered! -- EDIT Well I looked back and I haven't got a clue what i was on about! I do have everything setup and functioning so I would be happy to answer any specific questions you might have re the setup I use at this point.
  12. I've literally just come back to it today, tried that and was about to post that it's worked for me before I saw your post. Had no idea if it was going to work or not but it was a shot in the dark that got the mark for me. Thank you anyway!
  13. Hi, I have a need to access the nginx.conf file to try and fix a problem I'm having with larger header sizes with IdentityServer. Specifically in relation to: How can I set the following values for this container? http{ ... proxy_buffer_size 128k; proxy_buffers 4 256k; proxy_busy_buffers_size 256k; large_client_header_buffers 4 16k; ... } Currently I'm able to authenticate my app but I immediately get redirected to a 502 Bad Gateway from nginx.
  14. Hi, Just as the title suggests - I'm getting to a point where I'm using a lot of docker containers for various purposes - Ombi, Plex, Sab, Radarr & Sonarr as well as other nginx sites and (thank you linuxserver guys) a Visual Studio Code implementation too. But it's getting really crowded. I don't really need to see telegraf, HDDTemp or influx and without shifting the order around on the Docker tab, there's not really a way to organise things better. I would like to see some ability to group docker containers, optionally show/hide specific groups from the dashboard (for more critical dockers only). Being able to start/stop/restart the whole group at once would be an added bonus but not essential. For some idea of how i would see this being done, is that you could have under Settings/DockerSettings a section to add/remove docker groups, and to add a container to a group would require editing the container, and not being able to remove a group until it was empty, again editing applicable docker containers to either change their group or ungroup them. I don't know if I'm actually miss-using unRaid or if people don't tend to have 25/30 docker containers running without the need to organise them into groups? Thoughts?