Odd BIOS disk detection

ok, so I gathered up most of the spare hardware I have and crammed it into one server.... it's not a powerhouse, but it's got 1.5GB of ram and 60GB+80GB hard drives...
problem is, every time I reboot, I get "master hard disk failure" - I have to go into the bios, do the little disk detection, and then save and exit... happens every time I reboot...
anyone have a clue what could cause this? I don't really have alot of time to pull random pieces in and out...
I'll try it with just one single disk later on... but any speculations from the peanut gallery would be appretiated   

ghostwalker wrote:I would check to see if the cmos battery is working correctly. You did say it was old hardware? What is the mother board?
it's a tyan something or other... max support is for P3 @ 866MHz, so it's fairly old, but not *that* old...
I'll check the battery - I would have never thought of that 8) silly me

Similar Messages

  • Mediashield BIOS hangs Detecting Array

    Apologies for the long post...
    My mobo (MSI P7N Diamond 780i SLI / 570i SLI)
    The SATA drives are organised thus..
    SATA 1 - OCZ Vertex - Windows 7 Home (64bit) Retail version
    SATA 2 - Data HD
    SATA 3 - Mirror A
    SATA 4 - Mirror B
    SATA 5 - Mirror A
    SATA 6 - Mirror B
    more system details below...
    I had the system working reasonable well apart from a flip/flop array dead/alive problem that was really weird. See... https://forum-en.msi.com/index.php?topic=132584.0.
    In an attempt to get to the bottom of this problem I decided to install a new dual boot copy of Win 7 on SATA 2. I did this to see if a new install of Windows without my applications showed the same problem.
    On advice from the Win 7 forum, to ensure no corruption during the Win 7 install, I removed the SATA 3/4/5/6 cables from the drives. I then installed the new Win 7 and the latest nVidia raid driver on SATA 2.
    Then I reconnected the SATA 3/4/5/6 cables.
    Booted into the old Win 7 twice - the flip/flop problem still existed there. And then booted into the new Win 7. This showed the erring condition "array dead", but otherwise it worked ok. I restarted the new Win 7 expecting the flip/flop problem to show up, however, I never got into Windows.
    The system hung during the MediaShield BIOS with detecting array.
    The only way I could get it to boot, to get into the BIOS or Windows, was to remove all cables from SATA3/4/5/6.
    If I set the RAID mode to IDE, or disable the drives from RAID mode in the BIOS, I can restart with the cables attached. In windows explorer two of the array drives show up - one from each array. The other two drives show up in the Disk Manager apparently without a file system on them :-( 
    I have had this problem before and I found the only way to fix it was to run Darik's Nuke & Boot on the drives. Repartitioning them and reformatting did not get rid of the hang condition. I never did understand what was left on the drive after repartitioning/formatting that upset MediaShield.
    Does anyone have any advice on what I can do to narrow down to understand what is causing this to happen.
    BTW - This hardware has been running just fine for ages on XP. I have been trying to get a stable Win 7 setup for weeks now.
    Roy
    System Details
    Motherboard (MSI P7N Diamond 780i SLI / 570i SLI)
    No overclocking.
    CPU is Intel Core2 Duo E6850 3.00 Ghz
    Memory - 4Gig - Kingston Hyper KHX8500AD2K2/4G
    GPU - nVidia GeForce 9800 GT
    PSU - ThermalTake Toughpower 850 AP.
    There are no other cards in the system.
    The SATA drives are organised thus..
    SATA 1 - OCZ Vertex - Windows 7 Home (64bit) Retail version
    SATA 2 - Data HD (now new copy of Win 7 - Dual Boot)
    SATA 3 - Mirror A
    SATA 4 - Mirror B
    SATA 5 - Mirror A
    SATA 6 - Mirror B
    nVidia nForce drivers (11.1.0.33)
    Motherboard 1.51 BIOS, and latest
    Motherboard revision is 020.

    You started this topic already in the Win7 section. You stated to start a new one.
    I have a better idea: I will move the other topic in here.
    Next time, please ask to move a topic in stead of starting one with the same question.
    Thanks!!

  • [Athlon64] 'No disks detected' when installing WinXP64bit on striped SATA RAID

    I've been using my RS480M2 board with a dual boot config (WinXP Pro 32bit and WinXP Pro 64bit) using a Maxtor Diamond Plus 80G SATA hard drive configured as an IDE/ATA. I set the controller as "IDE Controller" in the bios. Everything has been working just fine and I must say that I really do notice a big performance improvement on the WinXP64bit compared to the WinXP32bit.
    I then purchased another Maxtor 80G SATA with the intention of setting up a SATA RAID 0 (striping) config to see if I will get more performance gain. So I changed the controller to "SATA Raid Controller" in the bios. Then I used the Sil3112A GUI (by pressing F4) to configure my 2 SATA hard drives as RAID 0. I tried installing WinXP Pro 64bit but the SATA RAID drivers I've tried just do not work. The Windows setup would indicate that there are no disks detected. I already tried the 32bit SATA RAID driver, the one at Silicon Image site, a few ones at PlanetAMD64, etc. No luck!!! 
    So I just installed WinXP Pro 32bit using the provided Sil3112 SATA RAID driver floppy diskette that came with my board. And it installed without any problems. All is well. So the problem is: WHERE THE HELL CAN I GET A SATA RAID DRIVER FOR WINXP64BIT???
    To anyone who has the solution to my problem, kindly email the driver (or link) at [email protected]
    Thanks. 

    Sorry for the late reply. I finally got to install Windows XP Pro 64bit onto my RS480M2-IL configured as SATA RAID 0 (striping) with 2 80G DiamondPlus SATA hard drives. The sata drive that worked is the one on this link:
    http://www.planetamd64.com/index.php?showtopic=9433
    Thanks a bunch to Mtalea 

  • My v3753au (32bit win7) bios cannot detect internal dvdrom & hard to detect internal hdd?

    hi...
    my v3753au is wonderfully running on 32 bit win7.  lately the bios cannot detect the internal dvdrom & kinda hard to detect (longer than usual) the internal hdd during startup.  i've tried with the other dvdrom & it's still the same.  however, the one that i used is still ok on other laptop.  fyi, i've tried with the original f.15 version as well as the latest f.28 version but both let me down.  when win7 runs, dvdrom doesn't appear either in win explorer or device manager.  i've also checked the registry for that filter thing but it isn't there.  any suggestions of what should i try next?
    tq for the help...

    > I couldn't reinstall/recover new system from CD cos Win7 couldn't detect any drive while installing.
    Its no matter if the SATA mode is set to AHCI or compatible mode. The HDD should be recognized by BIOS even if the AHCI mode has been selected.
    At the first BIOS page the HDD should be listed with the name and size.
    If it isnt the case, it could be possible that your HDD controller is faulty.
    What HDD did you purchase exactly? Is it a 2.5 SATA HDD?

  • DV7-1220ed BIOS disk test fails in full test (hangs). Is this the disk or the controller?

    Hi,
    my DV7-1220ed started failing with BSOD after I used CCcleaner software.
    I decided to reinstall the PC, but still there seems to be a problem with the disk.
    Sometimes it stalls, and then I can see the disk light on almost constantly and you can hear it spin in a repeating pattern.
    BIOS disk test is OK in Quick test, but hangs in Full test at 0%. Can't stop it with ESC key, have to poff/pon.
    Any idea if this is the disk or the controller?
    Can I move the disk to the free slot to see if this is a controller problem?
    Any help would be appreciated.
    I also used the 'mstd' utility to send info.
    Thanks,
    Jaap

    Hi,
    If you have created your set of Recovery DVDs, these will automatically format the HDD as part of the installation process as well as re-creating all the partitions that were originally on your notebook.
    Regards,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Bios Wont detect anything? is it motherboard problem?

    im fixing my own PC since 8 hours ago and im really desperate now.. here's my problem: 
    i brought my new HDD (500gb) and i installed it and im ready to install windows 7. 
    the problem is my bios wont detect it! Even my bios wont detect my optical drive.. 
    i tried other cables, exchanging ports etc etc. but it wont even work i tried almost anything 
    im starting to think maybe its my power supply or the mother board? 
    pls help me!! thanks guys
    (i did reset the cmos/bios i think 4 times and i did tried other power supply)

    anyone? pls

  • No boot disk detected or boot disk failed

    I'm asking this for my father. He does not have the internet right now.  Nothing to do with this issue though.
    He has a Pavillion 23, model # 23-1270.  A week ago he went to turn on his computer and got an error message saying, " No boot disk detected or boot disk failed.  My sister called HP and one of the techs said it was the hard drive and it needed to be replaced.  So it was replaced.  Went to put Windows 8 back on from the disk, and it still pops up with "No boot disk detected or boot disk failed".  My sister ran diagnostics on it and it comes back saying that the hard drive passed.   But nothing about the dvd/cd player.  Would it not pick that up?  It is part of the computer.  My question is:  Now that the hard drive has passed, and its not reading the Windows 8 disk, is it a dvd/cd problem, or is it some thing totally different?  My sister and my dad have money issues right now and can't afford to use an HP tech.  So I'm hoping that someone knows what could be wrong and what I may be able to try.
    Thank you so very much,
    Andrea K.

     Hello liv2lrn,     
    This is bad news especially around Christmas time. Your fathers computer is not worth fixing. Motherboard is corrupted, because these steps given faild. It is cheeper to buy another computer then it is replacing a motherboard.  That's even if HP has one in stock. What I would do is shop on E-Bay you can find real good deals there for another good used one.  I puchased a high value Sony VGC-LLT25E 24" screen computer for $300.00 Amazon at the time had two listed for $1999.00 and the other one at $1800.00 both were sold with in two weeks.  I got lucky . That computer has out lasted three HP computers witch are newer. It is in mint condition runs a whole lot better then my HP's computers do.  Shop wisely.  You can save lots of money like I did.
    Good Luck I am sure you can find a real good deal like I did.
    frrw.

  • UCS C460 Bios not detect raid

    Hi all,
    i have 2 ucs c460, 1st ucs i can boot into webios to create raid
    the other 1, pressing ctrl+h , still cant boot into webios
    when i check bios at boot options, there is no pci raid adapter detected, only cdrom,network card and efi shell
    but at cimc the raid card detected.
    please help

    Hello,
    Go to BIOS in the Server tab, then Advanced and then scroll down to the Option ROM (OPROM) settings and disable the Option ROM for all cards except for the RAID controller (if you will boot from local disks)
    Note: the OPROM enabled will tell the system to look for a "boot" image through that card, so if you will only boot from local disks (does not matter if you want to have remote data stores, this will not affect your connection to remote storage) disable all OPROM options for all the cards except for the RAID controller.
    HTH,
    -Kenny

  • WAAS hardware is OE612, but Rescue Disk detects model as OE512

    I've had this issue with 2 RMA'd OE612s already. They originally shipped with 4.0.19, which worked fine, but failed on upgrade to 4.2.1.
    Recovery attempt #1 with 4.0.19 Rescue disk displayed :
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
       MODEL: UNKNOWN
       FLASH: found, directory validated
      COOKIE: invalid
       IMAGE: NONE
    FLASHDEV: /dev/hda
    Installer Main Menu:
        1. Configure Network
        2. Manufacture flash
        3. Install flash cookie
        4. Install flash image from network
        5. Install flash image from cdrom
        6. Install flash image from disk
        7. Wipe out disks and install .bin image
        8. Exit (and reboot)
    Choice [0]: 3
    Unknown model, cannot create cookie.
    Subsequent Recovery procedures using Rescue disks from 4.1.7 and 4.2.1 detected the Model as OE512.  Option 2 creates a cookie as a MODEL OE512, which I wrote with option 3. Option 5 works, but trying to write the bin image on 4.1.7 displays this
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Choice [0]: 8
    Enter full URL of .bin image to install.
       ftp://[user:pass@]ip_addr/path/to/file
      http://[user:pass@]ip_addr/path/to/file
      file:/local/path/to/to/file
    URL for .bin image [file:/cdrom/images/WAAS41.bin]:
    Continue?  This will wipe out all disks! [n]: y
    Scrogging done
    Saving random seed...
    dd: opening `/state/random-seed': No such file or directory
      No volume groups found
    /ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
    /ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
    /ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
    /ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
    ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
    ssmgr: op_open or media_open
    ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
    ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
    ssmgr: op_create or media_init
    SSMGR RETURNING: 10 (No such file or directory)
    Reading and installing image, it may take a few minutes, please wait...
    Error, image NOT installed.
       MODEL: OE512
       FLASH: found, directory validated
      COOKIE: valid
       IMAGE: 4.1.7.11
    FLASHDEV: /dev/sda
    Installer Main Menu:
        1. Configure Network (done)
    I suspect that the Installer program on the Rescue CD can't detect the Hardware properly, and thus can't find the proper drivers for the platform.
    Is there any manual method of forcing the Rescue CD Installer to use a particular hardware model?
    Thanks,
    Tom

    Hi Zach,
    >What led you to change the Adaptec configuration?
    I was directed to do so by TAC, although I wasn't sure why, since our other WAE-612-k9s didn't have this option enabled.
    >What is the state of the device prior to upgrading?  Does the WAAS software boot?
    After disabling the hardware raid, the WAE could run any 4.0.x version, but could not upgrade to 4.1/4.2. I tried both the "rescue CDs" for 4.1/4.2, and the "copy ftp install" methods. "Rescue CDs" would work right up to the option for "wipe disks and install .bin" image, but would report "no disks" as shown above. The "copy ftp install" from version 4.0.27 would install the 4.2.1.38 image, but upon reboot, it would fail during the boot sequence
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin-top:0in;
    mso-para-margin-right:0in;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Frustrated, I looked at the boot logs and might have found an issue. On the "faulty" WAE-612, the boot script detects two SCSI adapters; only one shows up in BIOS POST.
    The first adapter (Adaptec AIC79XX) has no drives, but is assigned the device name "scsi0"
    Under the second adapter(Adaptec AIC94XX), the Hard disks are detected, and it's assigned a device name of "scsi1"
    ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 17 (level, low) -> IRQ 17
    scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 2.0.30
            aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs
    Adaptec aacraid driver 1.1-5[24495]custom-IBM
    Loading AIC-94xx Linux SAS/SATA Family Driver, Rev: 1.0.8-12
    Probing Adaptec AIC-94xx Controller(s)...
    ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 19 (level, low) -> IRQ 19
    scsi1 : Adaptec AIC-9405W SAS/SATA Host Adapter
    scsi 1:0:128:0: Direct-Access     IBM-ESXS ST3146755SS      BA33 PQ: 0 ANSI: 5
    adp94xx:0:128:0: Tagged Queuing enabled.  Depth 32
    scsi 1:1:128:0: Direct-Access     IBM-ESXS ST3146755SS      BA33 PQ: 0 ANSI: 5
    adp94xx:1:128:0: Tagged Queuing enabled.  Depth 32
    AIC-94xx controller(s) attached = 1.
    To contrast, our functioning WAE-612s do not have this second detected Adaptec host adapter, and are properly assigned a "scsi0" for their device name.
    Adaptec aacraid driver 1.1-5[24495]custom-IBM
    Loading AIC-94xx Linux SAS/SATA Family Driver, Rev: 1.0.8-12
    Probing Adaptec AIC-94xx Controller(s)...
    ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 19 (level, low) -> IRQ 19
    scsi0 : Adaptec AIC-9405W SAS/SATA Host Adapter
    scsi 0:0:128:0: Direct-Access     IBM-ESXS MBA3300RC        SA06 PQ: 0 ANSI: 5
    adp94xx:0:128:0: Tagged Queuing enabled.  Depth 32
    scsi 0:1:128:0: Direct-Access     IBM-ESXS MBA3300RC        SA06 PQ: 0 ANSI: 5
    adp94xx:1:128:0: Tagged Queuing enabled.  Depth 32
    AIC-94xx controller(s) attached = 1.
    On our faulty WAE-612,  in the section that tries to mount the detected drives, it appears that the script is looking for the physical drives under the "scsi0" device name, using the AIC94XX driver.. .
    2010 Jul  8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sda a
    t scsi1, channel 0, id 128, lun 0
    2010 Jul  8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sdb a
    t scsi1, channel 1, id 128, lun 0
    2010 Jul  8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi removable
    disk sdc at scsi2, channel 0, id 0, lun 0
    BOOT-100: disk apply
    scan_612_disk_map: Can't open . Errno=2
    change_disknum_612 failed!
    /ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdo
    wn, or it has unknown data.
    /ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
    I'm guessing this fails because there are no physical drives on "scsi0", they are assigned on "scsi1". If the disk mapping script  would've tried , I think the drives would've been mounted properly.
    I was hoping there was a modified script out there somewhere, but after our 3rd RMA'd WAE exhibited the same characteristics (these were all in Chennai India), I directed the onsite tech to remove the Adaptec 29320ALP UltrasSCSI adapter.
    With the adapter removed, the 4.2.1.38 code installed and booted properly.
    When I forwarded my results to TAC, our Rep mentioned that the WAE-612-k9 ships with both ACNS and WAE capabilities. He said that ACNS uses that additonal SCSI card.
    I'm fairly sure our configuration is not unique; our environment consists of  32 WAEs, and this is the first time that I've encountered this issue.
    I'm just happy it's resolved now.
    Thanks for your insight, Zach
    Tom

  • KT6 Delta FIS2R BIOS stopped detecting IDE1 & 2 optical drives

    I am working on a new system that has developed an unusual (to me) problem. The system is partially built and consists to date of the following:
    1. Chieftec MA-01BND case with Super-Flower TTGI TT-520SS (520 Watt) power supply.
    2. MSI KT6 Delta FIS2R motherboard with an AMD XP2600 CPU and one stick of Corsair CMX512-2700C2 RAM.
    3. Two Mitsumi MTM-1.44BL floppy drives.
    4. Two Maxtor 6Y080MO HDD’s connected to SATA 1 and SATA 2, not in RAID.
    5. Sony DDU1621BK DVD/CD ROM mastered on IDE1.
    6. Sony DWU10A-B2 DVD/CD RW 1 mastered on IDE2.
    7. Asus V9520 VS AGP video card.
    8. Windows 98SE installed on HDD1.
    Everything was operating properly, and I was installing software and drivers for peripherals, when the following problem appeared.
    At boot-up, the MB logo pops right up; but then, it takes approximately 80 seconds for the BIOS to initiate. Boot-up then proceeds as normally, and Windows 98SE initiates normally. However, neither optical drive appears in Program Manager; and, pushing the “open” button on either drive fails to open the tray.
    After the BIOS initiates, the usual message directing one to press the “DEL” key for access to BIOS Setup never appears. However, if the “DEL” key is held down anyway, the system will enter Setup. Note that there is also a delay of approximately 80 seconds for this to initiate.
    Once into Setup, the “Standard CMOS Features” page indicates no IDE devices. Resetting the detections to “Auto” across the board makes no difference. Resetting the CMOS via the “Clear CMOS Jumper” and via removing the CMOS battery changes nothing except that the CMOS returns to the default settings, and the BIOS still fails to detect the optical drives.
    Since SATA1 and SATA2 are detected and operating, I believe that the chipset is OK because they are served by the same Drive Station on the chipset as IDE1 and IDE2 which aren’t detected and operating. I also consider damage to the motherboard itself to be an unlikely cause because that can’t account for all of the systems, either. I suspect the BIOS because of the following:
    1. The BIOS is so slow to initiate, as is the entrance into setup.
    2. The direction to press the “DEL” key for access to BIOS Setup never appears.
    3. The BIOS has stopped detecting the drives on IDE1 and IDE2.
    4. All of these functions that take place prior to chipset initiation.
    Does anyone know what happened and what needs to be done to return the BIOS to normal operation? Or, is this a board failure, after all?

    Quote
    Originally posted by Fredrik Åsenius
    Sorry, I didn't think of the SATA when I read your specs.
    Easy to do with all that info.
    Quote
    OK, what is BIOS eventually booting from? Is your SATA working?
    What appears to be happenning is that the BIOS times out while trying to detect the IDE's (in this case, optical drives) and then just goes ahead and boots. The SATA's are working fine, as is Windows, once I wait out the time out for the BIOS. Except, of course, Windows also can't see and doesn't indicate in Program Manager the opticals that the BIOS couldn't find, which makes sense. The odd thing in this scenario is that, once the BIOS times out and goes on, it does not provide the customary message to hit "DEL" to enter Setup (but holding down "DEL" when the BIOS procedes will take me to Setup anyway!
    I talked to eSupport today, and the techie says it's a BIOS problem that their update will resolve. Well, of course it WILL; they sell updates (duhhh). Being the trusting soul I am, I'd like some independent confirmation. I've posted this on 4 forums hoping to catch someone who has seen this happen before, in addition to contacting eSupport (Amibios's update shop) and MSI Support.
    MSI's Support Department is, of course, silent, as usual.

  • 865pe Neo2 BIOS not detected

    I have just finished installing the 865pe neo2 and p4 3.0Ghz. When I boot up I get a message that BIOS is not detected. It will nevertheless boot seemingly properly into linux but booting into windows is a bit of a dissaster. I have run the live update from windows and it flashed my BIOS which failed when I rebooted and I had to use the rescue disk that I made b4 I flashed but I still get the message that no BIOS has been found and something about Dram timing.
    Any help would be greatly appreciated,
    Adam

    The huge problem is that you CANNOT get to the BIOS.  It hangs before you can get there.  LOL.
    Well, I tried using the bios recovery to get to version 1.3, but now it won't post at all.  The D-Bracket says that it is a memory problem, but the memory was fine before changing bios.  I am still working on it...
    Pauly

  • Laptop Bios cannot detect new HDD but still able to boot into windows

    I have a Pavilion Dv5 1010tu which the original HDD have died. So i bought a new Samsung 320GB Sata and install Windows 7 on it. After Windows installation finished successful, I manually restart the laptop without Windows setup disk and it stop at dos screen with the error message :
    Boot device not found.
    Please install an operating system on your hard disk.
    Hard disk (3F0) ...
    I check bios and it didn't show any hard drive but when i re-insert Windows setup disk and restart, it can boot in windows without any problem. How can i fix this issue? I already update Bios and run hard disk self test though Bios setup without failed but it still not recognize HDD
    Edit: My original HDD was Hitachi 250GB Sata 
    Bios version F.21A

    ~if advanced mode is off turn it on~ It sound easy huh. I would like to ask How can I access to advanced mode in Bios of Hp laptop? It's impossible.
     defective drive ??? It a newly purchased HDD and it run perfectly fine, i'm posting this message using the laptop i mention above with this HDD as the only hard drive and installed with Windows 7
    Any other idea/ help will be very appreciated , please 

  • Bios Disk Creation & Hard Drive Question A22p

    I am trying to create a disk to flash the bios on a A22p thinkpad.  I have followed the directions on the download page but can't get beyond the DOS screen that contains the license info so nothing ever gets copied to my floppy (dispite using a command line per the instructions).  I am very frustrated - any help on how to make a disk would be appreciated!!
    Second question, I am trying to upgrade the hard drive to 160gb.  Since the install of the OS stalls I am assuming it has something to do with the drive size, hence my reason for updating the bios.  Does anyone know what the max size is that can be installed in an A22p? 

    Welcome to the forum!
    There is an option of non-diskette BIOS upgrade, and that's the route I normally take. Save it to your desktop in Windows and run it from there.
    http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-4Q2KM3
    I don't have a positive answer regarding the HDD size, but will tell you that I've had a 100Gb drive in an A22p. Some older machines have a BIOS limit at somewhere around 137Gb if I'm not mistaken. Whether A22p falls into this group or not, I'm not 100% sure. Even if it does, I believe that it would simply fail to realize the "excess" size, so I believe that your issue may be someplace else.
    Hope this helps.
    Cheers,
    George
    In daily use: R60F, R500F, T61, T410
    Collecting dust: T60
    Enjoying retirement: A31p, T42p,
    Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
    Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

  • Bios auto detect

    after installing my sempron 2800+ socket A today I set the bios to auto detect the CPU . It detected it as an XP1900+ and set the DDR to 400 .
    However when I manually set the FSB to 166 and the mem divider to 1:1 then it detected it correctly as a sempron 2800+
    why did it do this ?
    The motherboard is an MSI K7N2 Delta-L
    I have the latest bios V5.8

    they all boot first time at 100 fsb
    if you clear cmos it will be 100 fsb again on most boards
    its normal

  • 975X Platinum PUE, 7.2 bios not detecting my SATA2 RAID?

    Just bought this mobo 3 days ago and had everything working great with XP and all, until I decided to update the BIOS to 7.2 (no specific reason, just wanting the latest!).
    Now XP wont boot :(
    It goes through post and all, but it doesnt show the SATA RAID settings (ctrl-i) screen anymore. It seems it only detects the harddrives if I put them as IDE drives in BIOS. If I choose RAID as I had before the flash, it wont detect them.
    It goes through all the bootchoices until resorting to a network boot.
    Should I try flash it back to 7.1?
    Pardon my english

    OK, after sending a troubleshooting report to MSI (very quick response by the way....minutes actually), they stated that they were having no problems with there tests systems that were running RAID 0 and the 7.2, or any other bios for that matter.  They also sent me a 7.33 bios   Of course, I flashed the bios and was greeted with the same problem.     But, that got me to thinking.      So, it tried disabling the Jmicron Controler and it F'N worked!!    
    In a Nut Shell, These are the BIOS setting I tried and the results:
    Jmciron:  IDE   =    No bootable Intel RAID for you.
    Jmicron:  RAID  =   No bootable Intel RAID for you.
    Jmicron:  DISABLED   =  A very bootable Intel RAID for you!   
    I guess trial and error is always good.  Again, MSI was very fast to reply.  I guess I can email this 7.33 if anyone else wants it.  I don't have anywhere to post it.

Maybe you are looking for