Latest FOG 0.33b
-
Snapin tasks now works.
r1131 released.
-
i suggest also to modify fog to do this:
GRUB2 stage1 location:
[LIST]
[][B]Stage 1[/B]: boot.img is stored in the master boot record (MBR), or optionally in any of the [URL=‘http://en.wikipedia.org/wiki/Volume_boot_record’]volume boot records[/URL] (VBRs), and addresses the next stage by an [URL=‘http://en.wikipedia.org/wiki/LBA48’]LBA48[/URL] address (the 1024 cylinder boundary of GRUB legacy is omitted); at installation time it is configured to load the first sector of core.img.
[][B]Stage 1.5[/B]: core.img is by default written to the sectors between the MBR and the first partition, when these sectors are free and available. For legacy reasons, the first partition of a hard drive does not begin at sector 1 (counting begins with 0) but at sector 63, leaving a gap of 63 sectors of empty space. That space is not part of any partition or file system, and therefore not prone to any problems related with it. Once executed, core.img will load its configuration file and any other modules needed, particularly [URL=‘http://en.wikipedia.org/wiki/File_system’]file system[/URL] drivers; at installation time, it is generated from diskboot.img and configured to load the [I]stage 2[/I] by its [URL=‘http://en.wikipedia.org/wiki/Path_(computing)’]file path[/URL].
[/LIST]
so copying only the MBR is not correct! we must copy also all data before sda1 starts -
Hi, I created (very) simple UML diagram of FOG 0.33. Just classes (that I found in /var/www/fog/lib/fog/) and their associations (no functions and variables of classes) and for now, doesn’t look nice, but it’s start. It’s been created in UMLet. I was not able to upload source (it has .uxf extension), so just .pdf. Is it possible to allow .uxf?
[url=“/_imported_xf_attachments/0/512_fog_0.33_v01.pdf?:”]fog_0.33_v01.pdf[/url]
-
Good morning all. Tom I am downloading new version as we speak will let you know if I have any problems.
-
[quote=“Tom Elliott, post: 21774, member: 7271”]It’s all good. You can decompress the init.gz with xz -d -c init.gz > init
Then mount the init file created to another directory. I Usually create a tmp folder inside /tftpboot/fog/images/
[code]
mkdir tmp
xz -d -c init.gz > init
mount -o loop init tmp
[/code][/quote]
i tryed to modify fog script.
simply modified the line:
partclone.${fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
with:
part_fs_type=
blkid $part | awk 'BEGIN {FS="\""} { print $4 }'### row patch to use correct partclone.fstype
partclone.${part_fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fogin upload section. I think that must work, but to test i recreated init.gz with:
umount ./init
xz -z -c init > init.gz
and overwrited original init.gz into tftp/fog dir : don’t boots
what i must do to recreate a working init.gz?
-
xz -C crc32 -z -c init > init.gz (I think)
That said, I don’t think that command will work.
extfs, ntfs, hfsp, btrfs, xfs are the partclone binary names. so if i read your script right, if it comes up as ext4, it’s going to try partclone.ext4 which is wrong.
-
[quote=“Tom Elliott, post: 21829, member: 7271”]xz -C crc32 -z -c init > init.gz (I think)
That said, I don’t think that command will work.
extfs, ntfs, hfsp, btrfs, xfs are the partclone binary names. so if i read your script right, if it comes up as ext4, it’s going to try partclone.ext4 which is wrong.[/quote]
administrator@fog:~/tmp/usr/sbin$ sudo ln -s partclone.extfs partclone.ext4
administrator@fog:~/tmp/usr/sbin$ sudo ln -s partclone.extfs partclone.ext3
administrator@fog:~/tmp/usr/sbin$ sudo ln -s partclone.extfs partclone.ext2works like a charm
-
[quote=“fabritrento, post: 21830, member: 21607”]administrator@fog:~/tmp/usr/sbin$ sudo ln -s partclone.extfs partclone.ext4
administrator@fog:~/tmp/usr/sbin$ sudo ln -s partclone.extfs partclone.ext3
administrator@fog:~/tmp/usr/sbin$ sudo ln -s partclone.extfs partclone.ext2works like a charm :D[/quote]
exist a develop environment where i can access and do testing? -
[quote=“fabritrento, post: 21828, member: 21607”]i tryed to modify fog script.
simply modified the line:
partclone.${fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
with:
part_fs_type=
blkid $part | awk 'BEGIN {FS="\""} { print $4 }'### row patch to use correct partclone.fstype
partclone.${part_fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog[/quote]
alternatively we can insert this:
else
part_fs_type=blkid $part | awk 'BEGIN {FS="\""} { print $4 }'| sed -e 's/1/fs/g' |sed -e 's/2/fs/g'|sed -e 's/3/fs/g'|sed -e 's/4/fs/g'### row patch to use correct partclone.fstype
partclone.${part_fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
partclone.${fstype} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
fi
what is the more correct solution? -
hey Tom I am getting a new error now. This is after dropping my old database because the currpted client would not let me access much and starting a new one I re inventory the computer whiched worked fine but now I am getting this.
Unable to determain snapin status because the MAC address was not correctly formated.
-
[quote=“fabritrento, post: 21833, member: 21607”]alternatively we can insert this:
else
part_fs_type=blkid $part | awk 'BEGIN {FS="\""} { print $4 }'| sed -e 's/1/fs/g' |sed -e 's/2/fs/g'|sed -e 's/3/fs/g'|sed -e 's/4/fs/g'### row patch to use correct partclone.fstype
partclone.${part_fs_type} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
partclone.${fstype} -c -s $part -O /tmp/pigz1 -N -f 1 2>/tmp/status.fog
fi
what is the more correct solution?[/quote]i’m testing image upload right now, in some minutes i say to you if patch worked…
-
Tom,
Could my errors be related to hyper-v?
-
I don’t know, what kind of errors are you getting now?
I’m currently working to fix multiple snapins to be deployed, so it could be that’s broken at the moment. I only got individual snapins working.
-
[quote=“fabritrento, post: 21837, member: 21607”]i’m testing image upload right now, in some minutes i say to you if patch worked…[/quote]
there is a problem, the blkid inclluded in init.gz don’t print the fstype.
on my server:
blkid
/dev/loop0: UUID=“04291dff-b6e6-4815-8549-b1a83d66f145” TYPE=“ext2”
/dev/sda1: UUID=“b842abee-3fbf-4347-a451-ec9e0b3b3aa8” TYPE=“ext2”
/dev/sda5: UUID=“0Oxvj0-osLb-ilwF-e7d0-oJeK-Za9o-IEsjcW” TYPE=“LVM2_member”
/dev/mapper/fog–vg-root: UUID=“b3e21764-e54a-4bbb-9907-0b9d05555c58” TYPE=“ext4”
/dev/mapper/fog–vg-swap_1: UUID=“82810d84-f19c-40ee-a3e8-fa51d6f6e84f” TYPE=“swap”on the client started with init.gz:
blkid
/dev/sda1: UUID=“b842abee-3fbf-4347-a451-ec9e0b3b3aa8”
/dev/sda2: UUID=“0Oxvj0-osLb-ilwF-e7d0-oJeK-Za9o-IEsjcW”i try to copy the binary of blkid by hand from server and re-run fog script.
-
That probably won’t work, but I’ll add it to the init.gz when I get a chance.
-
I am getting this error with out any snapins being deployed
Unable to determain snapin status because the MAC address was not correctly formated.
-
Is it because in fog the MAC address are using : and not -. I am not sure if that is the cause of the formatting error.
-
No, if you look at the access.log on your fog server, you can actually see the command being sent. I think, in my testing late last night, I set up different error tags to see if I could get things working, or see where they were failing. #!im was the error as it was easily identifiable. I may have forgotten to remove it from the snapins.checkin.php. I’ll be updating here shortly.
-
r1132 released.
Rewrite of the servicemodule-active script. Multiple snapins in deploy job works now. Error codes should be fixed.
-
Hey Tom,
Still getting invalid MAC error I attached fog service log.
[url=“/_imported_xf_attachments/0/513_fog2.txt?:”]fog2.txt[/url]
