June 26, 20233 yr Diagnostics attached. Hoping for some guidance on whether to replace / next steps tower-diagnostics-20230626-1757.zip
June 27, 20233 yr Community Expert It's logged as a disk problem, but could be OK now, run an extended SMART test
June 27, 20233 yr Author 2 hours ago, JorgeB said: It's logged as a disk problem, but could be OK now, run an extended SMART test Will do as soon as I get home Wednesday. I shut down server until I’m back from travel to be safe
June 27, 20233 yr Author 5 hours ago, JorgeB said: It's logged as a disk problem, but could be OK now, run an extended SMART test for my own learning, how can you tell it’s logged as a disk problem vs not a disk problem?
June 27, 20233 yr Community Expert It will depend on the controller, with an LSI HBA: Jun 26 11:12:18 Tower kernel: blk_update_request: critical medium error, dev sdd, sector 12148386216 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 If it contains "critical medium error" it usually means disk error, you can then confirm in the SMART report by looking for the related UNC @ LBA error: Error 1 [0] occurred at disk power-on lifetime: 38432 hours (1601 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 02 d4 19 a9 a8 00 00 Error: UNC at LBA = 0x2d419a9a8 = 12148386216
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.