Jump to content

Errors


MvL

Recommended Posts

Hi,

 

I need some help from a experienced user. Today i had my first errors on one of my 1TB drives. What is my next move? Test the drive? Remove the drive from the array? RMA? Thank you.

 

I'm using unRAID 5.0 Beta 2. All important stuff is backed up.

 

syslog:

Nov  5 20:05:29 Tower emhttp: shcmd (27): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Nov  5 20:05:29 Tower emhttp: shcmd (28): cp /etc/exports- /etc/exports

Nov  5 20:05:29 Tower emhttp: shcmd (29): echo '/mnt/disk2 -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=99,anonuid=100,all_squash)' >>/etc/exports

Nov  5 20:05:29 Tower emhttp: shcmd (30): echo '/mnt/user/Television-series -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=99,anonuid=100,all_squash)' >>/etc/exports

Nov  5 20:05:29 Tower emhttp: Restart CIFS...

Nov  5 20:05:29 Tower emhttp: shcmd (31): killall -HUP smbd

Nov  5 20:05:29 Tower emhttp: Restart NFS...

Nov  5 20:05:29 Tower emhttp: shcmd (32): exportfs -ra | logger

Nov  5 20:05:29 Tower emhttp: shcmd (33): /usr/local/emhttp/emhttp_event svcs_restarted

Nov  5 20:05:29 Tower emhttp_event: svcs_restarted

Nov  5 20:23:55 Tower emhttp: shcmd (34): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Nov  5 20:23:55 Tower emhttp: shcmd (35): cp /etc/exports- /etc/exports

Nov  5 20:23:55 Tower emhttp: shcmd (36): echo '/mnt/disk2 -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=99,anonuid=100,all_squash)' >>/etc/exports

Nov  5 20:23:55 Tower emhttp: shcmd (37): echo '/mnt/user/Television-series -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=99,anonuid=100,all_squash)' >>/etc/exports

Nov  5 20:23:55 Tower emhttp: Restart CIFS...

Nov  5 20:23:55 Tower emhttp: shcmd (38): killall -HUP smbd

Nov  5 20:23:55 Tower emhttp: Restart NFS...

Nov  5 20:23:55 Tower emhttp: shcmd (39): exportfs -ra | logger

Nov  5 20:23:55 Tower emhttp: shcmd (40): /usr/local/emhttp/emhttp_event svcs_restarted

Nov  5 20:23:55 Tower emhttp_event: svcs_restarted

Nov  5 22:09:05 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  5 22:09:05 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  5 22:09:05 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  5 22:09:05 Tower kernel: ata3.00: cmd 25/00:00:8f:98:12/00:04:00:00:00/e0 tag 0 dma 524288 in

Nov  5 22:09:05 Tower kernel:          res 51/40:62:2d:9a:12/00:00:00:00:00/e0 Emask 0x9 (media error)

Nov  5 22:09:05 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  5 22:09:05 Tower kernel: ata3.00: error: { UNC }

Nov  5 22:09:05 Tower kernel: ata3.00: configured for UDMA/133

Nov  5 22:09:05 Tower kernel: ata3: EH complete

Nov  5 22:09:10 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  5 22:09:10 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  5 22:09:10 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  5 22:09:10 Tower kernel: ata3.00: cmd 25/00:00:8f:98:12/00:04:00:00:00/e0 tag 0 dma 524288 in

Nov  5 22:09:10 Tower kernel:          res 51/40:62:2d:9a:12/00:00:00:00:00/e0 Emask 0x9 (media error)

Nov  5 22:09:10 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  5 22:09:10 Tower kernel: ata3.00: error: { UNC }

Nov  5 22:09:10 Tower kernel: ata3.00: configured for UDMA/133

Nov  5 22:09:10 Tower kernel: ata3: EH complete

Nov  5 22:09:15 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  5 22:09:15 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  5 22:09:15 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  5 22:09:15 Tower kernel: ata3.00: cmd 25/00:00:8f:98:12/00:04:00:00:00/e0 tag 0 dma 524288 in

Nov  5 22:09:15 Tower kernel:          res 51/40:62:2d:9a:12/00:00:00:00:00/e0 Emask 0x9 (media error)

Nov  5 22:09:15 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  5 22:09:15 Tower kernel: ata3.00: error: { UNC }

Nov  5 22:09:15 Tower kernel: ata3.00: configured for UDMA/133

Nov  5 22:09:15 Tower kernel: ata3: EH complete

Nov  5 22:09:19 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  5 22:09:19 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  5 22:09:19 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  5 22:09:19 Tower kernel: ata3.00: cmd 25/00:00:8f:98:12/00:04:00:00:00/e0 tag 0 dma 524288 in

Nov  5 22:09:19 Tower kernel:          res 51/40:62:2d:9a:12/00:00:00:00:00/e0 Emask 0x9 (media error)

Nov  5 22:09:19 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  5 22:09:19 Tower kernel: ata3.00: error: { UNC }

Nov  5 22:09:19 Tower kernel: ata3.00: configured for UDMA/133

Nov  5 22:09:19 Tower kernel: ata3: EH complete

Nov  5 22:09:24 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  5 22:09:24 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  5 22:09:24 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  5 22:09:24 Tower kernel: ata3.00: cmd 25/00:00:8f:98:12/00:04:00:00:00/e0 tag 0 dma 524288 in

Nov  5 22:09:24 Tower kernel:          res 51/40:62:2d:9a:12/00:00:00:00:00/e0 Emask 0x9 (media error)

Nov  5 22:09:24 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  5 22:09:24 Tower kernel: ata3.00: error: { UNC }

Nov  5 22:09:24 Tower kernel: ata3.00: configured for UDMA/133

Nov  5 22:09:24 Tower kernel: ata3: EH complete

Nov  5 22:09:28 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  5 22:09:28 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  5 22:09:28 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  5 22:09:28 Tower kernel: ata3.00: cmd 25/00:00:8f:98:12/00:04:00:00:00/e0 tag 0 dma 524288 in

Nov  5 22:09:28 Tower kernel:          res 51/40:62:2d:9a:12/00:00:00:00:00/e0 Emask 0x9 (media error)

Nov  5 22:09:28 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  5 22:09:28 Tower kernel: ata3.00: error: { UNC }

Nov  5 22:09:28 Tower kernel: ata3.00: configured for UDMA/133

Nov  5 22:09:28 Tower kernel: sd 3:0:0:0: [sdc] Unhandled sense code

Nov  5 22:09:28 Tower kernel: sd 3:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08

Nov  5 22:09:28 Tower kernel: sd 3:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor]

Nov  5 22:09:28 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov  5 22:09:28 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov  5 22:09:28 Tower kernel:        00 12 9a 2d

Nov  5 22:09:28 Tower kernel: sd 3:0:0:0: [sdc] ASC=0x11 ASCQ=0x4

Nov  5 22:09:28 Tower kernel: sd 3:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 12 98 8f 00 04 00 00

Nov  5 22:09:28 Tower kernel: end_request: I/O error, dev sdc, sector 1219117

Nov  5 22:09:28 Tower kernel: ata3: EH complete

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219048/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219056/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219064/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219072/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219080/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219088/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219096/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219104/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219112/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219120/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219128/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219136/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219144/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219152/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219160/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219168/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219176/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219184/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219192/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219200/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219208/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219216/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219224/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219232/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219240/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219248/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219256/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219264/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219272/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219280/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219288/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219296/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219304/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219312/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219320/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219328/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219336/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219344/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219352/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219360/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219368/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219376/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219384/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219392/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219400/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219408/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219416/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219424/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219432/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219440/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219448/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219456/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219464/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219472/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219480/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219488/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219496/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219504/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219512/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219520/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219528/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219536/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219544/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219552/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219560/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219568/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219576/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219584/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219592/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219600/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219608/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219616/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219624/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219632/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219640/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219648/2, count: 1

Nov  5 22:09:28 Tower kernel: md: disk2 read error

Nov  5 22:09:28 Tower kernel: handle_stripe read error: 1219656/2, count: 1

Link to comment

A media error is an un-readable sector. unRAID already re-wrote it to the ailing disk.

 

You can get a smart report on that disk and track it over time.

 

Disks typically have a pool of several thousand spare sectors, so unless there are more in a short time frame there's nothing to do at all.

 

If you see a lot of re-allocated sectors occurring, and it does not settle down (they don't stop occurring), then it is time to RMA the drive. 

Link to comment

Thanks for explaining Joe L.

 

I did some testing.

 

smartctl -d ata -tshort /dev/sdc
smartctl -d ata -tlong /dev/sdc

 

and the long test found some errors

 

Error 195 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

Error 194 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

Error 193 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

193 Load_Cycle_Count        0x0012  100  100  000    Old_age  Always      -      188

194 Temperature_Celsius    0x0002  240  240  000    Old_age  Always      -      25 (Lifetime Min/Max 21/54)

196 Reallocated_Event_Count 0x0032  100  100  000    Old_age  Always      -      54

197 Current_Pending_Sector  0x0022  100  100  000    Old_age  Always      -      1

198 Offline_Uncorrectable  0x0008  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x000a  200  200  000    Old_age  Always      -      0

 

So it has Load_Cycle_Count, Temperature_Celsius errors (error 195 is not listed). This is the first time i'm dealing with s.m.a.r.t data. I'm correct? I also attach the s.m.a.r.t output. What do you think?

smart.txt

Link to comment

Thanks for explaining Joe L.

 

I did some testing.

 

smartctl -d ata -tshort /dev/sdc
smartctl -d ata -tlong /dev/sdc

 

and the long test found some errors

 

Error 195 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

Error 194 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

Error 193 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       188

194 Temperature_Celsius     0x0002   240   240   000    Old_age   Always       -       25 (Lifetime Min/Max 21/54)

196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       54

197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       1

198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0

199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

 

So it has Load_Cycle_Count, Temperature_Celsius errors (error 195 is not listed). This is the first time i'm dealing with s.m.a.r.t data. I'm correct? I also attach the s.m.a.r.t output. What do you think?

The smart report you attached is NOT from the same disk as the smart excerpts you posted.  It shows none of the re-allocated sectors or events.
Link to comment

Drive looks bad. 54 reallocated sectors. Usually when you get that many they will continue to grow in numbers. RMA the disk.

 

Thanks for the feedback bjp999.

 

Thanks for explaining Joe L.

 

I did some testing.

 

smartctl -d ata -tshort /dev/sdc
smartctl -d ata -tlong /dev/sdc

 

and the long test found some errors

 

Error 195 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

Error 194 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

Error 193 occurred at disk power-on lifetime: 1297 hours (54 days + 1 hours)

  When the command that caused the error occurred, the device was active or idle.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

193 Load_Cycle_Count        0x0012  100  100  000    Old_age  Always      -      188

194 Temperature_Celsius    0x0002  240  240  000    Old_age  Always      -      25 (Lifetime Min/Max 21/54)

196 Reallocated_Event_Count 0x0032  100  100  000    Old_age  Always      -      54

197 Current_Pending_Sector  0x0022  100  100  000    Old_age  Always      -      1

198 Offline_Uncorrectable  0x0008  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x000a  200  200  000    Old_age  Always      -      0

 

So it has Load_Cycle_Count, Temperature_Celsius errors (error 195 is not listed). This is the first time i'm dealing with s.m.a.r.t data. I'm correct? I also attach the s.m.a.r.t output. What do you think?

The smart report you attached is NOT from the same disk as the smart excerpts you posted.  It shows none of the re-allocated sectors or events.

 

Did I?  :-[ Hmm, I'm not at home right now. When i'm at home i will check again. Sorry I wasted your time Joe L.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...