@Sebastian-Roth, it’s funny. Fog deployed successfully all partitions, simply pressing ENTER after each breakpoint.

@Sebastian-Roth That’s what I did.
Follows Settings you suggested:

After usual messages, these are what I get. Here are the images:

@Sebastian-Roth Follows here:

Below is a variable dump from FOG
osid=9
osname=Windows 10
mbrfile=
type=down
storage=172.24.3.144:/images/
img=PositivoD535Win10A8
imgType=mpa
imgFormat=0
imgPartitionType=All
disks=/dev/sda /dev/sdb
hd=/dev/sda
 * Press [Enter] key to continue

[Tue Sep 11 root@fogclient /]#

Typing fdisk -l, we have:

Disk /dev/sda:119.2 GiB, 128035676160 bytes, 250069680 sectors
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/physical): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start       End   Sectors  Size Id Type
/dev/sda1           1 500118191 500118191 238.5 ee GPT


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

@Sebastian-Roth said in Deploying FOG in a raw SSD disk:

ismajordebug=1

@Sebastian-Roth, where will I add these Host Kernel Args?

Hi, guys!

I have several computers that had SSD issues, forcing assistance to change them by newer, raw disks.
Each computer has two-disks (sda-SSD 100Gb, sdb-SATA 500Gb). Only SSD was changed.

So I cannot deploy image on them due to it.

That’s the classical error message:

Image store corrupted, unable to locate MBR, no file found (MBRFileName)

Other message I got (in other moment):

Error trying to restore GPT partition tables (restorePartitionTablesAndBootLoaders)

I saw some ancient issues opened here, but nothing of them conclusive.

As workaround, I make a clear-Windows 10 formatting; after that, I can deploy successfully on them.
Do we have any updated news about it?

Hi,

We have 1.4.4 installed, and it’s running very well. UEFI boot runs fine. Just an issue to solve: After white-backgrounded FOG menu, we have a black screen with just a blinking cursor for almost 2 minutes, so we have this message:

r8169 0000:01:00.0 (unnamed net_device) (uninitialized): rtl_ocp_tx_cond == 1 (loop: 2000, delay: 50).
Starting logging: OK
Populating /dev/ using udev: udevd[2675]: error creating epoll fd: Function not implemented
done
Initailizating random number generator... done.

After that, everything works fine. FOG finishes its task normally.

Is there anything I can do reduce this lag?

@george1421, it worked! I put it under an unmanaged switch, and the computer got boot. At the first try, it got chainloading error, but at second try, it worked! Thanks!

@george1421

1. Positivo AMIEFI BIOS version 0280.X Build Date 08/24/2017
   2.1 I think firmware is up-to-date
   2.2 Two computers are in the same subnet and network works sutiable in both
   3 My FOG version is 1.4.4 SV Revision 6077

I will consider about enabling dnsmasq for ProxyDHCP.

@quazz and @george1421, I did a workaround to it. As my DHCP works with subnets, I took apart one of them to offer ipxe.efi instead of undiolny.kpxe. Now I have other issue… I have two UEFI devices, to older got a iPXE boot as I did my workaround, but the other, newer, did not! It’s telling this:

Could not boot: Connection reset (http://ipxe.org/0f0a6095)
Chainloading failed, his 's' for the iPXE shell; reboot in 10 seconds

Hi,

Did somebody got a PXE boot from a Windows 2003 DHCP by UEFI? According to Wiki nobody got it yet. I would be the first, but I’ll be happier if somebody got it before! :-)

No regarding which Vendor Classes to register (because I think W2k3 will not follow this directive) they always try to read undionly.kpxe. If I force them to read any other, link as ipxe.efi, they return a “NBP filesize is 0 Bytes” condition.

Any ideas?