B_Sinn3d Posted February 13 Share Posted February 13 This morning I woke up and one of my disks (3) was disabled with Read/Write errors. It connected to LSI 9201 so I don't think it is cable since other drives that are on same SAS cable are OK. Should I replace it or is something else going on here? Posting Diags... Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=29s Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 Sense Key : 0x5 [current] Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 ASC=0x21 ASCQ=0x4 Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] tag#22 CDB: opcode=0x88 88 00 00 00 00 02 05 02 f4 f0 00 00 01 00 00 00 Feb 13 01:04:28 debo-server kernel: I/O error, dev sdk, sector 8674014448 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014384 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014392 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014400 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014408 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014416 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014424 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014432 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014440 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014448 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014456 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014464 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014472 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014480 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014488 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014496 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014504 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014512 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014520 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014528 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014536 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014544 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014552 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014560 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014568 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014576 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014584 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014592 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014600 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014608 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014616 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014624 Feb 13 01:04:28 debo-server kernel: md: disk3 read error, sector=8674014632 Feb 13 01:04:28 debo-server kernel: ata1: EH complete Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: rejecting I/O to offline device Feb 13 01:04:28 debo-server kernel: ata1.00: detaching (SCSI 1:0:0:0) Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] Synchronizing SCSI cache Feb 13 01:04:28 debo-server kernel: sd 1:0:0:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Feb 13 01:04:29 debo-server emhttpd: read SMART /dev/sde Feb 13 01:04:29 debo-server emhttpd: read SMART /dev/sdf Feb 13 01:04:29 debo-server emhttpd: read SMART /dev/sdl Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014384 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014392 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014400 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014408 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014416 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014424 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014432 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014440 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014448 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014456 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014464 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014472 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014480 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014488 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014496 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014504 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014512 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014520 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014528 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014536 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014544 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014552 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014560 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014568 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014576 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014584 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014592 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014600 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014608 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014616 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014624 Feb 13 01:04:42 debo-server kernel: md: disk3 write error, sector=8674014632 debo-server-diagnostics-20240213-0928.zip Quote Link to comment
itimpi Posted February 13 Share Posted February 13 I cannot see any SMART report for disk3 which suggests it has dropped offline. It might be worth power cycling the server to see if that gets it back online and if it does posting new diagnostics. 7 minutes ago, B_Sinn3d said: It connected to LSI 9201 so I don't think it is cable since other drives that are on same SAS cable are OK. this does not mean there is no cabling issue - it can be just a case of the connector working itself slightly loose. You also need to check the power side of things as this can also cause issues. Quote Link to comment
B_Sinn3d Posted February 13 Author Share Posted February 13 Thanks itimpi! I will power off, reseat the cable(s) and power back on. Here is the last SMART report for that disk from Feb 3rd. WDC_WD120EDAZ-11F3RA0_5PK2AWJB-2023-08-31 disk3 (sdb).txt Quote Link to comment
itimpi Posted February 13 Share Posted February 13 4 minutes ago, B_Sinn3d said: Here is the last SMART report for that disk from Feb 3rd. Nothing spring out as indicating a problem. Doing the Extended SMART test on a drive is a good indication that if it passes it is probably OK, and failure means should be replaced. Quote Link to comment
B_Sinn3d Posted February 14 Author Share Posted February 14 FYI, extended smart passed. I will follow the below procedure to put it back into the array. https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself WDC_WD120EDAZ-11F3RA0_5PK2AWJB-20240214-1032.txt 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.