chiaramontef

Just posting this so others might benefit. My 36 hours of struggle getting my Unraid server to boot back up isn't the star of the show here, but found the flash drive process to be extremely finicky and wanted to share "what worked for me". Currently running 6.9.2, but don't think think that's pertinent here. Some things that happened to me that have been covered in other posts: I noticed a licensing error in Unraid, essentially my flash was offline entirely. Rebooting seemed to correct the issue, however, only temporarily. Further licensing errors and rebooting resulted in "bond0" not found (using mode 6), which there have been lots of posts about on older and some new versions than what I'm running. Inevitably, this was an issue with my flash drive going bad, diagnostics couldn't be written and configurations from the /config directory weren't applied so when I did boot from my "bad" flash drive I would just be stuck with an APIPA address (169.254.x.x.). One of the key tells here, among others, since "bond0" can be a bit of a red herring is trying to capture diagnostics. You can run the command by simply typing "diagnostics" without quotes into the command prompt and you'll get the expected feedback, but when you remove the drive and put it in another computer in an attempt to read or upload the logs, you'll see nothing was actually able to be written to the drive. I had an unused/same Sandisk USB 3.0 16GB Ultrafit drive that I purchased 8 years ago, with the original one that had been running fine for the previous 8 years, but after applying the backup to this one, same issue, "bond0" can't write diagnostics, yadda yadda. Yes, I'm aware 3.0 not needed, but working fine and from the same 2-pack that I purchased long ago for this very reason. Using the flash creator tool or the manual copy/paste "make bootable" made no difference. Using a 2.0 USB port vs. a 3.0 port also made no difference. Every other, albeit very old, flash drive I had laying around and tried, nothing worked. Either couldn't use it or if I could, same error "bond0". I found it hard to believe that all my drives were bad, but knowing my newest one was 8 years old, I decided to pick up some new drives. I wasn't experiencing any other hardware issues on my server at least so I went to the store and picked up a few different varieties to ensure I was covered. Keeping them all at 32GB or less (for FAT32). Picked up some Lexar (USB 2.0/32GB), Sandisk (I know the history here, but purchased anyway, 32GB USB 3.0). Inevitably I got it working on the Lexar, here is how: The official flash gui didn't work, even though there were no errors on the process. After I put my backup on there I kept getting can't find boot disk messages. (Double/Triple checked all boot settings and boot devices). My Lexar flash was being picked up fine in the BIOS and the only bootable device. Also ensured fastboot=off, no dice. The manual process didn't work, again even though successful, after formatting FAT32 and labeling "UNRAID", and successfully running makebootable.bat with no errors, still didn't boot. Through all of this, it's not worth going into detail, but I did try different versions and restore points, none of which helped. Tried different varieties of only copying bz* files or just my config folder when the situation called for it. What did help and what I'm hoping might help others, was Rufus 4.1. I know that has been covered to some degree in other posts, but what worked for me was a bit different that what I found at least. Solution: I used my Lexar (32GB/USB 2.0) drive (port didn't matter) and Rufus 4.1 with the following settings: Boot selection "Syslinux 6.04 w/MBR partition BIOS (no UEFI for me, older server) I did tick the box to add fixes for older BIOSes Volume Label "UNRAID" of course and FAT32; quick format is fine. Then I merely copied all my files from my most recent backup except for ldlinux.sys and ldlinux.c32 Put the drive back in my server and it booted right up without issue, right to the Unraid bootloader menu, then successfully to my login prompt. No more "Bond0" messages which is definitely a red herring, but at least a well documented one. At this point, I'm not messing with it for a little while, but I am interested to see if this method works on some of the other flash drives I had laying around. Hope this helps!

Awesome! Thank you!

Hi All, Does anyone happen to have the .zip for version 6.9.2? The site only goes back to 6.10.3 and 6.9.2 was the version I was running before things got messy. Thought I would try something before reaching out for additional help. Thanks, Frank

I'm having an issue and I'm not really sure where to start. I'm not even 100% certain it's an issue with letsencrypt, which I run as a docker on UNRAID. Anyway, here is my situation. I recently moved, all infrastructure (unifi) moved with me, including my ATT gateway. Everything was shutdown at my home before I moved and I just booted everything back up (about 2 1/2 weeks later) at my new location. I have everything back up y and running again, all settings and configs are the same, including my WAN IP. All my dockers are up and running and fully functional except I for that I can no longer resolve any of my external applications that utilize letsencrypt with nginx reverse proxy. I can ping and resolve my domain name fine, and can even access PLEX externally, but nothing that was fronted by the letsencrypt docker seems to work, about 8 applications in all with the same generic error. No status code, nothing, just a "domain name" refused to connect message followed by a ERR_CONNECTION_REFUSED. Has anyone experienced any similar issues before where everything just stopped working? Thanks for any input.

Great catch. That was a facepalm moment, thanks for the help!

Originally, I only had 443 and 32400, but I've since added 80 & 81 to troubleshoot the issue. No luck. Here are the screenshots you requested. Thanks for taking a look.

Can anyone help with this? I updated letsencrypt today and now nothing is working. No other changes have been made. It's as if everything is trying to go over 8443 (which is what my UNRAID server is set to since there was a conflict between letsencrypt 443 and UNRAID 443. This is the error I'm getting: 2048 bit DH parameters presentSUBDOMAINS entered, processingSUBDOMAINS entered, processingSub-domains processed are: -d nextcloud.xxx.com -d office.xxx.com -d apps.xxx.comE-mail address entered: [email protected] validation is selectedGenerating new certificateSaving debug log to /var/log/letsencrypt/letsencrypt.logPlugins selected: Authenticator standalone, Installer NoneObtaining a new certificateSaving debug log to /var/log/letsencrypt/letsencrypt.logPlugins selected: Authenticator standalone, Installer NoneObtaining a new certificatePerforming the following challenges:http-01 challenge for apps.xxx.comhttp-01 challenge for xxx.comhttp-01 challenge for nextcloud.xxx.comhttp-01 challenge for office.xxx.comWaiting for verification...Cleaning up challengesFailed authorization procedure. apps.xxx.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://xxx.unraid.net:8443/.well-known/acme-challenge/xxx: Invalid port in redirect target. Only ports 80 and 443 are supported, not 8443, office.xxx.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://xxx.unraid.net:8443/.well-known/acme-challenge/xxx: Invalid port in redirect target. Only ports 80 and 443 are supported, not 8443, nextcloud.xxx.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://xxx.unraid.net:8443/.well-known/acme-challenge/xxx: Invalid port in redirect target. Only ports 80 and 443 are supported, not 8443, xxx.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://xxx.unraid.net:8443/.well-known/acme-challenge/xxx: Invalid port in redirect target. Only ports 80 and 443 are supported, not 8443IMPORTANT NOTES:- The following errors were reported by the server:Domain: apps.xxx.comType: connectionDetail: Fetchinghttps://xxx.unraid.net:8443/.well-known/acme-challenge/xxx:Invalid port in redirect target. Only ports 80 and 443 aresupported, not 8443Domain: office.xxx.comType: connectionDetail: Fetchinghttps://xxx.unraid.net:8443/.well-known/acme-challenge/xxx:Invalid port in redirect target. Only ports 80 and 443 aresupported, not 8443Domain: nextcloud.xxx.comType: connectionDetail: Fetchinghttps://xxx.unraid.net:8443/.well-known/acme-challenge/xxx:Invalid port in redirect target. Only ports 80 and 443 aresupported, not 8443Domain:xxx.comType: connectionDetail: Fetchinghttps://xxx.unraid.net:8443/.well-known/acme-challenge/xxx:Invalid port in redirect target. Only ports 80 and 443 aresupported, not 8443