NeoMatrixJR

Members
  • Posts

    53
  • Joined

  • Last visited

Everything posted by NeoMatrixJR

  1. Yeah...I can't find much past that. Dd failed 141...what does that mean? anyone know? I haven't found a good answer to that yet.
  2. found 'em. Only interested in logs pertaining to sdi at the moment. Logs still don't tell me much...either I don't know how to read them (good probability) or they don't detail the problem well enough for me to spot it. THECONSTRUCT-preclear.disk-20180503-1255.zip
  3. Is there a log or part of the log that details why a preclear failed?
  4. sdh is indeed the failed drive. I assume the CRC errors would carry over (stored on disk) from previous use. They've only been plugged into this machine for a couple days and they're now on my r710's backplane. One was in my desktop PC for YEARS, but I was noticing some issues with that drive recently...May have been loose/bad cable recently... The other was previously in an external USB case (HGST TOURO drive). The drive quit working and I shucked it for diagnosis and possible re-use. Seems like the USB controller went bad IMHO. The drive wouldn't even come up before, but no issues once plugged directly into sata.
  5. Attaching diagnostics.... Am I missing it or is there a further log on the preclear? I'm wondering if there's any more information than just that it fails.... This goes to @Kode - Sorry...I started writing this before you responded. I'm not sure what the failure was...it just says failed. @Sean M. - Preclear script: gfjardim - 0.9.5-beta. Plugin version is whatever one CA installs by default right now. theconstruct-diagnostics-20180427-1108.zip
  6. I'm still running 6.4.1 for now...I had a boot drive failure the other day and recovered from that other than a few corrupt docker templates. Now I've had my first actual drive failure in the array. I was getting a couple of disks prepped to add to the array when my 3tb drive hosting much of my data failed. I tried running preclear on the two drives I'm adding (used, from other systems) and they both fail post-read. I've read that preclear isn't necessary anymore, and some skipped the pre/post reads. I've managed to move all data from the failed 3TB drive to other drives in the array (disk is in emulation). SMART reads fine for both "new" disks (a 2TB and a 4TB) except yellow banners on UDMA CRC error count...can I add them to the array? Do I need to worry that they failed preclear? I'm running extended SMART tests on them now.
  7. My apologies if I missed this or the answer should be obvious, but is there any way to put my VPN clients on the same subnet as the rest of my LAN pc's or assign IPs from my router's DHCP? I have applications that look for 2 machines to be on the same LAN (or as some state...on the same WiFi <facepalm>) and they won't work over VPN in my current configuration. Also, should I want to expand beyond 2 clients...is there a different...non-AS docker I should be using?
  8. any way to specify if you want canary build? I ran an update on mine to canary, then it downloaded the latest docker image and now I can't get into the web interface...it says "the database has version 5 but the largest supported version is 4"
  9. Any chance you've had time to take a look at this? Not a big deal right now...just remembered this is on my "to fix" list.... Thanks!
  10. Got it sorted...kind of. Transmission VPN docker was eating all traffic forwarded from my router to my server....not sure how to fix yet except turn off that docker...which hasn't been used in a while...so that's fine for now.
  11. Running your Transmission VPN docker...whenever it's up and running it seems somehow it's eating traffic directed at other dockers. Running nginx on container 80, host 8081, and traffic forwarded from 80 --> 8081 on my router...no traffic ever reaches my nginx docker while transmission is up. Oddly, it's only external traffic. Traffic from within my network directed at 8081 gets to the appropriate docker fine.
  12. Docker Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="America/Chicago" -e HOST_OS="unRAID" -e "EMAIL"="<redacted>" -e "URL"="<redacted>.us" -e "SUBDOMAINS"="www,<sd1>,<sd2>" -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="2048" -e "VALIDATION"="http" -e "DNSPLUGIN"="" -e "HTTPVAL"="true" -e "PUID"="99" -e "PGID"="100" -p 8080:80/tcp -p 4343:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt Forwarding Container 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] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=redacted.dns SUBDOMAINS=www,<sd1>,<sd2> EXTRA_DOMAINS= ONLY_SUBDOMAINS=false DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=<redacted> STAGING= Backwards compatibility check. . . No compatibility action needed 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Sub-domains processed are: -d www.redacted.dns -d <sd1>.redacted.dns -d <sd2>.redacted.dns E-mail address entered: <redacted> http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for <sd2>.redacted.dns http-01 challenge for <sd1>.redacted.dns http-01 challenge for redacted.dns http-01 challenge for www.redacted.dns Waiting for verification... Cleaning up challenges Failed authorization procedure. www.redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.redacted.dns/.well-known/acme-challenge/edxukoZRwU7EPlVpHFg142PTBBrqyU2G94dp_KmApA0: Timeout, redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://redacted.dns/.well-known/acme-challenge/hMixnVqD8nuDQ8WFP4rYw2NL-lWDNx-gqifbSt0Yy8Y: Timeout, <sd1>.redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://<sd1>.redacted.dns/.well-known/acme-challenge/gjtxzSA3iVJOr5-uEKmtJaFH_1F-u9aG1g_03Km8fYI: Timeout, <sd2>.redacted.dns (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://<sd2>.redacted.dns/.well-known/acme-challenge/IzNN34bA1ALo-7NdbqWlN63vQNvvo4PP-pvea9FCpKE: Timeout IMPORTANT NOTES: - The following errors were reported by the server: Domain: www.redacted.dns Type: connection Detail: Fetching http://www.redacted.dns/.well-known/acme-challenge/<redacted>: Timeout Domain: redacted.dns Type: connection Detail: Fetching http://redacted.dns/.well-known/acme-challenge/<redacted>: Timeout Domain: <sd1>.redacted.dns Type: connection Detail: Fetching http://<sd1>.redacted.dns/.well-known/acme-challenge/<redacted>: Timeout Domain: <sd2>.redacted.dns Type: connection Detail: Fetching http://<sd2>.redacted.dns/.well-known/acme-challenge/<redacted>: Timeout To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
  13. have LE docker on unRAID 6.4. Was working previously...checked it yesterday and no joy. Attempts to http validate my domain/subdomains fails. Can't connect via HTTP. Firewall/ports/etc. set up ok (was working previously). I docker exec'd in to bash and I can't see that nginx is even running or listening on any ports. Did a config backup, full remove/remove image/wipe config and re-install...still no joy. HELP!
  14. I'm trying to get a camera to create a video device in linux. Device: Bus 001 Device 026: ID 04fc:6350 Sunplus Technology Co., Ltd Supposedly I need to be able to modprobe gspca_sunplus.
  15. So...for the docker inept (outside of using CA to get and install dockers) can you explain how to do the build on unraid? Do I need to navigate to a specific folder? Any specific commands to get the image where it's supposed to be? Can you explain more about "providing you've setup a docker.img file"? Is that the one that exists on the system if I'm using dockers or will that be a docker image for the docker file I'm building?
  16. 4th, 5th, and 6th time! All over the weekend. Definitely a hardware issue, and not the drive. I plugged it into my pc via USB and everything is fine on the drive. My options were either build a really janky power cable and keep my 2.5" SSDs and try to make that work, or find a better solution. Finding that the r710 onboard sata is ATA only not AHCI sealed the deal. I bought a pcie -> 2x M.2 + 2xSata board + 2x 256GB SSDs + a 2x esata -> Sata bracket (for my external blu-ray drive). Going to fix this the right way and get redundancy set up for cache.
  17. Thanks for the input. Since I swapped at purchase time I can still swap it at any point right now. I figured if it does fail I'll get a hold of a good one. MB ROM files? I was mostly going by how little space my existing install was taking up, so if I need to consider more I'll have to re-evaluate.
  18. Thanks! Got it bought. Needed to change USB...did trial on 8gb drive that was just going to waste in there...moved to freebie 1gb that ironically has Microsoft's name/logo on it! Everything looks like it's set right. Have array up in maint. mode for now and running checks so I can't check dockers and such yet, but looks good so far!
  19. My trial ran out and I was forced to reboot. Now it's time to buy. I installed 6.3.5 on a different stick that's also registered for a trial (had been testing some stuffs on it). Can I copy my stuff over from my main stick to the new stick and register it with all my "production" settings intact? I copied over *most* of my config directory including disk config and it *looks* like almost everything set back up properly except none of my drives are listed in my array. I don't want to just put them back in manually and fire it up for risk of losing data. any way to get it to read my old config?
  20. Ok, thanks everyone...I have different issues now I suppose so I'm going to open a different thread. I'll keep the items here in mind moving forward.
  21. Can't do anything now until I get home and get my new USB created and buy my license. I hope that process is automated or no plex until I'm back online.
  22. Thanks! Sorry I didn't follow up on the last one...Most likely it's because I didn't realize started topics don't auto-set subscribe so I lost track of it after I got it working. I caught that this time around and will watch for it in the future. 1.) Hardware issue... I've got an idea to help with this but I'm running a Dell r710 with proprietary cabling. I'm working on a solution for this though. Is there any way to get the system to re-check/reinitialize the drive while running? A reboot tends to seem to fix this and it happens rarely. (so oddly inconsistent for a hardware issue IMHO...), but I wish I didn't have to shut down to fix. Granted, I'm now out of trials so it won't matter anymore. Now I have to buy and reboots won't matter so much now. 2.) docker FAQ - Hadn't seen that, but will dig in ASAP.
  23. Ok, I've run to the end of my last extension. Oddly enough it seems my cache always dies just past my trial license...requiring a reboot. Debating if I should purchase unRAID now or move on because of this issue. It causes my dockers and VMs to die and I have a fair few of them. The really odd thing in the logs is the BTRFS errors...and I'm not using BTRFS. All drives (except boot) are XFS. (boot is vfat) Diagnostics are attached. My plan, over the weekend, was to move to a new USB stick, buy a license, and then upgrade to 6.4. Now I'm not sure what I'm going to do. There's a good chance this might just fix again after a reboot or two (last time one reboot ended up with all my shares missing...then coming back on reboot again??? Dunno what happened there...) but I can't keep doing this. Hardware is a Dell r710 with dual hex-core Xeon CPU & 24GB Ram. Running a Perc H310 in IT mode for HBA. Array is partially populated by various SATA disks...whatever I could scrounge up that worked with a shiny new 4tb drive for parity and another 4tb +others for data. Cache is an Intel 180gb SSD in an optical tray in the server for now until I can get around the limited power hookups in the r710. theconstruct-diagnostics-20180119-1026.zip
  24. I've had this happen to me twice now. I've seen suggestions that it could be as simple as a bad SATA cable, but running in an R710 makes it difficult for me to test that at this time. (proprietary SATA cable and SSD sled for the optical bay) Your drive is readable, create a space on the array, and copy everything over as a backup. Reboot. I found that typically a reboot reset the error state and everything was happy. The first time I swapped the drive and later learned that there was no need as the drive was still good. Thankfully I had access to a spare. ---aaaandd mine just hosed up again too.