19 replies
by bfilmfan
by bbusbee
by bbusbee
by absolutely
It could still be the BIOS. I know there is an 8GB limit, but I'm not sure whether that's a BIOS or Windows issue.
Alternatively, the number of cylinders, heads and sectors should be available in the documentation that accompanied your drive, or on the manufacturer's website. If those specs do not match what's in your BIOS, any operating system will "recognize" your drive according to that faulty identification. You may only need to manually input the CHS info into your BIOS, or you may need to flash it as BFilmFan said. I'd begin by trying to manually input data to the BIOS, mistakes in that process are much less damaging than incorrect flashing!
by absolutely
by breydel
Did you say you ran fdisk from a Win95 machine ?
If so, this could indeed be part of your problem...
Win95 fdisk does not recognise lrge partitions, so using it on a 60GB drive may create all sorts of unexpected results.
You need a minimum of Win98SE fdisk to do your testing.
Also, if the disk was originally on an XP machine, the filesystem may be NTFS and hence not readable by Win95 or Win98.(unless you use special utilities...)
The first thing I would do is take an image of the drive for backup reasons - then you can test and try all you want.
Then you can try to fix the MBR using the proper version of fdisk.
If all else fails, you can use a disk recovery tool to scan the drive and recover the data you need.
A low level format is not going to help you recover any data - on the contrary.
by bbusbee
I thought the limit on W95 was 2 gigs, am I wrong there? Also, the FDISK utility disk that I used was from a W98 system and since I booted from the disk itself I didn't think the W95 operating system would come into play, am I wrong there too?
I can't make an image of the drive, I can't see anything to make an image of. The file system is a FAT 32.
I guess I need to do the rest of the work on my XP machine. So if I put the drive as a slave into my XP system and run the FDISK utility will this correct anything or do nothing?
BTW, can you guys recommend a good Data Recovery software that will retrieve data without the boot record to reference, one that scans each sector individually?
Thanks for all your input.
by hal 9000
Well the first thing to do is set the BIOS to auto and download Power Max from Maxtor and run a Advanced test on the drive. That will tell you if the drive is working or not.
It is available from here
As for the Size on the Drive unless it is jumper ed to a 32 GIG Drive it should be seen in BIOS providing that the hardware can support something that big. Like a M'Board with a 486 will not see the full drive and most likely nor will some of the early Pentium stuff either.
Windows doesn't 95 play a part in recognizing the HDD size it is all hardware related about the only thing possible is with a very big HDD it may not all be seen properly with 95 but it should be seen perfectly all right in BIOS. Check that the BIOS actually supports a Drive that big before going any further if it does sounds as if the drive is fried. You can check if it is still UG you can get a RMA here if it is under the makers Warranty period.
Col
by hal 9000
You can reformat the drive again and use a program like On Track to recover the Data but it isn't cheap but if you have access to a licensed copy you'll be laughing
http://www.ontrack.com/easyrecoveryprofessional/
Failing that there is always XWays Davory which is around 40 Euros and is a lot cheaper though more time consuming to use. You can get a Trial copy which will recover the first 200 K of each file from here
http://www.x-ways.net/davory/index-m.html
And run a test to see what is findable on the drive. If that works you can buy a licensed copy on the net from that URL and they will e-mail you a code to activate the product so it works and recovers the entire file.
While not in the class of On Track it isn't anywhere near the price either and though it takes longer to recover files it's a lot cheaper. Just remember never to write recovered files to the drive that you are recovering from as they will over write other things on the drive and make the remaining files unrecoverable so save the recovered files to another folder on a different HDD and keep the one with the lost Data on it free and unwritten to until you have recovered all of your files. Davory will only recover one type of file at a time so you'll have to run a JPEG recovery then a DOC and so on. It gets time consuming of course if you know the name of a file you can recover that by itself but if you need to recover a lot of JPEG, DOS, XML and so on it is easier to run the file to recover each of those file types and just turn off the monitor and walk away until it has finished then start on the next file type.
Col
by bbusbee
Hal 9000, cool name!
After more testing tonight I discovered that my brand new ribbon IDE cable that I got with my ASUS mobo was defective. Now I am getting the correct readings in the bios on my XP machine but when I run the PowerMax or EZ Drive utilities they still see only the 8gigs. I am running the HDD Regenerator Demo version tonight looking for a bad sector but I don't think I'm gonna find one because I believe running the PowerMax tests last night told me everything was fine. But then again it may have seen only the 8 gigs as well. So back to my current problem, the bios sees the entire drive but XP sees it as a non-formatted drive and won't read it. Is there a way to get past the formatting problem to retrieve the data? If there are no bad sectors a utility like HDD Regen won't help.
by bbusbee
by ozi eagle
Hi,
Firstly any formatting will destroy your data!!
What OS was the computer it came out of using?
The 8GB was a limit on mobos at one time (maybe BIOS upgrade to fix).
Next W95 had FAT16 file system, limiting disk size to around 2GB. W98 had FAT 32, much better.
As suggested above take an image to a different HDD, then FDISK /MBR from a W98 disk.
XP should be able to read any file structure.
by bbusbee
by bbusbee
by bbusbee
by bbusbee
Poster rated this answer.
by bbusbee
by bbusbee
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending