Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: win2000 inaccesible_Boot_Device

  1. #11
    AOs Resident Troll
    Join Date
    Nov 2003
    Posts
    3,152
    Sounds like the 200 mb drive is flucked up somehow...physically...

    Maybe a bent pin on the connecter....

    Can you try it in another machine as slave???

    MLF
    How people treat you is their karma- how you react is yours-Wayne Dyer

  2. #12
    They call me the Hunted foxyloxley's Avatar
    Join Date
    Nov 2003
    Location
    3rd Rock from Sun
    Posts
    2,534
    the fixmbr always puts out that 'warning'

    I feel you need to fixmbr and to do it when the 200GB is set as master
    IMHO natch
    so now I'm in my SIXTIES FFS
    WTAF, how did that happen, so no more alterations to the sig, it will remain as is now

    Beware of Geeks bearing GIF's
    come and waste the day :P at The Taz Zone

  3. #13
    Howdy.

    No physical damage to the 200Gb drive, i set the jumper on it to slave, and put it in my suse box and it is detected at Bios, suse load ups, and i can see the drive, but it will not let me mount it.

    cheers
    f2B

  4. #14
    AOs Resident Troll
    Join Date
    Nov 2003
    Posts
    3,152
    What kinda of cable are you using???

    Is there a difference in the 2 boxes??



    MLF
    How people treat you is their karma- how you react is yours-Wayne Dyer

  5. #15
    Howdy.

    It's just a normal cable IDE cable {I think that's the word for it, i'm to tired to think. }
    One box is
    32bit, <-Suse10.0
    while the other is
    64bit<-windows box

  6. #16
    AO Curmudgeon rcgreen's Avatar
    Join Date
    Nov 2001
    Posts
    2,716
    I would put the 200g drive in alone, set as primary master.
    Boot from the windows install cd and partition the drive.
    then you could stop, reinstall the old drive as primary master,
    200g as slave whatever, and try to fix the problems on the
    40g drive. Like others have said, the MBR on the 200g is
    messed up. that's why you can't mount it under linux.

    I would consider the practice of copying a partition to
    another drive to be an experimental method.
    Prolly better to install from scratch.
    I came in to the world with nothing. I still have most of it.

  7. #17
    AOs Resident Troll
    Join Date
    Nov 2003
    Posts
    3,152
    You know maybe partition Magic has a limit on the harddrive size it can recognize\copy to...and the 200 gig threw it off...which then mucked everything up

    As suggested by rc ...try setting up a partition first...then use the partition magic to copy the os/??

    Hopefully you can recover the 40 gig drive

    Just thoughts

    MLF
    How people treat you is their karma- how you react is yours-Wayne Dyer

  8. #18
    Just Another Geek
    Join Date
    Jul 2002
    Location
    Rotterdam, Netherlands
    Posts
    3,401
    Originally posted here by .:front2back:.
    No physical damage to the 200Gb drive, i set the jumper on it to slave, and put it in my suse box and it is detected at Bios, suse load ups, and i can see the drive, but it will not let me mount it.
    Looks like the drive is borked.. Or perhaps the BIOS cannot handle disks that large..

    Since it's not working right now.. Have you tried just a quick 'n dirty w2k install on it?
    Oliver's Law:
    Experience is something you don't get until just after you need it.

  9. #19
    Howdy.

    well i ended up recovering the contents of the 40Gb drive. And the 200Gb drive has been returned to the shop that it was purchased from. And i was given a replacement.
    I took the drive into a local computer shop, Anyhow it took 'em from 9:30Am until 2Pm in the afternoon, but they used some program and were able to copy all the needed data over to a temp drive for me.

    Anyhow i don't think that i will be touching that damned partition magic anymore..

    greenies to all those that helped

    cheers
    f2B

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •