Posts made by Tom Elliott

My best guess to this issue is that your file storage information is not correct. Go to the web portal and click Storage Management->All Storage Nodes->DefaultMember. Then near the bottom of the page, make sure the password and username are correct. You’ll probably notice a rather random password in the field, which is causing the issue. You’ll likely have to setup a password for the fog user on the system as well. For example: fog and password. in the password field you just type the plain text password of the user. Then you’ll do the same under fog settings tftp username and password. Then you’ll probably have it up and running. I hope. Not being at the site makes it difficult to trouble shoot the issue though. Hopefully this helps you out.

Try multiple Partition, single disk in the image setup.

I hope this helps you. I only, yesterday, learned about this all. Good Luck!

Finished building and the kernel is up. I’m testing so if you try to download the bzImage named file you’ll get the same kernel if you try bzImageNEW

[url]http://fogproject.org/forum/threads/cant-have-partition-outside-disk.450/[/url]

Yep,

You won’t be able to do it because the drive you’re having the issue with is smaller in disk size than the systems disk that you created the image from.

Other than that I got nothing man~

Is fog service running on the system? Double check that the fog client is installed and see if that helps you out.

Do do this go to the webpage:

[url]http://<your-fog-server-ip>/fog/client[/url] and download and install the client on the machine. Then try deploying the snap-in.

If this doesn’t work, for some reason, I’m currently building a kernel based on 3.10.6. It’ll be a little bit, but the file will be called:

bzImageNEW when it’s done.

Try downloading this one and using it:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

You should be able to do it with a wget command. Maybe, to be exact, as I have self-signed certificates:

wget --no-check-certificate [URL=‘https://mastacontrola.com/fogboot/kernel/bzImage’]http://mastacontrola.com/fogboot/kernel/bzImage[/URL]

This kernel is based on 3.10.5, It’s also the kernel.core config setup. I am working to build an all kernel right now.

You’ll download this file to:

/tftpboot/fog/kernel/

So full steps would be:

Open terminal on fog server as root:

type:

cd /tftpboot/fog/kernel

mv bzImage bzImage.orig

then wget --no-check-certificate [URL=‘https://mastacontrola.com/fogboot/kernel/bzImage’]http://mastacontrola.com/fogboot/kernel/bzImage[/URL]

What kernel are you using?

Try updating to a more recent one and see if this helps you out. If worse comes to worse, I can probably build one that has all possible options available, though that would be a kernel around 35 MB’s, or possible larger.

I don’t know much about sysprep, other than it’s a method of putting a windows system, very nearly, back into Out Of Box status. After a sysprep is completed, it basically is as if you just started the system for the first time. There are different methods of sysprep, but most usually will, also, include the generalize option with basically removes all driver associations of the particular system so you could place that image onto any machine without issue.

I don’t know how many times you can use it from the current base image setup. Then again, when I recreate an image, I start completely from scratch so I’ve never had to worry about a number limit.

This is really odd, it looks like you uploaded two images at the same time, or had the image setup for Multiple Partition Image, All Disks and it just so happened that both Disks had, very nearly, the same information. Maybe check this setting out as well. Do you have, more or less, the same OS on two disks in the same system that you can switch in the BIOS?

I’ve got a busy week ahead of me at work, but I’ll try to look more into this this following weeked. I’ll add the components to my init.gz fog script to rewrite the mbr after the upload and after the reload of sys.img.000 and rec.img.000 and see if this works.

No problem man, it’s what we’re all here to do. Learn, and make life easier.

In dealing, today even, with the dreaded problem with no configuration issues, I’ve also seen this issue occur when a network has been affected by a broadcast storm. Essentially what ends up happening is the network is being flooded by another switch, kind of like a loopback into itself. (I know that sounds funny) However, the fix for this particular issue was to reset all mini-switches within the path of the network with a simple power down, power up. Then, as needed, reset the Layer 3 Switches if they became too bogged down by the broadcast error messages.

I hope this helps. The particular issue I saw with one of my systems is that the cable has a break in it somewhere. It had enough signal to boot the kernel and init.gz, but when fog tries to reset the device after boot up, the signal is lost and nothing can be found. Then we got the hdparm issue. Connected the system to a good connection from another area and all worked fine. It wasn’t the system, but the network. Check that this other system isn’t having many Multicast devices attached (iPads, Smartphones, Apple TV, etc.) Reset the switches, and reboot any miniswitches. You may narrow the problem down further this way. If your setup worked elsewhere, chances are it isn’t a configuration issue and I was just trying to help. I’m sorry if I lead you in the wrong direction, but hope that this helps you out.

the / marks are slashes. Many times, I’ve seen the pxe default file looking for web:

<IPADDRESS>/fog rather than <IPADDRESS>/fog/ <- (This is the trailing slash as it trails at the end.)

The default file is generally located in:

/tftpboot/pxelinux.cfg/

the file is just called default.

You can edit it however you want, but just make sure the slash is in the file and in the fog settings.

[quote=“Tom Elliott, post: 14178, member: 7271”]darkapec,

What type of pxe setup are you using? gpxelinux or pxelinux. In either case, your file should not be setup, as far as I can tell, with a prefix of: tftp:/ . Even if this is an okay header portion, try tftp://. If that isn’t working, and you’re using gpxelinux, make sure your file is accessible via a webserver. Then change the tftp:/ parts to http://

One other think that’s standing out, is the kernel line.
[FONT=Consolas]KERNEL linux.c32[/FONT]

[FONT=Consolas]Is this actually your kernel? It doesn’t look like it to me. Usually the kernel is vmlinuz or bzImage[/FONT]
Try using:
[FONT=Consolas]LABEL Ubuntu LTSP 12.04[/FONT]
[FONT=Consolas] MENU LABEL LTSP - Ubuntu Desktop[/FONT]
[FONT=Consolas] KERNEL tftp:/192.168.1.145/opt/ltsp/i386/boot/vmlinuz[/FONT]
[FONT=Consolas] append initrd=tftp:/192.168.1.145/opt/ltsp/images/i386.img ro quiet splash[/FONT]
If this doesn’t work try:
[FONT=Consolas]LABEL Ubuntu LTSP 12.04[/FONT]
[FONT=Consolas] MENU LABEL LTSP - Ubuntu Desktop[/FONT]
[FONT=Consolas] KERNEL [url]http://192.168.1.145/opt/ltsp/i386/boot/vmlinuz[/url][/FONT]
[FONT=Consolas] append initrd=[url]http://192.168.1.145/opt/ltsp/images/i386.img[/url] ro quiet splash[/FONT][/quote]

Also, just as I’m reading a little bit more, if this chainload is supposed to be happening as such maybe the lines should read:

[FONT=Consolas]LABEL Ubuntu LTSP 12.04[/FONT]
[FONT=Consolas]MENU LABEL LTSP - Ubuntu Desktop[/FONT]
[FONT=Consolas]KERNEL linux.c32[/FONT]
[FONT=Consolas]append initrd=tftp:/192.168.1.145/opt/ltsp/images/i386.img ro quiet splash[/FONT]

[FONT=Consolas]Remember, that you’ve already loaded a kernel, so loading vmlinuz shouldn’t work to my knowledge[/FONT]

One of the things I’ve learned with building a custom kernel is to Read the friendly Wiki page or (RTFW) as other so like to display.

If you’re building the kernel on a 64 bit system, make sure your make commands are:

make ARCH=i386 <command>

So when you’re doing the menuconfig do:

make ARCH=i386 menuconfig

Then make your changes and save the new config.

Then when you create the bzImage file do:

make ARCH=i386 bzImage.

I would almost recommend making this an actual part of the WIKI rather than just a note, as it wouldn’t hurt anything to do this from any platform whether i386 or 64 bit.

Thank you,

On the localboot line try:

localboot 0x80

Usually it is set to:

localboot 0 which doesn’t seem to work with ahci and gpxelinux.

darkapec,

What type of pxe setup are you using? gpxelinux or pxelinux. In either case, your file should not be setup, as far as I can tell, with a prefix of: tftp:/ . Even if this is an okay header portion, try tftp://. If that isn’t working, and you’re using gpxelinux, make sure your file is accessible via a webserver. Then change the tftp:/ parts to http://

One other think that’s standing out, is the kernel line.
[FONT=Consolas]KERNEL linux.c32[/FONT]
[FONT=Consolas] [/FONT]
[FONT=Consolas]Is this actually your kernel? It doesn’t look like it to me. Usually the kernel is vmlinuz or bzImage[/FONT]
Try using:
[FONT=Consolas]LABEL Ubuntu LTSP 12.04[/FONT]
[FONT=Consolas] MENU LABEL LTSP - Ubuntu Desktop[/FONT]
[FONT=Consolas] KERNEL tftp:/192.168.1.145/opt/ltsp/i386/boot/vmlinuz[/FONT]
[FONT=Consolas] append initrd=tftp:/192.168.1.145/opt/ltsp/images/i386.img ro quiet splash[/FONT]
If this doesn’t work try:
[FONT=Consolas]LABEL Ubuntu LTSP 12.04[/FONT]
[FONT=Consolas] MENU LABEL LTSP - Ubuntu Desktop[/FONT]
[FONT=Consolas] KERNEL [url]http://192.168.1.145/opt/ltsp/i386/boot/vmlinuz[/url][/FONT]
[FONT=Consolas] append initrd=[url]http://192.168.1.145/opt/ltsp/images/i386.img[/url] ro quiet splash[/FONT]