Partitioning Your Harddisk With Fdisk
Partitioning your HardDisk
Partitioning involves creating logical units on your hard drive that are then addressed as different drive letters. Not only does it help to organize your data (program files on one drive, games on another, documents on another) but also to speed up your PC. This is so because the drive head has to move a lesser distance for accessing data within one partition. You can also have different filesystems and OSs on the same hard drive.
Partitioning can be done using ‘fdisk’ in DOS/Windows 9x or ‘disk management’ in Windows 2000/ NT/XP. We will describe the procedure for fdisk, since disk management is GUI driven and the basics otherwise remain the same. While several other commercial packages like Partition Magic are available, these utilities (fdisk, computer management) are bundled with their respective OSs. You need a bootable floppy with fdisk.exe, format.com, and sys. com utilities. Before starting, decide how many partitions you want to create and their sizes. You can create one primary and one extended partition using the DOS fdisk. The extended partition can then have multiple logical partitions. Boot your machine using the bootable disk, and do the following.
Run fdisk. The utility will show you a numbered menu from where you can create, view, or delete partitions
The utility first asks you whether you want to enable large disk support. Type Y (for yes) and press enter if your hard-drive capacity is more than 4 GB. Large disk support creates a FAT32 partition, which can be greater than 2 GB
Select the first option from fdisk menu to create a primary partition. Specify the partition size in megabytes or percentage size when prompted for it
Similarly, create an extended partition. Extended partitions by themselves do not appear as drive letters. Instead, logical partitions must be created in them, which are then assigned drive letters
Exit fdisk and reboot the computer
Fdisk automatically assigns drive letters to all the partitions. You’ll need to format each partition in order to use it. Use format.com for the same
Your hard drive is now ready for taking an OS.
Showing posts with label harddisc. Show all posts
Showing posts with label harddisc. Show all posts
How to: Retrieve data from hard disc 1
Labels:
data recovery,
hacking,
harddisc
Dead disk drives?
There's a bunch of steps I would take if the drive weren’t being recognized by either the auto setup or manual entry.
1) Check your Master/Slave/Standalone jumper settings and make sure they are correct and don't conflict with another device on the same IDE channel.
2) Check for bent pins on the connectors.
3) Try a known good cable—Floppy and IDE cables often seem to go down the gurgler at the worst possible time for some unknown reason.
4) Try a known good drive on your IDE channel and check the channel. If it doesn't respond:· Try another IDE port (if there's two)· Disable onboard IDE and try another I/O card (one that’s known to be good of course)
5) Try the disk in another PC.
6) Here's where it starts getting tricky. By now you must be reasonably convinced you have a bad case of galloping disk rot. On some drives (not all), if you have an identical same model drive, you can swap over the logic board. This will let you know if it is the embedded controller on the logic board. With luck, your disk will roar into life and you can suck the data off onto somewhere safe.
7) If your disk is making a hideous noise like a peg-legged man with a vacuum cleaner on a wooden floor (whirrr, clunk, whirrr, clunk....), then it is likely you have a dropped head. This is where you have start making decisions about how much your data is worth, because to go any further is going to cost big time and may require factory technicians to try and repair the disk in a clean-room environment. If your data was that important, then it would have been backed up. (Of course it would have been, they all respond in loud voices).
There's a bunch of steps I would take if the drive weren’t being recognized by either the auto setup or manual entry.
1) Check your Master/Slave/Standalone jumper settings and make sure they are correct and don't conflict with another device on the same IDE channel.
2) Check for bent pins on the connectors.
3) Try a known good cable—Floppy and IDE cables often seem to go down the gurgler at the worst possible time for some unknown reason.
4) Try a known good drive on your IDE channel and check the channel. If it doesn't respond:· Try another IDE port (if there's two)· Disable onboard IDE and try another I/O card (one that’s known to be good of course)
5) Try the disk in another PC.
6) Here's where it starts getting tricky. By now you must be reasonably convinced you have a bad case of galloping disk rot. On some drives (not all), if you have an identical same model drive, you can swap over the logic board. This will let you know if it is the embedded controller on the logic board. With luck, your disk will roar into life and you can suck the data off onto somewhere safe.
7) If your disk is making a hideous noise like a peg-legged man with a vacuum cleaner on a wooden floor (whirrr, clunk, whirrr, clunk....), then it is likely you have a dropped head. This is where you have start making decisions about how much your data is worth, because to go any further is going to cost big time and may require factory technicians to try and repair the disk in a clean-room environment. If your data was that important, then it would have been backed up. (Of course it would have been, they all respond in loud voices).
Subscribe to:
Posts (Atom)