November 14, 201510 yr hi guys looking for some help again. I have a drive that has shown the Red status twice now in two weeks. The first time it happened, I pulled the reports and the SMART report did not show any attributes that would indicate an issue. So I rebuilt the drive, and since I was running v5.0, decided I would complete the upgrade as well. Now I just upgrade to V6 and after I forgot to shutdown the dockers before a trying to stop the array, I started a parity check and in the midst of it, it stopped and showed a Red status on the same drive again. Can someone help me take a look to see if I missed anything? Is my drive officially dead? WDC_WD5000AAKS-00YGA0_WD-WCAS83025655-diagnostics-20151114.txt
November 14, 201510 yr Author couldn't attach the full syslog due to size but here is the last entries: Nov 14 00:46:54 wilS-tower kernel: md: disk2: ATA_OP e0 ioctl error: -5 Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:04 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 14 00:47:17 wilS-tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
November 14, 201510 yr Community Expert The disk dropped offline, can’t do a SMART report like that, if you haven’t rebooted since the redball capture the entire syslog (or better yet tools > diagnostics). Then power off server, power on and try again a SMART report on that disk.
November 15, 201510 yr Author here is the smart report. but I can't copy the syslog as the file is too big WDC_WD5000AAKS-00YGA0_WD-WCAS83025655-20151114-2001.txt
November 15, 201510 yr Community Expert here is the smart report. but I can't copy the syslog as the file is too big ...better yet tools > diagnostics...
November 15, 201510 yr Author here is the smart report. but I can't copy the syslog as the file is too big ...better yet tools > diagnostics... How does that help? The syslog is 448kb and the forum attachment limit is 192kb?
November 15, 201510 yr Is the size of the syslog file that you quote the size before or after it has been compressed using zip? The diagnostic command uses zip which significantly reduces the size of the saved syslog file, as well as the other files it packages up for analysis. Have you tried running the diagnostic command to see what size file it produces?
November 15, 201510 yr Community Expert Based on the SMART report disk looks healthy, but keep an eye on this value: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 26 If it keeps increasing check your sata cable/connections. Without the diagnostics can’t say much more, but a healthy SMART report does not always equals an healthy disk, just recently had to replace a 3TB WD green that would go offline once in a while and SMART info also looked healthy, confirmed by using the disk on a different server and having the same issue, if you can’t do that try to connect it to a different controller (also use different power and sata cables)
November 15, 201510 yr SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Turn off the spindown timer on this particular drive. Then issue a smart long test. The short test is insufficient. Review the log after the completion of the test. According to this value, it will take almost 3 hours. Extended self-test routine recommended polling time: ( 154) minutes. Pending sectors sometimes do not show up until you scan the surface.
Archived
This topic is now archived and is closed to further replies.