Comprei um novo HDD WD Black de 4 TB e ele não foi detectado depois de conectado ao meu servidor HP ProLiant DL380. Eu apenas tentei em diferentes PCs e controladores, mas a mesma coisa que enviei para o HDD já retornei uma vez.
Aqui está um log de saída dmesg do meu sistema Linux Kali, depois de inserido diretamente:
[Tue Aug 13 06:56:41 2019] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Aug 13 06:56:41 2019] ata1.00: failed to read native max address (err_mask=0x100)
[Tue Aug 13 06:56:41 2019] ata1.00: HPA support seems broken, skipping HPA handling
[Tue Aug 13 06:56:47 2019] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable AA (error_mask=0x1)
[Tue Aug 13 06:56:47 2019] ata1.00: READ LOG DMA EXT failed, trying PIO
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: ATA-9: WDC WD4005FZBX-00K5WB0, 01.01A01, max UDMA/133
[Tue Aug 13 06:56:47 2019] ata1.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 32)
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable Sense Data Reporting, Emask 0x1
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable AA (error_mask=0x1)
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable Sense Data Reporting, Emask 0x1
[Tue Aug 13 06:56:47 2019] ata1.00: configured for UDMA/133 (device error ignored)
[Tue Aug 13 06:56:47 2019] scsi 0:0:0:0: Direct-Access ATA WDC WD4005FZBX-0 1A01 PQ: 0 ANSI: 5
[Tue Aug 13 06:56:47 2019] sd 0:0:0:0: Attached scsi generic sg1 type 0
[Tue Aug 13 06:56:47 2019] sd 0:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[Tue Aug 13 06:56:47 2019] sd 0:0:0:0: [sdb] Write Protect is off
[Tue Aug 13 06:56:47 2019] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[Tue Aug 13 06:56:47 2019] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Tue Aug 13 06:56:47 2019] ata1: failed to read log page 10h (errno=-5)
[Tue Aug 13 06:56:47 2019] ata1.00: exception Emask 0x1 SAct 0x1000000 SErr 0x0 action 0x0
[Tue Aug 13 06:56:47 2019] ata1.00: irq_stat 0x40000001
[Tue Aug 13 06:56:47 2019] ata1.00: failed command: READ FPDMA QUEUED
[Tue Aug 13 06:56:47 2019] ata1.00: cmd 60/08:c0:00:00:00/00:00:00:00:00/40 tag 24 ncq dma 4096 in
res 41/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[Tue Aug 13 06:56:47 2019] ata1.00: status: { DRDY ERR }
[Tue Aug 13 06:56:47 2019] ata1.00: error: { ABRT }
[Tue Aug 13 06:56:47 2019] ata1.00: both IDENTIFYs aborted, assuming NODEV
[Tue Aug 13 06:56:47 2019] ata1.00: revalidation failed (errno=-2)
[Tue Aug 13 06:56:47 2019] ata1: hard resetting link
[Tue Aug 13 06:56:47 2019] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable AA (error_mask=0x1)
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable Sense Data Reporting, Emask 0x1
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable AA (error_mask=0x1)
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:47 2019] ata1.00: failed to enable Sense Data Reporting, Emask 0x1
[Tue Aug 13 06:56:47 2019] ata1.00: configured for UDMA/133 (device error ignored)
[Tue Aug 13 06:56:47 2019] ata1: EH complete
[Tue Aug 13 06:56:47 2019] ata1: failed to read log page 10h (errno=-5)
[Tue Aug 13 06:56:47 2019] ata1.00: NCQ disabled due to excessive errors
[Tue Aug 13 06:56:47 2019] ata1.00: exception Emask 0x1 SAct 0x8 SErr 0x0 action 0x0
[Tue Aug 13 06:56:47 2019] ata1.00: irq_stat 0x40000001
[Tue Aug 13 06:56:47 2019] ata1.00: failed command: READ FPDMA QUEUED
[Tue Aug 13 06:56:47 2019] ata1.00: cmd 60/08:18:00:00:00/00:00:00:00:00/40 tag 3 ncq dma 4096 in
res 41/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[Tue Aug 13 06:56:47 2019] ata1.00: status: { DRDY ERR }
[Tue Aug 13 06:56:47 2019] ata1.00: error: { ABRT }
[Tue Aug 13 06:56:47 2019] ata1.00: both IDENTIFYs aborted, assuming NODEV
[Tue Aug 13 06:56:47 2019] ata1.00: revalidation failed (errno=-2)
[Tue Aug 13 06:56:47 2019] ata1: hard resetting link
[Tue Aug 13 06:56:48 2019] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Aug 13 06:56:48 2019] ata1.00: failed to enable AA (error_mask=0x1)
[Tue Aug 13 06:56:48 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:48 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:48 2019] ata1.00: failed to enable Sense Data Reporting, Emask 0x1
[Tue Aug 13 06:56:48 2019] ata1.00: failed to enable AA (error_mask=0x1)
[Tue Aug 13 06:56:48 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:48 2019] ata1.00: NCQ Send/Recv Log not supported
[Tue Aug 13 06:56:48 2019] ata1.00: failed to enable Sense Data Reporting, Emask 0x1
[Tue Aug 13 06:56:48 2019] ata1.00: configured for UDMA/133 (device error ignored)
[Tue Aug 13 06:56:48 2019] ata1: EH complete
[Tue Aug 13 06:56:48 2019] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Tue Aug 13 06:56:48 2019] ata1.00: irq_stat 0x40000001
[Tue Aug 13 06:56:48 2019] ata1.00: failed command: READ DMA
[Tue Aug 13 06:56:48 2019] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 18 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
Talvez alguém possa me ajudar com isso. Obrigado.
Responder1
Esse disco está quebrado. Ele reage ao primeiro comando de teste, mas assim que o sistema Linux tenta obter informações adicionais (como capacidade e tamanho da unidade), ele não responde.
E seus outros sistemas enfrentam o mesmo problema.
Efetivamente, o disco está completamente inutilizável.
Como é novo, ainda deve estar na garantia: substitua-o na loja onde o comprou ou envie-o para RMA diretamente para a Western Digital (os procedimentos do WD RAM podem ser encontrados em seu site).
Responder2
Para futuros googlers: recebi exatamente as mesmas mensagens de erro no log após deixar cair acidentalmente um disco no chão. Quando você recebe esses erros, há uma grande chance de seu disco estar torrado, como sugere a outra resposta. Antes do meu acidente, o disco funcionava perfeitamente.