withthePH

@JorgeB thanks for that info. it's great that there is a remote system log setup. I will get that setup for the second unraid server. more to come!

I am at a loss here and not sure what's causing the server to completely be unaccessible with docker services all down after about 10-14 days of no issues. I am attaching my diagnostic and hoping that it caught something. I am able to SSH when WebUI is down. phnas-diagnostics-20260402-1157.zip

I am realizing something.. how does this sound to keep it clean? I'm planning to disable Docker/VMs, and then manually remove the old .cfg files for the failed shares from the flash drive's /config/shares/ directory before doing the New Config. I'll keep the appdata and system configs so they stay mapped to my NVMe. then I'll just recreate the data shares fresh in the UI. Does that sound like a solid 'clean slate' approach?"

awesome, this is great news. since the most important share (appdata) is on my NVMe and that cache pool is still healthy, it sounds like the transition will be smoother than I feared. one quick follow-up: what happens to the 'Include Disks' settings for my old shares now that those physical disks (like Disk 1, 2, 3) no longer exist in the new array? will Unraid automatically ignore the missing disk IDs, or should I manually 'Clean' those settings to avoid errors?"

New question! I got new eight 6TB disks pre-clearing, I’m wondering what the best steps are to take. I’m currently manually copying the sole surviving 12TB Seagate data to my other Unraid server and plan to use that as the new Parity. I assume I need to create a new configuration with 12TB as the Parity and the rest as array disks. Do the previous Shares get preserved? I am guessing no. So then, do I recreate them as how they were setup before and my dockers will be happy again? No VMs. I really appreciate any help you can provide to make this transition as smooth as possible!

I was already running the 3.3v SATA Power Cable Mod on the SATA extension cables, per this guide, so my guess is that all the WD drives are toast then... I had my old Lantech with Power Adapter (without 3.3v line) and SATA to USB and tried that but nothing, just silence when power is delivered. Interesting that one Seagate IronWolf burned and the other Enterprise Seagate survived. Expensive lesson learned. Don't cheap out on PSU, make sure to validate and use that PSU's specific cables, and validate backups before troubleshooting esp when two disks already disabled.

I’ve recently completed a deep-dive troubleshooting session following a system crash/PSU failure to verify the remaining hardware. I’ve confirmed that my PSU, SAS cables, and power splitters are fully functional by testing them in a separate, known-good server. However, I’m seeing a strange brand-specific pattern: All of my Western Digital (WD/HGST) disks are completely unresponsive—they will not spin up at all. In contrast, my two Seagate drives survived; one is currently in data rescue, and the other is online and healthy. Is there a specific 'circuit breaker' behavior or protection circuit (like TVS diodes) on WD/HGST boards that is more sensitive than Seagate's? I am also wondering if this could be a 3.3V Power Disable (PWDIS) reset loop, though I’ve tested them across different power environments. Has anyone experienced a total 'WD-only' blackout after a power event while other brands survived? Are these drives likely toast, or is there a known protection state I can reset/bypass?"

Thank you! And yes absolutely agreed about parity not being a backup strategy. thankfully the most absolutely important docs and pics are in the cloud.

Thanks for confirming, @itimpi . That's what I suspected. I've been working with Seagate on disk 3, and it's covered under warranty with data rescue service available. They're estimating a 45-day turnaround, hopefully sooner. I'm fairly confident they can recover the data after swapping the PCB. My understanding is that Unraid doesn't encrypt data by default, so once they mount the drive, they should be able to access everything—is that correct? My plan to bring the array back online: Tools → New Config, then hit Apply Confirm all drives show blue icons on Main tab Unassign the 3 failed disks Start array and let parity rebuild complete Rebuild my ISO collection for disks 1 and 2 from scratch Once Seagate returns disk 3 data, copy it back to the array If the external drive they send back is shuckable, add it as a new disk and expand the array Does this approach look solid, or am I missing anything?

Hi @itimpi, thanks for the quick response. Unfortunately, disk 3 has definitely failed. During my troubleshooting, I accidentally used the wrong PSU cable and the SATA cable caught fire with visible smoke, quickly powered off but when I inspected disk 3, the PCB shows burn damage. I'm afraid to power it on at this point to verify if it still spins up or to pull SMART data. Disk 1 and 2's data is already gone, which I've made peace with. My main concern now is whether there's any way to proceed with the array while I send disk 3 out for professional data recovery, or if I should just wait until the data is recovered before doing anything.

I'm facing a worst-case scenario with my array and need advice on minimizing data loss. Current situation: Running dual parity Lost three disks total Disks 1 and 2 were cleared and failing during rebuild (persistent read errors) While troubleshooting cables and power, disk 3 failed Due to how my shares are organized, I can afford to lose disks 1 and 2, but disk 3 contains critical data My questions: Can I emulate or bypass disk 3 to cut my losses on disks 1 and 2, or is the array unrecoverable at this point? I'm planning to use Seagate Rescue Data Recovery for disk 3. Should I wait for them to recover the data before attempting to bring the array back online? Any guidance would be appreciated. This has been a steep learning curve.

oh my... that makes sense then. probably this setting right here. Do you think this is unnecessary? Or should I add the docker.img to the exclusion list?

Could someone help me with this error message? "Tar creation failed! Tar said: tar /mnt/user/system/docker/docker.img: file changed as we read it" Debug log ID: 4b68d0e2-9581-42ab-a971-33f4896ba364

thank you @zspearmint and @Gymnae. I had the same issue and removing myservers.cfg file stopped the error message.

First of all, thank you so much for this plugin. I recently found it and love using it to optimize my shares. Second, is it possible to stack or queue up different tasks?