Raid0 booted into AHCI. Now No bootable found


  1. Posts : 2
    Windows 10 x64
       #1

    Raid0 booted into AHCI. Now No bootable found


    Hello, :) nice forum, i'm glad to be here. Thanks and keep up the good work.

    This is raid0 - 101. Day one stuff... still no fix with windows 10? QQ.

    Raid0 booted into AHCI and now "no OS found".

    Don't need my hand held through this process, unless you have command prompt fix, just a quick answer or even a solution PLEASE.

    At this point, feel it's a windows error/repair issue, please direct me to correct Forum location if ADMIN or anyone feels i'm in the wrong. Will personally delete this thread and move topic to the correct URL as directed.

    --------------------------------------------------------------------------------------------------------------------------------

    -History- I've built several pc's and have IT background would never let OS raid0 boot into AHCI.

    -5am foggy eyed........ IDtenT..... I know better than to use a 3ed party driver updater! Garbage software off FileHippo, "Driver Talent" Garbage-ware caused a silent bios update/crash. Used the software on an HP elite book and it fixed the SD card reader.... So, i tried to use "driver talent" one of my Beasts for ONLY one USB peripheral "driver repair" - unable to find directly from the manufacturer.

    After Driver Talent's "required restart" PC wouldn't even boot to bios. Nice pretty interface, lol some "driver talent" indeed!!!
    --------------------------------------------------------------------------------------------------------------------------------
    Onboard Dr.Debugger reported 0x32 ["CPU post-memory initialization is start"]. I freaked, thinking 4.5ghz OC finally killed CPU.... disconnected everything from usb and PCI slots. Nothing, 0x32.

    Thc OC was stable for years, watercooled in Obsidian 800D case, never hit 70c. [90c Tj max].

    CMOS-reset did nothing.

    Unplugged 1200w powersupply and removed motherboard CMOS "watch battery" and went to bed.

    Next day- Nothing, 0-32 still, but it couldn't be a dead CPU.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Installed a new BIOS chip. Instant flashed most recent BIOS. [Interestingly, i wasn't able to instant flash this in del/F2 UEFI. But only with f6 instant flash. I flashed each bios via f6 in sequence. 1.0 to, 1.1 to, 1.5. to, 1.7 to, whatever next to, ect., to newest release 2.3]

    Then booted into newest released BIOS. The bios looks good. UEFI looks good.:)

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Set UEFI "storage config" to RAID and exit+ save changes. [crossing fingers]

    Intel (Ctrl-I) sata chipset still has everything correct, names, drives, sizes. :) With one exception- interesting the only visable change is both raids now are now shown as "bootable". The two RAIDs on the intel chipset- 1) raid0 OS and 2) raid5 storage (.mkv ONLY). Am confused about how the .mkv files on raid5 became "bootable".

    That said.... i continued.---------------------------------------------------------------------------------------------------------

    Hitting del/f2 into UEFI.

    The "boot options" show 1)- the OS raid0 as "Intel 840 pro" [which is not the given name in CTRL-I] and 2)- a UEFI drive... Interestingly, the BBS show "Intel 840 pro" [not the CTRL-I name] and but the RAID5 has the correct name.

    The OS raid0 is 2 Samsung 840pro. [not intel].

    **************************************************************************************************** *************************

    Put Windows 10 recovery on a USB and began a "start-up" recovery. :) Results were looking good, hamster wheels turned and eventually it asked me to select user and enter password. {can repeat this process by disconnecting power and Cmos battery out + time [doing exactly that, again, now]}

    Cannot reset or any of the options for non-advanced users. The "refresh PC" gives me a restart error like 80004000 or something close.

    Have a full image (5-6days old) backed up. Although it wont' find it in "system restore" (duh), and Re-image option claims the "drive is locked" or something of that nature.

    All other options have failed, thus far.

    If i left anything out please ask, can include images.

    Thank you in advance for any advanced advice.
      My Computer


  2. Posts : 2
    Windows 10 x64
    Thread Starter
       #2

    Bump
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:13.
Find Us




Windows 10 Forums