• Posts

  • Joined

  • Last visited

Everything posted by perfect

  1. Thanks for the prompt response! I actually still have a lot of available storage left on my array and am avoiding buying a new HD (at current prices). I'm only at 50% storage usage on my 30TB array - and this particular drive is only using 1.5TB total. Is there a way that I can safely transfer the 1.5TB data from this disabled drive onto another drive and simply unmount disk3? I will then remove it from the array permanently and let the data live on the rest of the array. Is there a procedure for this?
  2. I've attached the diagnostics file - thanks!
  3. Hello! I am running Unraid v6.8.3. I recently experienced a disabled disk in my array. The contents of the disk appear to be intact (I can still navigate into the disk and access the files). I have several other available disks that I can transfer the data onto. I plan to remove this disk since it's apparently having [reallocated] sector errors. I read several threads on the topic and most link to a deleted page: I'm happy to post any logs - but wanted to check here first so that I don't lose any data or screw up my array.
  4. I'm running Unraid OS Pro v 6.8.3 and have been using the Home Assistant (HASSIO) VM almost flawlessly this entire time. I am using SWAG as a reverse proxy (with duckdns). Occasionally, I have had instances where I couldn't connect to my Home Assistant VM (maybe once a month), but a quick reboot of the VM always solved the problem. Today, however, I have not been able to connect to my Home Assistant VM at all. I can see that the VM is grabbing an IP address (it shows up in my Unifi Controller), but I can't access the HA GUI via my external duckdns link or even my internal IP address. I can run the console (left click on the VM > VNC Remote) for HA... so I'm pretty certain that Home Assistant is actually running. When I run an external port checker test on the 8123 port, it says it's closed (I'm certain it used to say open) but... my internal IP address doesn't work either. I can confirm that I do have the port forwarding still setup in my Unifi Controller. I'm stumped... I haven't changed anything my Unraid config, HA configs, or even my Unifi Controller in a long time. Any ideas on where to begin troubleshooting next? Thanks!
  5. Has anybody experienced an issue where SWAG (formerly "LetsEncrypt") will inexplicably stop resolving the secure connection when using duckdns? I've been setting up Bitwarden using SWAG as my reverse proxy. I've properly forwarded my ports and I'm confident that I've correctly configured SWAG, BitWarden, and the necessary .conf files. I will check the SWAG log and it will say "Server Ready" for all of my duckdn subdomains. Life is good. I can access BW from my internal computers, my phone, and my work computer. Then, things will just stop working... I can no longer access BW using the duckdns link. The log file will start saying "Certificate Not Found, etc". Nothing has changed in my config... I'll restart my router, the NAS, and restart the SWAG docker a few times. Then - just as I'm pulling my hair out - I'll go for a run or walk the dog and come back to find that everything is working again. Is duckdns not reliable? Is anybody else experience this issue?
  6. I'm following SpacedInvaders Reverse Proxy setup video and am running into issues with the validation test (like many others). I have setup a subdomain. I have attempted to forward the 1443 and 180 ports in my Ubiquiti USG Pro-4 router. However, I'm getting the same validation errors that many others get ('cert does not exist, check port forwarding or dns'). I notice that when I use a port checking utility online, that my 1443 port is never actually "open" - even though I'm certain I have the port forwarding rule setup correctly (pointing port 1443 to port 443 on the unRAID IP). Any advice where to start troubleshooting? I'm doing this to setup the BitWardenRS docker. I'm using the latest SWAG docker, but I updated the config file to point to ports 180 and 1443 (just like in the video).
  7. Thank you both for the help and guidance! I realized that I still had an active port forward to my previous IP (when I was running HA as a VM on my Win7 machine). I deleted the old/unused Port Forward rule and then made the HA VM (via Unraid server) the primary port forward IP and it completely worked. It looks like my Unifi controller can't have more than one IP assigned a port forward rule (which makes complete sense...) SOLVED
  8. I am trying to correctly setup port-forwarding for my Home Assistant VM via Unraid. I have manually set a static IP for the HA VM ip (via Unifi router... using the MAC assigned from the VM), but I cannot access HA from the external IP. Testing the port forwarding continues to tell me that the port is closed. My Unraid network settings are as follows: Enable Bridging = Yes br0 Routing Table = (Metric 210) My HA VM is set as follows: Network Bridge: br0 Note - I can access the internal (local) IP of Home Assistant without an issue. So the issue is definitely that port-forwarding is not working correctly. I suspect that either my Unraid network settings aren't correct - or the VM isn't configured to use the network settings correctly. Thanks for the help!
  9. Frank, Thanks very much for the support. At this time, I ended up just using a different computer (mobo+CPU) since I was tired of fighting the Gigabyte/Athlon combo. I now successfully Unraid installed (albeit, not on the computer I originally intended). It is still strange why the boot sequence never initiated, but would for any other USB boot drive I tried to install. The new computer booted up with all of the USB drives correctly, so I'm still not convinced it was an issue on my end (but I'm a newbie, so who knows?!). I do believe that I followed the manual method correctly, but I don't remember specifically (I tried and tested quite a few different combinations). I had a variety of different USB drives - Kingston, Samsung, Sandisk, and some other generic varieties. Thanks again for the help! I'm happily running Unraid and diving into all of the quirks and features!!
  10. Frank - I tried both ways (it was originally EFI- so I renamed it to just EFI and it still didn't boot. Note - I'm also trying all of my USBs (5 of them) with a different machine and it still doesn't work. THIS IS NOT A BOOTABLE DISK. PLEASE INSERT A BOOTABLE FLOPPY AND PRESS ANY KEY... I can't win 😞
  11. I've tried with a 16GB stick and it still didn't work... not sure I have much smaller
  12. I loaded up FreeNAS/TrueNAS on the same USB stick and it starts the boot sequence after the BIOS posts. I'm convinced this has something to do with the Unraid boot sequence or boot files. Anybody ever see this before and have a fix?
  13. Another update... I tried using the manual method as outlined in the documentation (wiki) and was still not successful after following the steps. My computer is definitely recognizing the USB drive and attempting to find something bootable. If I don't plug in any USB it will bark at me after a few seconds that NO BOOT MANAGER FOUND... (or something to that affect). With the USB in place, it just sits there trying to do something but never does.
  14. Hello all! I'm facing a frustrating challenge towards getting Unraid 6.8.3 installed on my Gigabyte motherboard. I cannot get my Unraid USB to actually install anything after the BIOS post. At first I was convinced that this was an issue with Gigabyte motherboards (there are countless threads out there related to this exact topic)... However, I have no problem using the same USB drive that has any other Windows and Linux distro on it. My computer is definitely recognizing the USB - but doesn't ever actually start the installation after being found. I've read from some users that they used Rufus to write to their USB drive (and enabled the "Legacy / OLD Bios" support options... but I can't figure out how to use Rufus to accomplish this. It doesn't look like Unraid has an .iso option...? Is there another way to get Rufus to work for this? I'm now confident that my computer can, in fact, boot from USB... it just doesn't like the Unraid installation? I'm trying to install Unraid 6.8.3 using the Unraid USB Flash Creator (v1.6). I am NOT selecting the UEFI option (as my mobo doesn't support this). I'm writing to a Samsung 32GB USB and the write portion is deemed successful. Is there something that I need to modify with the installer files on the USB stick?