[SOLVED] A few "errors", "minor issues" and "drive related" items in syslog

[ieatwarez]

I have not used my anything on my unraid machine in a while, almost a week or so. Today I pulled up tower:8080 to check temps and noticed this in my syslog.

What can exactly happened and is there anything I can do to prevent this.

I am running 5.0-rc6-r8168-test

 

 

Aug 24 00:16:30 Tower kernel:  (Routine)
Aug 24 00:16:34 Tower kernel: mdcmd (144): spindown 1 (Routine)
Aug 24 00:16:34 Tower kernel:  (Routine)
Aug 24 01:51:28 Tower kernel: mdcmd (145): spindown 12 (Routine)
Aug 24 13:45:39 Tower kernel: mdcmd (146): spindown 12 (Routine)
Aug 24 14:19:32 Tower kernel: mdcmd (147): spindown 11 (Routine)
[color=red]Aug 24 21:00:21 Tower kernel: ata13.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)[/color]
[color=orange]Aug 24 21:00:21 Tower kernel: ata13.00: failed command: SMART (Minor Issues)[/color]
[color=limegreen]Aug 24 21:00:21 Tower kernel: ata13.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related)[/color]
[color=red]Aug 24 21:00:21 Tower kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors)[/color]
[color=limegreen]Aug 24 21:00:21 Tower kernel: ata13.00: status: { DRDY } (Drive related)[/color]
[color=orange]Aug 24 21:00:21 Tower kernel: ata13: hard resetting link (Minor Issues)[/color]
[color=limegreen]Aug 24 21:00:24 Tower kernel: ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Aug 24 21:00:24 Tower kernel: ata13.00: configured for UDMA/133 (Drive related)
Aug 24 21:00:24 Tower kernel: ata13: EH complete (Drive related)[/color]
Aug 24 21:44:32 Tower kernel: mdcmd (148): spindown 10 (Routine)
Aug 24 21:51:54 Tower kernel: mdcmd (149): spindown 11 (Routine)
Aug 25 00:10:51 Tower kernel: mdcmd (150): spindown 11 (Routine)
Aug 25 02:15:05 Tower kernel: mdcmd (151): spindown 11 (Routine)
Aug 26 04:23:41 Tower kernel: mdcmd (152): spindown 8 (Routine)

 

I have this as my smart information as shown in myMain:

I wonder if those random Seagates are junk.

 

[pantner]

Looks like that HDD is failing.

from http://en.wikipedia.org/wiki/S.M.A.R.T.

 

Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks that sector as "reallocated" and transfers data to a special reserved area (spare area). This process is also known as remapping, and reallocated sectors are called "remaps". The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future.[2] While primarily used as a metric of the life expectancy of the drive, this number also affects performance. As the count of reallocated sectors increases, the read/write speed tends to become worse because the drive head is forced to seek to the reserved area whenever a remap is accessed. A workaround which will preserve drive speed at the expense of capacity is to create a disk partition over the region which contains remaps and instruct the operating system to not use that partition.

 

and Spin Retry Count

Count of retry of spin start attempts. This attribute stores a total count of the spin start attempts to reach the fully operational speed (under the condition that the first attempt was unsuccessful). An increase of this attribute value is a sign of problems in the hard disk mechanical subsystem.

 

i would replace it ASAP

[ieatwarez]

Thanks. I appreciate the response.