Posts made by Alistair

This time I did not stop the task on the console.
Instead I hit CTRL C on the client.
It raced forward, created an empty image folder on the fogserver and rebooted back through pxe to Windows.

I don’t know if this is relevant.

Although I never had a problem with this Classroom-1 SFF model with regard to PXE, the BIOS always had an active “UEFI Boot Order” selection menu which was above the “Legacy Boot Order” menu. So I have now deactivated the UEFI menu and tried to take the image again. Same result.

I stopped the task on the console.
Then used CTRL C on the client which then led to the following lines:
Using hardisk sda
Saving partitiion tables … invalid partition data

I’m trying to take an image of the Classroom-1 SFF
The pxe process started ok going through a check list:
Checking OS = win 8
CPU cores = 4
etc…
until
Looking for harddisks…Done
flashing cursor

When one clicks the following at the top:

User, Host, Group, Image, Storage, SnapIn, Printer, Task Management

Could you immediately, by default, display the “List All” option.

I think most people will want to see this “List All” first.

xxxxxxxxxxxxxxx

The 2nd issue relates to a few of these pages where there are descriptions saying “Download” or “Upload”.
I have always and still do find these terms very confusing in connection with imaging. I don’t think I’m the only person on the planet who is not sure about these terms in an imaging context. But it really bugs me.

Could you change all references like download and upload to “Capture image” and “Deploy image”.
These terms are crystal clear, and would make a big difference to me.

It works!!

Used GParted to delete all partitions. (Didn’t want to bother you Tom to ask what you meant by “Boot the system as a debug task”. Chinese to me. So I took a chance on GParted.)

Disconnected network cable. (to avoid auto downloading of app store programs and other stuff after installation)
Deactivated UEFI in BIOS.
Put CD at top under “Legacy Boot Order”
Reboot
With no intervention did not boot from Win 8.1 DVD !!
Reboot
Need to press ESC to enter what I call the UEFI option page. Many UEFI options there including boot order. Weird since I have already deactivated “UEFI Boot Order” in BIOS.
Select Boot to CD - “Sata”
Win 8.1 DVD fires up
I do not do any partitioning. The disk space is unallocated. NEXT
After installation, the first page comes up asking for desktop colour and PC name. I press CTRL-Shift-F3 to enter Audit Mode.
I confirmed that the drive is now MBR !! Amazing.
Reboot to pxe fog and register client.
Reboot and with no intervention end up in Audit Mode.
Yeeeeeeeeees!!

Now, FINALLY, I can try imaging from Audit Mode.

Thanks so much Tom and JunkHacker!!

I’ll let you know how the imaging goes.

OK I’m sorry, I think I’m confusing you.
The 0x80 issue relates to the very old HP clients which I need to wipe or hopefully install Ubuntu 12 on, to give away to students or parents. I understand, I think fully, your advice about how to solve that issue. And I might do what you say there.

But much more important are the new HP Elite 8300 USDT clients that I need to get out to all the teachers. I have installed win 8.1 on one of these clients called “Teacher-1” This has the bios problem and the GPT drive.

The other new HP Elite 8300 clients are SFF and are for the classrooms and I have installed win 8.1 on one called “Classroom-1”.
(By the way I have confirmed that this Classroom-1 SFF model has an MBR drive, which is interesting since it also has a list of active UEFI boot options which have not automatically resulted in the creation of a GPT drive - curious. This should be no problem to image.)

From my understanding we are not talking about fog or imaging now.

I can in fact completely deactivate UEFI in the bios of the Teacher-1 USDT.
I just need to wipe the disk somehow and then reinstall Win 8.1 with only legacy bios options active.
That should result in the creation of an MBR drive.

I’ve done some research and now know what a GPT drive is.

Bottom line - how do I wipe the GPT drive, or how do I proceed to re-install Win 8.1? I have the latest Gparted Live boot CD if that’s a help.

“the GPT formatted disk means that you installed windows with UEFI enabled, and it has configured the hard disk as such. if you wipe the drive and re-install windows like you did before, but under Legacy, your hard disk will not be configured as GPT”

Tom, do you agree with Junkhacker? I need to take action now today.

Junkhacker, what is the quickest, easiest way to wipe the disk when I cannot do a legacy boot? Not sure about how to proceed.

[INDENT][I]it sounds to me like it would work if you wiped the drive and installed windows under legacy boot options. [/I][/INDENT]
[INDENT]Not sure how to do that or what the ramifications will be. [/INDENT]
[INDENT]Do you mean I could deactivate UEFI in the BIOS and somehow install windows again.[/INDENT]
[INDENT]But it just stops dead and says GPT disk or just shows the flashing cursor. How do I format the disk if I cannot get past the bios?[/INDENT]

Have just deactivated UEFI and done a legacy network boot on the USDT.
It worked and I registered the client with fog.
But as expected when it rebooted and timed out past the fog page, and returned control to the PC, all I see is a flashing cursor in the top left corner.

It cannot legacy boot to the disk because it is a GPT-formatted disk. Whatever that means.

I have appreciated your help but must cycle home now. It’s 9:30 PM. I’ll log in to the forum when I get home, but will not be able to test anything.

PXE timeout is now 10 seconds which gives plenty of time on the legacy network boot on the SFF, but makes no difference for the UEFI network boot on the USDT.

2 - Deactivate UEFI and then legacy pxe boot works but then after the timeout period (when fogserver is offline) it tries to boot further to the internal harddisk and gives an error message “GPT-formatted disk. Legacy boot not supported”.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Here is the the description I sent to Experts Exchange:

One group are USDT (ultra slim desktop). The other are SFF (small form factor).
All have the same latest BIOS. I have installed Win 8.1 Enterprise on one of each model in the same way. Before I installed Win 8.1 I deleted all partitions and allowed Win 8.1 to create its own 3 partitions:
300MB Recovery,
100MB EFI-system,

PXE Boot works on the SFF, but not on the USDT. I should say that the FOG imaging server which provides the PXE boot file is turned off. What I see on the 2 clients is that the SFF is clearly trying to find the PXE boot file for a while before booting further to the internal harddisk. The USDT makes no attempt to locate the PXE file. It just boots straight into the internal harddisk.

They have a slightly different BIOS Boot Order list. Here is the USDT:

UEFI Boot Sources

• Windows Boot Manager
• Atapi CD/DVD
• USB HD
• USB floppy/CD

Legacy Boot Sources
-Network Controller
-Hard drive
—Sata0
—USB Hard Drive

• USB floppy/cd

This list is identical on the SFF except for “Windows Boot Manager”
“Windows Boot Manager” is missing on the SFF which has no problem PXE-booting.

If I disable “Windows Boot Manager” on the USDT, then it attempts to PXE boot (fantastic), but then after a while it tries to boot further to the internal harddisk and gives an error message “GPT-formatted disk. Legacy boot not supported”. I have no idea what this means or how to get PXE working without getting this GPT problem.

Both BIOSes have:
SATA emulation: AHCI
Network boot: enabled
Secure Boot configuration: Legacy support:“enabled”, Secure boot:“disabled”
Remote wakeup boot source: Remote Server
NIC PXE option ROM download: PXE
Option ROM launch Policy - PXE Option ROMS: “Legacy Only” (can be UEFI Only)

Interesting comments and advice.

But to the real priority now: All the new PCs are HP Elite 8300.
Most are USDT (ultra slim) and some are SFF (Small form format).

The BIOS in the SFF model allows the use of legacy network boot.
As I had hoped, it worked almost perfectly and I registered the client.
But note that the FOG pxe option window went past in a split second.
I had to reboot to catch it again. It was VERY fast. How can I slow that down?

The USDT did not work. I have already had a long back and forth with Experts Exchange on how to get the network boot to work.
There are 2 ways.

1 - UEFI boot options: IP4 Network boot at the top of the list.
I never saw any sign of the FOG page. It waited for the pxe file for a short time and then booted to windows.

Just to explain, I want to put Ubuntu 12 on all the old HP PCs as a way of both erasing the hard drives and also making it possible for the parents in the school to have a free linux PC if they want, instead of throwing them away.

But the real priority is getting the new Windows 8.1 HP clients deployed.

I have just changed the boot order on the client with Ubuntu 12, to boot straight to the HD and Ubuntu booted as expected.
The harddisk is not corrupt.

It’s definitely the fog pxe file creating the problem.

Ubuntu 12.04.4

Thanks Junkhacker, I forgot to put in a DNS reference to fogserver.
Now PXE is working on the old HP
The registration works.
But now when the PC is rebooted, and I don’t touch anything, when it defaults past the FOG options, whilst the FOG pxe page is still visible, I see:

“Booting from SAN device 0x80”

and it freezes there. Nothing I press takes me further …

I have not set an imaging task or anything like that.

I’ll try the new HP and get back to you.

I have also tried one of the new HP clients. It does not find the pxe file either.

And could I have a definitive answer on if it is necessary with 33b to modify the bind-address= in /etc/mysql/my.cnf to my fogserver ip address? (as it was necessary with 32)

yes