Disk Error, Need help to figure out what to do


Recommended Posts

According to diagnostics the self-test was still running. Did it complete?

 

Aug 19 21:47:17 Server kernel: sd 7:0:1:0: attempting task abort!scmd(0x000000003ae4e576), outstanding for 15123 ms & timeout 15000 ms
Aug 19 21:47:17 Server kernel: sd 7:0:1:0: [sdc] tag#6804 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Aug 19 21:47:17 Server kernel: scsi target7:0:1: handle(0x0009), sas_address(0x4433221105000000), phy(5)
Aug 19 21:47:17 Server kernel: scsi target7:0:1: enclosure logical id(0x500605b006da4650), slot(6) 
Aug 19 21:47:21 Server kernel: sd 7:0:1:0: task abort: SUCCESS scmd(0x000000003ae4e576)
Aug 19 21:47:21 Server kernel: sd 7:0:1:0: [sdc] tag#3034 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=19s
Aug 19 21:47:21 Server kernel: sd 7:0:1:0: [sdc] tag#3034 Sense Key : 0x2 [current] 
Aug 19 21:47:21 Server kernel: sd 7:0:1:0: [sdc] tag#3034 ASC=0x4 ASCQ=0x0 
Aug 19 21:47:21 Server kernel: sd 7:0:1:0: [sdc] tag#3034 CDB: opcode=0x88 88 00 00 00 00 00 00 02 a7 00 00 00 00 20 00 00
Aug 19 21:47:21 Server kernel: blk_update_request: I/O error, dev sdc, sector 173824 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0
Aug 19 21:47:21 Server kernel: md: disk3 read error, sector=173760
Aug 19 21:47:21 Server kernel: md: disk3 read error, sector=173768
Aug 19 21:47:21 Server kernel: md: disk3 read error, sector=173776
Aug 19 21:47:21 Server kernel: md: disk3 read error, sector=173784

Maybe a connection problem.

 

Aug 19 17:35:09 Server root: Fix Common Problems: Other Warning: Background notifications not enabled

You should setup Notifications to alert you immediately be email or other agent as soon as a problem is detected.

Link to comment

It did finish, without errors. Everything was good 

Well, I'd like to hope that this was only because of a connection issue. But on the other hand, that HBA that is in that server works like champ. And, if it really is an issue like it, why is it only one drive when all of them are on the same channel on the HBA? 
I'm just curious because of the word "sector" in the error message, which could be the drive, If I'm not wrong? 


Yeah, I still need to set them up but I'm always confused how to set them up. 
I do need to do a ton of other stuff, like security and stuff 

Link to comment

The SMART report for all attached disks is already included in Diagnostics. That one looks like the earlier one except the test completed and passed.

 

The disk isn't even disabled according to those Diagnostics. You can reset the error count on Main at Array Operation - Clear Stats, or by rebooting.

 

I guess you could do a non-correcting parity check as a further test.

Link to comment

I was just curious because my check dropped from 270 mbits to 130mbits during the runtime of the check. But yeah, that makes way more sense

EDIT: No erros where found during the check, average speed was the same as before too. So, I guess, It was a random i/o error then?

Edited by deltaexray
Link to comment

To answer both of you: The only thing that changed over the last few days is that I updated from 6.8.3 to 6.9.2.
Everything else is and was the same. They are all powered up the same way as before and all cables are fixed in place.

Maybe the HBA is giving up? Don't really think that the Powersupply is the issues here, given that all 3 drives are on cable while the unit is 650 watts, do not really believe that they have to less power available.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.