alhatmy

Thanks. I'm currently using two HBAs, but I'm not certain which ones.. Or it's from the motherboard. So far, I haven't made any changes and everything has been working for 12+ hours. Question: Can I initiate a new parity check now? Or should I remove and re-add the first parity "which was disabled and never completed building - to rebuild"?

Update; Implemented a New Config > Same slots > Parity is already valid. So far, it's been working fine for about 10 minutes. Could you explain what might have caused this issue and if it's likely to happen again? Question: Can I initiate a new parity check now? Or to remove and reads the 1st Parity (disabled and never complete the built)? I've also attached new diagnostics. tower-diagnostics-20241116-2229.zip

Hello, Two hours ago, two disks were disabled, so I followed the normal procedure: stop, remove, add them back, and restart. However, the same two disks were disabled again immediately, leading to all disks showing as unavailable. When I attempted this process a second time, the second parity disk also became disabled. Could you please help with this issue? I've attached the diagnostics tower-diagnostics-20241116-1948.zip

Thanks! When I called Etisalat, they were clueless about the static IP (perhaps because it's reserved for business accounts only?). What is the specific name of the service you're referring to? As of cloudflare, what links/ports must include please ?

(Output is anonymized, use '-vv' to see full details) Unraid OS 6.11.1 with My Servers plugin version 2022.11.29.0742 ✅ Signed in to Unraid.net as alhatmy Use SSL is no ✅ Rebind protection is disabled for myunraid.net Local Access url: http://Tower.local ✅ 192-168-12-56.hash.myunraid.net resolves to 192.168.12.56 Remote Access url: https://[redacted].hash.myunraid.net:[redacted] ✅ [redacted].hash.myunraid.net resolves to [redacted] Request: { "keyfile": "[redacted]", "plgversion": "2022.11.29.0742", "internalhostname": "Tower.local", "internalport": "80", "internalprotocol": "http", "remoteaccess": "yes", "servercomment": "Media server", "servername": "Tower", "internalip": "192.168.12.56", "externalhostname": "*.hash.myunraid.net", "externalport": "[redacted]", "externalprotocol": "https", "unraidreport": "{\"os\":{\"serverName\":\"Tower\",\"version\":\"6.11.1\"},\"api\":{\"version\":\"2.54.0\",\"status\":\"running\",\"environment\":\"production\",\"nodeVersion\":\"v18.5.0\",\"emhttpMode\":\"nchan\"},\"apiKey\":\"valid\",\"myServers\":{\"status\":\"authenticated\",\"myServersUsername\":\"alhatmy\"},\"relay\":{\"status\":\"connected\"},\"minigraph\":{\"status\":\"connected\"},\"cloud\":{\"status\":\"ok\",\"ip\":\"52.40.54.163\"},\"flashbackup\":{\"activated\":\"yes\",\"error\":\"no\"}}" } Response (HTTP 200): [] success

Thanks .. I'll ignore then Rebulding 2 disabled drives in the hopes that it won't occur again.

still ..

Nov 27 03:34:19 Tower nginx: 2022/11/27 03:34:19 [error] 11559#11559: *4553 recv() failed (104: Connection reset by peer) while reading upstream, client: 192.168.12.141, server: , request: "GET //wsproxy/5700/ HTTP/1.1", upstream: "http://127.0.0.1:5700/", host: "192.168.12.56" Nov 27 03:39:26 Tower nginx: 2022/11/27 03:39:26 [error] 11559#11559: *8135 recv() failed (104: Connection reset by peer) while reading upstream, client: 192.168.12.141, server: , request: "GET //wsproxy/5700/ HTTP/1.1", upstream: "http://127.0.0.1:5700/", host: "192.168.12.56" Nov 27 06:08:24 Tower kernel: Plex Media Scan[36737]: segfault at 0 ip 000014ba456374dd sp 00007ffefe255d00 error 4 in libavcodec.so.58[14ba45605000+292000] Nov 27 18:08:09 Tower kernel: traps: Plex Transcoder[1195] trap divide error ip:1521fb7d9139 sp:7fff24e564d0 error:0 in libavformat.so.58[1521fb76d000+302000] Nov 27 18:08:09 Tower kernel: traps: Plex Transcoder[1195] trap divide error ip:1521fb7d9139 sp:7fff24e564d0 error:0 in libavformat.so.58[1521fb76d000+302000] Nov 28 04:12:12 Tower kernel: Plex Media Scan[11717]: segfault at 0 ip 0000146478b294dd sp 00007ffc94f16650 error 4 in libavcodec.so.58[146478af7000+292000] Nov 28 04:12:12 Tower kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f tower-diagnostics-20221129-0140.zip

I attempted to upgrade two drives with more storage space, but I couldn't get the rebuld to start because of this (Unmountable: Unsupported partition layout). Had to stop the build, restart, and format the new drives multiple times to get them to work, but now they display No data! Is there an app to recover? And does this mean that there is no way to recover from parity using rebuld?

Thanks, I'll post again if it occurs

I've attached diagnostics; could someone please confirm if this is a hardware issue? The last time this happened was around a month back, when I discovered the unraid server was still running but everything was down. tower-diagnostics-20221030-0813.zip

I don't know how to make it work. It has something to do with blocked ports.

Thank you, but I've already followed every step.. I'm certain it has to do with 443 being blocked by the ISP.

Hello, is it possible to change the default secure port 443? Neither the remote connection nor the flash backup are possible. It's likely because port 443 is blocked; if it's possible to change it, please tell me how.

at least - how can I find the issue myself ?