Posts made by Tom Elliott

[quote=“darkapec, post: 14184, member: 11250”]Are you saying I should leave [CODE] ltsp/i386/boot/vmlinuz[/CODE] completely out or does that need to be replaced by something else?[/quote]

Yes, I think Your menu option should look like this:

[FONT=Consolas]LABEL LTSP
MENU LABEL LTSP 12.04 x32
KERNEL ltsp/i386/boot/linux.c32
APPEND initrd=ltsp/i386/boot/initrd.img ro quiet splash[/FONT]
[FONT=Consolas] [/FONT]
[FONT=Consolas]If that still doesn’t work, try:[/FONT]
[FONT=Consolas]LABEL LTSP
MENU LABEL LTSP 12.04 x32
KERNEL ltsp/i386/boot/vmlinuz
APPEND initrd=ltsp/i386/boot/initrd.img ro quiet splash[/FONT]

Try changing the line 210 to:

$this->Group->addMember( $host );

Maybe this will help as the Group class appears to contain the addMember method.

If that doesn’t work, try:

$Group->addMember ($host);

I’m not running 0.32 so I can’t be a good tester for this! Sorry.

and if the variables really need to be adjusted for try:

$group = $this->Group->addMember( $host ); or
$group = $Group->addMember( $host );

Also, if The storage group is having the same type of issue try:

$storagegroup = $this->StorageGroup->addMember( $sn ); or
$storagegroup = $StorageGroup->addMember( $sn ); or
$this->StorageGroup->addMember( $sn ); or
$StorageGroup->addMember( $sn );

I know this is a lot, but it’s the best advice I can give.

As it states, addMember() is an undefined method, where is addMember defined within the FOGCore.class.php? I can’t find it and does the same issue occur For Storage group?

Line
[FONT=monospace][COLOR=#000000][RIGHT]286[/RIGHT][/COLOR][/FONT][FONT=monospace][COLOR=#000000] $storagegroup->addMember( $sn );[/COLOR][/FONT]
[FONT=monospace][COLOR=#000000][RIGHT]210[/RIGHT][/COLOR][/FONT][FONT=monospace][COLOR=#000000] $group->addMember( $host );[/COLOR][/FONT]

Both of these lines call for the same method, but the method doesn’t actually exist within FOGCore.class.php. I’ll download the tar and see if I can find the method to help with the troubleshooting of this.
[FONT=monospace][COLOR=#000000]B[/COLOR][/FONT]

If what you say is correct, do you have an uploaded image for the system you’re trying to image? If not, can you take an image that you’ve already uploaded and assign to the system you want to image and image it that way? This will let you know if it’s solely because you don’t have an actual image with the name you’re attempting to setup.

Again, I’m sorry if I’m missing anything. Not being there to help kind of hinders the troubleshooting steps I can perform and suggest.

You don’t need to extract or unzip anything. You just place it in the folder and you’re good to go. Try to boot up the system from PXE.

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.