rumblefish1 Posted March 4, 2017 Share Posted March 4, 2017 Hello Everyone, I just had a brown out while setting up a new server. I have been preclearing 23 drives for the last week but had not gotten as far as setting up a parity drive yet. I have been doing some data transfers to the drives for testing purposes. After the brown out one of the data drives now appears as unmountable Being new at this the only step I took was running the xfs repair with -n, and then the xfs repair. I started the array again and the drive still remains unmountable. I have attached the messages that appeared on the screen after running xfs repair as well as the error I found in the system log. Any help would be appreciated, unfortunately I have some data on that drive that is important for me to recover. Thanks Quote Link to comment
JorgeB Posted March 4, 2017 Share Posted March 4, 2017 You need to run xfs_repair on that disk, save the output and post it in case it remains unmontable after running it. Quote Link to comment
rumblefish1 Posted March 4, 2017 Author Share Posted March 4, 2017 Ran xfs_repair, stopped maintenance mode, then started the array again. The drive still appears unmountable, I have attached screen shot and disk log. Quote Link to comment
JorgeB Posted March 4, 2017 Share Posted March 4, 2017 I want to see the output of xfs_repar, not the log. Quote Link to comment
rumblefish1 Posted March 4, 2017 Author Share Posted March 4, 2017 sorry about that, not familiar with what I should be sending. This is what comes out on the screen after I run xfs_repair with nothing in the options box, and the system log. Quote Link to comment
rumblefish1 Posted March 4, 2017 Author Share Posted March 4, 2017 thank you that did the trick. Quote Link to comment
remati Posted March 4, 2017 Share Posted March 4, 2017 Is there a chance for data corruption even after running xfs_repair? Will a parity check fix data corruption if it happens like in a scenario like this?Sent from my iPad using Tapatalk Quote Link to comment
JorgeB Posted March 4, 2017 Share Posted March 4, 2017 There's a small chance of data corruption, if you were writing to that disk at the time of the unclean shutdown those files have a much greater chance of being corrupt, parity can't help in those situations, only checksums. 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.