Douglas_D Posted October 30, 2017 Share Posted October 30, 2017 Hi all, I received the following messages in the syslog last night (2:30AM Oct 30th) and I'm not really sure what the next step is from here. I ran a short SMART diagnostics on the drive and it didn't find anything wrong with the drive (Drive sdg in attached diagnostic log). Quote Oct 30 02:30:31 Galaxy kernel: sd 1:0:4:0: [sdg] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 30 02:30:31 Galaxy kernel: sd 1:0:4:0: [sdg] tag#1 Sense Key : 0x5 [current] Oct 30 02:30:31 Galaxy kernel: sd 1:0:4:0: [sdg] tag#1 ASC=0x21 ASCQ=0x0 Oct 30 02:30:31 Galaxy kernel: sd 1:0:4:0: [sdg] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 01 5e 11 2f 08 00 00 00 20 00 00 Oct 30 02:30:31 Galaxy kernel: blk_update_request: critical target error, dev sdg, sector 5873151752 Oct 30 02:30:31 Galaxy kernel: md: disk0 write error, sector=5873151688 Oct 30 02:30:32 Galaxy kernel: md: disk0 write error, sector=5873151696 Oct 30 02:30:32 Galaxy kernel: md: disk0 write error, sector=5873151704 Oct 30 02:30:32 Galaxy kernel: md: disk0 write error, sector=5873151712 So I'm curious if this is something that may have been a fluke or if there is some way to restore the Parity drive to functional and then try writing to these registers to test if it is truly bad. galaxy-diagnostics-20171030-0938.zip Quote Link to comment
JorgeB Posted October 30, 2017 Share Posted October 30, 2017 The disk looks healthy, but you can run an extended SMART test, if the extended SMART test finishes successfully you can swap cables/backplance with another disk, re-sync parity and see if the same disk fails again. 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.