The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Check cable connection. No boot device.

    Discussion in 'Alienware 18 and M18x' started by jinda, Oct 25, 2013.

  1. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    This in the picture happen to my aw18 after I disabled the raid0 partition on the stock 2x750gb hdd.

    I installed a 256gb msata as boot disk and fresh installed drivers. I formatted the disk0 raid partition (stock boot drive) and everything is ok booting to msata.

    Then I plan to remove one of the 750gb so I can put my 128gd SSD. So I disabled the raid from RST and reformatted the drives individually.

    It seems everything is working good being msata as C, 750s as D and E and optical as F.

    Then when I was about to reboot. This message appears.

    Please help.



    Sent from my SGH-T889 using Tapatalk
     

    Attached Files:

  2. BrickTop

    BrickTop Notebook Consultant

    Reputations:
    262
    Messages:
    266
    Likes Received:
    16
    Trophy Points:
    31
    What do you mean by 'fresh installed drivers' and booting ok to msata? What did you do between it booting ok from the new mSATA drive and displaying this error message?

    Check your boot device priority in the BIOS because at the moment it looks like the system can't find a bootable drive so it's falling back to trying to boot from the NIC - The cable disconnected does not mean your drives are unplugged.
     
    Mr. Fox likes this.
  3. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,354
    Likes Received:
    70,777
    Trophy Points:
    931
    If you see this message and afterwards Windows loads, your boot device order is out of sequence. That is boot from LAN and it should be last instead of first. Simply change the order in the BIOS.

    If you only see this and "No boot device found" it looks as though you may have formatted your active drive and made it no longer bootable. Try using your Windows DVD or USB thumb drive and choose the option to repair your computer. In the Windows Repair there is a utility to fix Windows installations that will not boot. It should restore your boot record and/or BCD, whatever it finds that is causing your system to no longer boot.

    Because your OS was booting from HDD RAID0 before, by breaking the RAID membership, this would make your Windows installation unbootable. When you installed Windows to mSATA it probably used the original active disk. That's why it is a good idea to disconnect any extra drives during Windows installation. It prevents that from happening by mistake. Had you broken the RAID members before installing Windows, Setup would have most likely made your mSATA the active device instead of leaving the RAID0 membership as the active device.
     
  4. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    I reinstalled windows and drivers to msata. I was already booting from it back and forth while reinstalling dell drivers.

    Problem started when I separated the 2x750gb drive from being combined as raid0 storage.

    Sent from my SGH-T889 using Tapatalk
     
  5. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    Now I'm just reinstalling windows again to the 128gb SSD because the laptop doesn't seem to boot from msata.

    Sent from my SGH-T889 using Tapatalk
     
  6. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,354
    Likes Received:
    70,777
    Trophy Points:
    931
    I explained why. Your RAID0 was the active device and installing Windows to the mSATA left it as the active device. When you broke the RAID membership that rendered you system as unbootable. This was a result of simple user error. Everything is OK with your hardware. You most likely could have repaired it. It will boot from mSATA just fine as long as the mSATA is made the active (bootable) device.
     
  7. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    Ok ill try repairing first Mr. Fox. Will report back. Thanks.

    Sent from my SGH-T889 using Tapatalk
     
  8. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    Ok I replaced one of the he'd with my ssd on disk0 and its showing BOOTMGR missing.


    Sent from my SGH-T889 using Tapatalk

    Do I have to reinstall again windows on msata?

    Sent from my SGH-T889 using Tapatalk

    Sorry Mr. Fox. I read your post but it's hard posting from the cell. The msata must still have the windows so I'll check the bios for boot sequence and see if it will boot. Tnx

    Sent from my SGH-T889 using Tapatalk
     
  9. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,354
    Likes Received:
    70,777
    Trophy Points:
    931
    No worries. I know web surfing is not very good using a phone browser. I avoid it as often as possible.

    It should still have Windows installed if you did not reformat the mSATA, but you may need to make it bootable. If the RAID0 volume was bootable before you installed Windows to mSATA it probably remained the active (boot) device and by breaking the RAID membership after installing Windows to mSATA that rendered your system unbootable. Running Windows Setup and choosing the repair option will most likely fix the problem. If it does not you will need to reinstall Windows.
     
    reborn2003 and jinda like this.
  10. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    Mr Fox!!! You are my saviour! I'm on PC browser now :)
    Repair fixed the boot.

    I'm now booting from mSata again, and have my 128GB SSD as drive D and the 750GB as drive E. I removed the other 750GB.
    Wow! That saved me from doing it all over again.

    I'm doing creating respawn backup :) Thanks. Now I can go out drink hehe!
     
    reborn2003 and Mr. Fox like this.
  11. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,354
    Likes Received:
    70,777
    Trophy Points:
    931
    Cool! I knew you could do it, buddy. Good job!
     
    reborn2003 and jinda like this.
  12. jinda

    jinda Notebook Evangelist

    Reputations:
    174
    Messages:
    571
    Likes Received:
    35
    Trophy Points:
    41
    Not without your help sir!
     
    reborn2003 likes this.