FamilyMan

Thanks for the assist. Rebuilding underway.

Thank you for helping. I swapped cables around on all disks, shut down and restarted. Disk still has red x and disabled. Ran SMART short self-test (passed), and got new diagnostic report (attached). Running SMART extended test, now sitting at 10% after nearly 1 hour. What's next do you think? tower-diagnostics-20240709-2256.zip

Thanks in advance for anyone who has a minute to check my diagnostics (attached). I think my next step is shut down and swap SATA cable, right? Or do I just swap cable while powered up? tower-diagnostics-20240709-0014.zip

Anyone know if we are still able to create new accounts to get an API key for the facebox, tagbox, etc. dockers? Starting at https://machinebox.io/account to get a key to run the box leads me to https://www.veritone.com/#/signUp?type=developer&source=machinebox which has a login link but I could not for the life of me find a place to create a new account. Am I blind? Thanks!

Well. I feel dumb. But I guess I'm used to it! As always, thanks to the helpful community!

For the past few years I've only logged in as root because any other user I create cannot log in (invalid username or password). I had hoped it would magically start working with updates. I've attached my logs. Any ideas? tower-diagnostics-20221129-0857.zip

Thank you. I'll do that. How could I have handled this better?

No idea how this happened. My last parity check a few weeks ago was fine, no disk errors ever. I pre-cleared two 10TB disks using the unassigned devices preclear plugin. I restarted the array (clean), then unassigned the 8TB Parity and assigned one of the 10TB to parity and started the array. Disk 3 started throwing read errors right away. I cancelled the parity build on the new disk and re-added the original parity thinking I might be able to unbalance data off disk3 and have the good parity drive fill in for any read errors. But then original 8TB parity started to rebuild parity, and I figured I should just let it finish. (I think maybe that was a mistake.) Disk3 eventually quit throwing read errors (after about 7300), and parity finished. But now there's a Red X on parity drive and it has thrown a few errors itself. Anyone have any idea what should I do now ? tower-diagnostics-20220829-2359.zip

Updated. Stop Array now functions normally. Thanks!

I had this problem and posted my diagnostics in the main forum b4 I realized the plugin was causing it. https://forums.unraid.net/topic/90873-683-solved-cant-stop-array-spawns-empty-tab-updatehtm/ Plugin removed, reboot fine. Plugin reinstalled, problem reappeared. New diagnostics attached. My Go file is default: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Thanks for looking into this...I've always used this plugin. tower-diagnostics-20200412-1130.zip