Image corrupted after upload to server

[Wayne Workman]

@danilopinotti It would appear that d1p1.img is missing…

Can you try a non-resizable image type, and try to re-upload ?

[Tom Elliott]

@Wayne-Workman I believe, on trunk, if the first partition is of type de, we don’t do anything with it as a safety precaution.

[Wayne Workman]

@Tom-Elliott Can you elaborate? What is a de partition?

[Tom Elliott]

@Wayne-Workman that’s the identifier in Linux for the dell recovery partition.

[Sebastian Roth]

Why shouldn’t we also capture and deploy this partition using partclone.imager ??

[Tom Elliott]

@Uncle-Frank because many times it’s an awkward size. Adjusting this partition in any way tends to break booting the system in whole.

[Sebastian Roth]

@Tom-Elliott Well, sure! You are absolutely right. I wasn’t aware of this being a resizable image. I tend to overlook this as we are mostly using non-resizable images here at work!

[Wayne Workman]

@Tom-Elliott said:

@Uncle-Frank because many times it’s an awkward size. Adjusting this partition in any way tends to break booting the system in whole.

Is it at all possible to verify (beyond doubt) that it is a Dell Recovery partition and simply upload the partition without attempting to resize it?

A partially re-sized image is much better than an inoperable image.

[danilopinotti]

@Wayne-Workman
The strange thing is that in my case, I do not use Dell computers (if it is a chance) and it only happens with this in particular. If I put an Ubuntu on the same computer, this works with FOG.

[Wayne Workman]

@danilopinotti said:

@Wayne-Workman
The strange thing is that in my case, I do not use Dell computers (if it is a chance) and it only happens with this in particular. If I put an Ubuntu on the same computer, this works with FOG.

Yes, but are you completely deleting every single pre-existing partition before you install Ubuntu or Debian ?

[danilopinotti]

@Wayne-Workman
No. I put another image on it with Ubuntu.
Before I could climb this (faulty) for FOG, but now does not. Now happens that I described.

[Wayne Workman]

@danilopinotti So you’re dual booting? It seems that English isn’t your mother tongue, look at this Wikipedia article to see what I mean by “dual booting” https://en.wikipedia.org/wiki/Multi-booting

[danilopinotti]

@Wayne-Workman

Sorry for my english.

I put an image from another computer (an image with Ubuntu) that this was giving problem. With that, I noticed that the problem is in the Debian image and not on the computer.
Previously, this image Debian did not have this problem. I have no idea why.
Did not do Dual Boot or anything else.

I’m better at reading English than to write, so write these means strange phrases.

[Wayne Workman]

@danilopinotti You’re English is good enough.

You said that previously, the Debian image worked?

What was the last SVN revision that it worked with? And it has previously worked with Debian 7 specifically?

[danilopinotti]

@Wayne-Workman Thank you

I don’t remember when I created the image (when it worked) I’ve used the Trunk or still using 1.2.0

[Wayne Workman]

@danilopinotti Is it possible for you to test using 1.2.0 ?

[danilopinotti]

@Wayne-Workman
Today is not possible but tomorrow i can try to arrange this.

[Wayne Workman]

@danilopinotti If you can get it to work in 1.2.0, then it’s just a matter of slowly upgrading that 1.2.0 server through the svn revisions until it no longer works. It would be best if you could build the 1.2.0 server inside of a virtual machine so you can take snapshots before each update and roll back if needed, in order to locate exactly what svn revision fog stops working for this situation.

If we can identify exactly which svn version it stops working with, then it will be easy for the @Developers to fix it.

[danilopinotti]

This post is deleted!

[danilopinotti]

@Wayne-Workman
It would have somewhere that explains how to do to go giving these small changes in SVN?
What is the SVN fog 1.2.0?