Compré un nuevo disco duro WD Black de 4 TB y no se detecta después de conectar mi servidor HP ProLiant DL380. Lo probé en diferentes PC y controladores, pero lo mismo que envié al HDD ya lo recuperé una vez.
Aquí hay un registro de salida de dmesg de mi sistema Linux Kali, después de ingresarlo directamente:
[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)
Quizás alguien pueda ayudarme con esto. Gracias.
Respuesta1
Ese disco está roto. Reacciona al primer comando de sonda, pero tan pronto como el sistema Linux intenta obtener información adicional (como las capacidades y el tamaño de la unidad), no responde.
Y sus otros sistemas tienen el mismo problema.
Efectivamente el disco queda completamente inutilizable.
Como es nuevo, todavía debería estar en garantía: haga que lo reemplacen en la tienda donde lo compró o envíelo para RMA directamente a Western Digital (los procedimientos de WD RAM se pueden encontrar en su sitio web).
Respuesta2
Para futuros usuarios de Google: recibí exactamente los mismos mensajes de error en el registro después de dejar caer accidentalmente un disco al suelo. Cuando recibe estos errores, existe una gran posibilidad de que su disco esté tostado, como sugiere la otra respuesta. Antes de mi accidente el disco funcionaba perfectamente.