April 10Apr 10 sunday night, i noticed that there was a disk that was emulated. so i jump and ordered a new disk, unfortunately, it was 22tb vs the required 20tb, which 20tb is my largest and my parity. so i put the new drive it and unraid wants to copy the parity. the parity copies but i noticed there was another disk missing so i reboot and F me, it wants to copy again, im now at nearly 50 hours of copying. now, this morning at 3am, i get up and notice its done so i start the array and it gets stuck in mounting disks. my logs are full of this "2026-04-10T19:16:46-04:00 Tower kernel: md: disk0 read error, sector=39078396962026-04-10T19:16:46-04:00 Tower kernel: md: disk0 read error, sector=39078396962026-04-10T19:16:46-04:00 Tower kernel: md: disk0 read error, sector=3907840168"im unsure what to do now. nothing seems to respond and seems that it wont accept the previous parity disk now. im unsure what direction to go now and any help will be welcomed.
April 11Apr 11 Author tower-diagnostics-20260411-0831.zipive attached my diagnostics. so the system is up BUT i had to do a new config and stated that the parity was correct. i however didnt add the sus bad drive. im not sure how to proceed now with one bad 20tb, one new 22tb drive. i rather not buy yet another drive. i thought about using unassigned devises and moving stuff off the drive. if im able to.thanks for the help
April 12Apr 12 Parity dropped offline and reconnected; it looks more like a power/connection issue. The errors for the other disk are not logged, but it looks like it also dropped, so first thing is to check/replace cables for both, then post new diags after array start.
April 12Apr 12 Author the system so far has been up for 36 hours, when i get back next saturday i will replace the cables and i will follow up then. thanks!
April 12Apr 12 On 4/11/2026 at 8:35 AM, blackb0x13 said:new config and stated that the parity was correct. i however didnt add the sus bad driveDon't see how parity could possibly be valid then.
April 12Apr 12 Author 55 minutes ago, trurl said:Don't see how parity could possibly be valid then.it probably isnt, i agree. it does allow me access however. i was able to mount the drive and im moving stuff off it as it allows. then ill trigger a parity check maybe and go from there. i still dont know how it happened but like i said, ill replace the cables once im back home and report another diagnostics.
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.