Mircea Posted March 30, 2020 Share Posted March 30, 2020 I did a big BooBoo! I installed an m.2 SSD onto the array (thinking that I could use it directly for video editing, not knowing that this is not supported. I found out after the new array was built. I removed the SSD and added it to where I learned it is supposed to be - the cache devices, where I have another 256 gb SSD. But now, I had a missing drive in the array. So after searching the forums, I did a New Config (with None selected). Then I started to put the HDD back to their places (2x6TB, 2x4TB, 2x2TB, all identical in pairs). One of 6Tb was the parity. After I put them all and started the array and the parity finished, my second 6TB is Unmountable:no file sistem, with AUTO as FS. I believe I reversed the parity HDD with the normal one (very close names). I changed the File system type from Auto to xfs. I'm in maintenance mode now and after 10 hours of xfs_repair with -nv .. I got this Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ....found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .. Exiting now. This is the moment I started freaking out thinking I lost all! from that drive! I NEED to mount that drive or at least recover what is on it. I'm on Version: 6.8.3. nas-diagnostics-20200330-0325.zip Quote Link to comment
trurl Posted March 30, 2020 Share Posted March 30, 2020 1 hour ago, Mircea said: I believe I reversed the parity HDD with the normal one If so there will be no way to recover except from your backups. Quote Link to comment
Mircea Posted March 30, 2020 Author Share Posted March 30, 2020 (edited) But I was very careful ... Can it be sooo easy to screw it up by just not remembering the exact last Characthers of the drives when you are building the new config?? Can't I try to remove the drive and recover the data in Windows/Linux? Edited March 30, 2020 by Mircea Quote Link to comment
itimpi Posted March 30, 2020 Share Posted March 30, 2020 50 minutes ago, Mircea said: But I was very careful ... Can it be sooo easy to screw it up by just not remembering the exact last Characthers of the drives when you are building the new config?? Can't I try to remove the drive and recover the data in Windows/Linux? If you put the wrong disk in as parity then rebuilding parity would have overwritten every sector on the drive not leaving anything to be recovered. The New Config tool always has the risk of a mistake in its use leading to data loss. You could have reduced the chance of making a mistake of the sort you seemed to have made if when using New Config you had started with the option to keep all current assignments and then made the minimal changes required to get to the end position you wanted as that avoids having to re-enter serial numbers unnecessarily (with potentially disastrous consequences). Quote Link to comment
Mircea Posted March 30, 2020 Author Share Posted March 30, 2020 It seems I had to learn the hard way. First time in 15 years I am loosing data (I even recovered from 2 totally dead HDD). Never expected I would mess up this. C'est la vie. Thank you for your answers Guys. @itimpi @trurl Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.