Posts made by cadyfish

Timo,

If you are using these computers on a domain you really NEED to use the sysprep process otherwise you will run into issues with Windows 7… XP was a different story due to you could use newsid.

It sounds like the issue is that once imaged the computer doesn’t know what drive is the boot device. In the commands below replace the drive letter with the OS drive, run it before uploading
[CODE]bcdedit /set {bootmgr} device boot {drive letter}
bcdedit /set {default} device boot {drive letter}
bcdedit /set {default} osdevice boot {drive letter}
[/CODE]

You also didn’t specify I assume you are using a sysprep process?

What is the output of
[CODE]ls -la /images/vistatest4[/CODE]

Have you tried a different OS yet? Maybe vista issue was not resolved I am not sure I have not used it with fog.

Each line needs to be entered together
[QUOTE]
[CODE]sudo apt-get install subversion
svn checkout http://svn.code.sf.net/p/freeghost/code/trunk freeghost-code
cd freeghost-code/bin
sudo ./installfog.sh[/CODE]
[/QUOTE]

Otherwise go to [url]http://sourceforge.net/p/freeghost/code/HEAD/tree/[/url] and click on Download Snapshot and navigate to the bin folder and run the last command

Piracy,

Most of the web changes I listed were personal preference, but here is a little more detail:

[U]GroupManagementPage & HostManagementPage[/U]
I prefer the upload and or deploy and mutlicast to not be right next to each other so I moved the icons around. I also removed the edit button since you can click on the host and it takes you to the same location, along with modifying the download header to Unicast (did the same thing in the TaskManagementPage. With making some of those changes I changed the alignment of the buttons make it line up better

[U]ImageManagementPage[/U]
I added the Image ID back to this page I thought it was useful in the older versions of fog if you do a fare share of full register and deploy directly from a computer since it asks you for a image number. Granted you can find it with “?” but if you have a large list of images or a small screen it might just be easier to know what the number is. I realize this number is auto generated with mySQl and doesn’t really mean much and that is probably why it was removed.

I removed the edit button off of this screen along with Storage group due to I didn’t use it. Changing Upload to Upload date was also a personal preference.

I also removed the comment when hovering over Image name and changed it to be on the Image Id to show the description on the image instead of when it was deployed and etc. since it was already on this page.

It looks like you might have missed a couple of things when you changed it to work with 1+ from .32

[U][B]Update schema[/B][/U]
[url]http://localhost/fog/commons/schemaupdater/index.php?redir=1[/url]

[U][B]Add the server IP address[/B][/U]
dhcp-boot=undionly.kpxe,{server IP}

[U][B]Comment out the following lines[/B][/U]
#dhcp-option=17,/images
#dhcp-option=vendor;PXEClient,6,2b
#pxe-service=X86PC, “Boot from local hard disk”, 0

[U][B]Save your file and restart your dnsmasq service with the following command:[/B][/U]
sudo service dnsmasq restart

[U][B]Make a symlink for the undionly.kpxe file so dnsmasq can find it.[/B][/U]
cd /tftpboot
sudo ln -s undionly.kpxe undionly.0

See this for export fix
[url]http://fogproject.org/forum/threads/mounting-file-system-error.10979/[/url]

Or you could install the fog latest version from code according to Tom this has been resolved:

sudo apt-get install subversion
svn checkout [url]http://svn.code.sf.net/p/freeghost/code/trunk[/url] freeghost-code
cd freeghost-code/bin
sudo ./installfog.sh

I have been using one with version 2196 and a couple of others with 1.2

I kind of figured regarding the management pages I didn’t think it would hurt to ask.

I like your selection box idea better than the coded option it leaves more universal. Going along that line would it possible to add in iso folder location for the boot menu selection? So say someone wants to add dell diagnostics for example just through it in that folder and fly away:). I realize you can modify the advanced boot menu I think it would just simply the process for others to add items that they may want to utilize.

Thank you,

[quote=“Keifer, post: 35350, member: 25622”]Here is the results.

foguser@fogserver:/$ ls -la /images/
total 20
drwxrwxrwx 5 root root 4096 Aug 13 20:50 .
drwxr-xr-x 26 root root 4096 Aug 9 16:37 …
drwxrwxrwx 2 root root 4096 Aug 13 20:50 dev
-rwxrwxrwx 1 root root 0 Aug 9 16:18 .mntcheck
drwxrwxrwx 2 root root 4096 Aug 9 16:18 postdownloadscripts
drwxrwxrwx 2 root root 4096 Aug 13 20:28 vistatest2

foguser@fogserver:/images$ ls -la vistatest2
total 2718156
drwxrwxrwx 2 root root 4096 Aug 13 20:28 .
drwxrwxrwx 5 root root 4096 Aug 13 20:50 …
-rwxrwxrwx 1 root root 2783365986 Aug 13 20:43 0800276c12c4.000
-rwxrwxrwx 1 root root 1 Aug 13 20:28 d1.fixed_size_partitions
-rwxrwxrwx 1 root root 15 Aug 13 20:28 d1.original.fstypes
-rwxrwxrwx 1 root root 259 Aug 13 20:28 d1.original.partitions
-rwxrwxrwx 1 root root 0 Aug 13 20:28 d1.original.swapuuids
[EMAIL]foguser@fogserver:/images$[/EMAIL][/quote]

Based on the .swapuuids it looks like your vistatest2 image operating system is set to linux instead of Windows Vista. Go into image management and change this and then re-upload. For a windows image you should see a d1.mbr file

Might want to check partions with gparted (boot disc) and check to see if you have any extra partions left from resizing. I would also do a checkdisk if not already done.

When you said
[quote=“neodawg, post: 35342, member: 87”]I have some 740s that wont deploy using a single disk image of XP however some other ones in the lab deploy just fine.
[/quote]
Are they the same model and image?
Also are they the same hardware (including hdd size/manufacturer) & bios wise?
Did you do anything different with them?

[quote=“Junkhacker, post: 35308, member: 21583”]the settings in [SIZE=2]/lib/fog/Config.class.php are not [/SIZE]relevant[SIZE=2] here, as the storage management section of that data has been moved to the database. the relevant settings to this are now found on the storage management page[/SIZE]

[SIZE=2]there should be no need to re-register the host either[/SIZE]

[SIZE=2]but i too would like to see the output of [/SIZE]ls -la /images/{image your trying to deploy}/
[SIZE=2]and[/SIZE]
ls -la /images/[/quote]

Sorry for the miss information… Thank you for correcting me

Try post 6 and later in [url]http://fogproject.org/forum/threads/stuck-on-dev-sda.11105/[/url]

[U][B]Regarding 1.1.2:[/B][/U]
I would suggest upgrading 1.1.2 to 1.2 and then making sure your DHCP is pointed towards undionly.kpxe for that server. With the 6400 model I noticed undionly.kkpxe doesn’t work. The default kernel should work in 1.2 if not go to fog settings>update kernel>unpublished kernels and install the 3.16*

[quote=“pmonstad, post: 35300, member: 17422”]Hm, I need some more info here as I really dont know what you suggest I have never chosen SANboot, and where do I turn it off? I have never run into this problem on hundreds of computers. Only these two R60e from Lenovo.[/quote]
With the current version of fog by default it uses SANboot as an exit type to get out of the fog menu. To change it do the following:
[LIST=1]
[]Navigate to the FOG configuration page (gear symbol)
[]Click on PXE Menu settings
[]Change the exit type to “grub”
[]Save settings
[/LIST]

Could you open up terminal and reply back with what shows up after the following to commands:
ls -la /images/{image your trying to deploy/

Also verify that the storage management page has the same settings for image location as in LN87 in /lib/fog/Config.class.php.

If you changed these settings after a host was already registered I would also remove it and re-add

[quote=“Grayda, post: 35292, member: 10496”]I tried going from 0.32 to 1.2.0, but when I went to update the schema, I got a LOT of database errors. So I tried updating to 1.0 then 1.2, but same deal, so in the end I had to go to 1.1.2 and go to 1.2. No biggie, but a bit frustrating. I’m thankful VMware has their snapshot feature! [/quote]

[COLOR=#000000]Not sure why but this issues occurs due the SQL pasword not being the same in (/lib/fog/Config.class.php) as in the pre-existing MySQL database. One way to correct it is to change in that php file and then reload the update schema.[/COLOR]

[quote=“Junkhacker, post: 35126, member: 21583”]does this model of computer have legacy boot support (ability to disable uefi)?[/quote]
It doesn’t Unfortunately. You have to turn off a setting in BIOS to get it load tftp at all though.
[LIST]
[]Get in to Bios
[/LIST]
[LIST=1]
[][LIST=1]
[]Turn off the surface
[]Hold the power up key
[]Press and release the power button on your Surface, then release the volume-up button.
The UEFI menu will display within a few seconds.
[/LIST]
[/LIST]
Alternative way
[LIST=1]
[][LIST=1]
[]While the surface is on hold the shift key and then hit the power off
[]Go to troubleshooting
[]Then their is an option to boot to UEFI settings
[/LIST]
[/LIST]
[LIST]
[]Turn off Secure Boot Control - otherwise due to security it wont boot at least with the Surface Pro 1
[/LIST]
I still had issues after doing this so I also ended up changing tftpboot service to use .efi
[LIST=1]
[]Download from code [url]http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/[/url]
[]Copy [URL=‘http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/ipxe.efi’]ipxe.efi[/URL] to /tftpboot and point your DHCP towards it
[*]run the following command: restart tftpd-hpa
[/LIST]
After doing this the image successfully uploaded. Keep in mind ipxe.efi will not work with hardware that doesn’t support UEFI so you would have to manually it change back and forth. Not ideal but it works

Also want to note there are two versions of the Microsoft adapter one is 10/100 the other is a Gigabit adapter the 10/100 wont work at all to boot into fog.

Here are a couple things to check:

-Are the images stored or mounted under /images?
-Verify on the website Image Management tab the image location is exactly the same as the image path on the server
-Run the following commands if not done so already:
sudo chown -R fog /images
sudo chmod -R 755 /images
sudo chmod -R 777 /images/dev

How were the images uploaded via 1.20 or .32 or earlier?