July 21, 20178 yr Just changed one of the disks that failed. After a couple of hours I started the parity check this is what I have.... Any suggestion??? Thanks
July 21, 20178 yr Community Expert Since it's correcting a large number of sync errors it's normal to slow down a lot, are so many sync errors expected?
July 21, 20178 yr Community Expert 1 hour ago, gideva said: Just changed one of the disks that failed. After a couple of hours I started the parity check this is what I have.... Why are you doing a parity check instead of a data rebuild? Post your diagnostics.
July 21, 20178 yr 2 hours ago, gideva said: Just changed one of the disks that failed. After a couple of hours I started the parity check this is what I have.... Any suggestion??? Thanks How did you change the disk? A disk rebuild? Assuming yes, I am not sure why you'd have sync errors. Did the rebuild proceed at normal speed? If so, that would be a good sign. Did you open the case AFTER the rebuild? Looking at the number of sync errors 154,000+. Sounds like a lot but isn't for 550G of processed space. Each block I think is 8 sectors (4K). so 154000 is only 600M. Way less than 550G! About 0.1%. So most of the disk is verifying, but some is not. The fact it is so slow is not due to the sync errors. There are too few of them to slow it down that much. Even if every block were bad, it would not be this slow. So either the rebuild went flawlessly and now there is some connectivity / HBA issue that is causing performance and data accuracy issues. Or the rebuild was suffering the same issues and we are seeing its continuation into the parity check. Parity is being updated to match the rebuilt disk. Probably a bad thing. Stop this, answer my questions, and post a diagnostic file.
July 21, 20178 yr Author Hi there and really thanks for the quick reply.... Coming to the answers: 1) it was a rebuilt and all seemed fine. The only weird thing was that after the rebuilt one of the other disks (cannot remember which) was marked as unreadable and the system was asking to format it. After I reboot the system all was normal. 2) I did not open the case I got your post just before leaving home and I had the chance to stop everything but not to get the diagnostic file and post it. As soon as I will be back home (on Sunday) I will post everything. Thank you again
July 21, 20178 yr Community Expert 5 hours ago, gideva said: Just changed one of the disks that failed. After a couple of hours I started the parity check this is what I have.... So are you saying the rebuild completed in only 2 hours and then you started a parity check?
July 21, 20178 yr Author Probably something more but did not take really long... This is my first time with rebuilt!
July 21, 20178 yr It is more likely your rebuild failed before finishing due a disk dropping offline.
July 21, 20178 yr Community Expert 3 hours ago, bonienl said: It is more likely your rebuild failed before finishing due a disk dropping offline. And now parity isn't likely to give a valid rebuild. We will have to hope to recover files from the original disk. gideva, you should have asked for advice before doing anything. It's best to try to understand why a disk failed before deciding what to do about it.
July 22, 20178 yr Author Great... now what??? Did I just lose some dats or all the array is compromised? What should do now not to make the situation even worser? You are right I should have asked before...
July 22, 20178 yr Go to Tools -> Diagnostics and get the diagnostics zip file. This will help to understand the current situation better.
July 22, 20178 yr Author Will be back home tomorrow and I will do it right the way... Once again thanks for your help
July 23, 20178 yr Author Here it is... hope it will help you to help me. monstruo-diagnostics-20170723-1511.zip
July 23, 20178 yr Community Expert Server came up from an unclean shutdown, besides that you're having issues with your SAS2LP, disable VT-D if you don't need it, try a different slot (you should anyway since it's on a x4 slot, especially if it's a DMI shared slot). Since the rebuild was before this log no idea if it was successful or not, but the sync errors and unclean shutdown suggest otherwise. Edited July 23, 20178 yr by johnnie.black
July 23, 20178 yr Community Expert Forgot to mention the filesystem corruption on disk4, you need to run xfs_repair on it, if that was the rebuilt disk it may also be a clue that the rebuild wasn't 100% successful, but it may also a consequence of the SAS2LP issues, same for some of the sync errors.
July 23, 20178 yr Author All copied... but not all understood completely (talking with a newbie)... Just to be sure I am going to do correctly this time: 1) I have to disable VT-D on BIOS 2) The change of slot is not really clear... 3) Will run xfs_repair on disk 4 (that was the failed disk) When I do all this shall I try again with the Parity Check and see if is ok or not? Thanks for help and patience Beppe
July 23, 20178 yr Community Expert 16 minutes ago, gideva said: 2) The change of slot is not really clear... Change the SAS2LP to one the top two PCIe slots. 17 minutes ago, gideva said: 3) Will run xfs_repair on disk 4 (that was the failed disk) It's likely that the filesystem corruption is because of an incomplete rebuild, is so data on that disk will also be corrupt, assuming you don't have checksums to figure out which files are bad is the old disk still readable?
July 24, 20178 yr Author all done but when I try to run xfs_repair on disk 4 does not work!!! It gives an error message like: ERROR: The filesystem has valuable metadata changes.....
July 24, 20178 yr Community Expert Not md1, md4 (disk4), and only if the disk is not currently mounting, it was on the last diags.
July 24, 20178 yr Community Expert If the old disk still works compare the files, or copy everything you can from it.
Archived
This topic is now archived and is closed to further replies.