scott47

Members
  • Posts

    31
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

scott47's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Thanks Johnnie! I had tried to figure out what the naming for the rc releases is on the aws page, but I couldn't get it figured out. This is exactly what I need. 🙂
  2. I was on Unraid 6.8 when I noticed that Acronis True Image started having problems creating/validating backups that were saved on my Unraid array. I'm not sure when the problems began, but I went back to 6.7.2 and everything is fine. I'd like to download and install the RC versions to see if I can figure out where the problem began to hopefully narrow down why it's happening. Is there a way to download the release candidate versions after the next rc or stable version is released? Thanks! Scott
  3. I was also having problems getting openvpn-as back up and going. Tonight I made sure everything was completely deleted and the I download the linuxserver version using the Apps tab. This way it wouldn't be using any of the settings that I might have in my personal dockers (I don't know if this part really mattered though). After I first ran the docker I saw these errors in my log file: ... But after that the web UI was working again. I stopped and started the docker and everything seemed to come back fixed: The last part I had difficulty with was figuring out where I could download the connection profile. I finally found that if I changed "https://###.###.###.###:943/admin/" to be "https://###.###.###.###:943/?src=connect", I was able to download what I needed. I'm sure there is an easier way but this did seem to work. Everything seems to be back in order! Sorry for such a long post, but I thought it might be helpful to see what I saw.
  4. Johnnie, thank you for posting this! My situation is a bit different as I'm running Unraid under ESXi, which isn't supported, but has done exactly what I need it to do for years. In my case, everything works perfectly using ESXi 6.0 and ESXi 6.5 but as soon as I tried upgrading to ESXi 6.7 I kept getting the "VFS: cannot open root devise "(null)" or unknown-block(0,0): error -6" message. I tried everything I could think of and had basically decided that ESXi 6.5 was the highest I could use while keeping Unraid. I added the " root=sda" on each of the append initrd lines, rebooted the VM, and it booted up perfectly. Honestly, I have no idea what this does or why it would make any difference at all, but it fixed booting an Unraid 6.6.6 VM in ESXi 6.7 Thanks!
  5. Thanks! This solved my problems. I left the INTERFACE variable alone (it was set to eth0 anyway) and changed the network type from Host to Bridge , saved the changes and openvpn-as started working perfectly again 🙂
  6. Hi Saarg, I was wondering if you had a chance to work on this template? The ddclient docker I have been using didn't update after an IP change last week so I was looking for a newer version. This seems like the newest version and if you have (or can make) a template to pull it from the linuxserver site that would be awesome! Thanks for any help you might offer! Scott
  7. This is truly just an annoyance and not causing any problems but when I goto to updates and choose next, I'm shown 6.6.0-rc4. I'm using 6.6.0 so going back to rc4 would be the prior, not the next release (at least I think it is)🙂 I only notice this when I'm checking to see if there is any new update out that I should look at. Thanks for all your hard work!! Scott
  8. Thanks, Jonathan, that is kind of what I figured. 🙂 I did figure out a few things, and while this is definitely an ESXi issue, I'm going to add them here in case it might help anyone else (and in case I need to remember what I found). First, I am using ESXi 6.0 and I don't know if any of the below applies to any other versions. For 6.0, the "ESXi600-201808001.zip" patch fixes the issue I reported above where the Unraid booting process stops on Booting SMP Configuration. This means that anyone experiencing this issue should be able to fix it by updating to the 201808001 patch or newer. In my case, I had one other problem in that I am using 2x Supermicro AOC-SAS2LP-MV8 SAS SATA cards (Marvell 88se9485) and need to pass them through ESXi to Unraid. This works until the "ESXi600-201711001.zip" patch, which broke something. So far I haven't been able to get the cards to work with the 201711001 patch or newer. What I ended up doing was the run the following in an SSH connection to ESXi: esxcli software vib install -d "/vmfs/volumes/datastore1/Patches/update-from-esxi6.0-6.0_update03.zip" esxcli software vib install -d "/vmfs/volumes/datastore1/Patches/ESXi600-201710001.zip" esxcli software vib update -d "/vmfs/volumes/datastore1/Patches/ESXi600-201808001.zip" --vibname cpu-microcode Step 1 updates ESXi to the most recent EXSi update. The path is where I saved the zip files, your location may differ. Step 2 installs the latest patches that will work with my SAS SATA cards. Step 3 installs just the vib that is needed to allow Unraid to boot in multi-processor mode. Honestly, I don't know for sure that this set up won't cause any problems down the line but so far I have tested with Unraid, WIndows, OSX and Linux VM's in ESXi and everything seems to be working perfectly.
  9. I have my unRaid setup running under ESXi 6 with 8 virtual cores and 16 GB ram. This worked fine with all prior versions, including 6.5.3, but with 6.6.0 the boot gets stuck on "x86: Booting SMP configuration:" When this happened, I first moved back to 6.5.3 and unRaid booted as expected. Then I re-downloaded the 6.6.0 update and tried booting again. It failed at the same spot. Lastly, I tried changing the number of cores in ESXi from 8 (4 virtual sockets with 2 cores per socket) to only 1 core (1 virtual socket with 1 core per socket). unRaid 6.6.0 booted up just fine after that. Currently, this is how I am running unRaid. My system includes a Supermicro X8DTH-i motherboard, 2 x 5690 Xeon CPU (provides 12 physical cores + 12 hyperthreaded cores) and 96 GB ECC DDR3 RAR (48 GB per CPU). This is running ESXi-6.0.0-20160302001 -standard version. Honestly, I'm not 100% sure this is a bug or a result of running under ESXi, but I would sure like to run unRaid 6.6.0 and I have to continue running it under ESXi. Thanks for your help! Scott tower-diagnostics-20180921-0829.zip
  10. I used the Advanced Buttons, update all dockers option after following Squid's instructions and everything worked perfectly! It still shows up as a problem with fix common problems but I'll just ignore the error. Thank you so much for your help! It's great to have Advanced Buttons back!
  11. Wow, Squid, this is great, thank you!! I installed this and set up the script but I don't currently have any dockers to update so I can't test it. I have the appdata backing up weekly so even if I do lose it, it's not a big deal. I will post an update as soon as I am able to test this. Thanks for all your help! Scott
  12. I hadn't thought about that, thank you! To be honest one problem is I really don't like things updating all by themselves. I prefer to know when something is updated so if there are problems I'll have any idea if anything changed recently. I'm going to look at this and give it some thought, but I would still prefer that all updates require some human intervention...
  13. Right after I installed 6.4.1 the "Fix Common Problems" plug-in sent me the following message: **** advanced.buttons.plg Not Compatible with unRaid version 6.4.1 **** I removed the plug-in but when I was updating the dockers one-by-one today, realized just how handy the Advanced Buttons plug-in is! It doesn't appear that the Advanced Buttons plug-in is still in the Apps tab so I couldn't re-install it there. My searching for it led me to this forum but based on zin105's comments I will not re-install it right now. I hope to see this plug-in updated and back soon!
  14. Nevermind. I rebooted the unraid machine and like magic the default image size prompt appeared....strange... :-)
  15. I am trying to increase my docker default image size and for some reason, I just can't seem to get it to work. Whenever I delete the docker.img file and then re-create it, the new file is always set to 15 GB. I need to increase that to 25 GB. Also, when Docker is disabled this error message is in the Docker version section: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 673 Couldn't create socket: [2] No such file or directory Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 673 Couldn't create socket: [2] No such file or directory Warning: array_merge(): Argument #1 is not an array in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 728 I'm attaching screenshots of the docker tab, in enabled and disabled mode in both the basic and advanced display. I have tried this in Chrome, Firefox and IE and they all (didn't) work the same way. Please let me know if you can spot anything that I'm missing or if there is an alternate way to increase the docker image. file Thanks in advance for your help! Scott