Posts made by Scott B

Recently tried upload an image on a PC we have done a ton of times before. Now its hanging on “Saving original disk/parts UUIDs”. Just sits there. Suggestions?

Partclone Image
Fog 1.3.0-RC-8
Unbuntu 14.04

@Wayne-Workman said in FOG Hangouts - What time is good for you?:

@Scott-B @Raymond-Bell @Bob-Henderson @RobertD Where were you guys?

Sorry, stupid life got in the way.

I am also seeing this.

A weeknight would be best for me. 7ish but can be flexible for almost anytime.

I created a test image as requested as a single disk non resizable. Info below. When deployed it worked fine.

root@FOG:/images/TEST1# ls -la
total 14356996
drwxrwxrwx  2 root root        4096 Jun  7 13:53 .
drwxrwxrwx 20 fog  root        4096 Jun  7 13:53 ..
-rwxrwxrwx  1 root root     1048576 Jun  7 13:40 d1.mbr
-rwxrwxrwx  1 root root    10371828 Jun  7 13:40 d1p1.img
-rwxrwxrwx  1 root root 14690122936 Jun  7 13:53 d1p2.img
-rwxrwxrwx  1 root root         190 Jun  7 13:40 d1.partitions

root@FOG:/images/TEST1# cat d1.partitions
label: dos
label-id: 0x9132375b
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=    82857984, type=7

@Sebastian-Roth said in Target partition is smaller than source:

Now that I have done some testing I don’t think this is the same issue than @robza has. He’s got a totally different partition layout (which I mentioned already) which we don’t do a very good detection on yet. His problem will never be fixed by re-trying I am sure! Will get to this later.

Now back to @Scott-B’s issue. Your partition layout is very simple and should not cause any trouble. Don’t get me wrong. Not saying that I don’t believe you but I need to kindly ask you to give us some more information. The picture you posted is Roger Saffle’s. While I don’t mind reusing anyones pictures we really need your information here to figure out what’s going wrong (with your image/partition layout).

So can you please to me a favor: Create a new image definition (so you don’t need to mess with your working ones) and make it Single disk - non-resizable. Upload from the same client you have before (so we have the same information in d1.partitions). Then deploy this new image in debug mode to one of your clients. If you get an error, please take a picture and run the following command when you get back to the command shell: sfdisk -d /dev/sda (again take a picture). If it does not fail could you please try over and over till you see the error.

I can, but won’t be able to get to it till Monday. @Roger-Saffle and I work together. Same machines in question.

@Wayne-Workman 0_1464981879587_4000SYSPREP.zip

@Wayne-Workman , @Tom-Elliott, @Sebastian-Roth

@Scott-B Would you still be so kind to answer my question(s) so I might be able to find the issue to get it fixed eventually?

No problem.

1. I start on a VM that has a 40GB hdd. I install windows and make a sysprep image. I image that up to FOG. I call it sysprepmaster in FOG.

2. I deploy that sysprepmaster image to the pcs we have in our classrooms. We are lucky to only have 5 basic models. That sysprepmaster comes down to those pcs with no issue.

3. On each of those specific types of PCs I make any other changes that need done specific to their model or use. Then I run sysprep to make and image for each one of them. 4000SYSPREP or DAK81SYSPREP for example. These machines have different hard drive sizes, 80GB in the case of the 4000SYSPREP which is where my previous post examples come from.

4. Finally I pull down the model specific images on the other similar models. That’s where I see the error in question.

What other information can I give you to help?

@Wayne-Workman said in Target partition is smaller than source:

@Scott-B Can you try a resizable image? If for no other purpose than to see the result?
@Scott-B Remember after changing that on the image you need to re-upload. Or just create a new image.

I made new images and made them realizable. They all seem to be working just fine that way so I’ll go with it.

@Wayne-Workman Sure, I’ll report back what I find.

@Wayne-Workman The master image with 99% of our settings/changes are done on the VM. Then that image is installed on one of each type of host (5 main ones). Then any specifics for that type are made and then syspreped again to create a master for that specific model.

@Wayne-Workman said in Target partition is smaller than source:

/dev/sda2 is the second partition. It’s possible the destination drive is a little smaller. One sector less would break it, but I think you have a hand-full of sectors smaller in this case.

Pop the hood on the reference machine and troubled machine - compare HDDs, look at sector count per head/cylinder. Look at model numbers.

Just for testing I made the image on an 80GB drive and the destination workstation is a 250GB. The sysprep host is a VM based on a 40GB drive.

This issue was originally brought up by @Roger-Saffle in THIS THREAD but we didn’t want to hijack the OP’s original post.

We have noticed an issue when pulling down our images where we receive the error below at which point it reboots in 1 min. If you let host try and try again, the images eventually does download. Could be on 1 reboot, could be on 10, but so far eventually it does finish.

"Target partition size (XXXXXX MB) is smaller than source (XXXXXX MB).  Use option -C to disable size checking.

As seen in this image as well.

All of our images are now Win10x32 set to “Multiple Partition Image - Single Disk (Not Resizable)” using Partclone. This is also our first time using sysprep in the image creation so I don’t know if we are doing something wrong in its setup that could cause this.

We have been testing mostly with our HP 4000 desktops, info on their image is below.

root@FOG:/images/4000SYSPREP# ls -al
total 9917704
drwxrwxrwx  2 root root        4096 Jun  2 13:09 .
drwxrwxrwx 19 fog  root        4096 Jun  2 13:09 ..
-rwxrwxrwx  1 root root     1048576 Jun  2 12:59 d1.mbr
-rwxrwxrwx  1 root root    10370946 Jun  2 12:59 d1p1.img
-rwxrwxrwx  1 root root 10144291774 Jun  2 13:09 d1p2.img
-rwxrwxrwx  1 root root         190 Jun  2 12:59 d1.partitions
root@FOG:/images/4000SYSPREP#

root@FOG:/images/4000SYSPREP# cat d1.partitions
label: dos
label-id: 0x9132375b
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=   155273392, type=7

FOG SVN: 7959
OS: Ubuntu 14.04.4 LTS

@Wayne-Workman said in Protect Host from Imaging:

@Scott-B The way I would handle that is by removing that one computer from the group - permanently. You could tell this to any I.T. staff you have. At my current job, nothing is stored locally; We blast everything every year no ifs-ands-or-buts.

Nothing should be stored locally… but we all know the only copy of that PowerPoint was the one place it shouldn’t have been.

@Wayne-Workman said in Protect Host from Imaging:

I’m assuming this happened to you. There is a confirmation page for imaging. And using the iPXE menu in network booting, you have to supply credentials to image.

I was thinking for for say a lab where you want to image 30 desktops, but for the teacher pc. There all in the same room, same type of pc, get the same printers, but the teacher PC has the smartboard tools or a slew of local files they will be using the next morning ect…

It would be nice if you could protect a host from being imaged the way an image can be protected from being overwritten.

SVN: 7947

When using the create task button for either creating an image or pulling down an image the blue button to do so does nothing. Tried in Chrome and IE.

@Jbob said in no reboot after image, rename, add to AD:

Well I am confused. According to that log everything worked perefectly…

I’m about to pull down a few other images. I’ll post back.

Here is a fog log from one of our hosts. I did need to manually reboot it each time.

 5/26/2016 12:03 PM Main Overriding exception handling
 5/26/2016 12:03 PM Main Bootstrapping Zazzles
 5/26/2016 12:03 PM Controller Initialize
 5/26/2016 12:03 PM Entry Creating obj
 5/26/2016 12:03 PM Controller Start

 5/26/2016 12:03 PM Service Starting service
 5/26/2016 12:03 PM Bus Became bus server
 5/26/2016 12:03 PM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 5/26/2016 12:03 PM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 5/26/2016 12:03 PM Client-Info Version: 0.10.6
 5/26/2016 12:03 PM Client-Info OS:      Windows
 5/26/2016 12:03 PM Middleware::Authentication Waiting for authentication timeout to pass
 5/26/2016 12:03 PM Middleware::Communication Download: http://ServerIPAddress/fog/management/other/ssl/srvpublic.crt
 5/26/2016 12:03 PM Data::RSA FOG Server CA cert found
 5/26/2016 12:03 PM Middleware::Authentication Cert OK
 5/26/2016 12:03 PM Middleware::Authentication ERROR: Could not get security token
 5/26/2016 12:03 PM Middleware::Authentication ERROR: Could not find file 'C:\Program Files\FOG\token.dat'.
 5/26/2016 12:03 PM Middleware::Communication POST URL: http://ServerIPAddress/fog/management/index.php?sub=requestClientInfo&authorize&newService
 5/26/2016 12:03 PM Middleware::Response Success
 5/26/2016 12:03 PM Middleware::Authentication Authenticated


 5/26/2016 12:03 PM Bus Registering ParseBus in channel Power
 5/26/2016 12:03 PM Middleware::Communication URL: http://ServerIPAddress/fog/management/index.php?sub=requestClientInfo&mac=18:A9:05:1B:09:B8||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
 5/26/2016 12:03 PM Middleware::Response Success
 5/26/2016 12:03 PM Middleware::Communication URL: http://ServerIPAddress/fog/service/getversion.php?clientver&newService&json
 5/26/2016 12:03 PM Middleware::Communication URL: http://ServerIPAddress/fog/service/getversion.php?newService&json

 5/26/2016 12:03 PM Service Creating user agent cache
 5/26/2016 12:03 PM Middleware::Response Module is disabled globally on the FOG server
 5/26/2016 12:03 PM Middleware::Response No Printers

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 5/26/2016 12:03 PM Client-Info Client Version: 0.10.6
 5/26/2016 12:03 PM Client-Info Client OS:      Windows
 5/26/2016 12:03 PM Client-Info Server Version: 7845
 5/26/2016 12:03 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 5/26/2016 12:03 PM Client-Info Client Version: 0.10.6
 5/26/2016 12:03 PM Client-Info Client OS:      Windows
 5/26/2016 12:03 PM Client-Info Server Version: 7845
 5/26/2016 12:03 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 5/26/2016 12:03 PM Client-Info Client Version: 0.10.6
 5/26/2016 12:03 PM Client-Info Client OS:      Windows
 5/26/2016 12:03 PM Client-Info Server Version: 7845
 5/26/2016 12:03 PM Middleware::Response Success
 5/26/2016 12:03 PM HostnameChanger Checking Hostname
 5/26/2016 12:03 PM HostnameChanger Removing host from active directory
 5/26/2016 12:03 PM HostnameChanger The machine is not currently joined to a domain, code =  2692
 5/26/2016 12:03 PM HostnameChanger Renaming host to 5800-066-023
 5/26/2016 12:03 PM Power Creating shutdown command in 60 seconds
 5/26/2016 12:03 PM Bus {
  "self": true,
  "channel": "Power",
  "data": "{\r\n  \"action\": \"request\",\r\n  \"period\": 60,\r\n  \"options\": 2,\r\n  \"command\": \"/r /c \\\"FOG needs to rename your computer\\\" /t 0\",\r\n  \"message\": \"This computer needs to perform maintenance.\"\r\n}"
}
 5/26/2016 12:03 PM Bus Emmiting message on channel: Power
------------------------------------------------------------------------------

 5/26/2016 12:03 PM Service Power operation being requested, checking back in 30 seconds
 5/26/2016 12:04 PM Service Power operation being requested, checking back in 30 seconds
 5/26/2016 12:04 PM Power Creating shutdown request
 5/26/2016 12:04 PM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
 5/26/2016 12:04 PM Service Power operation being requested, checking back in 30 seconds
 5/26/2016 12:04 PM Bus {
  "self": true,
  "channel": "Power",
  "data": "{\r\n  \"action\": \"shuttingdown\"\r\n}"
}
 5/26/2016 12:04 PM Bus Emmiting message on channel: Power

@Jbob said in no reboot after image, rename, add to AD:

I’ll get a full fog.log. Does one have to reset the encryption on a host each time its imaged or should the imaging process get around that?