Skip to main content

Recover Data from Drive with Not initialized Disk Error

Having an Internal or External Hard Disk that you were using without any problem, but suddenly it is giving error that the disk is not initialized! In this situation you can not see any disk Drive in My Computer, but when you go to the Windows Disk Management utility, it is shown there with message “You must initialize a Disk before Logical Disk Manager can access it“.

I started getting this message on my 500 GB external Hard drive since it fell down the ground. I tried many data recovery software, but no recovery software was able to communicate with the faulty drive as the disk starts communication with the PC once it is initialized.

Googling this initializing problem, i found it works some times but sometimes it even worsen the case. So i was not taking that risk and continued googling found a Magic Solution for my issue, the software called Partition Find and Mount

What this tool does, Scans for the drive and the mounts it as a Normal Drive, and open Windows Explorer… After you can simply copy and paste all of your important data from the mounted drive to your Computer’s working drive… So easy???

You can download a free version of this Find and Mount Tool, but the free version has only the limitation of copy transfer rate of 512 KB/Sec, and that transfer rate can be increased with Pro Version.

For Scanning the drive
Open Partition Find and Mount program
Click Scan your faulty drive with default or Recommended Option.
Once the scan is completed, Just Copy and Paste your Important data to other location.

After taking backup of your Important data, you can play with your faulty drive as you want, mean try to initialize, partition or format it.
Labels:

Comments

Post a Comment

Popular posts from this blog

Connection control operation failed for disk 'ide1:0'

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine.

What worked for me, is
1. Uncheck the "Connected and Connect at power on" from Device Status.
2. Then Change the Device type from "Datastore ISO File to Client Device" Radio Button
3. and press OK to save the changes.

Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui

where it asks

"The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?"

You need to select yes to eject the CD-ROM and then remove the ISO file successfully.
Post a Comment
Read more

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application.

As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps.


Open your mRemoteNGCreate a folder if you want segregation of multiple networksCreate a new connectionEnter the IP address of remote server under connection in Config paneUnder the config pane, select protocol "SSH version 2".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below.


In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.



Post a Comment
Read more

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.
Post a Comment
Read more