Default Boot Device Missing or Boot Failed - Windows 10
-
I can easily create and upload an image. After reboot the following error message appears in UEFI mode: "default boot device missing or boot failed ".
In legacy mode a black screen is displayed with the cursor blinking in the upper left corner. However, no error message is displayed.The following settings are active:
- Secure & Fast Boot is deactivated
- PXE and the network card is activated.
This problem occurs with the following devices:
- Acer Aspire E-15
- ASUS computer (I7-7700, 3.6 GHz, 16 GB)
I have created a separate image for both computers which both do not work. In the Host Settings I tried all “Host Bios Exit Type” settings but without success.
I am new to FOG. I urgently need support to solve this problem
-
This can be caused but a number of things depending on what is actually throwing the error.
-
If you change the boot order in the firmware to hard drive first does it boot?
-
Did you sysprep the image before you captured it with FOG?
-
Are you capturing and deploying to the same model of computer?
-
Is both the source and target computers the same firmware type (uefi -> uefi or bios -> bios)
-
What version of FOG are you using?
-
-
- Yes I change the boot order but it doesn’t work.
- I installed basic programms like Office and Adobe and after that i captue it. With Clonezilla it does work so.
- Yes I used the same model of computer.
- Yes they had the same firmware.
- I use 1.5.9-RC2
Thx for help.
-
@El_Pagrxn27 said in Default Boot Device Missing or Boot Failed - Windows 10:
- Yes I change the boot order but it doesn’t work.
ok if you change the boot order so that the hard drive is first and you still have the problem then its not related exactly to fog. Now understand it still may be related to the cloning process but its not what I would thinking with the exit manager from FOG [refind] causing a problem.
- I installed basic programms like Office and Adobe and after that i captue it. With Clonezilla it does work so.
This isn’t exactly what I asked, did you run sysprep or just shutdown the computer, pxe boot and then capture with FOG?
- Yes I used the same model of computer.
OK under these circumstances if you are going from same model computer to same model of computer you don’t need to “specifically” sysprep the image.
- Yes they had the same firmware.
Ok that is good because you can only clone source -> target if the firmware type is exactly the same.
So when you go into the bios(firmware) and you go to the boot manager’s page (whatever its called in your firmware), uefi firmware will only let you see disks that have a valid uefi boot partition on them to select as a bootable disk. Does your uefi firmware see the hard drive as a valid bootable device?
When the system boots, do you see the windows logo and the rolling marbles? Or does it go to the black screen right away?
Lastly did you remove any bitlocker encrypted partitions before capturing with FOG? I believe the fog program was adjusted to warn you if you are trying to backup an encrypted drive but it will still back it up. If bitlocker is enabled then for sure it won’t boot on a second computer.
-
@george1421 said in Default Boot Device Missing or Boot Failed - Windows 10:
This isn’t exactly what I asked, did you run sysprep or just shutdown the computer, pxe boot and then capture with FOG?
I just shutdown, pxe boot and caputer it. I doesn’t run the sysprep
- Yes I used the same model of computer.
OK under these circumstances if you are going from same model computer to same model of computer you don’t need to “specifically” sysprep the image.
ok fine.
- Yes they had the same firmware.
So when you go into the bios(firmware) and you go to the boot manager’s page (whatever its called in your firmware), uefi firmware will only let you see disks that have a valid uefi boot partition on them to select as a bootable disk. Does your uefi firmware see the hard drive as a valid bootable device?
I can see the hard drives in the uefi mode
When the system boots, do you see the windows logo and the rolling marbles? Or does it go to the black screen right away?
No, I don’t see the Windows Logo. It goes straight to the black screen
Lastly did you remove any bitlocker encrypted partitions before capturing with FOG? I believe the fog program was adjusted to warn you if you are trying to backup an encrypted drive but it will still back it up. If bitlocker is enabled then for sure it won’t boot on a second computer.
Bitlocker isn’t enabled.
-
When you captured the image you used single disk resizable?
The target drive is the same size or larger than the source drive?
The target drive is the same media type as the destination drive, i.e. both sata or both nvme drives?
The source computer still boots, right?
This is an interesting problem, because it should be working.
We may need to try to debug the target computer. If you schedule another deploy task, but before you hit the deploy task button, tick the checkbox that says debug. Then pxe boot the target computer. You will see several screens of text that you need to clear with the enter key, eventually you will be dropped to a linux command prompt. At that linux command prompt key in
lsblktake a picture of it and upload the picture to this thread. If the picture won’t upload then upload to a file share site and post the link here. I want to see what the disk structure looks like on the target drive. -
I used Multiple Disk a
-
@El_Pagrxn27 Whg to you use image type Multiple Disks??
I didn’t see this mentioned anywhere before.
-
@Sebastian-Roth @george1421 I used multiple partition - all disks because I wanted to copy all Partitions.
-
@El_Pagrxn27 Just to be clear your computer has multiple disks installed or you just picked that option just in case there are multiple disks?
-
@george1421 Yes, there are 2 Diskss installed. One SSD for the OS and one HDD.
-
@george1421
lsblkon target computer: https://imgur.com/a/A9QC2r4 -
@El_Pagrxn27 Well your image is strange. I see 2 disks in the picture. One is physically larger (about 1TB) and the other is ~256GB. That is OK but what is strange is their partition tables are exactly the same. So the 1TB drive is only configured as having a 256GB size.
Also if we guess the 1TB drive is the HDD and hte 256GB drive is the SSD, they have their positions switched. /dev/sda is the 1TB drive and /dev/sdb is the 256GB drive. I can understand why it didn’t boot.
So the question I have is did you run the lsblk command on the target computer or the source computer?I see the answer, so can you run the same command on the source computer? Does the source computer report the disks in this order? -
@george1421 The SSD and HDD aren’t switched, or at least they are the same on the source computer. The source computer only has the SSD structured in different partitions, like it should be while the HDD isn’t partitioned. I now found a way to boot the image. after Capturing the image in “Multiple Partition Image - All Disks” i changed it to “Multiple Partition Image - Single Disk” bevore deploying it. The image is now bootable, but it deployed it onto the HDD. any way to force it to deploy it onto the SSD?
-
@El_Pagrxn27 Well when I say they are switched, inside FOS linux they are being reported as switched. According to FOS linux the first hard drive is the 1TB drive connected to /dev/sda and the SSD being connected to /dev/sdb. So the question is, is the linux kernel confused and randomly switching the order or if you look physically at the drive connection is the 1TB drive connected to the sata connector 0 and the SSD connected to sata connector 1?
The other question is on the source computer do they appear “switched” as they are on the target computer?
-
@george1421 The disks are indeed switched on the source computer, the same as on the target computer. I checked the discs on the target system physically, the SSD is connected to SATA 6 and the HDD is connected to SATA 5.
-
@El_Pagrxn27 said in Default Boot Device Missing or Boot Failed - Windows 10:
the SSD is connected to SATA 6 and the HDD is connected to SATA 5.
This is why linux is seeing them backwards. The lowest sata number will be /dev/sda.
So this means that all of these computers are setup this way?
What I still find strange if they are all setup that way is the target HDD has the same partition sizes as the SSD. Does lsblk show the same results on the source disk? I want to make sure something else isn’t going on here. I might understand about not not bootable part as long as the source and target disks are structured exactly alike.
-
@El_Pagrxn27 said in Default Boot Device Missing or Boot Failed - Windows 10:
The source computer only has the SSD structured in different partitions, like it should be while the HDD isn’t partitioned.
What i meant by that is the HDD is one single partition, with the correct size of 1TB. Like the target system, the HDD is /dev/sda. The SSD has 4 Partitions, where the image was created and windows was manually installed first. All the computers are set up like that.
Could this have something to do with the “Multiple partition image - all disks” option, so Fog images both of the drives? -
@El_Pagrxn27 I guess I’m doing a terrible job explaining what I see.
If we refer to the picture you provided. You see /dev/sda is exactly as you say the 1TB hard drive connected to sata5. Also you see that /dev/sdb is exactly as you say the 256GB drive. Now what I’m saying is the partition layout for both the 256GB and 1TB drive are exactly the same. So something happened here. I would expect /dev/sda3 to be ~900GB in size, not 256GB unless this is how its configured on the source computer. I would say the layout that is on /dev/sdb is a typical windows boot image format.
I’m suspecting some how the image for disk /dev/sdb was overwritten onto /dev/sda. This is why the target computer will not boot.
While I understand this is how your fleet of computers are currently setup, the configuration is a bit uncommon. The more common approach is that the boot/OS disk to be on /dev/sda (i.e. lowest sata port number) and the storage disk to be on some sata port number higher than /dev/sda (5 in this case). Now understand that it is possible to have the OS disk setup like you have it and work, but FOG may be making an assumption that you have a default design. I don’t know this bit yet. Right now I’m having a hard time understanding why both disks have exactly the same partition layout.
