Yup.
Before tonight I had no idea that my failed "disk2" would still be accessible as a disk share. It was a 2TB WD EADS drive that I bought just a few weeks ago, and for some reason it's throwing errors galore. I tried changing SATA cables, taking the drive out of the hot-swap cage and connecting it with new cables, anything I could think of that might lead me to a solution... but it turns out it's the drive, not the interconnecting hardware.
So I removed it, restarted UnRAID and copied everything from my "disk2" share over to other drives in my array. This wasn't as painful as it may sound because I only had a dozen GB of stuff on it since it was so error-prone.
It worked like a charm. I am currently rebuilding my array with a 750GB drive in the old 2TB drive's place since I don't have another 2TB drive handy... the "Restore" button comes in handy for this, which is one reason I never upgraded to a newer version of UnRAID yet - I like the functionality of the Restore button, although no one likes the nomenclature.
Importantly, I was only safe using the Restore button because I had already copied the data from my "missing" disk2 to other drives in the array. As others have said, don't go pressing it if you don't know what it will do.
You can upgrade with peace of mind.
The button has been removed in recent versions, but its exact equivalent was put into place as the
initconfig command.
You did not "restore" your data, you
"Initialized a New Disk Configuration and Immediately Invalidated Parity based on any Prior Configuration"
You copied your data to a working disk, replaced the old larger disk with a smaller one and then asked unRAID to Initialize a new disk configuration. The functionality was not removed, only the VERY misleading name (and the button that too easy for less experienced unRAID owners to press in situations when it should not be pressed)
