diehardbattery

The flash drive I use now I think is several yrs old.. only 8GB... I cant imagine it's USB 3.0 I'll try a different port next time.. thats the only thing I have not tried... it had been several months since the last time before this so who knows.. I wouldnt have cared as much if I didnt have to rebuild the drive again...

So far no luck on the headers.. and not looking too hot for something that is USB 2.0 specific... guess I'll try a different port...

Gotcha. I checked the manual and it seems that all the ports on my nas are USB 3.0... The BIOS is not updateable but its never been a problem... maybe I need to find a USB 2.0 expansion card...

My NAS already has a DOM with the QNAP OS on it.. wonder if it could be repurposed for Unraid?

Once the rebuild is finished I'll double check, but I'm reasonably sure it's in a 2.0 port. My writes look similar to yours though...

I'm not sure what my problem is. Over the last 6 months I've had no less than 4 USB sticks of varying quality (ones that normally spend their life in a desk drawer, to recommended ones from other users, i.e. Samsung Bar) go corrupt requiring to shut down, pull the stick, insert it in my Windows PC, fix the errors and put back. It runs for a while, then rinse, repeat. It's mildly annoying but ok, whatever. What's more annoying is that this happened at some point last night, during a data rebuild. It's a 22TB drive that took 39 hours to do. When I checked this morning it said it was finished but had the dreaded flash drive corrupted message. I couldn't stop the array from the gui and thought it probably couldnt stop from the command line either because of the corruption. So I did a clean shutdown and fixed the drive and rebooted. The array was in a stopped state and warning that the drive that I just rebuilt was gonna be overwritten once I started the array. Maybe I should have just stopped there and researched if there is a way around that. But I figured the data might have been corrupted somehow anyway due to the flash drive issue, and started the array. It is now rebuilding the same drive a second time. 39 hours wasted. I'm not 100% discounting a hardware issue with my NAS (QNAP TS-873 that I've had now for 3 yrs), but the USB slots have only been used for Unraid and nothing else. I guess I could try another port. It's just frustrating because I have an 8 drive array and am replacing the drives one by one (It is the safest, correct? Unless there's a faster way?)...

Gotcha... time will tell but so far so good. Thank you.

Okay, but why would it just start all of a sudden having issues? Everything was fine until the 6.12.2 update? Also if you could please remove my hostname from your message? I wasn't sure if unraid anonymized it or not.

I upgraded to 6.12.3 because I was having the /mnt/cache issue. That seems resolved at least. But I'm still losing the webui.. more often now it seems. I've also tried accessing from another PC on the lan with the same result. I mirrored the syslog to flash and have attached it. No errors found on the flash drive. Question though. I am trying to rebuild parity which is going to take close to 48 hrs.... if I lose the webui again should I just wait it out until I know the parity rebuild should be finished? It's getting frustrating to reboot and start over every time I lose the webui.... syslog

Okay, that worked for me. Thank you.

I have been trying to figure out the whole syslog server thing and have setup something remotely. Also I discovered one of my parity drives was failing (thought maybe that's what was causing it), so I was waiting to replace it. I have replaced the parity drive and it is currently rebuilding but I crashed again. I've been using Kiwi syslog Service Manager on my PC, monitoring the Unraid server. I created a tech support file with it. Hopefully that helps. Syslogd_TechSupport.zip

Well when I connect to Tailscale, I am expecting to access my shares via local ip. I am new to using vpn to remote access the nas so maybe I'm not doing it correctly.

Done tailscale-diag-20230714-175609.zip

I did have the docker container installed, but uninstalled when I did the plugin.. not sure why it would show in the diagnostic... I've attached a fresh diagnostic for good measure. diagnostics-20230714-0841.zip

Here you go diagnostics-20230712-2356.zip

I was able to get it installed.... however after running tailscale up and registering I dont seem to be able to access anything using mobile data as a test connection...

Thanks. I'll probably just play it safe and replace one at a time.

Got the feeling I'm doing something wrong. The plugin doesn't seem to want to install? It shows pending on the apps page, and manually installing from here doesn't seem to to do anything?

So Unraid (6.12.2) is currently reporting one of my current parity drives as having smart errors (even though a short test passes). I have 8 WD 8TB mybook drives total (2 parity, 6 data). Given their age, I am going to take the opportunity to replace and expand the array with 8 Ironwolf Pro 22TB drives (I like space LOL). From what I've gathered, the replacement process seems fairly straightforward. To clarify and check my sanity, this is how I am seeing it done: Stop the array. Unassign the parity drive with errors. Shut down NAS, replace with 22TB drive. Power on NAS, assign 22TB drive as parity, start the array and rebuild. Rinse, repeat for second 22TB drive. For the data drives, do they also need to be replaced 1 by 1 or can I replace them all once the array is rebuilt with the two 22TB parity drives?

Seeing a bit of an odd issue where after about 24 hrs, I cannot access the webui of unraid. The browser just spins. I can access my shares and everything else seems normal. However when I run /sbin/reboot it gets stuck on forcing shutdown requiring me to manually power off my server. Anyone else having this? diagnostics-20230706-0006.zip

I'm in the same situation as OP. So now I have to wait for support to fix it which means my NAS is useless until then. This is not acceptable. Why is this even a thing? Even recommended flash drives can fail within a year's time. My USB just failed (I can't remember if it's been less than a year).

Thank you!

I'm having this issue as well... however I don't know much about troubleshooting/fixing things like this. Can you ELI5 what you did? Thanks!

I'm usually pretty good at following guides to set up things I'd like to have/use. But, when something goes wrong, especially for networking, I'm apparently not yet good enough to troubleshoot it properly (but hey, I can plug and unplug an ethernet cable?), so here we are... I am doing my best to document every step I have taken thus far, so apologies if it's incomplete. Currently I am stuck with what appears to be a port forwarding situation on my OPNsense router with regard to SWAG. I get a 502 when trying to access the subdomain from either LAN or another WAN (Verizon Wireless from phone). I can hit the SWAG Welcome Page when trying to access the root domain from another WAN (also Verizon Wireless from phone) but not from LAN. I am trying to figure out the correct sequence for OPNsense. What I've tried so far with OPNsense: Sequence: WAN interface ANY > WAN ADDRESS > TCP 80/443 > 18001/18443 > (Unraid IP)/32 (1 entry each). In other words, I have port forwarding rules for 80 and 443 from ANY, to WAN address, then forward as ports 18443 and 18001 respectively to the Unraid server with a /32 CIDR. Enabling or disabling NAT Reflection (hairpin NAT?). Filter rule association set to pass. For NAT Outbound, I have it set to hybrid due to having rules for my gaming consoles/upnp. What I've tried so far for Cloudflare: Turning proxy on/off for the domain/subdomains. Purging the site cache. Changing SSL/TLS encryption modes (Full and Full Strict). What I have done with SWAG: Consulted with linuxserver.io SWAG page under troubleshooting 502 errors: port unchanged except for upstream_port and upstream_app match the guacamole container (see conf below). Recreated relevant conf parameters for auto proxy in the ApacheGuacamole Docker template (added labels for swag=enable, swag_port and swag_url). My guacamole.subdomain.conf: ## Version 2021/05/18 # make sure that your dns has a cname set for guacamole and that your guacamole container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name guaca.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app ApacheGuacamole; set $upstream_port 7575; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_buffering off; } } The nginx error log says this: [error] 8002#8002: *6 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xx.xx.xxx, server: guaca.*, request: "GET / HTTP/2.0", upstream: "http://172.18.0.2:7575/", host: "guaca.xxxxxx.io" Where client is my WAN IP, guaca.* is my subdomain (with CNAME pointed to @), 172. address is the custom docker network. If the problem lies within SWAG, I'm not sure what is not correct as there are no errors in the logs. If it is within OPNsense, I'm also not sure about that as it looks correct to me. Any other combination of port forwards (i.e. reversing the ports, doing 443/80 for everything, etc) gets a 522. I know something is not right, but I am not experienced enough to determine what. I wish I knew what to do next... hopefully someday I will lol...

If I want to bypass the tunnel for a particular subdomain, is it as easy as setting said subdomain to dns only assuming the tunnel passes everything to swag/npm?