Images From 1.2 not working on 1.3

[Grizzly]

Sorry. I’ll try to provide some more information. The picture attached is what it says when it’s done imaging. After that it reboots but tries to load our encryption software which isn’t apart of the base images. After it tries to load the encryption software the computer just reboots.

[x23piracy]

@Grizzly said in Images From 1.2 not working on 1.3:

Sorry. I’ll try to provide some more information. The picture attached is what it says when it’s done imaging. After that it reboots but tries to load our encryption software which isn’t apart of the base images. After it tries to load the encryption software the computer just reboots.

ok and that worked before? the only difference is the fog version?
have you changed from bios to efi or vice versa?
@tom-elliott is fog in newer versions > 1.2.0 touching the mbr in some way?

Regards X23

[Grizzly]

@x23piracy Yes this image was working fine before on 1.2. When we finish a couple other jobs in a bit I’ll re-image again using the old server just to triple check.

We haven’t switched any firmware booting between the upgrades.

Thanks for the help.

[Tom Elliott]

@x23piracy no touching MBR.

[x23piracy]

@Tom-Elliott said in Images From 1.2 not working on 1.3:

@x23piracy no touching MBR.

do you have an idea while reading through that thread? the encryption software is maybe the prob?
@Grizzly could you compare partition layouts between working and not working after deployment?

[Tom Elliott]

@x23piracy that’s what I’m thinking. What’s being installed? OS ? What’s the disk layout look like? Is secure boot enabled? Is it only this system or any receiving image?```
Insert Code Here

[Grizzly]

@Tom-Elliott None of the images are working from the copy over from 1.2 to 1.3 but I’ll test on a couple machines here in a bit. I have that same model from earlier as well as another I can test with again. If I do a capture and deploy from 1.3 it works fine though, but I’d rather not go back through our images and recapture if I can help it.

[Grizzly]

@x23piracy I have two machines that I’ll image here in a bit with 1.2 and then get back to you with the partition layout in Windows. One is the same model in the picture from before and one is a different model.

[Tom Elliott]

@Grizzly I believe the problem, then, is related to how I’m laying out the partitions in 1.3.5 vs. how they were being applied in 1.2.0.

This last week I’ve been pretty heavy in fixing the resizing script.

[Grizzly]

@x23piracy Well I’m not sure what is different but now it just worked. The partitions are a single partition. I just imaged one with the 1.2 server then the 1.3 and the imaging went through correctly. I’m wondering if it was because the other computer we tested with was previously encrypted or maybe the SSD was bad? I’ll have to wait till we get another machine in for re-imaging that is encrypted although this wasn’t a problem in 1.2.

I’m doing one more machine now and hopefully that works. I apologize for wasting time on this.

Thanks.

[Grizzly]

@Grizzly I just tried on another machine with a different image. I got the same message as before saying the clone was successful but on reboot it’s saying no boot device found, please install an operating system.

I’m at a loss of what might have happened. I just compared file sizes of the images and they look to be fine.

[Grizzly]

@Tom-Elliott Can I provide anymore information in order to help out with this?

[Tom Elliott]

@Grizzly while it suvks mind updating (reinstalling) and retrying the upload again? Unless I’m mistaken it was brought to my attention that the capture process was accidentally shifting start position. While I don’t think this is the issue you are seeing I don’t want other issues happening.

[Tom Elliott]

The problem you are describing may be due to variance in how the image was captured vs how it’s being applied.

This might include things like uefi vs legacy, most common problem I see with the blinking cursor. If the image was captured from legacy system but the booting system is in UEFI mode it has no way of booting the system. Similarly in reverse this will occur.

Maybe possible from switching SATA modes, ATA vs ahci vs raid.

[Grizzly]

@Tom-Elliott I can upload a new capture. I did this a couple weeks ago and it seemed to work out fine. If this is the solution I can just image with 1.2 then capture again with 1.3. We’re moving to Windows 10 machines with UEFI soon so I need to get things switched over and that working as well.

I’m not changing any of the SATA modes. The machines are all setup in the same manner using legacy.

[Grizzly]

@Tom-Elliott Looks like the RC11 update has fixed this at least with my legacy 4530s image. I’ll be doing a couple more tests with our other models as I can get my hands on them to make sure.

Is there another section where you would like me to report this?

[Wayne Workman]

@Grizzly said in Images From 1.2 not working on 1.3:

Is there another section where you would like me to report this?

Here is fine as long as the topic doesn’t stray from your original post’s problem.

[Grizzly]

@Grizzly Also tested this on an Lenovo X230 image I created in 1.2 that works as well. Thanks for the fixes!