phoenix73 Posted June 7, 2014 #1 Posted June 7, 2014 Hi all Yesterday I got an email from my NAS about read errors after 5 tries. I rebooted system and did a quick SMART test on both disks, no error reported. Today, same problem and I took a look in /var/log/messages via ssh Jun 7 23:14:58 MyNas kernel: [ 689.255816] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Jun 7 23:14:58 MyNas kernel: [ 689.255818] ata1.00: irq_stat 0x40000008 Jun 7 23:14:58 MyNas kernel: [ 689.255822] ata1.00: failed command: READ FPDMA QUEUED Jun 7 23:14:58 MyNas kernel: [ 689.255828] ata1.00: cmd 60/08:00:c0:50:11/00:00:01:00:00/40 tag 0 ncq 4096 in Jun 7 23:14:58 MyNas kernel: [ 689.255829] res 41/40:00:c0:50:11/00:00:01:00:00/40 Emask 0x409 (media error) Jun 7 23:14:58 MyNas kernel: [ 689.255832] ata1.00: status: { DRDY ERR } Jun 7 23:14:58 MyNas kernel: [ 689.255834] ata1.00: error: { UNC } Jun 7 23:15:02 MyNas kernel: [ 695.867866] ata1.00: read unc at 17912064 Jun 7 23:15:02 MyNas kernel: [ 695.867872] lba 17912064 start 9453280 end 3907015007 Jun 7 23:15:02 MyNas kernel: [ 695.867874] sda5 auto_remap 0 Jun 7 23:15:02 MyNas kernel: [ 695.867880] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 Jun 7 23:15:02 MyNas kernel: [ 695.867883] ata1.00: irq_stat 0x40000008 Jun 7 23:15:02 MyNas kernel: [ 695.867887] ata1.00: failed command: READ FPDMA QUEUED Jun 7 23:15:02 MyNas kernel: [ 695.867893] ata1.00: cmd 60/08:00:00:51:11/00:00:01:00:00/40 tag 0 ncq 4096 in Jun 7 23:15:02 MyNas kernel: [ 695.867894] res 41/40:00:00:51:11/00:00:01:00:00/40 Emask 0x409 (media error) Jun 7 23:15:02 MyNas kernel: [ 695.867897] ata1.00: status: { DRDY ERR } Jun 7 23:15:02 MyNas kernel: [ 695.867899] ata1.00: error: { UNC } Jun 7 23:15:05 MyNas kernel: [ 699.612299] ata1.00: read unc at 17912064 Jun 7 23:15:05 MyNas kernel: [ 699.612304] lba 17912064 start 9453280 end 3907015007 Jun 7 23:15:05 MyNas kernel: [ 699.612307] sda5 auto_remap 0 Jun 7 23:15:05 MyNas kernel: [ 699.612313] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 Jun 7 23:15:05 MyNas kernel: [ 699.612315] ata1.00: irq_stat 0x40000008 Jun 7 23:15:05 MyNas kernel: [ 699.612319] ata1.00: failed command: READ FPDMA QUEUED Jun 7 23:15:05 MyNas kernel: [ 699.612325] ata1.00: cmd 60/08:08:00:51:11/00:00:01:00:00/40 tag 1 ncq 4096 in Jun 7 23:15:05 MyNas kernel: [ 699.612326] res 41/40:00:00:51:11/00:00:01:00:00/40 Emask 0x409 (media error) Jun 7 23:15:05 MyNas kernel: [ 699.612329] ata1.00: status: { DRDY ERR } Jun 7 23:15:05 MyNas kernel: [ 699.612331] ata1.00: error: { UNC } Jun 7 23:15:09 MyNas kernel: [ 703.345645] ata1.00: read unc at 17912064 Jun 7 23:15:09 MyNas kernel: [ 703.345650] lba 17912064 start 9453280 end 3907015007 Jun 7 23:15:09 MyNas kernel: [ 703.345653] sda5 auto_remap 0 Jun 7 23:15:09 MyNas kernel: [ 703.345659] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 Jun 7 23:15:09 MyNas kernel: [ 703.345661] ata1.00: irq_stat 0x40000008 Jun 7 23:15:09 MyNas kernel: [ 703.345665] ata1.00: failed command: READ FPDMA QUEUED Jun 7 23:15:09 MyNas kernel: [ 703.345671] ata1.00: cmd 60/08:00:00:51:11/00:00:01:00:00/40 tag 0 ncq 4096 in Jun 7 23:15:09 MyNas kernel: [ 703.345673] res 41/40:00:00:51:11/00:00:01:00:00/40 Emask 0x409 (media error) Jun 7 23:15:09 MyNas kernel: [ 703.345675] ata1.00: status: { DRDY ERR } Jun 7 23:15:09 MyNas kernel: [ 703.345677] ata1.00: error: { UNC } No more doubt disk1 has defect sectors. I shutdowned NAS, remove disk 1 and NAS restarted from disk 2 in degradated mode. Question : - Why did SMART didn't reports any errors before this failure ? - SMART on WD Green is safe ? - Do you thing Data Lifeguard Diagnostic for Windows will be able to fix bad sectors and remap them or should I send disk to repair ? Thanks for your help
Recommended Posts