Hard cannot be access but shows up in device manager

  • Thread starter Thread starter Gill/ian
  • Start date Start date
G

Gill/ian

My Question is related to having two hard drives
one a seagate ST320014a which is my primary, set to
master jumper, while the second drive is a western
digital WD205AA with the jumper set to Dual Slave
both off of the same bus cable. Both are recognized
by the BIOS and the device manager sees them both,
but the WDC cannot be seen by windows or accessed
by windows. Can somebody give me a possible
conclusion and resolution? or point me in the right
direction?
Operating system is win2K
system manufacurer is a gateway (I know please don't sayit)
700 mhz
256meg mem
two CD's one reader/player other writer.
I have enough interrupts.
 
- I've never heard of a "dual slave" jumper setting; usually it's just
"slave," which implies there's a "master" on the cable/controller.

- If the HDD is not partitioned and formatted W2k Explorer can't deal
with it. Device Manager can be used to partition and format it.
Hope this helps.
 
I have a similar problem. Gateway PC (boo!)with winNT
4.0, a seagate as master on IDE1, I put a second hdd
(western digital)as master on IDE2 in order to move the
data from the master drive prior to format/upgrade to
win2k. Booted up, winNT4.0 saw the slave drive so I
moved the data, pulled the slave drive off, put a ghosted
image of win2k on the master drive, worked fine, put the
slave drive back on to move the data back, it is detected
in the bios but not in device manager or WDC...I've put
the slave drive on other pcs and the same problem exits,
it can be seen in the bios but not by windows. On
western digital's site i found the exact problem, but
they want me to call and pay for support, saying it is a
microsoft operating system issue. I have searched
microsoft's website but no answers! Maybe we can put our
heads together and find a solution! Here is the link to
the western digital FAQ (just FYI):

http://wdc.custhelp.com/cgi-
bin/wdc.cfg/php/enduser/std_adp.php?
p_sid=Oym_UoTg&p_lva=&p_faqid=1076&p_created=1063317716&p_
sp=cF9zcmNoPSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTU0JnBfY2F0X2x
2bDE9MjcmcF9wYWdlPTE*&p_li=


Kattmee
:)
 
Have you tried the Recovery console and "fixmbr"?
I have a similar problem. Gateway PC (boo!)with winNT
4.0, a seagate as master on IDE1, I put a second hdd
(western digital)as master on IDE2 in order to move the
data from the master drive prior to format/upgrade to
win2k. Booted up, winNT4.0 saw the slave drive so I
moved the data, pulled the slave drive off, put a ghosted
image of win2k on the master drive, worked fine, put the
slave drive back on to move the data back, it is detected
in the bios but not in device manager or WDC...I've put
the slave drive on other pcs and the same problem exits,
it can be seen in the bios but not by windows. On
western digital's site i found the exact problem, but
they want me to call and pay for support, saying it is a
microsoft operating system issue. I have searched
microsoft's website but no answers! Maybe we can put our
heads together and find a solution! Here is the link to
the western digital FAQ (just FYI):

http://wdc.custhelp.com/cgi-
bin/wdc.cfg/php/enduser/std_adp.php?
p_sid=Oym_UoTg&p_lva=&p_faqid=1076&p_created=1063317716&p_
sp=cF9zcmNoPSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTU0JnBfY2F0X2x
2bDE9MjcmcF9wYWdlPTE*&p_li=


Kattmee
:)
 
I'm assuming you mean try "fixmbr" on the slave drive,
but I'm not able to access the drive at all...I've booted
to DOS and tried to Fdisk the drive that has my data, but
it doesn't see it. I thought fdisk would work on a drive
with any OS since it is so low level, but it doesn't see
this drive at all. I'm just not ready to give up I guess!

I saw on some website that I should try putting in the
freezer for an hour to see if the heads would rise from
the cold....silly as it sounds but at this point I'm
ready to try anything...
 
Can you hear the drive spin up at power on?
I'm assuming you mean try "fixmbr" on the slave drive,
but I'm not able to access the drive at all...I've booted
to DOS and tried to Fdisk the drive that has my data, but
it doesn't see it. I thought fdisk would work on a drive
with any OS since it is so low level, but it doesn't see
this drive at all. I'm just not ready to give up I guess!

I saw on some website that I should try putting in the
freezer for an hour to see if the heads would rise from
the cold....silly as it sounds but at this point I'm
ready to try anything...
 
Back
Top