Problem with the Western Digital My Passport Essential (WDBAAA5000ASL) 500 GB USB Hard Drive. I go to computer and manage. I see the drive there, but I no longer get the prompt to unlock it and it is not seen with the other drives on my laptop. I have many files on this drive that I cannot lose. I have been all over the WD site and nothing has helped.
Hello,
Have you test your drive using a different computer? Also how about a different USB cable?Â
Hello, Yesterday a friend of mine came over to me with exactly the same (type of) hard-disk and exactly the same symptons.She hopes Iâm able to recover the files on the disk (unfortunately she didnât make backups) Anyway, some digginâ learned that: - Thereâs no valid partition table. USB connection is made, but because there are no valid partions, no drives are mounted. (BTW: Iâve tried different computers & different USB cable, good suggestion I hadnât thought of) - Hooking it on a Windows 7 machine, the storage manager indicates thatâs a uninitialised 2TB drive. And asks how to initialise it (MBR or something else). Didnât think itâs the best thing to do it if you want to recover the files on it⊠Hmmm, 2TB doesnât sound right So before I screw things up or ill advise here to throw away the disk / pay a lot of money to a company to try and recover the data, I switched to linux. Ran some diagnostics and hope someone in this community has a good advise Iâm afraid the problem is with het hardwarecontroller / firmware (??) of the harddisk AFAIK even unitialised disks report there correct geometry and size and are readable in linux with dd Any suggestions ?? Kind regards, Cees ------------ scanning the USB bus ------------------- mortimer:~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1058:070a Western Digital Technologies, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub mortimer:~ # lsusb -v -s 1:3 Bus 001 Device 003: ID 1058:070a Western Digital Technologies, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x070a bcdDevice 10.32 iManufacturer 1 Western Digital iProduct 2 My Passport 070A iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered) ------------ Checking the geometry of the disk ------------------- mortimer:~ # hdparm -g /dev/sde /dev/sde: geometry = 2096482/64/32, sectors = 4293595136, start = 0 mortimer:~ # hdparm -I --verbose /dev/sde /dev/sde: outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00 data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: sb: 72 00 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 00 00 00 00 40 50 00 00 00 00 00 00 00 00 00 00 SG_IO: desc: 09 0c 00 00 00 ff 00 00 00 00 00 00 ATA_16 stat=50 err=00 nsect=ff lbal=00 lbam=00 lbah=00 dev=40 ATA device, with non-removable media Standards: Likely used: 5 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 â Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY(may be)(cannot be disabled) Standby timer values: specâd by Vendor R/W multiple sector transfer: Max = 0 Current = ? DMA: not supported PIO: pio0 Logical Unit WWN Device Identifier: 50014ee2594191b8 NAA : 5 IEEE OUI : 0014ee Unique ID : 2594191b8 Checksum: correct ------------ trying to read some raw data from the disk ------------------- mortimer:~ # dd if=/dev/sde bs=1024 count=1 of=first1024.bin dd: reading `/dev/sdeâ: Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00683184 s, 0.0 kB/s ------------ plus the error-log ------------------- mortimer:~ # tail -n 18 /var/log/messages May 17 10:10:01 mortimer kernel: [3227.559978] sd 7:0:0:0: [sde] Unhandled sense code May 17 10:10:01 mortimer kernel: [3227.559987] sd 7:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE May 17 10:10:01 mortimer kernel: [3227.559995] sd 7:0:0:0: [sde] Sense Key : Data Protect [current] May 17 10:10:01 mortimer kernel: [3227.560026] sd 7:0:0:0: [sde] Add. Sense: Logical unit access not authorized May 17 10:10:01 mortimer kernel: [3227.560045] sd 7:0:0:0: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00 May 17 10:10:01 mortimer kernel: [3227.560081] end_request: I/O error, dev sde, sector 0 May 17 10:10:01 mortimer kernel: [3227.560090] quiet_error: 443 callbacks suppressed May 17 10:10:01 mortimer kernel: [3227.560097] Buffer I/O error on device sde, logical block 0 May 17 10:10:01 mortimer kernel: [3227.560107] Buffer I/O error on device sde, logical block 1 May 17 10:10:01 mortimer kernel: [3227.560113] Buffer I/O error on device sde, logical block 2 May 17 10:10:01 mortimer kernel: [3227.560119] Buffer I/O error on device sde, logical block 3 May 17 10:10:01 mortimer kernel: [3227.561969] sd 7:0:0:0: [sde] Unhandled sense code May 17 10:10:01 mortimer kernel: [3227.561975] sd 7:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE May 17 10:10:01 mortimer kernel: [3227.561981] sd 7:0:0:0: [sde] Sense Key : Data Protect [current] May 17 10:10:01 mortimer kernel: [3227.561988] sd 7:0:0:0: [sde] Add. Sense: Logical unit access not authorized May 17 10:10:01 mortimer kernel: [3227.561998] sd 7:0:0:0: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 May 17 10:10:01 mortimer kernel: [3227.562044] end_request: I/O error, dev sde, sector 0 May 17 10:10:01 mortimer kernel: [3227.562051] Buffer I/O error on device sde, logical block 0 mortimer:~ #
Aaargh, $*(@#*(*# javacript editors
Layout is completely messed up. (pasted from a flat tekst document).
importing removed line-breaks
sorry,
Cees
If the drive shows in Disk Mamagement you can try fixing partition with TestDisk http://www.cgsecurity.org/wiki/TestDisk or Easuse Partition Manager http://www.partition-tool.com/ and see if they will rebuild partition data.
Joe
Hello Joe,
Thank you for your reply.
Iâve tried TestDisk, but unfortunately, it doesnât work
The output from the program was:
TestDisk 6.12, Data Recovery Utility, May 2011
Christophe GRENIER grenier@cgsecurity.org
Please waitâŠ
Disk /dev/sde - 2198 GB / 2047 GiB - CHS 2096482 64 32, sector size=512
Disk /dev/sde - 2198 GB / 2047 GiB - CHS 2096482 64 32
Partition Start End Size in sectors
Partition: Read error
What worries me is the reported size of the disk 2TB
Itâs also impossible to read anything from the disk, eg
dd if=/dev/sde bs=1024 count=1 of=first1024.bin
should read the first 1024 bytes from the disk, initialised or not, partition table or not
(If I remember correctly, the partition tabel is located in the first 512 bytes of the disk, so any tool able to restore the partition table should read/write the first 512 bytes)
Iâm afraid thereâs no IO to any data on the disk
Kind Regards,
Cees
this is exactly what happened to my same WD product! It is reported  as a 2Tï»żB disk. I clearly remember i purchased a 500GB disk and its not working and all my data is lost. Anyone with other suggestions?
Ceesvn wrote:
Hello Joe,
Thank you for your reply.
Iâve tried TestDisk, but unfortunately, it doesnât work
The output from the program was:
TestDisk 6.12, Data Recovery Utility, May 2011
Christophe GRENIER grenier@cgsecurity.org
Please waitâŠ
Disk /dev/sde - 2198 GB / 2047 GiB - CHS 2096482 64 32, sector size=512
Disk /dev/sde - 2198 GB / 2047 GiB - CHS 2096482 64 32
Partition Start End Size in sectors
Partition: Read error
What worries me is the reported size of the disk 2TB
Itâs also impossible to read anything from the disk, eg
dd if=/dev/sde bs=1024 count=1 of=first1024.bin
should read the first 1024 bytes from the disk, initialised or not, partition table or not
(If I remember correctly, the partition tabel is located in the first 512 bytes of the disk, so any tool able to restore the partition table should read/write the first 512 bytes)
Iâm afraid thereâs no IO to any data on the disk
Kind Regards,
Cees
just to clarify what Joe is telling you (and, Joe, I hope this is what youâre getting at). but you most likely corrupted your partition and enough data that testdisk wonât be able to recover it. you must always make sure to safely remove your drive before just pulling the data cable, especially right after transferring a ton of data. if the drive buffers arenât flushed, you will corrupt data on the drive. itâs even worse if data is still being written when you pull the cable. you can lose the partition as well. which it appears you did. as it is, youâre pretty much stuck with repartitioning and reformatting the drive.
metak wrote:
this is exactly what happened to my same WD product! It is reported as a 2Tï»żB disk. I clearly remember i purchased a 500GB disk and its not working and all my data is lost. Anyone with other suggestions?
you may need to start your own thread. because unless you actually just blew your partiton, there may be other issues. what does disk management say about the drive?
Hello Wayne,
I didnât pull the usb cable without âsafely removing the disk from the OSâ. The drive belongs to a friend of mine, who hoped I could rescue here files after the disk was no-longer recognised by the os (on connecting).She isnât a computer expert, but sheâs smart enough to know that you shouldnât do such a thing
Iâve been playing with hard-disk partions for 15 years (installing Linux/Windows dual boot configurations etc.) This disk however is totally unaccessible. On a Linux box dd wonât read anything from it (and you can use dd to read/write raw data to unpartioned disks!)
Also, tools for checking the disk geometry give wrong results. AFAIK this isnât the result of a corrupt partition disk!
So, please read my original posting (I admit layout is bad: but importing flat text in the webbased editor removed the newlines. Iâve tried several times with no succes), before suggesting I screwed up my partition table and have to repartition and reformat my friends hard-disk. (I havenât tried it but am for 99% sure it wonât work. fdisk wouldnât read the current table!)
Kind Regards,
Cees
BTW Iâve my doubts that disconnecting a USB-drive while writing could/will corrupt your partion table. It will corrupt files, directory indices etc. but under normal usage thereâs little (if any) writing activity to the partition table (However, Iâve no intention to try on a disk it with precious data )
It absolutely can. anytime youâre writing data that is caching, you run the risk of corrupting files or the file system if there is a loss of power. pulling the passport data cable out of the port without safely removing it causes an immediate loss of power.
You donât even have to pull the cable if you want to wreck it⊠lots of folks end up with corrupted/unusable drives simply because the drive isnât getting sufficient power to function properly from the USB port.
Wayne wrote:
It absolutely can. anytime youâre writing data that is caching, you run the risk of corrupting files or the file system if there is a loss of power. pulling the passport data cable out of the port without safely removing it causes an immediate loss of power.
Hello Wayne,
Youâre talking about corrupting files and filesystems. I my previous post I wrote I think thatâs possible. I have my doubts about corrupting the partition table (bytes 446-510 in the MBR). On normal usage there is no reason to write to the MBR (other than to install a virus ;))
But weâre getting off-topic here.
This is the problem:
On the USB drive the partiontable isnât readable (and I guess not writable to, but I wouldnât try it).
The drive is seen by the OS, but because no partition info is given: no partitions are mounted and the WD software for decrypting the data partition isnât started.
On a lower level: there is no data readable from the disk. On Linux, you can read raw data from an unmounted device (see de man entry for âddâ). Partition table or no partition table. On this drive it doesnât work.
The drive reports itself as a 2TB drive, which is also suspicious (I canât remember Iâve manually adjusted disk geometry settings the last 15 years)
So I guess the problem âhardwareâ related. Firmware? Controller?
Kind Regards,
Cees
If the drive is reporting itself as 2 TBâs, thatâs a major drive failure. From what Iâve been told, something has most likely gone wrong in the firmware. If youâre looking to save the data, youâre probably looking at data recovery.Â
I purchased a WD 1.0TB Passport SE. Iâve never backed up a pc hard drive. I plugged it in and it showed
âinstalling drivers,â did that successfully, but no home screen, startup wizard, nothing. Can anyone lend any advice? I would GREATLY appreciate any help/answers.
Thank you!!
Did you open My Computer (Computer) to see if the drive shows up? If you donât get an Autoplay window after the drive is read, then you need to go to Computer to see the drive. Double click on the drive and a window will open to show you the drive contents.
bill_s wrote:
If the drive is reporting itself as 2 TBâs, thatâs a major drive failure. From what Iâve been told, something has most likely gone wrong in the firmware. If youâre looking to save the data, youâre probably looking at data recovery.
Hello Bill.
Thanks.
I suspected a firmware problem and hoped there is a utility available to âreflashâ the firmware.
My friend is a student and the disk contained schoolwork. Data recovery might work, but (if I remember correctly) pricing starts at 200 euros for a first diagnosisâŠ
So last time a spoke her she was retyping the lost documents (and i think thats in the future she makes backup copies)
I know it â â â â â , but that was one of the hard lessons I had to learn - back up your data. So, I empathize with your friend. As for reflashing the firmware, I donât know if it will work like that.Â