Unrecognised HD

Discussion in 'Hardware' started by Toke, Jul 9, 2004.

  1. Toke

    Toke MajorGeek

    Hi guys, trawled all through post but no reference to my prob.. I installed a SATA 120 gig that went to wrong HD and marmalised it. Have spent 10 weeks trying to retrieve data but have now given up..I have now fdisked the marmalised one and partitioned and formatted, now the com will not recognise its there, have tried all jumper settings/with without sata connected but still not recognised. I took out and installed in other computer and recognised NP. HD's are
    Drive #1 - ExcelStor Technology J680 (76 GB) Drive C:(master) EIDE
    Drive #2 - ST312002 6AS SCSI Disk Device (111 GB) drive H: (slave) SATA
    Missing one a 120 Gig maxtor (slave) EIDE

    Motherboard Name Abit AN7 I, 1 AGP, 3 DIMM, Audio, LAN, IEEE-1394)

    CPU AMD Athlon XP-A, 2166 MHz (13 x 167) 3000+

    Operating System Microsoft Windows XP Professional

    Motherboard Chipset nVIDIA nForce2 Ultra 400
    System Memory 512 MB (PC3200 DDR SDRAM)
    BIOS Type Award (01/06/04)

    any clues please .. :)
     
  2. krazykrl

    krazykrl Sergeant Major

    Do you have a 120GB SATA drive or a 120GB EIDE drive? Or both?

    Do you have SATA onboard or are you using a PCI card or something?

    What jumper settings are you trying to use?
     
  3. Just Playin

    Just Playin MajorGeek

    What is the meaning of "marmalised"?
     
  4. Toke

    Toke MajorGeek

    Hi Krazykrl.. lets start from the begining. a while ago I installed a 120 Gig SATA with 2 other EIDE a 120 and an 80, when sata instalation was performed it went to the wrong drive (120 Gig) to copy and format,(yes i should have disconnected) and in the processs (marmalised)= jumbled/anihilated the 85gig of data that was on there. The computer still recognised it was there and I had tried to retrieve all data but it was coming back all jumbled and well of know use. So I then formatted and since, the computer will not recognise its there. have tried all jumper settings. This morning I had a spare HD and put it in its place, and it was recognised no prob.I then took the unrecognisede HD put in another com and formatted installed XP on it, brought it back as slave to the original computer and it still will not recognise it.. Ummm. it as set as slave I am now going to disconnect the SATA and see if it will recognise,Umm it gets worse. I have tried every way but which way. Whenever the other EiDe (Master)80 Gig (Maxtor) is connected as well as the one I want to recognise (slave)120 Gig (marmalised) it will not show, disconnect the master (maxtor 80 gig) and it (the 120 slave) will be recognised as slave with or without the slave jumper setting. So it seems that the confilct lies between these two, but what is beyond me.. I think i will put plan (B) into action, I'll go get another 120 SATA and set up a RAID system and see what happens from there. With the RAID I will then have an 80 and a 120Gig Eide connection as storage I hope. Hope this makes sense,Thanks for your reply and any suggestions would be most welcome.. PS. Should the SATA drive show in Bios as it isnt..??
     
  5. Toke

    Toke MajorGeek

    Hi Krazykrl just an update if your still around. haven't managed to get the other SATA yet out of stock but as an update I was in BIOS yesterday and found where to get ALL info on HD like cylinder size etc. but no information was available on any HD's, it gets even more puzzling.. :rolleyes:
     
  6. krazykrl

    krazykrl Sergeant Major

    OK.....It depends on your BIOS on whether or not it will recognize SATA drives. My guess is no. It is possible there is an upgrade that can , you will have to check.

    It seems to me this is a jumper issue. Take the two drives (the 80GB and the 120GB EIDE) and look up the specifications of each drive. It is possible one of them requires a particular setting when there is a slave present, or something along those lines. :)

    Good luck.
     
  7. Toke

    Toke MajorGeek

    Hi again Krazy K , Umm. took your tip about Jumper settings and sat and thought that the only setting I hadn't tried was NO Jumper at all, (on the unrecognised HD) and low and behold that seems to have done the trick. I started with jumper slaved and Booted with HD on its own, then added one (HD) each boot. When all 3 were connected no recognition so thats when I took out the Jumper altogether from the offending HD and all was Ok, have now formatted it is now empty and ready for data storage. Slight hiccup whereby I sometimes get the ''send prob to Microsoft'' window when accessing the drive but as i am going along that is getting less and less and hopefully will settle it self down, (just accessed it now 10 times and all ok) so many thanks for your help and now to begin more nightmares when i get the other SATA to set up RAID lol but this has been a learning curve so hopefully all will go smoothly .. Thanks again Krazy Kay :)
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds