clevoir Posted April 12, 2020 Share Posted April 12, 2020 I am running 6.8.3 and had a disk fail (Disk 5) Replaced disk OK and left array to rebuild, this has just completed but I have 475 million errors in Disk 3 Please find attached diagnostic file backup-diagnostics-20200412-2156.zip Quote Link to comment
trurl Posted April 12, 2020 Share Posted April 12, 2020 Disk 3 has disconnected. You probably disturbed the connections when you replaced the disk. Are you sure there was really something wrong with that original disk5? Disabled disks have many causes and bad disks are often not the cause. Quote Link to comment
clevoir Posted April 13, 2020 Author Share Posted April 13, 2020 Yes I tried connecting Disk 5 to another PC and it was not detected. Quote Link to comment
trurl Posted April 13, 2020 Share Posted April 13, 2020 Check all connections, power and SATA, both ends, including any power splitters. Then post new diagnostics. Quote Link to comment
trurl Posted April 13, 2020 Share Posted April 13, 2020 In case it's not obvious, stop the rebuild, it isn't working. You will have to try again after fixing the connections and posting diagnostics. Quote Link to comment
clevoir Posted April 13, 2020 Author Share Posted April 13, 2020 I tried omitting the disk 3 , restarting the array, stopping the array and restarting again to force the disk to be rebuilt However I kept getting a message about a fault on md5 and to run an xfs repair. I had to reboot the array as the terminal I had attached to the server had gone blank, and if I call up a command prompt window it is blank? Run xfs repair and it found corruption and carried out repair. I am now carrying out a data rebuild on Disk 3 again with 7 hours to go. I attach a new diagnostics file, I realize that this may not show anything as the array has been rebooted backup-diagnostics-20200413-0111.zip Quote Link to comment
clevoir Posted April 13, 2020 Author Share Posted April 13, 2020 Disk 3 rebuilt OK and the array is up and running. So it appears that an xfs fault in md5 was causing problems for disk 3 to rebuild? Quote Link to comment
trurl Posted April 13, 2020 Share Posted April 13, 2020 3 hours ago, clevoir said: So it appears that an xfs fault in md5 was causing problems for disk 3 to rebuild? No, parity doesn't know or care about xfs, it is all just bits. Possibly whatever caused the xfs corruption (bad connection, etc) was causing problems for the rebuild. Quote Link to comment
clevoir Posted April 13, 2020 Author Share Posted April 13, 2020 Thanks for your reply, thankfully the array is now back up and working with no errors Quote Link to comment
sota Posted April 14, 2020 Share Posted April 14, 2020 now go make a backup of your important stuff. Quote Link to comment
clevoir Posted April 14, 2020 Author Share Posted April 14, 2020 Disk 3 was disabled again overnight, it is an infamous Seagate ST20000DM0001 and about 5 years old I have taken it out of the array and am now doing a preclear to test it. Prior to that I have checked all SATA and power connectors, and reseated my HBA cards 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.