December 3, 201015 yr Long story short, I have a new 2TB parity drive (to replace a 1.5tb that I already securely wiped), and I have another 1.5TB that blew up, and I replaced with another 2TB drive. (I have 4 other working drives) Turned on system, and I matched all the drives up as much as I could and select the two new 2TB drives as the missing/replaced drives. Well obviously, since I replaced 2 drives, unRAID is telling me it's an invalid configuration with wrong/missing drives. I know this, I know I have and will lose data. How do I bring the array up anyways? PS. Next time you plan on replacing a drive, don't pull it out and do a DOD level secure wipe of the drive till your new drive is in the unRAID and up and running
December 3, 201015 yr Author I just read this from another post, going to try it, hopefully I don't lose anymore data Yes, you can set a new initial configuration. To do so, you need to log in as "root" on either the system console or via telnet. Then, you need to stop the array via the web-interface, and then type on the command line initconfig It will prompt you for to respond with "Yes" Type exactly that (three letters, Capital "Y", lower case "es") followed by the enter key. Then, on the web-interface, refresh the browser. All the indicators should turn BLUE. You can then assign the drives as you like on the "Devices" page as you have forces a new disk configuration. Please note that forcing a new configuration will immediately invalidate parity based on the old configuration so when you next start the array a full parity calculation will occur. Ok that seems to work.
December 3, 201015 yr Sorry about your luck. Glad you got everything back up and running though. I ALWAYS keep my old parity drive around for 2 weeks or so before I go and wipe it. I do a couple parity checks and then let the monthly one run before I wipe and put the old parity drive back into service as a data drive.
December 3, 201015 yr I think that's good practice. Of course the first rule is: never replace more than one drive at a time, but you already found that out the hard way. Sorry for the lost data. I hope it's not too painful to reconstruct it.
December 8, 201015 yr Each shot ? makes you go the same way, each ??? one over a pool ??? of water with a target. You are ??? meant to get in this final fantasy leveling by getting rid of your final fantasy gold wings. You do this ff14 gold by right clicking them. See its not all ffxiv power leveling for the high levels. In mulgore ff14 power leveling if you do not do ffxiv power leveling this you will die when you hit a tent.
December 8, 201015 yr I ALWAYS keep my old parity drive around for 2 weeks or so before I go and wipe it. I'm puzzled about the value of doing this. Surely, as soon as a single byte is written to any of the drives which were protected by that parity disk, then the parity becomes worthless?
December 8, 201015 yr I ALWAYS keep my old parity drive around for 2 weeks or so before I go and wipe it. I'm puzzled about the value of doing this. Surely, as soon as a single byte is written to any of the drives which were protected by that parity disk, then the parity becomes worthless? Ir really depends. If you are trying to recover a failed disk where that "byte" was not located in a file or that byte was in a file but represented a single pixel of a movie or a single sample bit of an mp3 file then the odds of you preferring to get back (re-construct) the remaining files on that disk, even though one might have a tiny blip in it are pretty high. Obviously the more you write to the array, the less useful the parity drive will be to recover anything. Joe L.
December 8, 201015 yr What Joe L said above is correct. I don't write to my array all that often, as I have moved my torrents et al. off to the cache drive. The chances of recovering the majority of the files is usually pretty high for me.
Archived
This topic is now archived and is closed to further replies.