Hello !

Need full firmware /modules/ for this drive :

wd80efax-68knbn0 F/W - 81.00a81

Thanks !

AFAIK, that's a native HGST model, possibly a rebadged HGST Ultrastar 7K8 / DC HC320.

_________________
A backup a day keeps DR away.

I would imagine it has locked FW?

_________________
HDD, SSD, Flash and RAID Data Recovery
Founder of The Data Recovery Professionals Group

Drive is spinning, windows can see it, victoria see it.
if I have to be honest the drive behaves as if it is locked with an ATA password.
SMART is not shown correctly.

Some suggestion ..what can i do to repeir the drive ?
Information on the rive is not important.


When try to do read test in Victoria :

08:26:59 : Starting Reading, LBA=0..15628053167, FULL, sequential access, timeout 10000ms
08:26:59 : Block start at 0 (0) Read error: UNCR "Data error (cyclic redundancy check)"
08:26:59 : Block start at 2048 (1 Mb) Read error: UNCR "Data error (cyclic redundancy check)"
08:26:59 : Block start at 4096 (2 Mb) Read error: UNCR "Data error (cyclic redundancy check)"
08:26:59 : Block start at 6144 (3 Mb) Read error: UNCR "Data error (cyclic redundancy check)"


Status in Victoria :


Model: WDC WD80EFAX-68KNBN0
Firmware: 81.00A81
Serial: VAHXE6WL
Disk size: 15628053168 LBAs 8.0 Tb
SMART: Enabled, Errlog, Selftest
CACHE: Unk.size; L/A=ON; Wr=ON; ok
Support: LBA, HPA, APM, DLM, DCO, DMAUDMA-6
APM val: 164 Enabled
Erase: ~ 12 hours 20 minutes
Security: OFF
ATA-8: SATA3, NCQ, PEC, SCT, SFDLM, WrUnk
SCT: AC2, AC3, AC4, AC5
SSD ext: SANITIZE
Sector: Logic 512 bytes Phys 512

"Data error (cyclic redundancy check)" points at media or HSA trouble.

_________________
Digitalsupport Data Recovery
https://digitalsupport.dk

Thanks.
What can i do to understand ?

He thinks this a DIY case. I offered him a very chip repair. He denied it.

Hi, BGman.
This is not true.
This was time ago and for WD60PURX HDD's.And if you remember ...the disk was 2 or 3.You offer me to repair drives and one of them to remain for you as a gift for your work done.No offence , ok ? I told you that I will try it myself.For 6 months I have been paying for a vdmarvel license and a lot of discs have passed through me already. I'm not bragging, I'm just gaining experience.These first for me /WD60PURX/ disks are currently working in a raid array successfully. I just didn't have that much experience these early days. And now I don't have much, but I'm learning successfully.

So..

For the current disk - I found it almost without money in OLX and decided to take a risk.
It became clear that with vdmarvel can not do much - drive is not Marvel.

I have no experience with no marvel hdds.

By the way, we heard each other on the phone.

This is for information and for the protocol.
BGman is cool.

Hello again !

So .. the hdparm says :
What do you suggest ?

root@PartedMagic:~# hdparm -I /dev/sdb

/dev/sdb:

ATA device, with non-removable media
Model Number: WDC WD80EFAX-68KNBN0
Serial Number: VAHXE6WL
Firmware Revision: 81.00A81
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0; Revision: ATA8-AST T13 Project D1697 Revision 0b
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 15628053168
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 00 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Logical Sector size: 512 bytes
Physical Sector size: 512 bytes
device size with M = 1024*1024: 7630885 MBytes
device size with M = 1000*1000: 8001563 MBytes (8001 GB)
cache/buffer size = unknown
Form Factor: 3.5 inch
Nominal Media Rotation Rate: 5400
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 0
Advanced power management level: 164
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* Media Card Pass-Through
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* URG for READ_STREAM[_DMA]_EXT
* URG for WRITE_STREAM[_DMA]_EXT
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
unknown 119[6]
unknown 119[7]
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* NCQ priority information
* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
Non-Zero buffer offsets in DMA Setup FIS
DMA Setup Auto-Activate optimization
Device-initiated interface power management
In-order data delivery
* Software settings preservation
unknown 78[7]
unknown 78[10]
unknown 78[11]
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
* SANITIZE feature set
* OVERWRITE_EXT command
* reserved 69[3]
* DOWNLOAD MICROCODE DMA command
* WRITE BUFFER DMA command
* READ BUFFER DMA command
Security:
supported
not enabled
locked
not frozen
not expired: security count
not supported: enhanced erase
740min for SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000cca099db0387
NAA : 5
IEEE OUI : 000cca
Unique ID : 099db0387
Checksum: correct
root@PartedMagic:~# ^C
root@PartedMagic:~#

And hdat2 reported : Security status : disabled/locked.
Master password revision code 0000h future is not supported.

What can i do for tihis drive to return in ok status ?
Like i said before ...data is not important.

Thank you !

Somedoby ... ? Advise ?
Trow it ? Fight for it ?

Well show us this incorrect SMART, Can you write to the disk?

No , I can not write to disk.
Incorrect smart - tomorrow.
I am not at home now, but incorrect smart was shown in Victoria.

smart attached

Just curious ...

What do hdparm and Victoria report if you remove the PCB and connect it on its own?

What is the history of this drive? Did it come out of a DVR?

Could we see the BIN file produced by Victoria?

_________________
A backup a day keeps DR away.

OK, so HDD is probably ATA password locked. Victoria interpreted return data from IDENTIFY DEVICE (0xEC) command as SMART.
If you want to be sure connect your drive to 32-bit Windows 7 after it boots, run Victoria in PIO mode and show us Standard and SMART tabs.

i will try and post.
History - for me : unknown.
Was very cheap in olx.This is free online platform for second hand sales.
I found it almost without money in and decided to take a risk.Disk age is about one year - feb 2019.
Seller says that disk was part of a big lot of goods from ebay.

So ..

HGST
victoria screens attached.


fzabkar
Only PCB :

hdparm :

/dev/sdb:
multcount = 0 (off)
IO_support = 0 (default)
readonly = 0 (off)
readahead = 256 (on)
geometry = 972801/255/63, sectors = 15628053168, start = 0

............................................................................

extended info gparted disk health :

smartctl 7.0 2018-12-30 r4883 [x86_64-linux-5.4.6-pmagic64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD80EFAX-68KNBN0
Serial Number: VAHXE6WL
LU WWN Device Id: 5 000cca 099db0387
Firmware Version: 81.00A81
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Jul 13 10:05:48 2020 AKDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 164 (intermediate level without standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]

Read SMART Data failed: scsi error badly formed scsi parameters

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error badly formed scsi parameters

ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error badly formed scsi parameters
Read GP Log Directory failed

SMART Extended Comprehensive Error Log (GP Log 0x03) not supported

Read SMART Error Log failed: scsi error badly formed scsi parameters

SMART Extended Self-test Log (GP Log 0x07) not supported

Read SMART Self-test Log failed: scsi error badly formed scsi parameters

Selective Self-tests/Logging not supported

SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 0 Celsius
Power Cycle Min/Max Temperature: -3/ 3 Celsius
Lifetime Min/Max Temperature: 0/ 0 Celsius
Under/Over Temperature Limit Count: 0/0

Write SCT Data Table failed: scsi error badly formed scsi parameters
Read SCT Temperature History failed

Write SCT (Get) Error Recovery Control Command failed: scsi error badly formed scsi parameters
SCT (Get) Error Recovery Control command failed

Device Statistics (GP/SMART Log 0x04) not supported

ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error badly formed scsi parameters
Read SATA Phy Event Counters failed

bin files :

fzabkar - sorry hdparm usage with no "-I" , my mistake.
Will post again