dedighar Posted December 30, 2023 Share Posted December 30, 2023 Hi, I just purchased and shucked a WD80EZAZ-11TDBA0 8TB disk, but I am not able to get the unraid box to recognize it correctly. See attached diagnostic zip file. The dmesg log file show these related entries: [ 23.373062] sd 7:0:0:0: [sdf] Attached SCSI removable disk [ 29.214235] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 330) [ 29.214581] ata8.00: supports DRM functions and may not be fully accessible [ 29.214628] ata8.00: ATA-9: WDC WD80EZAZ-11TDBA0, 83.H0A83, max UDMA/133 [ 29.215030] ata8.00: failed to enable AA (error_mask=0x1) [ 29.225580] ata8.00: Read log 0x00 page 0x00 failed, Emask 0x1 [ 29.225629] ata8.00: NCQ Send/Recv Log not supported [ 29.225667] ata8.00: Read log 0x00 page 0x00 failed, Emask 0x40 [ 29.225706] ata8.00: NCQ Send/Recv Log not supported [ 29.225742] ata8.00: Read log 0x00 page 0x00 failed, Emask 0x40 [ 29.225781] ata8.00: 15628053168 sectors, multi 0: LBA48 NCQ (depth 32) [ 29.225822] ata8.00: Security Log not supported [ 29.225867] ata8.00: failed to set xfermode (err_mask=0x40) [ 29.225907] ata8: limiting SATA link speed to 3.0 Gbps I have use a molex to sata adaptor to get around the 3.3v issue, and I can hear that the drive spin up, but the drive is not recognized. Does anyone have an idea or clue of what might cause this error? What do I need to do in order to make use of this disk in unraid? The data cable used was borrowed from another disk known to be working OK. tower-diagnostics-20231230-1718.zip Quote Link to comment
Nano Posted December 31, 2023 Share Posted December 31, 2023 17 hours ago, dedighar said: Hi, I just purchased and shucked a WD80EZAZ-11TDBA0 8TB disk, but I am not able to get the unraid box to recognize it correctly. See attached diagnostic zip file. The dmesg log file show these related entries: [ 23.373062] sd 7:0:0:0: [sdf] Attached SCSI removable disk [ 29.214235] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 330) [ 29.214581] ata8.00: supports DRM functions and may not be fully accessible [ 29.214628] ata8.00: ATA-9: WDC WD80EZAZ-11TDBA0, 83.H0A83, max UDMA/133 [ 29.215030] ata8.00: failed to enable AA (error_mask=0x1) [ 29.225580] ata8.00: Read log 0x00 page 0x00 failed, Emask 0x1 [ 29.225629] ata8.00: NCQ Send/Recv Log not supported [ 29.225667] ata8.00: Read log 0x00 page 0x00 failed, Emask 0x40 [ 29.225706] ata8.00: NCQ Send/Recv Log not supported [ 29.225742] ata8.00: Read log 0x00 page 0x00 failed, Emask 0x40 [ 29.225781] ata8.00: 15628053168 sectors, multi 0: LBA48 NCQ (depth 32) [ 29.225822] ata8.00: Security Log not supported [ 29.225867] ata8.00: failed to set xfermode (err_mask=0x40) [ 29.225907] ata8: limiting SATA link speed to 3.0 Gbps I have use a molex to sata adaptor to get around the 3.3v issue, and I can hear that the drive spin up, but the drive is not recognized. Does anyone have an idea or clue of what might cause this error? What do I need to do in order to make use of this disk in unraid? The data cable used was borrowed from another disk known to be working OK. tower-diagnostics-20231230-1718.zip 88.93 kB · 1 download have you got any black electrical tape? I think that's the next best option as it could be the adapter, I also would not trust them as they are known to burn. Quote Link to comment
dedighar Posted December 31, 2023 Author Share Posted December 31, 2023 Tried the tape-trick first, same result. I found the original adapter to the disk, the one connected to power and data, and makes it a usb drive. Connected it to windows. Windows see the disk, but all operations to the disk fails. Diskmanager see the disk, but unable to perform any action to the disk. Windows report that the disk is un-initialized, but is not able to initialize the disk. So, my conclusion is that the disk is really dead - just turned into an expensive paper weight.... Quote Link to comment
JorgeB Posted December 31, 2023 Share Posted December 31, 2023 That looks like a drive issue, but try swapping cables/port with known good ones, if the same it's likely the disk. Quote Link to comment
Solution dedighar Posted December 31, 2023 Author Solution Share Posted December 31, 2023 Tried the disk in 3 different machines. 'Borrowed' ports/cables from known good disks, so ports and cables probably OK. Same result. Better to move on, take the loss, and order a new disk. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.