Posts made by Mr.Myagy

[quote=“Tom Elliott, post: 26866, member: 7271”]Fog does clean the drives first. But only on the download task. Creating the initial image is completely up to you. I wouldn’t have the “FOGGIEST” of idea’s on what it is you’re planning to do to actually have FOG create the image for you. I hope this makes sense.

If you’re trying to make an MBR style OS on a disk that originally in GPT format, you have to make sure all is well.

Converting from GPT to MBR has some quirks. Converting from MBR to GPT is fairly easy with some minor modifications. FOG wouldn’t have any interaction in this process.

The reason why this is all important to know is because, if GPT is “present” on the Disk, FOG 1.0.0 will create a backup of the GPT partitioning table. GPT is present in many cases if you don’t properly wipe the drive and partitioning tables prior, especially if your OS came preinstalled with UEFI enabled on the system.[/quote]

I redid the test in a virtual machine. Still not working. The same result. Please check the pictures. I can’t figure what am I doing wrong…

[url=“/_imported_xf_attachments/0/754_vm.png?:”]vm.png[/url][url=“/_imported_xf_attachments/0/755_vm1.png?:”]vm1.png[/url]

[quote=“falko, post: 26949, member: 48”]you mean adding an ISO to the Boot menu?[/quote]

I would be interested in knowing how to do that as well

It’s MBR. As for the hard drive, no, I did not clean it before. I was under the impression FOG will do that for me. I have 10 computers, on which I want to deploy Windows today, Ubuntu tomorrow, then Windows again, and so on. Going with a live cd at every computer would defeat the purpose of using FOG…
Given the above, I feel I missed a feature/option somewhere, that might clean the hdd for me, in which case, I must beg forgiveness for my ignorance and ask where can I find that.

Has anyone been able to clone a linux client? I’ve been trying for some time now with no luck. When I select Multiple disks for the image type, I don’t get any error, but PartClone doesn’t even start. When I select single disk multiple partitions, it complains about the partitioning layout of the destination and exits. Unfortunately DD isn’t really an option since the HDD is 80GB, but the Ubuntu partitions (including swap) are 12GB.

Tom, issue in [url]http://fogproject.org/forum/threads/latest-fog-1-0-0.10417/#post-26547[/url] is still persisting.
Did you manage to take a look over it? I really need to be able to clone this Ubuntu 14.04 client, and I can’t find a way to achieve this…

I still can’t find a way to wrap my head around this, but maybe these make any sense for you since they seem to report the same error:
[url]http://ubuntuforums.org/archive/index.php/t-1966148.html[/url]
[url]http://ubuntuforums.org/archive/index.php/t-2122496.html[/url]

While I don’t really know what is happening behind, I’m just wondering: would sfdisk be able to save the day ?
([FONT=verdana][COLOR=#000000]sfdisk -d /dev/sda > parts_sda.txt then [/COLOR][/FONT][FONT=verdana][COLOR=#000000]sfdisk -d /dev/sda < parts_sda.txt[/COLOR][/FONT] )

[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?

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?

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]

[quote=“Tom Elliott, post: 26535, member: 7271”]When you installed Ubuntu 14.04, did it install as EFI or MBR? Also, what’s the size of the d1.mbr for this particular image?

I ask for size because it’s the “size” of the mbr file that determines if it’s an MBR or GPT type of MBR. From what I can tell, this is a multicast deploy with a linux OSID.

I don’t have an easy method to check if the mbr is GPT or mbr, so I’ve used file sizes to make this determination.

The steps that make an mbr, or gpt backup are:
On upload, it runs gdisk -l /dev/sda and searches for the gpt: present line. If it’s not present, it does a normal dd backup of the mbr, or in the case of linux, it copies all the data from 1 to the 63 sector at 512 bytes each sector. So the “filesize” is: 32256 bytes, but is still of MBR type. This was just a guess, but may be inaccurate for Ubuntu.

My guess to the error you’re seeing is because of this. Maybe MBR Ubuntu 14.04 is actually larger so the deploy action is writing the d1.mbr as GPT structured rather than MBR?[/quote]

Well…
[CODE]# ls -lah
total 1.3G
drwxrwxrwx 2 root root 4.0K May 3 16:14 .
drwxrwxrwx 6 root root 4.0K May 3 16:18 …
-rwxrwxrwx 1 root root 32K May 3 15:58 d1.mbr
-rwxrwxrwx 1 root root 1.3G May 3 16:14 d1p1.img
-rwxrwxrwx 1 root root 125 May 3 16:14 d1p2.img
-rwxrwxrwx 1 root root 59M May 3 16:18 d1p5.img
[/CODE]

[CODE]# gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
[/CODE]

Is there any way in which I can get around this?

Already encountered the first problem…
Any hint please?

[url=“/_imported_xf_attachments/0/704_Ubu_dep-2014-05-03-16-28-49.png?:”]Ubu_dep-2014-05-03-16-28-49.png[/url]

Tom, as promised in the previous thread, I am coming back with feedback about Win8.1.
Disclaimer: yesterday I was in the lab I have at work, while today I virtualized everything; however, the errors were the same.

Possible bug: FOGMulticastManager still isn’t starting properly, I had to start it manually.
Win8.1 worked like a charm with “Multiple partition image - single disk”, after I started FOGMulticastManager manually.

Now I will try to replace Windows 8.1 with Ubuntu 14.04. Will come back with updates.
Just out of my curiosity, what is “Other (99)” for ? How is it different from Windows 8 or Linux?

This is quickly turning into my favourite open source project!

[quote=“Tom Elliott, post: 26496, member: 7271”]So, as Windows 8.1 is fairly new and not thoroughly tested with resizable images, I’d recommend maybe switching the image type to Multi Partition Single or All disk. I don’t know how the win8.mbr file was created, but from the sounds of it, it only contains one partition in total, which is why you’re seeing the /dev/sda2 not found error. I didn’t make the win8.mbr, so I don’t know all the specifics.

It does, however, sound likely that you probably need to do another fresh install. I know it’s more work, but it’s the best I can give you for now.[/quote]

I have no problem reinstalling. I am (intermittently) trying to do this for the last 2 weeks now, so you can image I did quite some reinstalls. However, I would like to help the project if I can. I will come back with the results (probably tomorrow) from the “Multiple partition image - single disk”, as for the current problem, if you need any log, file, etc. I am more than happy to provide.

[quote=“need2, post: 26497, member: 21891”]Sure, but was that drive used for previous Windows installations? It just seems like there was junk partition info left on the drive from the images that were being made on the server. Also, if you are doing an NTFS Resizable partition, it doesn’t matter what the original partition size is, only how much of it is used by data.

EDIT: Tom’s post gave me an idea. I assume this is a Windows 8 install that you upgraded to 8.1? 8.1 is not a service pack, its almost like an OS reinstall that you happen to get to keep your programs and files through. I would not be shocked if the 8.1 upgrade does some partition junk during its upgrade process to give it some fallbacks in case it fails during its install.[/quote]

I didn’t update from 8 to 8.1. I installed 8.1 from the ISO. As for previous Windows installations, yes, there were, but I can’t see how those affected this. Granted, I didn’t do a low level format, but I did recreate the partitions every time I reinstalled WIndows.

[quote=“need2, post: 26492, member: 21891”]If possible I would recommend doing a basic wipe on that drive and reinstalling. For some reason it looks like some crap partitions are left over.[/quote]

This was a fresh install. Fresh, as in…I just got to setup the user, installed .net and fog service, sysprep’ed and that’s it. As for the HDD configuration: it’s a 80GB hard drive, out of which I chose to install Windows on only 20 of them, leaving the rest unformatted. I did this, because I am planning to deploy this image on 11 machines, and even thou they all have 80 GB hard drives, they are different brands, so there might be some small differences, and I read in another thread that you should always be careful not to deploy an image that is bigger than the hdd (which kind of makes sense).

[quote=“need2, post: 26488, member: 21891”]Just to clarify, I was asking if this was an OEM Windows install you were imaging or a clean install you did yourself from an install medium.[/quote]

Clean Windows install using the trial ISO downloaded from MSDN.

[quote=“Tom Elliott, post: 26484, member: 7271”]From what I can see, it looks like that image is now a container for both a Windows 7 (or possibly image as multipartition single disk (the d1 files) AND single disk resizeable. It seems like it hasn’t created the partition tables properly and for that I have no quick answer.

A few questions, when you uploaded the file, did it display which partitions it was copying? My guess is Windows 8 image a slightly off at the moment because you’re using Windows 8 in MBR mode, while the “mbr” from windows 8 within the init is not set to give the 100mb part and the data part. Just my guesses at whats wrong. Maybe try changing the OS to Windows 7 and try deploying the task again?

Deploy, for the purposes of FOG is a generic term meaning -> sending of a task. Much as a squad of solders get’s deployed to various regions in the world. Whether they’re deployed from the US to IRAQ, or from Germany to the US. Download means to put the image on the client, Upload means to grab the image from the client.[/quote]

When uploading, it uploaded /dev/sda1 which seemed legit (windows install disk reports ~350mb) because it finished in a quite a short while (don’t have the exact time, and I’m not very good with time estimates as my spouse is telling me), then we had /dev/sda2 which reported to upload just over 9GB (this being the reason I was asking earlier about compression). I did pay attention, and it didn’t throw any errors. If it matters with anything, the Windows in question is a 8.1 sysprep’ed and shutdown. As for the deployment part, /dev/sda1 seems to work fine, but when it reaches /dev/sda2, Partclone loads, then throws a 2 words error (can’t remember exactly) from outside Partclone, Partclone dies, then I get the “no such file or directory” message.
If it helps in any way, I am willing to provide access to the machines, or send you any information that might help in any way with closing this issue.

[quote=“Tom Elliott, post: 26480, member: 7271”]What’s worrying me is the fact that you have d1p1.img d1p2.img AND rec.img.000 and sys.img.000

What type of image is this? Multi-Part Single Disk, or Single Disk Resizable?[/quote]

“NTFS Only, Resizable” and Windows 8 for OS.

[quote=“Tom Elliott, post: 26470, member: 7271”]When you uploaded the image, did all of the data get copied properly?

Image location is:
/images/<IMAGENAME>

It sounds like, to me, the image uploaded, but didn’t create/copy the proper MBR file.[/quote]

need2, this is a clean 0.33b install, but I updated it several times. I can do a fresh install if that is the issue.

Tom, this is what I have:
[CODE]:~$ ls -lah /images/testW1/
total 5.1G
drwxrwxrwx 2 root root 4.0K May 2 16:07 .
drwxrwxrwx 6 root root 4.0K May 2 16:23 …
-rwxrwxrwx 1 root root 512 Apr 26 15:45 d1.mbr
-rwxrwxrwx 1 root root 222M Apr 26 15:46 d1p1.img
-rwxrwxrwx 1 root root 1.5G Apr 26 15:54 d1p2.img
-rwxrwxrwx 1 root root 13M May 2 16:07 rec.img.000
-rwxrwxrwx 1 root root 3.4G May 2 16:22 sys.img.000
[/CODE]

I updated to r1556, and now [FONT=Consolas]FOGMulticastManager[/FONT] works. However, I still cannot deploy because of:

[CODE]* Performing Clean up (Stage 1)…Done

• Performing Clean up (Stage 2)…error: /dev/sda2: No such file or directory[/CODE]

Any help please?

[quote=“Tom Elliott, post: 26453, member: 7271”]When you “deployed” the image, did you do a unicast or multicast job? It multicast, check that the FOGMulticastManager service is running.

There is compression. The default is set to 9, but you can change the compression rating on the FOG GUI under FOG Boot Settings tab in FOG Settings. 9 is best compression, slowest upload, 0 is worst compression, fastest upload.[/quote]

I was trying to do a multicast deploy (is this the difference between the deploy and download buttons ?), so I investigated on the FOGMulticastManager.

[CODE]root@gen8:~# /etc/init.d/FOGMulticastManager start

• Starting FOG Computer Imaging Solution: FOGMulticastManager [fail]
  [/CODE]

and since I couldn’t find any logs, I also tried the bash debug (-x). I got this:
[CODE]root@gen8:/etc/init.d# /etc/init.d/FOGMulticastManager start

• PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/bin:/usr/sbin
• DAEMON=/opt/fog/service/FOGMulticastManager/FOGMulticastManager
• NAME=FOGMulticastManager
• PIDFILE=/var/run/fog/FOGMulticastManager.pid
• DESC=‘FOG Computer Imaging Solution’
• test -f /opt/fog/service/FOGMulticastManager/FOGMulticastManager
• . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in ‘$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)’
  ++ ‘[’ -r /lib/lsb/init-functions.d/20-left-info-blocks ‘]’
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in ‘$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)’
  ++ ‘[’ -r /lib/lsb/init-functions.d/50-ubuntu-logging ‘]’
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ ‘[’ -e /etc/lsb-base-logging.sh ‘]’
  ++ true
• case “$1” in
• log_begin_msg ‘Starting FOG Computer Imaging Solution: FOGMulticastManager’
• log_daemon_msg ‘Starting FOG Computer Imaging Solution: FOGMulticastManager’
• ‘[’ -z ‘Starting FOG Computer Imaging Solution: FOGMulticastManager’ ‘]’
• log_use_fancy_output
• TPUT=/usr/bin/tput
• EXPR=/usr/bin/expr
• ‘[’ -t 1 ‘]’
• ‘[’ xxterm ‘!=’ x ‘]’
• ‘[’ xxterm ‘!=’ xdumb ‘]’
• ‘[’ -x /usr/bin/tput ‘]’
• ‘[’ -x /usr/bin/expr ‘]’
• /usr/bin/tput hpa 60
• /usr/bin/tput setaf 1
• ‘[’ -z ‘]’
• FANCYTTY=1
• case “$FANCYTTY” in
• true
• /usr/bin/tput xenl
  ++ /usr/bin/tput cols
• COLS=237
• ‘[’ 237 ‘]’
• ‘[’ 237 -gt 6 ‘]’
  ++ /usr/bin/expr 237 - 7
• COL=230
• log_use_plymouth
• ‘[’ n = y ‘]’
• plymouth --ping
• printf ’ * Starting FOG Computer Imaging Solution: FOGMulticastManager ’

• Starting FOG Computer Imaging Solution: FOGMulticastManager ++ /usr/bin/expr 237 - 1

• /usr/bin/tput hpa 236
  + printf ’ ’
  ++ dirname /var/run/fog/FOGMulticastManager.pid
• mkdir -p /var/run/fog
• ‘[’ ‘!’ -f /var/run/fog/FOGMulticastManager.pid ‘]’
• log_end_msg 1
• ‘[’ -z 1 ‘]’
• ‘[’ 230 ‘]’
• ‘[’ -x /usr/bin/tput ‘]’
• log_use_plymouth
• ‘[’ n = y ‘]’
• plymouth --ping
• printf ‘\r’
• /usr/bin/tput hpa 230
  + ‘[’ 1 -eq 0 ‘]’
• printf ‘[’
  [+ /usr/bin/tput setaf 1
• printf fail
  fail+ /usr/bin/tput op
• echo ‘]’
  ]
• return 1
• exit 0
  [/CODE]

As an alternative, I also tried the download button (this is probably unicast). After some minor successes, one line said:
[CODE]* Performing Clean up (Stage 1)…Done

• Performing Clean up (Stage 2)…error: /dev/sda2: No such file or directory
  [/CODE]
  Isn’t fog creating the partitions before deployment? I must be missing something here, because it deployed fine on /dev/sda1 (windows boot partition).

And I now checked the apache error log. Nothing appears when Partclone hangs.

I hope this isn’t something too trivial (like the last time), but here goes:
I installed Windows 8.1, installed .net 3.5, fog service, sysprep-ed (simple generalize), imaged the disk (NTFS, resizable). When I tried to deploy, I got this (see pic) and it stucks here. Any hint on what I might be doing wrong?

Second question: is there any compression when uploading the image? PartClone said the image has over 8GB when uploading, but on the server I got
[CODE]root@gen8:/images# du -ch testW1/
5.1G testW1/
5.1G total[/CODE]

[url=“/_imported_xf_attachments/0/698_2014-05-02 16.27.04.jpg?:”]2014-05-02 16.27.04.jpg[/url]