Posts made by electronico_nc

each image folder looks like this:

./win7_64:
total 19743952
-rwxrwxrwx 1 fogproject root           4 juin   9  2020 d1.fixed_size_partitions
-rwxrwxrwx 1 fogproject root     1048576 juin   9  2020 d1.mbr
-rwxrwxrwx 1 fogproject root         266 juin   9  2020 d1.minimum.partitions
-rwxrwxrwx 1 fogproject root          15 juin   9  2020 d1.original.fstypes
-rwxrwxrwx 1 fogproject root           0 juin   9  2020 d1.original.swapuuids
-rwxrwxrwx 1 fogproject root   174989773 juin   9  2020 d1p1.img
-rwxrwxrwx 1 fogproject root 15691190007 juin   9  2020 d1p2.img
-rwxrwxrwx 1 fogproject root  4350547200 juin   9  2020 d1p3.img
-rwxrwxrwx 1 fogproject root         266 juin   9  2020 d1.partitions

Hi all,
I lost this fog 1.5.9 VM.
The /images is still OK.
New fog install, then mount of /images
Is there a way to import the content of /images into fog ?
Thanks in advance for your time.

@danvaida : by curiosity, have you been able to use FOG with these Lenovo ?

[quote=“Tom Elliott, post: 23505, member: 7271”]It’s not fog thinking every MBR is 512 “BYTES” not Kilobytes
…
[/quote]
Hi Tom,
Sorry about typo on MBR unity :oops: .
I was too hurry when I posted, I have edited the previous post.
Nicolas

Using standard FOG 0.32 :

In any case : if you choose PXE as first boot option, workstation will never boot on HD as fallback. [S]This seems to be due to FOG thinking every MBR is 512K large wich is false (2048 for these Lenovo).[/S]
You can try to modify chain loader but you won’t be able to boot on anything else than PXE and sda ( [url]http://fogproject.org/forum/threads/lenovo-m72e.3709/[/url] ).

If you want to keep the original Lenovo MBR :
Manual image creation of [U]ONLY SDA2[/U] & upload :

• Launch workstation to image in FOG upload-debug mode (select PXE @ boot), then create and upload the sda2 image to FOG :
  [CODE]mkdir /images
  mount -o nolock,proto=tcp <IP.OF.FOG.SERVER>:/images/dev/ /images
  mkdir /images/{temporarynameofimageupload}
  mkfifo /tmp/pigz1
  pigz -p 1 -3 < /tmp/pigz1 > /images/{temporarynameofimageupload}/sys.img.000 & partimage save /dev/sda2 /tmp/pigz1 -V9900000000 -z0 -o -d -f3 -b 2>/tmp/status.fog
  [/CODE]
• On FOG server, move the uploaded image to the proper location :
  [CODE]mv /images/dev/{temprorarynameofimageupload} /images/mygoodpc/sys.img.000[/CODE]

Manual image download of [U]ONLY SDA2[/U] to new workstation :

• Launch new workstation in FOG debug mode and copy image to sda2 :
  [CODE]mkdir /images
  mount -o nolock,proto=tcp <IP.OF.FOG.SERVER>:/images/ /images
  partimage restore /dev/sda2 /images/mygoodpc/sys.img.000 -f3 -b[/CODE]

This way, you keep the original MBR and possibility to launch the factory Lenovo system restoration, but it is an “all manual” process…
I have modified Tom’s kernel to include a small ‘image2sda2.sh’ that avoids typing all commands to restore but it keeps being a pain to work with these Lenovo.

Thank Tom !
worked as expected
Nicolas
PS : sorry for the delay, motorbike fall has taken me away from computers these days.

Brief resume :
Lenovos don’t have a standard 512B MBR. (/dev/sda1 starts @ 2048)
So no integrated FOG function can clone an HD (as MBR is replaced by standard Win7 one).
PXE boot can’t be used as first boot device neither as the chainloader (booting from local HD) is broken (probably because of this long MBR too).
Way found (thanks to Tom Elliott) is to debug-upload a well configured /dev/sda2 to FOG, and to debug-deploy it to destination HD using partimage.
Tom has kindly (and fast) built an init.gz that has all the keymaps, so debug mode is now easy for a non-QWERTY keyboard.
As I would like to keep the original MBR (which allows to boot from /dev/sda3 : Recovery partition by pressing F11 key at startup), I have to use debug mode.
So I need to add a small restore_pc1sda2.sh script in /root that mounts FOG_SERVER:/images and starts the restore process of ONLY /dev/sda2
FOG Wiki is telling to gunzip init.gz, but I’m told :
[QUOTE]gzip: init.gz: not in gzip format[/QUOTE]Could someone please assist on how to decompress init.gz and recompress it ?
Thanks (once more) for your time.
Nicolas

Congratulations, keymap is well loaded !
Thanks again !
Nicolas

Thanks Tom, init.gz is downloading.
Could you please tell where I may get your 3.12 kernel ?
Thanks again.
Nicolas

Yes it is well a 0.32 version

thanks Tom !

FOG 0.32
I need to have a AZERTY keymap while in debug on workstation.
Embedded 2.6.39.1 bzImage shows :
[QUOTE]/etc/init.d/S99.fog line 17 loadkeys not found[/QUOTE]
Line 17 in /etc/init.d/S99.fog is :
[CODE]loadkeys $keymap;[/CODE]
/tftpboot/pxelinux.cfg/default shows all commands in menu with:
[QUOTE]keymap=fr-latin1[/QUOTE]
as FOG_KEYMAP is set to fr-latin1
bzImage 3.8.8 shows the same thing.
Could you please advise how to load correctly the keyboard layout ?
Thanks in advance for your time.
Nicolas

Just for information,
I have updated Lenovo Thinkcentre 72 to the latest available BIOS : F1KT58AUS (dated 2013-11-28) and the problem remains :
Can’t boot from HD if PXE has been selected first.
Nicolas

Sorry for the delay (I thought to have replied).
The restore command : [CODE]partimage restore /dev/sda2 /images/pc1sda2/sys.img.000 -f3 -b[/CODE]went OK.
Thanks again Tom !
Nicolas

(sorry I can’t edit my post : edit box is empty)
So tried too :
[CODE]pigz -dc -p 1 -3 < /images/pc1sda2/sys.img.000 > /tmp/pigz1 & partimage restore /dev/sda2 /tmp/pigz1 2>/tmp/status.fog
[/CODE]But got same error code …

[quote=“Tom Elliott, post: 20654, member: 7271”]I’d recommend, performing upload - debug mode in your case.

I’m assuming you’re running FOG 0.32, in which case, the upload commands for your system would be:
Assuming your doing a multi-partition image:

[code]mkdir /images
mount -o nolock,proto=tcp <IP.OF.FOG.SERVER>:/images/dev/ /images
mkdir /images/{temporarynameofimageupload}
mkfifo /tmp/pigz1
pigz -p 1 -3 < /tmp/pigz1 > /images/dev/{temporarynameofimageupload}/sys.img.000 &
partimage save /dev/sda2 /tmp/pigz1 -V9900000000 -z0 -o -d -f3 -b 2>/tmp/status.fog[/code]

Download, you should be set. Though I’d recommend, performing the testdisk MBR fix and then reupload the image to the server using regular means.

Once you’re complete with the image upload process, log in to your FOG Server as root and type into a terminal window.:

[code]mv /images/dev/{temprorarynameofimageupload} /images/{IMAGENAME}[/code][/quote]
Thanks a lot Tom for these infos !
Right : FOG 0.32
The upload proccess went ok, except a little code error about image location:
[CODE]pigz -p 1 -3 < /tmp/pigz1 > /images/dev/{temporarynameofimageupload}/sys.img.000 & partimage save /dev/sda2 /tmp/pigz1 -V9900000000 -z0 -o -d -f3 -b 2>/tmp/status.fog[/CODE]
that has to be:
[CODE]pigz -p 1 -3 < /tmp/pigz1 > /images/{temporarynameofimageupload}/sys.img.000 & partimage save /dev/sda2 /tmp/pigz1 -V9900000000 -z0 -o -d -f3 -b 2>/tmp/status.fog[/CODE]
Then I moved image from /images/dev to /images/pc1sda2 and chmod -R 777 /images/pc1sda2.
FOG did not saw the image, so I created it with ‘multi-partition’ type.
Assigned pc1sda2 to a registered PC in FOG and tried to deploy image, I got : “image store corrupted, unable to load MBR”

Then I assigned the ‘Single partition’ type to image and tried to Deploy-debug, FOG told :
[QUOTE]
osid=5
osname=Windows 7
mbrfile=/usr/share/fog/mbr/win7.mbr
storage=10.10.20.2:/images/
img=pc1sda2
part=/dev/sda1
[/QUOTE]
/dev/sda1 ?? I have imaged /dev/sda2 …
Thinking I have to tell FOG how to proceed, tried :
[CODE]mkdir /images
mount -o nolock,proto=tcp 10.10.20.2:/images/ /images
mkfifo /tmp/pigz1
unpigz -p 1 -3 < /images/pc1sda2/sys.img.000 > /tmp/pigz1 & partimage restore /dev/sda2 /tmp/pigz1 2>/tmp/status.fog[/CODE]
but last line gives :
[QUOTE]can’t read the following volume file : /tmp/pigz1[/QUOTE]
It seems that unpigz is not installed in the system.
Could you please assist a bit more so I could try to restore this imaged /dev/sda2 to another computer ?
Thanks in advance for your time.
Nicolas

Well I use FOG for years without troubles on ‘normal’ computers.

I have 20 of these Lenovo that have :
1500MB boot partition (instead of the usual 100MB)
450GB Win 7 pro
14GB Recovery partition

A test computer has been configured has wanted (removed Norton Internet Security, etc…) and an image uploaded to FOG.
When trying to deploy the image on another computer, I get :
“there has been a signature failure” at reboot
Lenovo seems to have hardware authentication on these damned 1500MB boot partition that makes the OS not able to boot.

If I flag /dev/sda2 (C: win7) as boot and install Testdisk MBR on first HD sector, system can boot normaly.

So, I thought : nice, just need to backup the 450GB (system) partition and deploy it.
But FOG refuses to upload it because there is more that 2 partitions on HD …

I’m ‘a bit’ lost with these Lenovo …
Thanks in advance if someone could give me a track.
Nicolas