I’ve had a couple of odd situations of late that seem to be be MBR-related. The first turned out to be missing mbr files from the fog server (why they disappeared I have no idea), but the second is slightly odder and leads me to the question:

Why does Fog write its own OS-specific MBR rather than use the one that is on the target that I’m uploading from?

I ask as since I used bcdedit to make changes to the default boot behavior to suppress the recover option my images have started failing to load with either file system errors or allegedly corrupt system files.

Second question: If I need to make changes to the MBR of my system, do I need to make changes to the one stored on the Fog server?

I’m using Fog 0.32.

Thanks in advance for any advice.

Hi,

A very odd thing has started happening, whenever we create a new task and a config file is written out to /tftpboot/pxelinux.cfg it contains corruption in this form on one line:

kernel lsfog/kernel/bzImage

It should read:

kernel fog/kernel/bzimage

I have put a temporary fix in place with a cron job that monitors the directory for new files and edits them to remove the rogue ‘ls’.

Could somebody please point me in the direction of the script that writes that file out so I can try and work out what has happened? The fact that the text is ‘ls’ makes me think that some command is failing and causing a variable to be poorly formed, but then again maybe it’s not that.

Thanks in advance,

Jon