Knights21 Posted October 4, 2021 Share Posted October 4, 2021 Hope someone can give me advice, Had an error warning stating: Tower kernel: blk_update_request: I/O error, dev sdg, sector 732971568 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 and array shows 1 error against sdg. This was after a successful parity check stating the array health was a pass. SMART page states an error but nothing is obvious (to me) in the extended SMART report. HP Proliant Microserver Gen 8 1 SATA parity drive 3 SAS drives via HBA 1 SATA Cache HUS723030ALS640_YVK45Z0K_35000cca03eb0b998-20211004-0701.txt tower-diagnostics-20211004-0731.zip Quote Link to comment
JorgeB Posted October 4, 2021 Share Posted October 4, 2021 Error was after spin up, some combinations of drives/controller can cause this, you should update the LSI firmware to latest, it might help, if it doesn't you can try reporting the issue in the SAS spin sown plugin support thread, or disable spin down for that drive. Quote Link to comment
Knights21 Posted October 4, 2021 Author Share Posted October 4, 2021 I had trouble with the HP 220 branded Broadcom / LSI 2308 card after I updated to V20 as I then had problems with SSD trim operations which turns out V20 doesn't support so I had to downgrade to p16. Quote Link to comment
Knights21 Posted October 4, 2021 Author Share Posted October 4, 2021 Just happened again when I came out of maintenance mode: Oct 1 04:20:53 Tower kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 1 04:20:53 Tower kernel: sd 1:0:3:0: [sdg] tag#487 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Oct 1 04:20:53 Tower kernel: sd 1:0:3:0: [sdg] tag#487 Sense Key : 0x2 [current] Oct 1 04:20:53 Tower kernel: sd 1:0:3:0: [sdg] tag#487 ASC=0x4 ASCQ=0x2 Oct 1 04:20:53 Tower kernel: sd 1:0:3:0: [sdg] tag#487 CDB: opcode=0x88 88 00 00 00 00 00 2b b0 42 30 00 00 00 08 00 00 Oct 1 04:20:53 Tower kernel: blk_update_request: I/O error, dev sdg, sector 732971568 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 All three SAS drives are identical so odd that only sdg is flagging? 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.