System Hangs - Boot from SAN device

[dholtz-docbox]

@Tom-Elliott : After executing boot.php. Let me go take a picture of it with my phone.

-Dustin

[Tom Elliott]

You might need to try:

http://fogserverIP/fog/service/ipxe/boot.php?mac=<macofhosttryingtoboot> (Of course replacing the <macofhosttryingtoboot> with the mac of the host trying to boot)

[dholtz-docbox]

Yeah, that was what the output below was from, actually.

#!ipxe
set fog-ip 10.1.10.42
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
exit

edit: I hit ‘s’ to enter PXE before booting, otherwise it stated that chainloading failed…

-Dustin

[Tom Elliott]

@dholtz-docbox Can you check the apache error logs then? If the error is still “chainloading…s to continue” or whatever it is, likely there’s some error being displayed that’s “breaking” things right now.

[dholtz-docbox]

@Tom-Elliott : Okay. Let me purge this log and get a clean log for you.

-Dustin

[dholtz-docbox]

@Tom-Elliott : I unfortunately have no errors in my /var/log/apache2/error.log file after cleaning it and running through the process again. Would they be generated somewhere else?

-Dustin

[dholtz-docbox]

I tried playing around with other types, and none appear to work. The machine uses GRUB boot loader, so I thought I would try to boot into GRUB, but it leaves me in the GRUB interface where I appear to be able to do nothing. I am not quite sure how to configure this so that it boots into the drive directly when no tasks are present.

-Dustin

[dholtz-docbox]

I have new errors after reformatting the machine in question and starting over. To iterate, the machine has two drives, is running Ubuntu Server 14.04, and is a LVM installation. The first drive is ignored, so I am using Single Disk - Resizable, setting its Primary Disk to /dev/sdb. Last, the host is set to exit its BIOS w/ type SANBOOT.

If there is a task to capture an image, there is no issue from what I can tell. The machine boots into Partimage and begins cloning /dev/sdb without issues. However, when I go to boot into the system w/o tasks, the system NEVER boots properly.

So… the new error. Upon reformatting, I switched the BIOS exit type back to SANDISK - after exhausting the initial selections prior. This time when I boot into the system, I am prompted with the following messages…

Booting from SAN device 0x80
Boot from SAN device 0x80 failed: Exec format error (http://ipxe.org/2e852001)
Could not boot: Exec format error (http://ipxe.org/2e852001)
Could not boot: Exec format error (http://ipxe.org/2e852001)

Looking into what this error means, so far I am reading that it regards the kernel. This doesn’t make sense to me. I am not sure why the system can’t just resume its boot process, I guess; or what the impediment is - when using BIOS exit type = ‘EXIT’ - if that is the standard course of action.

-Dustin

[dholtz-docbox]

Okay… I may have solved this at the end of the day, finally.

I believe it was a sequence of a few items not matching up once I tested certain phases. In the end, I had to switch the boot priority so that the drive with the OS had priority over the data drive. I tried this earlier, but it was after already moving past SANBOOT and when looking into EXIT as an option instead. Now that I have corrected the drive and changed the boot priority, SANBOOT is functioning as intended. I will do a few more tests before I officially resolve this, so I will post back by tomorrow morning on my results - time is limited today.

-Dustin

[Wayne Workman]

So it was not a fog issue?

[Tom Elliott]

@Wayne-Workman There was a fog issue, which I fixed. The issue in fog initially was the “exit” type wasn’t being populated into the exit types.

[dholtz-docbox]

Everything here works now though - including EXIT where I need it. Thanks again.

-Dustin