Jump to content

stuckless

Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

3 Neutral

About stuckless

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah, the umountable drive scared me, since my expectation was that unRAID could continue to work with a single drive failure. I'm happy that it did in fact recovery everything, and that the unmountable drive became mountable again. Maybe unraid "fixed" the problems??
  2. I've steered many people to unRAID for a variety of reasons. It's a decent "server" technology for running containers, with the added benefit of getting data protection. I've not experienced a drive failure since running unRAID, but, I've had many leading up to unRAID, which was why I decided to use it myself. This past week a friend of mine called me up and said, 'My unRAID is toast". I remoted into his machine and sure enough one of his drives was "missing" and the other drive was "unmountable" and the parity drive was good. My first thought was "oh crap" he lost 2 drives and now he lost everything. I admit I didn't do much research, but I told him to order a new drive and install it, which he did. I then remoted in and assigned it, and unRAID came back with a message about rebuilding the data, so I was hopeful. 5 hours later, it was done, and after a restart on the Array, all data was back. unRAID worked, and it did what it supposed to do. So just wanted to say "thanks". You always hope when you buy something that it'll work as advertised, but you never know Great job guys.
  3. @Blacksmoke Thanks for the find... It does seem like this is my issue as well. Once I can get access the system, I'll try the solution posted there, but I'm pretty confident that it's the same issue, so hopefully the same solution works. @trurl thanks for that explanation. I didn't realize /etc was a memory fs, but that explains why my edits did take. Thanks guys for the help. I'll report back once I get confirmation of the fix.
  4. @Squid thanks, I'll try to get that as soon as I can. Unfortunately this was a client update in another city, so when they are back on Monday, I'll remote into their machine and perform the diagnostics. Does unRAID have a backout from a failed upgrade -- something that can be run from a console? Is there a way, from a console, to downgrade? Now that I've hacked it to get the UI working, is there a plugin that can do a downgrade? (I thought about maybe installing the dvb plugin and using its list of kernels to see if I could downgrade.. but not sure what that would do, and I really don't want to mess up their system any more than it is). One thing that comes to mind when I did the upgrade on their machine, is that I clicked the "update" link, twice. The first time it ran through the download and extract process, and I clicked done, and then I got distracted with some other tasks, so when I came back, I clicked the "update" again, and it did the download and extract. I can't imagine that doing this twice could be this destructive, especially since unRAID doesn't force a reboot and they don't disable or check if the update happened before doing it again.
  5. I was finally able to hack the configuration to allow the UI to start by commenting out the ssl cert stuff in the nginx configuration. # Ok to use concatenated pem files; nginx will do the right thing. # ssl_certificate /etc/ssl/certs/unraid_bundle.pem; # ssl_certificate_key /etc/ssl/certs/unraid_bundle.pem; # ssl_trusted_certificate /etc/ssl/certs/unraid_bundle.pem; but this is just a hack, since on a reboot, it appear to uncomment them, and then the UI won't start again. Hopefully unRAID can determine what is going on and provide a fix.
  6. Just upgraded to 6.5 and now I can't access the web ui. I finally logged into the physical machine and booted into gui and tried to access the web UI from there, but still can't connect. Tried starting nginx manually and i get the following error, which is likely why the web ui doesn't work. nginx: [emerg] PEM_read_bio_X509_AUX("/etc/ssl/certs/unraid_bundle.pem") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE) How can I get back to 6.3.5 or fix this issue?? Thanks, Sean.
  7. I don't disagree. I run my own open source projects, and I tell people the same thing... ie, it's just easier to pick and choose what you are willing to support. I just threw it out there because someone as asking me about supporting it in my SageTV container, but this is a kernel things, so I passed it along here
  8. The hauppauge site does list links for linux drivers for HDPRV2. Not sure when that happened. http://www.hauppauge.com/site/support/linux.html#tabs-3 Not sure how well this can be incorporated with the unRAID kernel, but, drivers do exist (apparently).
  9. I don't know if unRAID has a GUI cron (or if there is a cron plugin, etc), but docker is fully command line driven. So, if you can find a way to create a CRON, you can probably use 'docker restart' command and restart it. https://docs.docker.com/engine/reference/commandline/restart/
  10. To add to this... is the web ui using 'docker kill' vs 'docker stop'... If so, I think the "STOP" in the WebUI should be using 'docker stop' to allow the container to gracefully shut down. Could the unRAID admins clarify the process here? thx. I found this post on the difference http://superuser.com/questions/756999/whats-the-difference-between-docker-stop-and-docker-kill And as CraziFuzzy suggested, I think the WebUI should have a "STOP" that sends 'docker stop' and a "FORCE STOP" that sends 'docker kill'.
  11. At long last - acknowledgement that not everyone has a machine running Microsoft (or even Apple)! Surprisingly we've gotten only a couple requests for that over the last few years. I revamped our internal development machine recently and a small part of that was moving from grub to syslinux so half of the r&d work for the make bootable script was already done as part of that revamp. The requests may be minimal, mainly because it's clearly documented that it only works on Windows/Mac... and most people have access to either... but I am thankful that it now supports linux... I just setup 2 unRAID servers for friends, and I would have rather used the linux script So thanks!
  12. Is the v2 template stuff documented somewhere? When i was creating my templates, I ended up just finding existing unRAID templates and figuring it out from there... it would be nice if the unRAID web ui provided a quick link to the docker template structure. Is the v2 templates a CA thing or an unRAID thing?
  13. I also installed the CA plugin, so I just have stock unRAID. If I manually add my template repo https://github.com/stuckless/sagetv-dockers/tree/master/unRAID/stuckless-sagetv And select something from there... I don't get any variable names... just default values... I have 2 machines that are running unRAID Basic, and I updated both today to the RC1, and this is the behaviour that I'm seeing on both I guess I need to see if there is a way I can downgrade to another version and wait for RC2. EDIT: I downloaded to beta-23 and I get the proper display for the docker configuration. Odd that no-one else experienced this but I experienced it on 2 difference machines
  14. Not the behavior I'm seeing which container are you adding? I see it specifically when I add deluge-vpn, sagetv-server-java-8, and any pretty much anything that I add when I add it from the "Apps" tab. But as i said, If I edit an existing container, or try to add from the my templates section.. it shows up correctly.
  15. After upgrading to RC1, when I go to install a Docker container using a template that I have not used before, all the VARIABLE sections are missing the actual variable names? Is this by design?? I've attached 2 images... one if from the RC1 and shows no variable names, just the default value... and the other shows what it used to look like. When I edit existing docker configs I see the correct layout... so this is ONLY happening when I'm installing something new that has never been installed.