Latest FOG 0.33b
-
r1191 released to fix header row alignment issues. Adds a few other changes as well.
-
r1192 released.
Adds the r8106e drivers to the kernel.
Adds checking if the drive is gpt or mbr on a very simplistic method. It uses gdisk -l /dev/sda ($hd for dynamics) and greps for the GPT areas. If gpt is not present, it does mbr backup methods, if it’s anything else (present usually) it backups up the GUID Partitioning tables (GPT). This is only needed during the upload of the image for mps or mpa (multi-part single/multi-part all)
On the download, it checks the size of the mbr file created (yes on upload it still uses the .mbr identifier for simplicity sake). If the size is 512, it’s not linux but loads as mbr methods do. if it’s 32256, it is linux mbr and loads as such. If it’s anything else, it assumes it’s GPT as I don’t imagine GPT gets any larger or smaller anyway.
Like I said, very simplistic but should do what we’ve kind of been stuck on for a little bit.
-
Tom,
Are there still problems with deplopying a windows 7 image with image type “Multiple Partition Image - Single Disk”?
I deployed a uploaded window 7 image with 2 partitons (system reserved and system partition) to a pc with a clean hard disk. Partclone exits at the first time with only the message “error exit”, after I started the task again, partlcone succesfully deployed the image to the pc.I used revision 1192.
Ty,
Lukas -
Does it specify the error at all?
-
r1193 released.
Should properly create GPT tables, but I don’t know as I don’t have GPT disks to test, so please let me know.
Fixed a time sending issue on autologout service.
-
[quote=“Tom Elliott, post: 22519, member: 7271”]Does it specify the error at all?[/quote]
Partclone shows only “error exit”, but directly after partclone exits, I saw that “error: /dev/sda1 no such file or directory”. I booted then into debug mode with fog and executed “fdisk -l”. It lists me /dev/sda1 with system HPFS/NTFS/exFat.
Looks like that the partitions are not there at the moment, where partlcone tries to deploy the image.Edit:
Forgot to mention that at upload, fog shows me something with “unary operator expected” in file fog.upload at line 258, 262, 266. -
I’m saw the error, but the MBR data is correct and get’s written as we all of a sudden see /dev/sda2.
Are you sure it said “error: /dev/sda1 no such file or directory” and not “error: /dev/sda2 no such file or directory”?
-
I tested it again and maked a screenshoot and there I see /dev/sda1. How I wrote in my post number 830, something goes wrong at the first time, but after starting the deploy again. Partclone and fog then works fine.
-
Alright,
Found the issue. Needed to wipe out the MBR/GPT structures which is now implemented.
r1194 released should correct this issue.Thank you,
-
[quote=“Tom Elliott, post: 22525, member: 7271”]Alright,
Found the issue. Needed to wipe out the MBR/GPT structures which is now implemented.
r1194 released should correct this issue.Thank you,[/quote]
I updated to new revision, same problem. After starting the task again, all works fine then.
-
[quote=“Albatros, post: 22521, member: 16710”]Edit:
Forgot to mention that at upload, fog shows me something with “unary operator expected” in file fog.upload at line 258, 262, 266.[/quote]I found this issue and already fixed it. It’s because of the variable call in the script. Sorry I forgot to wrap them in double quotes.
r1195 released should fix that issue.
-
[quote=“Albatros, post: 22526, member: 16710”]I updated to new revision, same problem. After starting the task again, all works fine then.[/quote]
Did you restart the system after updating. If not, it’s still using the old/bad init.gz
-
I updated to revision 1195,restarted the system and overwrote the init.gz with that from the subversion directory.
Sorry same problem. -
Can you do me a favor Albatros,
I’ve seen on a couple instances where the installfog.sh doesn’t update all the files appropriately, for some reason.
Can you try directly copying my init.gz to your /tftpboot/fog/images folder, reboot the client and try again?
-
I deleted the init.gz from /tftpboot/fog/images/ directory and placed there your init.gz. Same problem
.
I am now away, see you later -
If you get a chance, can you try re-uploading the image, then deploy?
I’m thinking the MBR checking got screwed up somewhere and this is why it’d doing a double deploy issue. I’m not seeing the issue anymore.
-
Anyone Here handy with debugging scripts?
-
Hey tom how you been. I can take a look and ask around and see if I can find any issues with it
-
If you’re up-to-date on the revision (current 1195) then please take a look in src/buildroot/package/fog/scripts/bin/fog.download
There’s some bug in there I’m unable to track down. I’m guessing it’s between the MBR parts and the Partclone parts, but I just can’t see it.
-
A couple of bugs in fog configuration, pxe boot menu page, under advanced configuration options.
- textarea box not being populated with FOG_PXE_ADVANCED setting from globalSetting table.
- FOG_PXE_ADVANCED, only written to pxemenu, not saved to globalSetting table as well.
I’ve also increased the size of the text area.
Relevant for us as we have several other entries in the boot menu, dell diags etc.
fixed in the attached file.
[url=“/_imported_xf_attachments/0/538_FOGConfigurationPage.class.zip?:”]FOGConfigurationPage.class.zip[/url]