eubbenhadd

Members
  • Posts

    25
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

eubbenhadd's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. ugh. I tried steps 2 and 3 to no avail. 2 worked to take me to the final build of 17.x but from there i get the can't install major upgrade... I tried step 3 to manually upgrade to v18 instead of the latest build and it also failed, but when I try step 2 again, it reports as follows with two conflicting versions then I get the can't install major upgrade error. HELP! ---------------------- Nextcloud Updater - version: v18.0.9-8-g27dac77 Current version is 18.0.14. Update to Nextcloud 17.0.10 available. (channel: "stable") Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-17.0.10.zip Open changelog ↗ Steps that will be executed: [✔] Check for expected files [✔] Check for write permissions [✔] Create backup [✔] Downloading [✔] Verify integrity [✔] Extracting [✔] Enable maintenance mode [✔] Replace entry points [✔] Delete old files [✔] Move new files in place [✔] Done Continue update? [y/N]
  2. Argh. Ran through the excellent tutorial and had no success. Can not access the webUI. Got the following log. Have tried setting key 5 (interface) to both eth0 and br0, no luck. Have bonded interface (active balanced 1) with bridging enabled. Docker is set up with separate IP (different from server). Any help GREATLY appreciated! EDIT: I notice on some other startups (from other people), there's this line but it doesn't show up on my install (which I've now tried re-installing, no difference) Pi-hole blocking is enabled LOG ------------------ s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11) nameserver 127.0.0.11 options ndots:0 Existing PHP installation detected : PHP version 7.0.33-0+deb9u8 Installing configs from /etc/.pihole... Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! chown: cannot access '': No such file or directory chmod: cannot access '': No such file or directory chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory ::: Pre existing WEBPASSWORD found Using custom DNS servers: 1.1.1.1 & 1.0.0.1 DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "192.168.15.2", "VIRTUAL_HOST" => "192.168.15.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete ::: Pre existing WEBPASSWORD found Using custom DNS servers: 1.1.1.1 & 1.0.0.1 DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "192.168.15.2", "VIRTUAL_HOST" => "192.168.15.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete [✗] DNS resolution is currently unavailable [✗] DNS resolution is currently unavailable
  3. Argh. Ran through the excellent tutorial and had no success. Can not access the webUI. Got the following log. Have tried setting key 5 (interface) to both eth0 and br0, no luck. Have bonded interface (active balanced 1) with bridging enabled. Docker is set up with separate IP (different from server). Any help GREATLY appreciated! s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11) nameserver 127.0.0.11 options ndots:0 Existing PHP installation detected : PHP version 7.0.33-0+deb9u8 Installing configs from /etc/.pihole... Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! chown: cannot access '': No such file or directory chmod: cannot access '': No such file or directory chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory ::: Pre existing WEBPASSWORD found Using custom DNS servers: 1.1.1.1 & 1.0.0.1 DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "192.168.15.2", "VIRTUAL_HOST" => "192.168.15.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete ::: Pre existing WEBPASSWORD found Using custom DNS servers: 1.1.1.1 & 1.0.0.1 DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "192.168.15.2", "VIRTUAL_HOST" => "192.168.15.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete [✗] DNS resolution is currently unavailable [✗] DNS resolution is currently unavailable
  4. REALLY stupid question. I set this up fine a few weeks ago and have totally forgotten the password so I wanted to just re-create the VM. Thing is I can't even delete the existing VM so I can re-run the app to create a new one. Appreciate any assistance.
  5. Got it worked out, turns out there was a separate bridge set up, not sure how, but I changed the name in the VM and it worked. Thanks!
  6. Nope, haven't set up jack for VMs, I don't even have any other VMs set up anymore.
  7. Got to the part where I can start the VM, and I get the following execution error: "Cannot get interface MTU on 'br0': No such device". Nothing useful in the VM log. Any suggestions? ------------- Supermicro X10SL7-F v1.01 Intel Xeon E3-1230 v3 16gb DDR 3 ECC
  8. So went through the steps and getting some weird stuff now.
  9. Sorry, one last question. At what point should I physically remove the bad drive?
  10. Thanks! Does it make a difference if I'm removing from a 2-device pool?
  11. @Johnnie.Black I'm also wanting to remove a drive from a 2-drive pool. My first device seems to be corrupt (has a ton of read errors that are unfixable). Had a couple of questions: 1) should I follow the instructions you referenced in the UnRaid v6 FAQ or use the command line instructions in this post? I'm not sure if I want to replace the bad drive with a new one or just stick to a single cache drive setup
  12. FWIW I have the same timeout issue starting with 6.4.1. Didn't have it on 6.3.x and was hoping 6.5.0 would fix problem.
  13. I had the timeout issue on 6.4.1. I'm trying to decide if 6.5.0 is better or worse