Format Lockup

don_keyballs44 · 04-23-2005, 10:21 PM

A while ago I was reformating my hard drive and during the format the computer locked up. I was forced to reset and when I did the hard drive was not recognized.

It wasnt a big deal because of the computers age. The hard drive was only 10gig so I just upgraded and installed another one.

I tried slaving the damaged drive off of my new drive and it didnt recognize it that way.

Like I said the drive is about six years old and doesnt really have much support from the company. I was just wondering if anyone has had this happen to them and how they dealt with it. I'd like to get it working but if anything I'd like to know what happend in case It happens again.

Here is the hard drive:

IBM Titan 10.1GB 5400 RPM Ultra DMA/33 IDE Hard Drive

The computer is a Micron PII 400MHz 128MB RAM running Win98SE

I also have another computer running XP if that would help.

04-24-2005, 06:10 AM

Hi,

One question that might help (O.K. a shot in the dark at best) is that when you slaved it to the new drive, did you change the jumper on the new drive to be a master. Most new drives come set as CS from the manufacturer and it is easy to get them to work, but when we put a slave to them, we must change the jumpers to master. If it is not set that way, I would give it a shot to see if it is recognized.

If that does not work, then put it back as master and use this process:

Obtain or download a boot disk: from here::

http://www.bootdisk.com

Select the option in BIOS setup to boot from A: as the first in line

Put the boot disk in the A; Drive and start your computer

When loaded, type in FDisk

Select the option to delete all partitions

Create a new partition

Make the partition active

Shut down the computer

Type in Format and it will format the disk you have partitioned

Shut down the computer when done

When it boots back up select to load with CDRom Support

When it boots up, type setup and away it will go and install your OS.

(hope I didn't miss anything)

OR IF YOU WANT PICTURES AND A TECHNICAL EXPLANATION USE THIS LINK:

http://www.blackviper.com/Articles/OS/fdisk/fdisk1.htm

don_keyballs44 · 04-24-2005, 07:34 PM

I did have right jumper settings when I slaved it.

I tried your solution but I forgot to mention that it is not recognized on the BIOS screen.

When I ran fdisk it could'nt do anything becouse there was no disk there. When I tried it I had removed the new drive and attached my damaged one and tried it with cable select and master settings.

04-24-2005, 08:00 PM

Hi,

In my opinion, here is the skinny of things. If you have it set as master on the end of a known good ribbon cable and the BIOS is set to autodetect and it does not find it, you probably have a drive that is gone. As a double check, you might set it up in your other machine and see if it detects it. If not, then you probably can guess what the verdict is.

don_keyballs44 · 04-24-2005, 08:38 PM

Thanks,

Thats what I figured. Like I said, its an old drive and isnt a big loss. I was just curious and wanted to see if I could fix it and mabye learn something in the process.

04-23-2005, 10:21 PM	#1 (permalink)
don_keyballs44 Registered User Join Date: Mar 2005 Posts: 3 OS: WinXP	Format Lockup A while ago I was reformating my hard drive and during the format the computer locked up. I was forced to reset and when I did the hard drive was not recognized. It wasnt a big deal because of the computers age. The hard drive was only 10gig so I just upgraded and installed another one. I tried slaving the damaged drive off of my new drive and it didnt recognize it that way. Like I said the drive is about six years old and doesnt really have much support from the company. I was just wondering if anyone has had this happen to them and how they dealt with it. I'd like to get it working but if anything I'd like to know what happend in case It happens again. Here is the hard drive: IBM Titan 10.1GB 5400 RPM Ultra DMA/33 IDE Hard Drive The computer is a Micron PII 400MHz 128MB RAM running Win98SE I also have another computer running XP if that would help.

04-24-2005, 06:10 AM	#2 (permalink)
mark3567 Guest Posts: n/a OS:	Hi, One question that might help (O.K. a shot in the dark at best) is that when you slaved it to the new drive, did you change the jumper on the new drive to be a master. Most new drives come set as CS from the manufacturer and it is easy to get them to work, but when we put a slave to them, we must change the jumpers to master. If it is not set that way, I would give it a shot to see if it is recognized. If that does not work, then put it back as master and use this process: Obtain or download a boot disk: from here:: http://www.bootdisk.com Select the option in BIOS setup to boot from A: as the first in line Put the boot disk in the A; Drive and start your computer When loaded, type in FDisk Select the option to delete all partitions Create a new partition Make the partition active Shut down the computer Type in Format and it will format the disk you have partitioned Shut down the computer when done When it boots back up select to load with CDRom Support When it boots up, type setup and away it will go and install your OS. (hope I didn't miss anything) OR IF YOU WANT PICTURES AND A TECHNICAL EXPLANATION USE THIS LINK: http://www.blackviper.com/Articles/OS/fdisk/fdisk1.htm

04-24-2005, 07:34 PM	#3 (permalink)
don_keyballs44 Registered User Join Date: Mar 2005 Posts: 3 OS: WinXP	I did have right jumper settings when I slaved it. I tried your solution but I forgot to mention that it is not recognized on the BIOS screen. When I ran fdisk it could'nt do anything becouse there was no disk there. When I tried it I had removed the new drive and attached my damaged one and tried it with cable select and master settings.

04-24-2005, 08:00 PM	#4 (permalink)
mark3567 Guest Posts: n/a OS:	Hi, In my opinion, here is the skinny of things. If you have it set as master on the end of a known good ribbon cable and the BIOS is set to autodetect and it does not find it, you probably have a drive that is gone. As a double check, you might set it up in your other machine and see if it detects it. If not, then you probably can guess what the verdict is.

04-24-2005, 08:38 PM	#5 (permalink)
don_keyballs44 Registered User Join Date: Mar 2005 Posts: 3 OS: WinXP	Thanks, Thats what I figured. Like I said, its an old drive and isnt a big loss. I was just curious and wanted to see if I could fix it and mabye learn something in the process.