[kwlug-disc] DRDY errors on drive that passes smartcontrol

[Bob Jonkman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've seen this (Ubuntu server 12.04.5). The only thing running a smart
self-test will do is to completely bork the drive and make the data
unavailable.

Some data on that drive is already unavailable. Back up what you can
(might take a LONG time, what with the errors and all), and be
prepared to restore missing data from a previous backup taken before
the errors occurred.

- --Bob.

On 28/12/15 07:46 PM, Paul Nijjar wrote:
> I don't understand. I have a server running Ubuntu Server 14.04 .
> It is showing the following in the kernel log:
> 
> 
> Dec 28 07:27:37 my-server kernel: [3725104.096008] EXT4-fs (sdb2):
> error count since last fsck: 11 Dec 28 07:27:37 my-server kernel:
> [3725104.096017] EXT4-fs (sdb2): initial error at time 1449229394:
> ext4_readdir:167: inode 11 Dec 28 07:27:37 my-server kernel:
> [3725104.096021] EXT4-fs (sdb2): last error at time 1449792670:
> ext4_find_entry:1302: inode 2 Dec 28 15:21:18 my-server kernel:
> [3753525.630476] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0
> action 0x0 Dec 28 15:21:18 my-server kernel: [3753525.695122]
> ata2.00: irq_stat 0x40000001 Dec 28 15:21:19 my-server kernel:
> [3753525.757481] ata2.00: failed command: READ DMA Dec 28 15:21:19
> my-server kernel: [3753525.819524] ata2.00: cmd
> c8/00:08:08:29:00/00:00:00:00:00/e0 tag 12 dma 4096 in Dec 28
> 15:21:19 my-server kernel: [3753525.819524]          res
> 61/04:08:08:29:00/00:00:00:00:00/e0 Emask 0x1 (device error) Dec 28
> 15:21:19 my-server kernel: [3753526.083712] ata2.00: status: { DRDY
> DF ERR } Dec 28 15:21:19 my-server kernel: [3753526.083713]
> ata2.00: error: { ABRT } Dec 28 15:21:21 my-server kernel:
> [3753527.904312] ata2.00: failed to enable AA (error_mask=0x1) Dec
> 28 15:21:21 my-server kernel: [3753527.973446] ata2.00: failed to
> enable AA (error_mask=0x1) Dec 28 15:21:21 my-server kernel:
> [3753528.038829] ata2.00: configured for UDMA/133 (device error
> ignored) Dec 28 15:21:21 my-server kernel: [3753528.038844] ata2:
> EH complete Dec 28 15:21:21 my-server kernel: [3753528.038960]
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 28
> 15:21:21 my-server kernel: [3753528.104207] ata2.00: irq_stat
> 0x40000001 Dec 28 15:21:21 my-server kernel: [3753528.104209]
> ata2.00: failed command: READ DMA Dec 28 15:21:21 my-server kernel:
> [3753528.104213] ata2.00: cmd c8/00:08:08:29:00/00:00:00:00:00/e0
> tag 13 dma 4096 in Dec 28 15:21:21 my-server kernel:
> [3753528.104213]          res 61/04:08:08:29:00/00:00:00:00:00/e0
> Emask 0x1 (device error) Dec 28 15:21:21 my-server kernel:
> [3753528.104214] ata2.00: status: { DRDY DF ERR } Dec 28 15:21:21
> my-server kernel: [3753528.104215] ata2.00: error: { ABRT } Dec 28
> 15:21:25 my-server kernel: [3753528.167662] ata2.00: failed to
> enable AA (error_mask=0x1) Dec 28 15:21:25 my-server kernel:
> [3753528.230040] ata2.00: failed to enable AA (error_mask=0x1) Dec
> 28 15:21:25 my-server kernel: [3753528.230042] ata2.00: configured
> for UDMA/133 (device error ignored) Dec 28 15:21:25 my-server
> kernel: [3753528.230139] ata2: EH complete Dec 28 15:21:25
> my-server kernel: [3753528.494663] ata2.00: exception Emask 0x0
> SAct 0x0 SErr 0x0 action 0x0 Dec 28 15:21:25 my-server kernel:
> [3753528.494664] ata2.00: irq_stat 0x40000001
> 
> 
> The Internet seems to think this means the drive is dead:
> 
> http://serverfault.com/questions/511669/kernel-panic-no-idea-how-to-fix/511671
>
>  but when I network boot the machine into a Live CD and run 
> gsmartcontrol, both the short and extended tests pass. I can also
> fsck the file systems successfully.
> 
> I no longer trust the drive and do not intend to use it further.
> But I do not understand why I cannot find evidence that the drive
> is bad.
> 
> This makes me worried that the problem is not the drive but the 
> server.
> 
> Do these symptoms make sense to anybody on the list?
> 
> - Paul
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Ensure confidentiality, authenticity, non-repudiability

iEYEARECAAYFAlaCpN0ACgkQuRKJsNLM5epjgACfW8x2vQr4RjiSiJ7GGGuD/5xN
c68AoOull5+YVgo4hdyjBNA03KPSYhIR
=YXul
-----END PGP SIGNATURE-----