Cant initialize hard disk help please....

[xelyon]

I have a TOSHIBA USB 3:0 500gb external HDD which cant be initialized in computer management
It all started when the HDD didn't appear on my computer i have tried several tricks but none of them worked
i always get an I/O error until i tried this from a site

"set devmgr_show_nonpresent_devices=1 --> Press Enter

cd\ ---> Press Enter

cd windows\system32 --> Press Enter

start devmgmt.msc --> Press Enter

"Device Manager" window will be opened.

Now in the device manager, click on "View" --> Select "Show hidden devices"

Now expand all the nodes by clicking on "+" symbol. If you find any greyed

entries --> Right click on it --> Select "Uninstall".

Restart your PC --> Now try connecting your external drive. "


Moreover the allocated space bar has dissapeared after i used this method

After this i have been getting a "The Drive Cannot Find The File Requested" Error

Can someone please help

 

[John_VanKirk]

Hi there, & Welcome to Tom's Hardware!

Best thing to help everyone ID the problem, is to connect the ext drive to your computer and turn it on if it has a separate power block.
The boot up your computer, and go to Disk Manageent, (click in the left lower corner of Computer Management)

Then upload a screenshot of the Disk Management dialog box, expecially the lower graphical area showing all your drives and volumes.

That way, someone will be able to accurately see and help you determine what is wrong and how to correct it.

Also you should try the ext drive on a desktop computer, and try a separate USB connector to rule out those possibilities as the culprit.

 

[fzabkar]

Inside the enclosure is a USB-SATA bridge IC or bridge PCB, plus the HDD itself. The PC talks USB, the drive talks SATA, and the bridge is their interpreter. It appears that the bridge is being detected by Windows but the HDD is not.

A UVCView report will tell us about the bridge, while a HD Sentinel or HDDScan report will tell us about the HDD.

http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe
http://www.hdsentinel.com/
http://hddscan.com/

 

[xelyon]

Inside the enclosure is a USB-SATA bridge IC or bridge PCB, plus the HDD itself. The PC talks USB, the drive talks SATA, and the bridge is their interpreter. It appears that the bridge is being detected by Windows but the HDD is not.

A UVCView report will tell us about the bridge, while a HD Sentinel or HDDScan report will tell us about the HDD.

http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe
http://www.hdsentinel.com/
http://hddscan.com/

UVCView report

---===>Device Information<===---
English product name: "External USB 3.0"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: High
Device Address: 0x03
Open Pipes: 2

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x14

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x14

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0210
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0480idProduct: 0xA007
bcdDevice: 0x0001
iManufacturer: 0x01
English (United States) "Toshiba"
iProduct: 0x02
English (United States) "External USB 3.0"
iSerialNumber: 0x03
English (United States) "20120417004659F"
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0020 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0xFA = 500 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x08 -> This is a Mass Storage USB Device Interface Class
bInterfaceSubClass: 0x06
bInterfaceProtocol: 0x50
iInterface: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x14

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x14
========================
HDD Scan
========================
Open Disk
Test : RD-Read


Executing
Bad block found, start LBA : 0
(Same result with all tests)
========================

 

[xelyon]

Hi there, & Welcome to Tom's Hardware!

Best thing to help everyone ID the problem, is to connect the ext drive to your computer and turn it on if it has a separate power block.
The boot up your computer, and go to Disk Manageent, (click in the left lower corner of Computer Management)

Then upload a screenshot of the Disk Management dialog box, expecially the lower graphical area showing all your drives and volumes.

That way, someone will be able to accurately see and help you determine what is wrong and how to correct it.

Also you should try the ext drive on a desktop computer, and try a separate USB connector to rule out those possibilities as the culprit.

I am using a desktop computer

the device properties under the volume tab
http://i1073.photobucket.com/albums/w386/xyroid/point3_zpsbf5f21b1.png

Disk Management (Note:- the HDD is drive 6)
http://i1073.photobucket.com/albums/w386/xyroid/part1_zpsa295a8c2.png

And the error which i get from trying to initialize it
http://i1073.photobucket.com/albums/w386/xyroid/part2_zps50c80829.png

 

[fzabkar]

I was more interested in the identity information, ie HDD model number, capacity in LBAs, security settings, features.

For example, sometimes a drive with firmware problems will identity itself with its "factory alias", eg ST_M13FQBL or ROM MODEL HAWK, or it will report a capacity of 0 LBAs, or it may have a strange serial number.

The SMART data are also a useful indicator of the drive's health, especially in regard to bad sectors.

BTW, the drive is spinning, isn't it?

 

[xelyon]

I was more interested in the identity information, ie HDD model number, capacity in LBAs, security settings, features.

For example, sometimes a drive with firmware problems will identity itself with its "factory alias", eg ST_M13FQBL or ROM MODEL HAWK, or it will report a capacity of 0 LBAs, or it may have a strange serial number.

The SMART data are also a useful indicator of the drive's health, especially in regard to bad sectors.

BTW, the drive is spinning, isn't it?

Model Name: External_unit EXT.HDD 500GB (RAVEN BLACK)
Product Category: Option Part
Model-Part Number: HDTC605AK3A1
Serial Number: 42H2TN6MTQQ7
Registration Number: W205252541
Capacity: 500GB1
Interface: USB 3.0 with up to 5Gb/s2 transfer rate
Rotational Speed: Up to 5,400RPM
Average Seek Time: 12ms
Cache Buffer: 8MB
Dimensions & Weight: 3.1” W x 4.7” D x 0.53” H; 5.2 oz
Backward compatible with USB 2.0
Internal shock sensor and ramp loading technology protects your drive and data

And yes the drive is spinning

And the SMART data from the hdd scan software is this
========================
HDD Scan
========================
Open Disk
Test : RD-Read


Executing
Bad block found, start LBA : 0
(Same result with all tests)
========================
if you didnt notice it from my previous post

 

[fzabkar]

Somewhere in amongst all that should be the model number of the actual drive, eg MK5059GSXP. A lot of the information (eg Dimensions & Weight) has been pulled from a product brochure, not from the drive itself. It's not clear whether the capacity information is coming from a brochure, either.

As for SMART data, what you have provided is the result of a surface scan. Instead I'm looking for something like the following:

1,Raw Read Error Rate,32,100,100,OK,00000003AB7F,0,Enabled
2,Throughput Performance,20,100,100,OK,000000000000,0,Enabled
3,Spin Up Time,25,90,87,OK,000000000003,0,Enabled
4,Start/Stop Count,16,96,96,OK,000000000A0B,0,Enabled
5,Reallocated Sectors Count,24,100,100,OK,000000000000,0,Enabled
7,Seek Error Rate,20,100,100,OK,00000000003F,0,Enabled
...

If you can retrieve the drive's SMART data, then this will prove that the drive's firmware area is at least partially accessible (assuming the SMART data are stored on the platters).

 

[xelyon]

Somewhere in amongst all that should be the model number of the actual drive, eg MK5059GSXP. A lot of the information (eg Dimensions & Weight) has been pulled from a product brochure, not from the drive itself. It's not clear whether the capacity information is coming from a brochure, either.

As for SMART data, what you have provided is the result of a surface scan. Instead I'm looking for something like the following:

1,Raw Read Error Rate,32,100,100,OK,00000003AB7F,0,Enabled
2,Throughput Performance,20,100,100,OK,000000000000,0,Enabled
3,Spin Up Time,25,90,87,OK,000000000003,0,Enabled
4,Start/Stop Count,16,96,96,OK,000000000A0B,0,Enabled
5,Reallocated Sectors Count,24,100,100,OK,000000000000,0,Enabled
7,Seek Error Rate,20,100,100,OK,00000000003F,0,Enabled
...

If you can retrieve the drive's SMART data, then this will prove that the drive's firmware area is at least partially accessible (assuming the SMART data are stored on the platters).

ah....np i got it fixed myself thnks for the help anyway

 

[xelyon]

Best answer selected by xelyon.