Image corrupted after upload to server

[danilopinotti]

Hello,
recently I came across a problem that have been giving a lot of headaches.
I have a computer I use to create Image of Debian. When I give upload the image to the server, the computer image stops working and displays the following message: “Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key.”
NOTE: The image that went to the server also has this problem if I try to use it on some other computer.
NOTE 2: The image I am trying to create is Debian. With another image (eg Ubuntu) this problem does not appear.
NOTE 3: The problem started only appear for a while now and just that image (Debian 7).
NOTE 4: You tried to delete the server image and climb it again, but the error persisted.

I use FOG 4469

[Wayne Workman]

Are the firmware settings different on the destination machine and source machine? Especially the HDD operation modes ?

[danilopinotti]

They are perfectly equals. As i said, just the fact that I raise the image to the server, the system will be corrupted.

[Wayne Workman]

@danilopinotti
FOG currently only supports resizing Ext4 type partitions… so if you weren’t using Ext4, I’d suggest a non-resizable image.

Is the source Debian machine a server? Does it happen to have RAID? There are special kernel arguments for RAID.

[danilopinotti]

Yes, the partition is the type Ext4. For server i use Ubuntu 14.04 without RAID

[Wayne Workman]

@danilopinotti Can you post the output of the image directory?

ls -laht /images/NameOfImage

and also, ls -lahRt /images/dev

[danilopinotti]

@Wayne-Workman

**ls -laht /images/ItautecDebian022015/**
total 7,7G
drwxrwxrwx 14 root root 4,0K Out 21 15:52 ..
drwxrwxrwx  2 root root 4,0K Out 21 15:52 .
-rwxrwxrwx  1 root root 7,7G Out 21 15:52 d1p2.img
-rwxrwxrwx  1 root root   47 Out 21 15:46 d1.original.swapuuids
-rwxrwxrwx  1 root root   31 Out 21 15:44 d1.original.fstypes
-rwxrwxrwx  1 root root  18K Out 21 15:44 d1.mbr
-rwxrwxrwx  1 root root  324 Out 21 15:44 d1.sgdisk.original.partitions
-rwxrwxrwx  1 root root    2 Out 21 15:44 d1.fixed_size_partitions

**ls -lahRt /images/dev**
/images/dev:
total 12K
drwxrwxrwx  3 root root 4,0K Out 21 15:52 .
drwxrwxrwx 14 root root 4,0K Out 21 15:52 ..
drwxrwxrwx  2 root root 4,0K Ago 13 12:09 b4b52f50bfc8
-rwxrwxrwx  1 root root    0 Jul 29 09:47 .mntcheck

/images/dev/b4b52f50bfc8:
total 8,0K
drwxrwxrwx 3 root root 4,0K Out 21 15:52 ..
drwxrwxrwx 2 root root 4,0K Ago 13 12:09 .

Mod edited to use code boxes.

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