Rittzy Posted April 4, 2022 Share Posted April 4, 2022 (edited) Hi, Quick one from me, I stopped the array to add a new data disc and for some reason unraid unassigned my WD parity disc from the array and wants the old Seagate disc back in. When I go to add the WD disc it wants to rebuild the array again. My server only just completed a parity check last night with the WD disc in and has been running with this parity disc in for about 2 weeks so I know it was built correctly. I take it there is no way around this but to rebuild the whole thing again? More want to understand why it unassigned itself in the first place to prevent it from happening again. Thanks homeserver-diagnostics-20220404-1417.zip Edited April 4, 2022 by Rittzy Diagnostics Added Quote Link to comment
JorgeB Posted April 4, 2022 Share Posted April 4, 2022 Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 ee cf 00 00 00 80 00 Apr 4 08:44:44 HomeServer kernel: blk_update_request: critical medium error, dev sda, sector 15650560 op 0x0:(READ) flags 0x80700 phys_seg 1 Problems with the flash drive, and likley why the drive changes weren't recorded. 1 Quote Link to comment
Rittzy Posted April 4, 2022 Author Share Posted April 4, 2022 17 minutes ago, JorgeB said: Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Apr 4 08:44:44 HomeServer kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 ee cf 00 00 00 80 00 Apr 4 08:44:44 HomeServer kernel: blk_update_request: critical medium error, dev sda, sector 15650560 op 0x0:(READ) flags 0x80700 phys_seg 1 Problems with the flash drive, and likley why the drive changes weren't recorded. 8:44 is when the system was roughly restarted after an update. I updated the system since the array was offline anyway and was trying to figure out what was going on. Thinking i intially took the array offline about 8:15. I tried looking through the logs but couldn't see anything before this time. Are the logs wiped after a restart? Quote Link to comment
itimpi Posted April 4, 2022 Share Posted April 4, 2022 Just now, Rittzy said: . Are the logs wiped after a restart? Yes (unless you have activated the syslog server). 1 Quote Link to comment
Rittzy Posted April 4, 2022 Author Share Posted April 4, 2022 23 minutes ago, itimpi said: Yes (unless you have activated the syslog server). Well, i'll probably never know then unfortunately. Thanks for the help anyway! 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.