Windows reports a second HDD with about 150 GB of data as Unformatted

[Arno]

IBM ThinkCentre 8142; P4-3.0 HT; XP Pro SP3, current updates; 2GB RAM.

I have a second HDD, WD Caviar 320 as a data disk.
A week ago I ran the IBM PC-Doctor5 utility and everything in the computer passed.

Two days ago it all of a sudden started to take up to 2 minutes to open a file in Windows Explorer and yesterday morning during boot up Windows reported "one of your disks needs to be checked for consistency"and that it had to run CHKDSK.
CHKDSK reported a large number of file record segment to be unreadable, 7228 - 7231, 45900 - 45902; 45952; 46220 -46237; 73244 - 73247, 84836 - 84839, 84816 - 84847; 84864; 110472 - 110484; 110592; 143246 - 143271 and 143360.
Then CHKDSK is verifying indexes (staqe 2 of 3)
Deleting an index entry from index $0 of file 25.
Deleting an index entry from index $0 of file 25.
Insufficient disk space to correct errors in index $0 of file3769.
(All above data taken from screen shots with a camera.)

After that the computer booted up normally and when double clicking on the drive letter Windows reported that the disk in that drive letter is not formatted.
I shut down the system and, booting up an hour later, Windows booted up normally but it now does not even display a drive letter for that HDD.

Does anyone know of a way to recover data from that drive by using a programme on a floppy or have any suggestions as what to do.

(As the warranty expires January 15, 2011 I have requested a RMA from Western Digital and have received my RMA shipping label Western Digital.)

[Geek-9pm]

Your chances are slim.    
Take a look at this:
http://www.runtime.org/data-recovery.htm
The product is either pricey, but you don't buy it until you know it works.
- OR-
http://www.easeus.com/
Thar products are excellent and may work for you.

[Arno]

I guess your first sentence says it all.

If inserted as a second drive the BIOS does not recognise it either.

Thanks,
Arno

[Geek-9pm]

I guess your first sentence says it all.

If inserted as a second drive the BIOS does not recognise it either.

Thanks,
Arno

Well, now you know where this is going.
Either you have a bad cable or the motherboard is failing.
It is cheaper to buy another cable instead of a motherboard. And spare cable is always handy. But I would assume you got a new cable with the new drive.
A failing PSU is another possibility. But I don't think so.
Your data might still be on the drive.

[Computer_Commando]

...If inserted as a second drive the BIOS does not recognise it either...

What do you mean "inserted as a second drive"?
What is your goal, you already have the RMA to return the drive?
Do you want to just attempt  to retrieve data before the return to WD?  If so, forget about it, unless you want to spend $89 on this software, which is still no guarantee:  http://www.grc.com/sr/spinrite.htm

[Arno]

Either you have a bad cable or the motherboard is failing.
It is cheaper to buy another cable instead of a motherboard. And spare cable is always handy. But I would assume you got a new cable with the new drive.
A failing PSU is another possibility. But I don't think so.
Your data might still be on the drive.

I don't think that this is applicable as any of my old 40 GB HDD are doing fine as #2 with those cables.

I started this thread after the completion of this one http://www.computerhope.com/forum/index.php/topic,112580.0.html

In a nut shell, new 160 GB HDD, 2 months later getting BSOD, increasing frequency, started that thread, followed instuctions until such time that the re-booting started during rebooting.
Got another computer, put the 160 in as second drive and started to copy data via Network to the 320.
The day before completion Windows Explorer opening of a TXT file took up to 2 minutes and the following day that 320 to which I had saved all data failed, see post # 1.

[Arno]

What do you mean "inserted as a second drive"?

Slave

What is your goal, you already have the RMA to return the drive?
Do you want to just attempt  to retrieve data before the return to WD?  If so, forget about it, unless you want to spend $89 on this software, which is still no guarantee:  http://www.grc.com/sr/spinrite.htm

I fully agree with you that I will not spend any extra money, particularly since one of the links posted by Geek-9pm said to make sure the drive is recognised by the BIOS.

Yes, asking here was an final attempt at a kick of the can to see if I could get data off it.
(BTW, I think I've been using Steve's Shield Up for almost 10 years now.)

Thanks,
Arno

[Computer_Commando]

...(BTW, I think I've been using Steve's Shield Up for almost 10 years now.)...

Given the errors you're getting, Spinrite might be the ticket for you.  It's resurrected a couple drives for me.  You know that Steve's stuff works!

[Arno]

I have since found an important database on one of the 40 GB HDDs and another programme on another one and will leave it at that.


Advise please.
Although this thread isn't solved it had come to a practical end.
Should I click the [mark solved] box or just leave it be.
(Same applies to the Recovery console thread as that computer does not exist any longer.)

[Geek-9pm]

From your posts I come ton the following conclusions.
1. The BIOS does not work right with the 160 GB drive.
2. The whole system works fie on the 40 GB drive.

Therefore build this as a 40 GB print spool-er or file server on your network. Or as a spare workstation for visitors to your pad. 

Don't throw it away just because it does not like large drives.

[Arno]

From your posts I come ton the following conclusions.
1. The BIOS does not work right with the 160 GB drive.

The 160 referred to the quoted thread http://www.computerhope.com/forum/index.php/topic,112580.0.html
It works fine as the second HDD (slave) on the IBM ThinkCentre.

2. The whole system works fie on the 40 GB drive.

Not any longer. Windows Explorer takes 46 seconds to open the right click menu or to open a file.
Everything else is fast; opening a folder happens the second I release the mouse button.
Attaching a file in the eMail client also happens upon releasing the button. Clicking "Launch" in that attachment window immediately opens that file.
I did some searching and came across this but it does not really describe my problem  http://www.computerhope.com/forum/index.php/topic,60755.15.html however, I followed some of the instructions anyway.

Don't throw it away just because it does not like large drives.

Nothing is being thrown away as I have the RMA for the 320 drive, just some Data will be lost but I now have secured the critical ones.

[Computer_Commando]

...Advise please.
Although this thread isn't solved it had come to a practical end.
Should I click the [mark solved] box or just leave it be.
(Same applies to the Recovery console thread as that computer does not exist any longer.)

I think you need 1000 posts to mark it; I'll do it.

[uniquepos]

Use windows management console....

[Arno]

It works fine as the second HDD (slave) on the IBM ThinkCentre.
Not any longer. Windows Explorer takes 46 seconds to open the right click menu or to open a file.
Everything else is fast; opening a folder happens the second I release the mouse button.

Since posting the above I had noticed that WX worked fine as long as the old PIII was powerd up.
I did not have any mapped drives, as confirmed by Windows. Searched the Registry for UNC and drive letter entries but found nothing.

After a massive MS update over night it and before powering up the PIII I found that everything worked in a snap, as it should.

Have no idea if it was caused by a rogue update a couple of weeks ago or what.

Thanks to all who were trying to help.