Since ages:
NFS = Not For Security

Hello fog featurists(?)

Currently i can’t see anywhere, if the fog script at the client fails, or?
The “report page” only shows: “Script was run then and took xxx seconds”

Debugging and ~ reporting is very complicate or impossible.
If this is not my ridiculous newbee fault i would like to ask:

Would it make sense the setup a remote syslogd so the fog-script could sent persistent log file entries
to the fog-server (eg).
IIRC this are only some few lines of configuration in /etc and installing (see below)

As the clients fog script/kernel already knows where to pull the images he could sent UPD-packages in this direction.
What is my error there? I can’t imagine why this is not already done instead of “blind filying”.
The webpages and set up must be expanded, some day. But in the first step only the PXEied kernels have to be patched, or?

[url]http://www.debuntu.org/how-to-remote-syslog-logging-on-debian-and-ubuntu/[/url]

Hello Tom

thanks your “wondering” (and your work on/at fog)

Your are right: It’s hard to get rid off GPT. But that’s by intension, but
I’m lucky currently not to have to handle GPT-
I think i will use fog to deploy an “embedded” OS.
So the disks delivered are empty (i think all “00”), uses MBR.
But don’t (usually) have a BIOS compatible console.
So there is problem with the debug-option
No keyboard, No screen.
Deploying via fog would have been so elegant.

If i could give help i would like to help to find the reason while that big fog script fails to detect that the disk is empty.
I see it is looking on /proc/partition and asks sfdisk. All say: There is a “/dev/sda” (but no /dev/sda1)
I used a dd | hexdump to see that the first 32MB are really empty(=zero(0)).

A new feature request thread (i’ll place there):
Would it make sense the setup a syslogd so the fog-script could sent persistent log file entries the fog-server.
IIRC this are only some line of configuration in /etc and installing

[INDENT]Would it be possible to change this text as it does not become clear (for me noobie) what is going on as it always goes “to a computer” (Someone used copy&paste and then replaced “send” with “upload”?)

Good:[URL=‘http://10.51.251.180/fog/management/index.php?node=host&sub=deploy&id=10&type=1’]
[I]Download[/I][/URL][I] Deploy action will send an image saved on the FOG server to the client computer with all included snapins.[/I]
[I] [URL=‘http://10.51.251.180/fog/management/index.php?node=host&sub=deploy&id=10&type=2’]Upload[/URL] Upload will pull an image from a client computer that will be saved on the server.[/I]

Not clear what will be written where(if you don’t already know):
[URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=15’]
[I]Download - Debug[/I][/URL][I]
Download - Debug mode allows FOG to setup the environment to allow you send a specific image to a computer, but instead of sending the image, FOG will leave you at a prompt right before sending. If you actually wish to send the image all you need to do is type “fog” and hit enter.[/I]
[I] [URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=16’]
Upload - Debug[/URL]
mode allows FOG to setup the environment to allow you Upload a specific image to a computer, but instead of Upload the image, FOG will leave you at a prompt right before restoring. If you actually wish to Upload the image all you need to do is type “fog” and hit enter.[/I][/INDENT]
[INDENT]
maybe it becomes more clear to a noobie what’s done when:
[URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=15’]
[I]Download - Debug[/I][/URL]
[I]Download - Debug mode allows FOG to setup the environment to send a specific image to a client computer, but FOG will leave you at a prompt right before [COLOR=#ff0000]restoring[/COLOR]. If you actually wish to [COLOR=#ff0000]store[/COLOR] the image to the client all you need to do is type “fog” and hit enter.[/I]
[I] [URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=16’]
Upload - Debug[/URL] [/I]
[I] [COLOR=#ff0000][B]Upload - Debug[/B][/COLOR] mode allows FOG to setup the environment [COLOR=#ff0000]for pulling[/COLOR] a specific image [B][COLOR=#ff0000]from[/COLOR][/B] a client computer, but FOG will leave you at a prompt right before [COLOR=#ff0000]pulling the image[/COLOR]. If you actually wish to [COLOR=#ff0000]pull[/COLOR] the image from the client all you need to do is type “fog” and hit enter. [/I][/INDENT]

OK.Thanks for the infos/views.

Hm, is there no way just to (remotely) “dd” a dummy mbr (i have a quite good mbr that works…see “/image” or?)
and partition table (only if the first 512 byte/32MB are all zero(*))?
And fog deploy will overwrite the dummy partition entries.

OK, thanks 4 info.
How can i move it to the feature request section or do i have to make a second post there?

I have German Keyboards where Z and Y are swapped…
i have sysprepped windows.
if i only once misstyped in fog dialog
fog will boot off disk, making the sysprepped windows useless so i have to restart the entire process.

so i second:
[QUOTE]
[LIST]
[*]Where it asks the yes/no questions, like joining the domain, it accepts input of other characters other than y/n. Is there any way to have FOG only accept y/n and if anything else is entered, prompt again, this time entering y/n? It would avoid having to shut down and restart the registration if you accidentally enter the wrong key
[/LIST]
[/QUOTE]

Yes.
Very useful.
Thanks .

If it would be activated by default using fog would be much easier for a newbie.
If he has some day 1000 clients, he’s no newbie anymore and can turn it off

Would it be possible to change this text as it does not become clear (for me noobie) what is going on as it always goes “to a computer” (Someone used copy&paste and then replaced “send” with “upload”?)

Good:
[URL=‘http://10.51.251.180/fog/management/index.php?node=host&sub=deploy&id=10&type=1’]
Download[/URL] Deploy action will send an image saved on the FOG server to the client computer with all included snapins.
[URL=‘http://10.51.251.180/fog/management/index.php?node=host&sub=deploy&id=10&type=2’][IMG]http://10.51.251.180/fog/management/images/restoredebug.png[/IMG]
Upload[/URL] Upload will pull an image from a client computer that will be saved on the server.

Not clear what will be written where(if you don’t already know):
[URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=15’]
Download - Debug[/URL] Download - Debug mode allows FOG to setup the environment to allow you send a specific image to a computer, but instead of sending the image, FOG will leave you at a prompt right before sending. If you actually wish to send the image all you need to do is type “fog” and hit enter.
[URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=16’][IMG]http://10.51.251.180/fog/management/images/restoredebug.png[/IMG]
Upload - Debug[/URL] mode allows FOG to setup the environment to allow you Upload a specific image to a computer, but instead of Upload the image, FOG will leave you at a prompt right before restoring. If you actually wish to Upload the image all you need to do is type “fog” and hit enter.

maybe becomes clear to a noobie too what’s done when:

[URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=15’]
Download - Debug[/URL] Download - Debug mode allows FOG to setup the environment to send a specific image to a client computer, but FOG will leave you at a prompt right before [COLOR=#ff0000]restoring[/COLOR]. If you actually wish to [COLOR=#ff0000]store[/COLOR] the image to the client all you need to do is type “fog” and hit enter.
[URL=‘http://10.51.251.180/fog/management/index.php?node=tasks&sub=hostdeploy&id=10&type=16’][IMG]http://10.51.251.180/fog/management/images/restoredebug.png[/IMG]
Upload - Debug[/URL]
[COLOR=#ff0000][B]Upload - Debug[/B][/COLOR] mode allows FOG to setup the environment [COLOR=#ff0000]for pulling[/COLOR] a specific image [B][COLOR=#ff0000]from[/COLOR][/B] a client computer, but FOG will leave you at a prompt right before [COLOR=#ff0000]pulling the image[/COLOR]. If you actually wish to [COLOR=#ff0000]pull[/COLOR] the image from the client all you need to do is type “fog” and hit enter.

Same corner?

Wrong image size, wrong date
The storage is local on the fog server.

Image Management On Client On Server
Multiple Partition Image - All Disks (Not Resizable) 346.68 GiB 2.02 GiB Today, 4:29pm

ll -h

total 4.8G
drwxrwxrwx 2 root root 4.0K Aug 7 18:29 ./
drwxrwxrwx 8 root root 4.0K Aug 7 18:29 …/
-rwxrwxrwx 1 root root 512 Aug 7 18:16 d1.mbr*
-rwxrwxrwx 1 root root 8.0M Aug 7 18:16 d1p1.img*
-rwxrwxrwx 1 root root 4.8G Aug 7 18:29 d1p2.img*
-rwxrwxrwx 1 root root 18M Aug 7 18:29 d1p3.img*

An other image:
Multiple Partition Image - All Disks (Not Resizable) 0.00 iB 4.01 GiB 01-01-1970 12:00am

ll -h

total 9.2G
drwxrwxrwx 2 root root 4.0K Oct 18 2013 ./
drwxrwxrwx 8 root root 4.0K Aug 7 18:29 …/
-rwxrwxrwx 1 root root 4 Oct 18 2013 bla.txt*
-rwxrwxrwx 1 root root 512 Oct 18 2013 d1.mbr*
-rwxrwxrwx 1 root root 8.0M Oct 18 2013 d1p1.img*
-rwxrwxrwx 1 root root 3.6G Oct 18 2013 d1p2.img*
-rwxrwxrwx 1 root root 577K Oct 18 2013 d1p3.img*
-rwxrwxrwx 1 root root 5.6G Oct 18 2013 sys.img.000*

Such a “step-by-step-tutorial” is of great help! Thanks.
I am doing the same “step-by-step” as the surface of fog have some more dark corners
of, em, unconventional usability ways

BOT:
So is my finding is right…

“Not partition no fog!”

But i don’t understand the sense and that’s not what i would have expected.
Are there historically reasons? (See the obsolete hint, that partitions are not resizable)

First:
What’s the use of a remote deploy system when i have to “go” to each machine and create partition manually?
Why is that required?
Why can’t this be done remotely. automatically best before the restore?
I found someone has written tons of bash code handling partition, disk detection and resize.
What’s all that code for?

Second:
why isn’t that flagged as an error in the machine report?
Only the fast time of less a second gives a hint, that there was something wrong.

Of cause, now adays, almost every (Windows) PC is delivered with a partition. i Assume that’s the reason why the board is not full of reports like this.
But VMs and new (replacemant) disks are not pre-partioned and embedded system are not either.
(Initializing the partition on a headless (embedded) system is difficult,
without a local keyboard and console :-))

Third(general problem)
how can i get better (debug) loggings?
I hacked the bangshe line to get llittle clue what’s is going on (add -x) , but that’s only locally vissible.

i use fog 1.2 on ubuntu 4

Hello

Fog download to a wiped disc do not work here (debugging that i ran in an other problem, so pardon for the second thread in 2 days)
I have manually to create a (dummy)partition on the client to make download work.
But that can’t be true for a remote imaging system, or?

Image are not restored on empty disks

Steps to reproduce:

Create a VM for Windows 7 32 bit using Virtual Box 4.3.15beta (.14 is broken)
Disk 25GB dynamically, (is filled with zeroes, unformated, uninitialized)

Insert CD iPXE.iso (I don’t think that step matters, it’s only for my convience as a can’t change DHCP)
boot iPXE (sets only chain next server IP etc)
boot from fog “default.ipxe”
Perform Full Host Registration and Inventory (works flawlessly)

Hostname:xx
Image ID:1
Group:
Produktkey:
AD:n

Primary User: t
#1 tag
#2 tag
Image now? N

At fog-Server Webfront end:

Manage Hosts
List all host
Host Name:tt
Host Image: Gold
<update>

List all hosts
click “download”

“Download trask created”

Task management

Client boots via ipxe

Linux is directly booting
Some messages with “OK” can be seen
I have to press enter several times
VM boots immediately again without any transfer

No image transfer occured
Task became deleted on the fog server
Task became reported as “OK”.

FOG “Report Management” says:

fog tt 2014-08-05
11:31:41 2014-08-05
11:31:42 00:00:01 Gold Download

1 sec: impossible. There was no transfer at all. There is no windows on the client.

root@fog2:~# uname -a
Linux fog2 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linux
root@fog2:~#

Client in debug mode:
root@10#uname -a
Linux 10.0.2.15 3.15.6 #1 SMP PREEMPT … i686 GNU/Liunux

On the clients “debug” console:
(have to retype the screen output of virtual box…all typos are mine)
Client debug download
root@10#Hexdump –C –n 1M
Shows all zero
root@10#cat /proc/partition
0 0 262144000 sda
root@10#Fdisk /dev/sda
…
Device does not contain a recognized partition table
Created a new DOS disklabel with disk identifier .l…
w

root@10#fog (start an download at the server)
Does a lot stuff but do not download the images

Next try:
Create a partition:
root@10#fdisk /dev/sda
n
p
1
w
q

root@10#fog (start a download at the server)

surprise!
“download” works now!
Part clone launches and writes images with 2GB/min
The only difference:
A Partition was written!

After the use of the fast wipe command the restore(download) will not work too.

Any takers?
Any hint why only I have that problem?

[quote=“Junkhacker, post: 34699, member: 21583”]is there a reason you quoted yourself without adding anything new?[/quote]
No, a quote was not my intention, sorry.
sorry this BB is new to. I’ll try to find the button to turn that useless quoting off.

Hi
new try:

generated a new 25GB dynamical disk in virtual box
select this disc in the VM.
tried a dowload: fails as always
(so the problem is reproducible for me, but why am i the only one?)
tried debug download:
did hexdump -C -n 32M /dev/sda
hd shows all zeroes (not random numbers)
“fdisk -l” shows the right dimensions
fdisk /dev/sda complaints “Devie does not contain a recognized partiotion table”
“Created a new DOS disklabel with disk identfier …”
“w” write does not alter the disk…?
Where did fdisk -l got its data from?

tried “sh -x fog” and initiate a disk surface test:
Finds /dev/sda and finishes in fraction of a second
(would like to add a screendump, there seems to be no way with virtual box, sorry)

#fogpartinfo --list-parts /dev/sda
Error: /dev/sda: unrecognized disk label

#fogpartinfo --list-devices
Error: /dev/sda: unrecognized disk label

???

[quote=“Michael Thomas, post: 34689, member: 25383”]Thanks for the fast reply(during weekend i had no access). I wasn’t aware that a have to unzip the img-file and
that partclone does not use any “magic number” to detect the .img format.
OK, that explains why may manually restore did not work neither.
But i tried that only because the normal download way falied without any hint what’s going wrong (The task is clearly removed from schedule as if all went well…that surprised me.)

I inspected the logs files i know (in /var/log/) but didn’t find a hint. So my idea was that fog is logging somewhere else using the syslog protocol. But there are no logs fog at all?

---

spec_
FOG Version 1.2
Linux fog2 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linu
Running Virtual Box 3.15 2 CPU 90% PIIX3, IO-APIC, no EFI, 512MB RAM, VT/x+Nested

I don’t change the DHCP server settings (066,067 unset).
Instead I made and boot an iPXE-Iso which includes the required Server/File settings and PXE modules fog needs.
So i don’t have to finger in the BIOS enabling PXE and always run a known working PXE (there were problems with VirtualBOX-BIOS-PXE some time ago)

IiPXE.iso[/I]
I#!ipxe[/I]

Idhcp[/I]
Iset filename undionly.kpxe[/I]
Iset filename default.ipxe[/I]
Iset next-server 10.51.251.180[/I]

Iecho Z My IP address: ${net0/ip}[/I]
Iecho Z Subnet mask: ${net0/netmask}[/I]
Iecho Z Will boot ${filename} from ${next-server}[/I]

Iprompt --key 0x02 --timeout 20 Press Ctrl-B for the iPXE command line… && shell ||[/I]

I# chain tftp://10.51.250.180/undionly.kpxe[/I]
Ichain tftp://${next-server}/${filename}[/I]

Iautoboot[/I]

I---------------[/I]
Idefault.ipxe[/I]
I# cat /tftpboot/default.ipxe[/I]
I#!ipxe[/I]
Iecho This is tftp://default.ipxe[/I]
Icpuid --ext 29 && set arch x86_64 || set arch i386[/I]
Iecho CPU-Id is ${arch} ${net0/mac} ${net1/mac} ${net2/mac}[/I]
Iparams[/I]
Iparam mac0 ${net0/mac}[/I]
Iparam arch ${arch}[/I]
Iisset ${net1/mac} && param mac1 ${net1/mac} || goto bootme[/I]
Iisset ${net2/mac} && param mac2 ${net2/mac} || goto bootme[/I]

Iecho Note: default.ipxe chain [url]http://10.51.251.180/fog/service/ipxe/boot.php##params[/url][/I]
Iecho params param ##params[/I]
I#shell[/I]
Ichain [url]http://10.51.251.180/fog/service/ipxe/boot.php##params[/url][/I]

Current progress:
I can enter the fog management server
I can boot PXE-Iso
http:boopt.php is lanched and that iPXE-menu is shown
i can register the box, run memtest etc.
all well and flawless.
i can upload (i see partcones menu, it shows it is uploading bar and speed (approx 12MB/s in entire virtual environment)
On the server i can add a task to download to an other, fresh VM with a fresh VDI.
The PXE boot occurs, it checks the settings, does not find a problem, and…closes instead of downloading.

[SIZE=5]Idea:[/SIZE]
[SIZE=5]As if partclone does not make any plausibility tests to the image, may i assume it does not validate the MBR too in any way too?[/SIZE]
[SIZE=5]So if the MBR/Partition contains garbage, it silently an imediately dies? (Would explain why i don’t see any logs and that it is now working, after i manually “initialize” the MBR/partion?[/SIZE]

[SIZE=5]Partclone seems to die before it can zero out the mbr…or?[/SIZE]

[SIZE=5]Question:[/SIZE]
[SIZE=5]Is my assumption right partclone died as MBR was filled with garbage (random noise)?[/SIZE]
[SIZE=5]If my assumptions are right:[/SIZE]
[SIZE=5]Will partclone get input validations so that such problems will be logable with comprehensive error messages?[/SIZE]
[SIZE=5]Until that day:[/SIZE]
[SIZE=5]Is there a way to “short” zero out the MBR before partcone runs? (i don’t want to wipe the entire 4TB disk :))[/SIZE]
[SIZE=5]I see, that the fog script is attempting this, but i think it’s too late: [/SIZE]
[SIZE=5]something already died on the non-sense MBR.[/SIZE]
[SIZE=5]Any help?[/SIZE][/quote]

Thanks for the fast reply(during weekend i had no access). I wasn’t aware that a have to unzip the img-file and
that partclone does not use any “magic number” to detect the .img format.
OK, that explains why may manually restore did not work neither.
But i tried that only because the normal download way falied without any hint what’s going wrong (The task is clearly removed from schedule as if all went well…that surprised me.)

I inspected the logs files i know (in /var/log/) but didn’t find a hint. So my idea was that fog is logging somewhere else using the syslog protocol. But there are no logs fog at all?

---

spec_
FOG Version 1.2
Linux fog2 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linu
Running Virtual Box 3.15 2 CPU 90% PIIX3, IO-APIC, no EFI, 512MB RAM, VT/x+Nested

I don’t change the DHCP server settings (066,067 unset).
Instead I made and boot an iPXE-Iso which includes the required Server/File settings and PXE modules fog needs.
So i don’t have to finger in the BIOS enabling PXE and always run a known working PXE (there were problems with VirtualBOX-BIOS-PXE some time ago)

IiPXE.iso[/I]
I#!ipxe[/I]

Idhcp[/I]
Iset filename undionly.kpxe[/I]
Iset filename default.ipxe[/I]
Iset next-server 10.51.251.180[/I]

Iecho Z My IP address: ${net0/ip}[/I]
Iecho Z Subnet mask: ${net0/netmask}[/I]
Iecho Z Will boot ${filename} from ${next-server}[/I]

Iprompt --key 0x02 --timeout 20 Press Ctrl-B for the iPXE command line… && shell ||[/I]

I# chain tftp://10.51.250.180/undionly.kpxe[/I]
Ichain tftp://${next-server}/${filename}[/I]

Iautoboot[/I]

I---------------[/I]
Idefault.ipxe[/I]
I# cat /tftpboot/default.ipxe[/I]
I#!ipxe[/I]
Iecho This is tftp://default.ipxe[/I]
Icpuid --ext 29 && set arch x86_64 || set arch i386[/I]
Iecho CPU-Id is ${arch} ${net0/mac} ${net1/mac} ${net2/mac}[/I]
Iparams[/I]
Iparam mac0 ${net0/mac}[/I]
Iparam arch ${arch}[/I]
Iisset ${net1/mac} && param mac1 ${net1/mac} || goto bootme[/I]
Iisset ${net2/mac} && param mac2 ${net2/mac} || goto bootme[/I]

Iecho Note: default.ipxe chain [url]http://10.51.251.180/fog/service/ipxe/boot.php##params[/url][/I]
Iecho params param ##params[/I]
I#shell[/I]
Ichain [url]http://10.51.251.180/fog/service/ipxe/boot.php##params[/url][/I]

Current progress:
I can enter the fog management server
I can boot PXE-Iso
http:boopt.php is lanched and that iPXE-menu is shown
i can register the box, run memtest etc.
all well and flawless.
i can upload (i see partcones menu, it shows it is uploading bar and speed (approx 12MB/s in entire virtual environment)
On the server i can add a task to download to an other, fresh VM with a fresh VDI.
The PXE boot occurs, it checks the settings, does not find a problem, and…closes instead of downloading.

[SIZE=5]Idea:[/SIZE]
[SIZE=5]As if partclone does not make any plausibility tests to the image, may i assume it does not validate the MBR too in any way too?[/SIZE]
[SIZE=5]So if the MBR/Partition contains garbage, it silently an imediately dies? (Would explain why i don’t see any logs and that it is now working, after i manually “initialize” the MBR/partion?[/SIZE]

[SIZE=5]Partclone seems to die before it can zero out the mbr…or?[/SIZE]

[SIZE=5]Question:[/SIZE]
[SIZE=5]Is my assumption right partclone died as MBR was filled with garbage (random noise)?[/SIZE]
[SIZE=5]If my assumptions are right:
Will partclone get input validations so that such problems will be logable with comprehensive error messages?[/SIZE]
[SIZE=5]Until that day:[/SIZE]
[SIZE=5]Is there a way to “short” zero out the MBR before partcone runs? (i don’t want to wipe the entire 4TB disk :-))
I see, that the fog script is attempting this, but i think it’s too late:
something already died on the non-sense MBR.
Any help?[/SIZE]

Append:

i previouly to the above text i entered the “fog” command in the debug console.
It gives a lot of status informations, all seems to be well,
but when i entered the “last” return, the client closes immediately. I saw no partclone dialog, only the reoboot screen.
No hint what was going wrong.

Now, after manually mounting the nfs share and manually overwirting(dd) the mbr and
got those rediculose error messages, i lanches the fog command (i thoug it would be senseless too)
It starts and
I could read the line similar to “deleting old start mbr”
and then partclone starts to run!

What’s going on there?
Do i have to wipe(zero out) the disk manually first? (i only created an empty vdi)
Would not make sense for a disk cloning software to do the manually on the cloent, or?

Hello

uploading an image seemed to have worked, but download never had success. i don’t know where could find any
detailed error message. Do i have to set up a syslog server? Where to go? Any hints, please?

More detail:
fog 1.2 on ubuntu
Linux fog2 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linu

As i only see “flashings” of PXE i can’t read, I tried using the “debug download”
and see a funny error message:

i mount the nfs share from the fog server
#mkdir /images
#mount -o nolock nn.nn.nn.nn://images/ /images

i coppied the d1.mbr to /dev/sda
#dd if=/images/W7/d1.mbr of=/dev/sda

#/usr/sbin/partclone.ntfs -s /images/W7/d1p1.img -o /dev/sda1 -r
Partclone v0.2.69 [url]http://partclone.org[/url]
Starting to restore image (/images/W7/d1p1.img) to device (/dev/sda1)
There is not enough free memory, partclone suggests you should have 1548900463201413591 bytes memory
Partclone fail, please check /var/log/partclone.log !

Pretty clear error message but: Where do i get 1.548.900.463.201.413.591 of RAM? From NSA?

I tried on the fog server to see if the image is OK at least:

root@fog2:~# /home/fog/fog_1.2.0/src/buildroot/package/fog/partclone32/partclone.chkimg -s /images/W7/d1p1.img
Partclone v0.2.69 [url]http://partclone.org[/url]
Starting to check image (/images/W7/d1p1.img)
There is not enough free memory, partclone suggests you should have 1548900463201413591 bytes memory
Partclone fail, please check /var/log/partclone.log !

(On both machines i got the same memory value)

i installed the ubuntu partclone package on the fog server:

root@fog2:~# partclone.chkimg -s /images/W7/d1p1.img
Partclone v0.2.43 [url]http://partclone.org[/url]
Starting to check image (/images/W7/d1p1.img)
The Image magic error. This file is NOT partclone Image
Partclone fail, please check /var/log/partclone.log !

root@fog2:~# file /images/W7/d1p1.img
/images/W7/d1p1.img: gzip compressed data, from Unix, last modified: Thu Jul 31 15:42:20 2014, max compression

What do i miss?
I have no clue where to search an waht’s going wrong.

root@fog2:~# ll /images/W7/
total 4172508
drwxrwxrwx 2 root root 4096 Jul 31 13:52 ./
drwxrwxrwx 6 root root 4096 Jul 31 13:53 …/
-rwxrwxrwx 1 root root 512 Jul 31 13:42 d1.mbr*
-rwxrwxrwx 1 root root 8274330 Jul 31 13:42 d1p1.img*
-rwxrwxrwx 1 root root 4136221212 Jul 31 13:52 d1p2.img*
-rwxrwxrwx 1 root root 512 Jul 31 13:52 d2.mbr*
-rwxrwxrwx 1 root root 128126142 Jul 31 13:53 d2p1.img*

fog server i a ubuntu server running in Oracel Virtual Box 4.3.15 r95226 (4.3.14 is broken)
client is a virtual machine Oracel Virtual Box 4.3.15 r95226 too.