Hdd

backed up all my stuff on my 160 gig last night and i formatted my 120.(OS) after i got windows 2k back intalled my second hdd was not apearing so i went to disk management and i have Disk 0 with is Basic (MY OS) then i have Disk 1 and it is Dynamic and Unreadable..when i click on it it dose nothing and when i click revert back to baic it says all data will be lost and i say no. How can i get back my stuff ,,cuz i have everything backed up on that and i NEED IT...

 

Do you have the jumpers on the back of the drives configured to master and slave

Rick

 

yes it worked before format

 

I'm having trouble figuring out which drive is which, and what you did with each. Maybe you could spell it out.

Which drive was your primary before the re-install? What filesystem were you using? What drive letter did your OS give it? What was on it? What changes did you make to the drive?

Wich drive was your secondary before the re-install? What filesystem were you using? What drive letter did your OS give it? What was on it? What changes did you make to that drive?

Did you disconnect either drive as part of your re-install, or make any changes to the way they were hooked up to your system?

You said "i have Disk 0 with is Basic". What do you mean by that? Could you also explain "revert back to baic" with reference to your comment re Disk 1 (whichever that one is).

 

ok lets do it this way

Drive A= 120GB OS Drive System Drive
Drive B= 160GB Everything Else

Drive A was my primary drive before and after reinstall

I am and was using NTFS

Drive A was given the drive letter C

Drive B was not given a drive letter after the format

Drive A had all system files

Drive B had anything else

No Changes Made

Drive B

No

There is Disk 0 Wich is Primary Master
There is Disk 1 Wich is Primary Slave

When i right click disk 1 it gives me the option to revert back to basic wich formats it



Any more questions?

 

Re: Hdd and NTFS

That helps, but we've got too many labels for your drives floating around. I'm going to summarize what I've gotten out of what you said. Check the following for accuracy:

Your primary master (Disk 0) is your 120GB drive, labelled C: by your OS. You've called it "A". You re-formatted that drive with NTFS, and re-installed Win2K on it. You have not changed that drive's position on the drive cable, and you have not changed its jumper settings.

Your primary slave (Disk 1) is your 160GB drive; your OS used to see as D: but now does not recognise it. You've called it "B".) You have an NTFS format on this drive, and you did not re-format it. You have not changed its position on the drive cable, and you have not changed its jumper settings. You have a backup for this drive.

Does your system BIOS see the primary slave? Does the BIOS show the appropriate settings and size for that drive?

If your BIOS can see the drive but your OS will not recognise that drive and assign it a drive letter, I can think of only two possible causes:

• it has been marked "hidden", or
• your OS does not recognise the format on that drive.

You'd likely know if the drive has been marked "hidden". It doesn't happen by accident, and I doubt that Microsoft provides the software to do things like that. (Partition Magic does, though.)

There are several possible causes for your OS's failure to recognise the D: drive. They include:

• the drive is not formatted.
• the master boot record or partition table has been corrupted in a way that prevents your OS from recognising the drive.
• the existing format is one that your OS cannot recognise.

Given that the last is not likely in the circumstances as I understand them, this does not augur well for whatever you had on that drive. I hope your backup is a good one.

Other possibilities that those above probably exist. And I am not familiar with NTFS. Now that we have established that you are using NTFS, it's time for me to back out of this discussion. Perhaps someone who is familiar with NTFS can step in here.

 

http://www.jared.dageeks.com/1.jpg

http://www.jared.dageeks.com/2.jpg

here is what it says

yes all that was right

i was sapose to disconnect the drive before reinstallation but i didn't know that at the time. I have to do some DOS work to try to get this all back. Im kinda at a hault right now waiting for more goahead from another person, if u got anymore info let me know

 

http://www.jared.dageeks.com/3.jpg

 

I couldn't have told you that -- but now that you've said it, does that mean that both drives got re-initialized by the Win2K re-install?

Anyway, that's something for you to check up on when you catch somebody who knows Win2K and NTFS. I've no idea what the terms "dynamic" and "basic" refer to in the screen shots you've provided. That terminology doesn't appear in the software I use.

 

??? i think yes but im not sure about the question

 

Initialized: zeroed out; blanked; returned to starting point. That's what pressing the "reset" button does to your CPU. You get the idea.

Find out whether a Win2k re-install does this to all drives on the system - and if it doesn't, you could try asking someone who also runs Win2K to hook the drive up to their machine and look at it to see what's on it.

If by some chance your 160GB drive was initialized by the Win2K re-install, it'll be in the same condition it was when it left the manufacturer. It will need (in this order):

• partitioning (in DOS or Win9x, you'd use FDISK.EXE or a 3rd-party utility that does the same thing). This is the process that creates the partition tables and the master boot record, regardless of whether you have a single partition on the drive or many partitions;
• if it were to be a boot drive, you'd mark it as "active" at this point. The partitioning software provides that service.
• formatting (in DOS or Win9x, you'd use FORMAT.COM or a 3rd-party utility that does the same thing);
• if it were to be a boot drive, you'd have the formatting software transfer essential system files to the drive as part of this process. At least one of them has to be in exactly the right place on the drive, because it must be loaded into memory before any operating system can be functional enough to find it.
• transferring whatever software or data files you want to that drive.

Until it's partitioned and formatted, your OS won't recognise the drive as valid.

I've no idea what utilities Win2K provides for those functions. They may (or may not) have the same names. Besides, you've presumably yet to establish that your data did go to the Great Bit-Bucket in the Sky. I've no idea what Win2K does to a secondary drive that is active when the install is done.

 

that did not happen. it was not zeroed out but it was put in a state where the information will be hard to get

 

dose anyone else have any ideas??

 

sigh

 

IT CAME BACK!!!!!

i ran the recovery disk i found for the drive and it said my comp was not supporting 137+GB so it did that and restarted and IT'S THERE..everything is there!!!!

 

Thanks for letting us know what the problem was. Now we know what we overlooked.