DukeVimes

Attached is a new set of logs downloaded just now, array is online and functional with the exception of Drive B being listed as unmountable. tower-diagnostics-20230602-1345.zip

Hi @JorgeB, I apologize for monopolizing your time like this, if there's a paid resource/tech support or someone else who you'd like me to reach out to, I'm happy to do that. Potentially losing about 15TB of data has me a little out of sorts at the moment. You mentioned that I can recreate the array without 'that' disk. For clarification, here are the statuses of the 3 disks that comprised my array before the initial issues happened earlier this week: Drive A, 14TB is the array drive which stopped responding, prompting me to start this thread. I've tried swapping power and SATA cables, as well as plugging it into an external bay on my desktop, but it doesn't appear to be powering on at all. Drive B, 14TB is the array drive that, after doing a New Config, is listed as "Unmountable, Unsupported or no file system" Drive C, 14TB is my parity drive, which since the New Config appears to be being overwritten by the new array I created. Despite my pausing the parity sync last night, it apparently restarted, and is now 73% complete. From my understanding, I need any two of the original three disks intact/functioning, which I then could use to rebuild the third. Since Drive C, my parity drive, is now being overwritten, that would mean that I need to get Drive A working, then somehow recreate an array with it and Drive B, which can rebuild the (correct) parity onto Drive C.

@JorgeB no, it appears to be completely dead, tried different power and sata cables and even an external enclosure, can't even get it to spin up. If I'm able to fix it somehow, is there a way to "roll back" to the last config using it and the other two original drives, even though I've deleted that config, and now started to overwrite the parity?

@JorgeB, I might have just done something pretty bad. I wasn't able to get that drive to work, so I figured I'd add in some smaller/older drives and then rebuild the array that way. I put the drives in, but wasn't able to start the array, as it said I couldn't both remove and add drives at the same time. So... I did a New Config, thinking that since 1 array drive and the parity drive were going to stay the same, it would be fine. I put all of the drives in the new config, and started the array for a Parity-Sync. But instead of reading from the parity and writing to the array like I expected, it started reading from the array and writing to the parity. Additionally, the original 14TB functioning array drive from the pre-breakdown setup is now listed as "Unmountable: Unsupported or no file system". The array is currently started, but I've paused the Parity-Sync and am just sitting in a bit of limbo now. I've downloaded and attached my latest diagnostics file, and I'm desperately hoping that I didn't just erase the entire contents of my server. I'm not religious, but if there are gods of technology, I'm about to go burn a CD at their altar if I can recover from this self-inflicted snafu. tower-diagnostics-20230531-2257.zip

Version 6.11.5 I significantly upgraded my setup a few weeks ago, swapped out a 6TB parity and several 4TB and 6TB array drives for a 14TB parity and 2x 14TB array drives. Things have been fine (or so I thought), but I went in to make some changes to my Plex Docker this evening, and received an error message about a drive having some sort of issue. Unfortunately, I didn't screenshot or otherwise write down what that error was. However, I did download the diagnostics and SMART reports (attached) before I shut down. I switched SATA and power cables to make sure it wasn't one of those, but the drive still seems to be missing. Hoping there's something in the log files that points towards an answer, I just don't know what to look for. tower-diagnostics-20230530-1736.zip tower-smart-20230530-1735.zip