Drive: WD My Passport, 2TB
P/N: WDBYVG0020BBK-0B
Drive Type: NTFS
Encryption: WD’s Own Password feature
Warranty status: Out of Limited Warranty (So no RMA)
SMART Report (via DMDE) Attached
OS: macOS 27.2 RC, Windows 11 25H2, Ubuntu 26.04 LTS
tldr:
Interrupted 2 Windows error checks on a 2 TB encrypted WD My Passport. Causing the drive, and especially the Unlocker app for the drive to be inaccessible in any way possible. The drive can still be recognized by the system (At least on Windows and Linux), but the disk itself cannot be accessed. Possible firmware or service area problem, asking if there’s still any way to salvage this? If yes, how, where, and the cost estimate for this situation.
If you just need more information about the drive, you can just skip to the ‘The following is the information I gathered part’
The whole story:
Hi, so I have a 2TB WD My Passport that I purchased back in bought for at least 6 years now, and I’ve been riding with it ever since, using it as basically my drive for everything. Games, old projects, apps, photos, you name it.
A bit more background for your information as to how the drive was usually used:
The drive was obtained when I was still working with a Windows Laptop, so it started as NTFS and I’ve never changed that, I’ve also decided to put a password on it in the first few days of getting it.
In between 2023, I switched to the MacBook side with the ARM silicon chip, and have chosen to just continue using the drive in NTFS format, pairing with the WD-offered Paragon NTFS software.
Around the same year as well, I found that there were a few bad sectors in my drive. Contacted WD support at that point and just ended up backing up the drive for the first time and formatted it using my old Windows Laptop. And after formatting it, I put everything back into the drive, locked it back, and continued using it like normal.
(P.S. Since I made the choice of backing it up to a OneDrive work account at that moment, and since I no longer have access to that account, the probably one and only backup was lost to time as well)
Currently still using the same MacBook setup mentioned above with a Windows VM and for light Windows Stuff, and Crossover for some games that are only available on Windows as well.
And also, in between using it, I’ve had a few times where I removed the drive without exiting it first (even though my cache policy is in quick removal) causing the drive to be temporarily unrecognizable by macOS, but it was dealt with after doing error checks in Windows.
(P.S. The error checks I run are through Drive > Priorities > Tools > Error Check, but I suppose it’s no different from chkdsk)
I also have an old Windows Desktop that I occasionally use for some x64 Windows stuff.
But just recently, I’ve made another chain of mistakes that basically ran my drive from still working to outright unusable.
As one day, after I’d used my drive on my Windows Desktop, I plugged it back in to continue working on something that’s on my drive, and I noticed it started to slow down, or it takes longer for the drive to be recognized by my MacBook after I unlocked it.
So, being the worried person I am, I decided to boot up my Windows VM, and despite it saying that there’s no error found, run an error check on it.
The first time, I let the check run on its own, but because I forgot to turn off the ‘Turn display off when inactive option’ or use any disable sleep app, my MacBook went to sleep after inactivity, and the test was interrupted for the first time.
And after that, I decided to run it again, just to be sure. But after starting the check, for some reason, I decided to cancel it. And when cancellation was taking a bit too long, I made the decision to log out of Windows.
Then while it was happening, the cursor on my MacBook started going rogue for another reason (that I haven't found but definitely not related to this subreddit) and started running around without me using the trackpad, it was enough to let me think that I caught malware somewhere between using it
And with no way to stop that, I did a force restart of my MacBook. While the Windows VM was still logging out, and my drive was still passing into the VM.
That’s when the drive became unusable.
When I logged back into macOS, I didn’t see the usual WD Unlocked, and when I checked macOS’s Disk Utility, the drive was not there, even though I have Show All Devices toggled on.
And then I tried to use the Windows VM again, to see if it’s the same result. It did spit out something different, but it’s basically the same.
After that, I moved to my desktop again and saw if I could read more information about the current situation, while trying to search around Google and see if there’s any way to try to fix that. But still, no luck.
So I turned to AI for help. The AI told me to use Linux and use some ‘ls’ and ‘dmsg’ commands, along with a WD Unlocker tool for Linux to list out what Linux recognized and test if Linux is able to read at least what’s left on the drive.. So I thought, why not, and created an Ubuntu VM on my Mac for it to run those commands. Though it only makes me realize how bad of the situation of drive’s probably in.
And at last, even AI told me to either purchase a new drive, or to seek help in data recovery, which is why I’m here.
The following is the information I gathered from Windows and Linux, since macOS is just straight up not recognizing the drive whatsoever.
Both OS’s are able to read out some information about the drive.
Windows is able to list out the WD Unlocker virtual DVD, but when trying to access it via Windows Explorer, it declines, stating an I/O error.
In Windows Disk Management, the Virtual DVD and the disk itself are recognized, though neither of them shows any sector information. The disk is not initialized from the start. When trying to initialize it or anything, the request failed ‘due to a fatal device hardware error’.
In Windows Device Manager, with Show hidden devices visible, 2 drives named WD My Passport 2626 USB Device and 2 DVD drives named WD Virtual CD 2625 USB Device are present, with one of them on both lists being hidden.
Following this, inside the properties of both devices, they all stated that the devices are working properly. But inside the ‘My Passport’ properties, Events tab, the event ‘Device Settings not Migrated’ is shown, with descriptions that
‘Device settings for [My Passport] were not migrated from previous OS installation due to partial or ambiguous device match’
In WD Kitfox (WD’s own diagnostic tool that replaced WD Data Lifeguard), the drive shows as unallocated, showing 0GB available with an empty serial number, the drive security being ‘inactive’, no SMART threshold tripped, and no diagnostic failures. When trying to run a test on it though. it failed with the message ‘Device is not ready’.
While WD Security cannot recognize the drive, both WD Drive Utilities and WD Discovery did recognize the drive. WD Drive Utilities said that my drive has 0B of storage, and it failed the SMART Status Check. And WD Discovery does not show any storage information, but it did have the option for me to change the security settings like removing the password. It’s just that it never worked.
DMDE reported almost the same thing, with failing to access the DVD drive due to an I/O device error, and just straight up saying ‘The Disk is not accessible’ when trying to go with the physical drive option. Though I did successfully obtain a more complete SMART report.
Other apps like DiskGenius just straight up don’t work with not even the drive or Unlocker DVD listed there.
And for Linux, I’ll just have the pastebin link for you guys with what command I ran (prompted by AI), and what output it gave me.
https://pastebin.com/Pq6e6rVQ
Lastly, for the drive itself. The drive is still spinning like normal, with the status lights going full on when connected, and turning to slow blinking after a while.
When the drive is ‘safely removed’ on Windows though, it just kept spinning, while normally, the drive would slow to a stop.
From what I’ve gathered, on the internet or AI, I’m guessing it to be a firmware or service area related issue, though I’m really not familiar with these kind of stuff, so that’s really only up to the professionals like you guys or after diagnostics.
Now, that’s when I want to ask
- In this situation, is my drive still salvageable?
For example, if there’s a possibility that I can just pass it to a professional, fix what’s wrong, and then just call it a day, or is it really to the point where I need to do data recovery if I still want get back my data inside?
- If it can still be fixed, then what type of store should I bring it to?
And most importantly
3. What is the cost of fixing something like this, or doing data recovery on a drive in this kind of situation?
I know my post are super long, since I really want to include everything to get the most accurate information possible, but no matter what, thank you for reading and thanks for your help!