Latest FOG 1.0.0
-
From what I can see, everything should be fine.
The gdisk -l /dev/sda would be from the Client system, which I’m assuming is what the 2nd code block is coming from?
That being said, is that message actually causing a problem or is it just a message being thrown?
-
I think this should answer your question better than I could…In short: nothing happens
[url=“/_imported_xf_attachments/0/708_Ubu_dep-2014-05-03-22-16-21.png?:”]Ubu_dep-2014-05-03-22-16-21.png[/url]
-
r1567 released.
Updated the ipxe files (undionly.kpxe, ipxe.krn, snponly.efi) to the latest from github. Added the ability to assign hosts an image from the Image page as well as “unassign” an image from a host.
-
r1569 released.
Updated the installer files so it will now create a backup of both the web and the tftp directories if they exist called: /tftpboot.prev and /var/www/{webdir}.prev. This way, it should be known to actually copy the new files without issue. Should also fix an issue with the undionly.kpxe from 1567, sorry mistakes happen.
-
Tom, do you think you could get HFS/HFS+ working? I think the info you need is all here - if you need more, just let me know
[url]http://www.fogproject.org/forum/threads/latest-fog-0-33b.6476/page-65#post-24721[/url]
-
[quote=“ArchFan, post: 26555, member: 19266”]Tom, do you think you could get HFS/HFS+ working? I think the info you need is all here - if you need more, just let me know
[url]http://www.fogproject.org/forum/threads/latest-fog-0-33b.6476/page-65#post-24721[/url][/quote]
I’ve already tried testing it all. While I could add all of the needed elements to the download scripts, I haven’t been able to figure out a good method to force MAC’s to actually Network Boot and allow image Uploads through FOG. So for right now it’s on hold. If you know how to get all of that working, please share and I’ll be more than happy to try getting it all working.
-
r1571 released.
Fixes another found issue with undionly.kpxe. I’ve fully tested and it’s back to working. Also fixes an issue with the Node Failures, where if there was a node failure found, it would keep telling you so unless you had other nodes within the same group. So when you had only one Node, the host reported the failure wouldn’t be able to image until the nfsFailures Table was cleared, even though it should really only wait for 5 minutes. This has been corrected for. I don’t know if this worked properly in 0.32, but I now know, for sure, it works in 1.0.0!
-
[quote=“Tom Elliott, post: 26556, member: 7271”]I’ve already tried testing it all. While I could add all of the needed elements to the download scripts, I haven’t been able to figure out a good method to force MAC’s to actually Network Boot and allow image Uploads through FOG. So for right now it’s on hold. If you know how to get all of that working, please share and I’ll be more than happy to try getting it all working.[/quote]
I was able to upload and download NTFS Windows 7 images to/from a Mac before using one of the methods below, but not natively. Unfortunately those are the only ways I’ve figured out as I don’t understand the cause of the issue or possess any coding skills. I don’t understand why booting from an iPXE iso from their website works, yet FOG uses iPXE and they won’t boot from that. Are you still chainloading from PXE to iPXE? That’s the only thing I can figure, but I know you had reasons for doing it the way you did.
- get the iPXE image from their site, burn to CD or copy to flash drive, then boot from the newly created iPXE media. Then FOG is found and booted from without further interaction. The con is that to boot from FOG again, you have to use the CD/Flash drive each time.
2)get a Mac install disc compatible with the machine, boot from it, and re-bless the disk using the command “bless --mount /Volumes/Macintosh\ /HD/ --setBoot --legacy --verbose”. The legacy argument seems to force the machine to use some type of legacy BIOS emulation. Reboot, then the machine will boot from FOG as many times as you’d like - I don’t know whether this will persist once the machine is reimaged or not.
- get the iPXE image from their site, burn to CD or copy to flash drive, then boot from the newly created iPXE media. Then FOG is found and booted from without further interaction. The con is that to boot from FOG again, you have to use the CD/Flash drive each time.
-
Maybe I missed some readme or something, but what changes when I select the Operating system of an image? For instance, how is Win7 different from Win8, Linux or Other?
-
Hi
I had to change the ip to the server fog is installed. I have changed in fog settings the ip in all sections and fog did not work.
So i manual change settings in config.php default.ipxe and in the table [SIZE=14px][FONT=Verdan][COLOR=#000000]nfsGroupMembers and now it is working as it shoud be.[/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Verdan][COLOR=#000000][/COLOR][/FONT][/SIZE]Thanks for the nice project and sorry for my bad english
-
[quote=“Mr.Myagy, post: 26562, member: 23824”]Maybe I missed some readme or something, but what changes when I select the Operating system of an image? For instance, how is Win7 different from Win8, Linux or Other?[/quote]
The OS Type is used during the imaging process, but really only needed between Linux and Windows. Other is for some other type of OS. Linux tells the system that it needs to backup and restore the GRUB and MBR. Windows (any) tells the system, in Single Disk Resizable, how to create the partition tables and how to restore the MBR/partition tables.
I realize this is confusion.
Windows 2000/XP Single Disk Resizable Imaging Upload resizes the partition (there’s only one usually) before uploading.
Windows 2000/XP Single Disk Resizable Imaging Download uses the present winxp.mbr file to restore the drive, and expands the drive to it’s full size.
Windows Vista Single Disk Resizable Imaging Upload resizes the ntfs partition before uploading.
Windows Vista Single Disk Resizable Imaging Download uses the present winvista.mbr file to restore the partitions on the hard-drive. Expands the Main partition to the full size.
Windows 7 Single Disk Resizable Imaging Upload resizes the ntfs partitions before uploading.
Windows 7 Single Disk Resizable Imaging Download uses the win7.mbr file to restore the partitions to the hard drive. It assumes the partitions are: 1st 100MB and 2nd Whatever size (70GB I think). Then expands the 2nd partition after imaging completes.
Linux Multipart All or Single upload runs the same as Multipart works on Windows Vista/XP/7/8 except it copies the MBR AND GRUB during the upload process. Same on in reverse for download. -
[quote=“Tom Elliott, post: 26564, member: 7271”]The OS Type is used during the imaging process, but really only needed between Linux and Windows. Other is for some other type of OS. Linux tells the system that it needs to backup and restore the GRUB and MBR. Windows (any) tells the system, in Single Disk Resizable, how to create the partition tables and how to restore the MBR/partition tables.
I realize this is confusion.
Windows 2000/XP Single Disk Resizable Imaging Upload resizes the partition (there’s only one usually) before uploading.
Windows 2000/XP Single Disk Resizable Imaging Download uses the present winxp.mbr file to restore the drive, and expands the drive to it’s full size.
Windows Vista Single Disk Resizable Imaging Upload resizes the ntfs partition before uploading.
Windows Vista Single Disk Resizable Imaging Download uses the present winvista.mbr file to restore the partitions on the hard-drive. Expands the Main partition to the full size.
Windows 7 Single Disk Resizable Imaging Upload resizes the ntfs partitions before uploading.
Windows 7 Single Disk Resizable Imaging Download uses the win7.mbr file to restore the partitions to the hard drive. It assumes the partitions are: 1st 100MB and 2nd Whatever size (70GB I think). Then expands the 2nd partition after imaging completes.
Linux Multipart All or Single upload runs the same as Multipart works on Windows Vista/XP/7/8 except it copies the MBR AND GRUB during the upload process. Same on in reverse for download.[/quote]So if I want to image a dual boot (Windows + Linux) drive, I should use Linux or Other, right?
-
Really, you should use linux and Multipart.
There’s no real support directly relating to Dual Boot systems, so if Multipart doesn’t work, try RAW.
-
r1573 released.
All the pages should now not report warning about array passed as I’m now enforcing all to be a variable. The warnings weren’t a problem, just if you printed the message to the browser it could become annoying. Updates the FOG_PIGZ_COMP slider bar to use pure jquery.
-
have you been updating the 1.0.0.tar.bz2 on your site with each new revision or will i have to get them manually?
-
I update it regularly. Though you will have to redownload every time there’s a release using the tarball method.
-
ok thanks. svn and bt sync are blocked at work so downloading from your site is the only option I have.
-
I found a bug in the recent svn version, well not a bug, but a configuration error. On Ubuntu Server 12 “[SIZE=14px][FONT=Ubuntu Mono][COLOR=#222222]pam_service_name=vsftpd” in /etc/vsftpd.conf[/COLOR][/FONT][/SIZE] has to be “[SIZE=14px][FONT=Ubuntu Mono][COLOR=#222222]pam_service_name=ftp[/COLOR][/FONT][/SIZE]” or you’ll get ftp login errors on Image upload.
-
Isn’t the Pam service being made by vsftpd? The only change that I’m aware of for the service was changing from an init.d startup to an upstart startup of the service. Maybe this is one of the differences? You could test this by, with keeping your current configuration and stopping the service with upstart methods. Then try to start it using init.d style startup. If this fails we know that the main difference is in upstart/init.d. And not the configuration directly. It’ll also give us a means to fix this issue in the installer.
-
[quote=“Tom Elliott, post: 26614, member: 7271”]Isn’t the Pam service being made by vsftpd? The only change that I’m aware of for the service was changing from an init.d startup to an upstart startup of the service. Maybe this is one of the differences? You could test this by, with keeping your current configuration and stopping the service with upstart methods. Then try to start it using init.d style startup. If this fails we know that the main difference is in upstart/init.d. And not the configuration directly. It’ll also give us a means to fix this issue in the installer.[/quote]
Upstart doesn’t seem to work.
[code]administrator@ubuntu:~$ start vsftpd
start: Rejected send message, 1 matched rules; type=“method_call”, sender=“:1.10” (uid=1000 pid=6267 comm=“start vsftpd “) interface=“com.ubuntu.Upstart0_6.Job” member=“Start” error name=”(unset)” requested_reply=“0” destination=“com.ubuntu.Upstart” (uid=0 pid=1 comm="/sbin/init ")[/code]I normally use “servcie x start/stop/restart” which works fine.
