inaccessible boot device
Results 1 to 3 of 3

Thread: inaccessible boot device

  1. January 9th, 2001, 06:24 AM #1
    Borut_P
    Borut_P is offline
    Registered User
    Join Date
    May 2000
    Location
    Slovenia
    Posts
    67

    Red face inaccessible boot device

    Probably some of you ,have been faced with these problem.

    Situation 1 : Win2k Server/Pro mobo pass away unexpectedly.
    ****************************************
    You can`t get the same replacement. No backup.If you put a new board in , you will get inaccessible boot device . Hard drive is OK + ....Repare options with setup don`t work . You can upgrade , but that is not a good solution.
    ******************************************

    Situation 2 :Win2k Server/Pro. You decide to upgrade or what ever....
    ********************************************
    You change board witch has identical chipset , practically the same mother board but different manufacturer.Repare don`t work , but you can upgrade.ACPI enable on both , the same Aword BIOS , and so on.
    *******************************************

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    I`m trying to find THE solution ,for these problem. I remove HCLM/hardware hive + i use sysprep with situation 2 . Repare don`t work . Upgrade do work , but you have to setup a lot of things , so it is a little less work ,if you start from zero, but if you take in to the account a server , well ....

    ------------------------------------
    Sorry for my English
    Mr. B
    Reply With Quote Reply With Quote
  2. January 10th, 2001, 03:02 PM #2
    JoshKr
    Guest

    Post

    It sounds like it's just a matter of the new motherboard not using the same HDD parameters as the old motherboard (in situation 1 anyway). If you can't get the dead motherboard to boot to anything at all, you may have a problem because you really need to see what the boot drive was originally set to (# of sectors, cylindars, etc). If that isn't possible you should maybe try to auto-detect the Hard drive in the CMOS and try each of the options it suggests (as far as normal mode, LBA mode...) and maybe you'll get lucky and one of them will work.
    Reply With Quote Reply With Quote
  3. January 12th, 2001, 01:08 AM #3
    Borut_P
    Borut_P is offline
    Registered User
    Join Date
    May 2000
    Location
    Slovenia
    Posts
    67

    Post

    I`m giving an update :
    Windows 2k boots in to the graphical display , so ARC path is not wrong .Driver is
    not in question , because it is the same chipset , practicably physical the same board.

    There must be a problem with configuration of some kind , or detection of hardware?


    Borut_p : MCSE , CCNA , ACT , A+
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Bookmarks

Posting Permissions

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

Forum Rules