October 25, 20214 yr Hello I recently purchased (about 1 month now) 2 Seagate Exos x16 16TB drives I replaced parity with 1 and another array disk with the other Unraid was able to replace parity, upgrade the new disk, and rebuild parity successfully. My first Parity Check (scheduled) launched this weekend and I started getting a bunch of read errors on both 16TB drives Here's what I did so far: - I was forced to stop parity check - I ran smart extended checks on both drives -- they both passed - I did xfs_repair on the array drive -- because it was reading as unmountable - Parity drive was reporting as disabled -- I removed and reassigned Parity drive - Started Parity Re-build 30 mins into rebuild i'm getting disk read errors on the array drive (Exos 16TB): [77822.306452] md: disk8 read error, sector=248659112 [77822.306456] md: disk8 read error, sector=248659120 [77822.306459] md: disk8 read error, sector=248659128 [77822.306462] md: disk8 read error, sector=248659136 [77822.306466] md: disk8 read error, sector=248659144 [77822.306469] md: disk8 read error, sector=248659152 [77822.306473] md: disk8 read error, sector=248659160 [77822.306477] md: disk8 read error, sector=248659168 [77822.306481] md: disk8 read error, sector=248659176 [77822.306484] md: disk8 read error, sector=248659184 [77822.306487] md: disk8 read error, sector=248659192 [77822.306491] md: disk8 read error, sector=248659200 [77822.306496] md: disk8 read error, sector=248659208 [77822.306499] md: disk8 read error, sector=248659216 [77822.306503] md: disk8 read error, sector=248659224 [77822.306507] md: disk8 read error, sector=248659232 [77822.306511] md: disk8 read error, sector=248659240 [77822.306514] md: disk8 read error, sector=248659248 [77822.306517] md: disk8 read error, sector=248659256 [77822.306519] md: disk8 read error, sector=248659264 [77822.306521] md: disk8 read error, sector=248659272 [77822.306523] md: disk8 read error, sector=248659280 [77822.306524] md: disk8 read error, sector=248659288 [77822.306525] md: disk8 read error, sector=248659296 [77822.306526] md: disk8 read error, sector=248659304 [77822.306530] md: disk8 read error, sector=248659312 [77822.306532] md: disk8 read error, sector=248659320 [77822.306535] md: disk8 read error, sector=248659328 [77822.306536] md: disk8 read error, sector=248659336 [77822.306537] md: disk8 read error, sector=248659344 [77822.306541] md: disk8 read error, sector=248659352 [77822.306543] md: disk8 read error, sector=248659360 [77822.306545] md: disk8 read error, sector=248659368 [77822.306546] md: disk8 read error, sector=248659376 [77822.306548] md: disk8 read error, sector=248659384 [77822.306549] md: disk8 read error, sector=248659392 [77822.306550] md: disk8 read error, sector=248659400 [77822.306551] md: disk8 read error, sector=248659408 [77822.306555] md: disk8 read error, sector=248659416 [77822.306557] md: disk8 read error, sector=248659424 [77822.306560] md: disk8 read error, sector=248659432 [77822.306561] md: disk8 read error, sector=248659440 [77822.306562] md: disk8 read error, sector=248659448 [77822.306565] md: disk8 read error, sector=248659456 [77822.306567] md: disk8 read error, sector=248659464 [77822.306570] md: disk8 read error, sector=248659472 [77822.306571] md: disk8 read error, sector=248659480 [77822.306572] md: disk8 read error, sector=248659488 [77822.306573] md: disk8 read error, sector=248659496 [77822.306575] md: disk8 read error, sector=248659504 [77822.306579] md: disk8 read error, sector=248659512 [77822.306581] md: disk8 read error, sector=248659520 [77822.306583] md: disk8 read error, sector=248659528 [77822.306585] md: disk8 read error, sector=248659536 [77822.306586] md: disk8 read error, sector=248659544 [77822.306589] md: disk8 read error, sector=248659552 [77822.306591] md: disk8 read error, sector=248659560 [77822.306594] md: disk8 read error, sector=248659568 [77822.306595] md: disk8 read error, sector=248659576 [77822.306596] md: disk8 read error, sector=248659584 [77822.306598] md: disk8 read error, sector=248659592 [77822.306601] md: disk8 read error, sector=248659600 [77822.306604] md: disk8 read error, sector=248659608 [77838.048467] sd 1:0:4:0: Power-on or device reset occurred What else can i check to validate whether they are BAD drives versus a config issue with my Unraid?
October 29, 20214 yr Author Thanks for taking a look. Here is the diagnostics requestedthetower-diagnostics-20211029-0638.zip
October 29, 20214 yr Community Expert Looks more like a power/connection problem, replace swap cables and try syncing parity again.
October 29, 20214 yr Author Hmm odd as there were drives in there before and it's a hotswappable 24 bay Norco. But I'll try what you have suggested this weekend and report back
November 4, 20214 yr Author @JorgeB I pulled all of the drives from the server and rearranged to different slots. I paired the 16tb drives to consecutive slots (they we not before). I fired the server back up and started rebuild which seems to have completed successfully in little over 2 days without any noticeable errors. Have parity check set to monthly, so will monitor next month when it runs again Thanks for the help.
June 2, 20251 yr i got the same exact problem after shrinking my array ( its been 3 months since my last parity check)Same exact errors too. on two out of my 6 exos x16I tried to swap one drive arround but the errors followed the drive to the other slot too. I am running long smart tests on both drives if they pass I am moving the whole setup to a lower row with new power cables and another ccontroller to check if its my backplane dying.
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.