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.

Comments

Popular posts from this blog

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.

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.