iPXE boot problem

The error “This is not partclone image” does not sound very healthy. I guess the image is corrupt. Can you run this command on the FOG server ls -al /images/mikreleaseup and post the output here. Anyhow, I guess it would be a good idea to capture this image from your host again. When and how was this image created?

Bcetinkaya

@Sebastian-Roth

I don’t have /images directory … The image is an upload of a master, you think the image is corrupted ?

Sebastian Roth

Well at least the second partition seams to have an issue.

Where are you images stored then?? /images is the default path used by FOG.

Bcetinkaya

This post is deleted!

Bcetinkaya

@Bcetinkaya

OK I found the directory it was /opt/images

[root@fog ~]# cd /opt/images
[root@fog images]# ls -al
total 40
drwxrwxrwx 9 fog root 4096 Jan 28 16:17 .
drwxr-xr-x 12 root root 4096 Dec 24 11:27 …
drwxr-xr-x 2 root root 4096 Jan 8 17:39 DELLPRECISIONWIN7V4c
drwxrwxrwx 2 fog root 4096 Jan 28 16:17 dev
drwxrwxrwx 2 root root 4096 Jun 9 2015 mikrelease310
drwxrwxrwx 2 root root 4096 Dec 9 16:39 mikrelease310render
drwxrwxrwx 2 root root 4096 Jan 28 16:16 MikreleaseTEST
drwxrwxrwx 2 root root 4096 Dec 9 16:19 mikreleaseup
-rw-r–r-- 1 root root 0 Jan 24 2014 .mntcheck
drwxrwxrwx 2 root root 4096 Nov 27 2014 w7milpcmaster

I uploaded a new Image from a Master (MikreleaseTEST) but i still have the message error for the 2nd partition…

Sebastian Roth

And you don’t see any errors while uploading the image again?? Please show us what you have in those directories ls -al /opt/images/MikreleaseTEST /opt/images/mikreleaseup

Bcetinkaya

@Sebastian-Roth

no message error when I uploaded the image again …

[root@fog ~]# ls -al /opt/images/mikreleaseup
total 149280
drwxrwxrwx 2 root root 4096 Dec 9 16:19 .
drwxrwxrwx 8 fog root 4096 Jan 28 17:01 …
-rwxrwxrwx 1 root root 0 Dec 9 16:18 d1.has_grub
-rwxrwxrwx 1 root root 1048576 Dec 9 16:18 d1.mbr
-rwxrwxrwx 1 root root 111009518 Dec 9 16:18 d1p1.img
-rwxrwxrwx 1 root root 20 Dec 9 16:18 d1p2.img
-rwxrwxrwx 1 root root 40625085 Dec 9 16:19 d1p4.img

[root@fog ~]# ls -al /opt/images/MikreleaseTEST/
total 151012
drwxrwxrwx 2 root root 4096 Jan 29 09:06 .
drwxrwxrwx 9 fog root 4096 Jan 29 09:06 …
-rwxrwxrwx 1 root root 0 Jan 29 09:05 d1.has_grub
-rwxrwxrwx 1 root root 1048576 Jan 29 09:05 d1.mbr
-rwxrwxrwx 1 root root 111009517 Jan 29 09:05 d1p1.img
-rwxrwxrwx 1 root root 20 Jan 29 09:05 d1p2.img
-rwxrwxrwx 1 root root 42394069 Jan 29 09:06 d1p4.img

Sebastian Roth

Why is partition two image file (d1p2.img) really small?? And why is d1p3.img missing? What does your partition scheme on this client machine look like? I am confused.

Has uploading and downloading an image ever worked with this machine? I doubt it.

Bcetinkaya

@Sebastian-Roth

I have no problem with the machine I uploaded the image, I can show you all the partitions in the computer with a “df -h” :
there is no /dev/sda3,I suppose that’s why there is no d1p3. img file in /opt/images/****

Filesystem Size Used Avail Use% Mounted on
/dev/sda2 39G 11G 26G 29% /
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 0 32G 0% /dev/shm
tmpfs 32G 1.2M 32G 1% /run
tmpfs 32G 0 32G 0% /sys/fs/cgroup
/dev/sda4 189G 102M 180G 1% /datas
/dev/sda1 477M 114M 335M 26% /boot
nas.fx.fr:/apps/ 300G 262G 39G 88% /s/apps
nas.fx.fr:/xchange 100G 1.4G 99G 2% /s/xchange
nas.fx.fr:/Prods 36T 34T 3.0T 92% /s/prods

Sebastian Roth

Showing the partitions with fdisk would be more interesting. Can you please run fdisk -l /dev/sda as root on this system and post the output here?

df shows that /dev/sda2 is mounted as the root partition (/). So this is a really important part af your system and should not be only a few kilobyte as an image file. What do you see when uploading an image when partclone is coming up with /dev/sda2?? Does it take several minutes or just skipping away in seconds?

Bcetinkaya

@Sebastian-Roth

[root@pc101 ~]# fdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000a6794

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 82724863 40849408 83 Linux
/dev/sda3 82724864 97656831 7465984 82 Linux swap / Solaris
/dev/sda4 97656832 500117503 201230336 83 Linux

That’s what I have during the upload of the 2nd parition:

https://www.dropbox.com/s/xzxyta9dw2xr8kb/Photo 29-01-16 11 37 46.jpg?dl=0

https://www.dropbox.com/s/xh7rk8n1nijjzfb/Photo 29-01-16 11 37 52.jpg?dl=0

But I have this now on the Fog server :

[root@fog MikreleaseTEST]# ls -al
total 3805676
drwxrwxrwx 2 root root 4096 Jan 29 11:37 .
drwxrwxrwx 9 fog root 4096 Jan 29 11:38 …
-rwxrwxrwx 1 root root 0 Jan 29 11:30 d1.has_grub
-rwxrwxrwx 1 root root 1048576 Jan 29 11:30 d1.mbr
-rwxrwxrwx 1 root root 111009523 Jan 29 11:30 d1p1.img
-rwxrwxrwx 1 root root 3738781709 Jan 29 11:37 d1p2.img
-rwxrwxrwx 1 root root 42333526 Jan 29 11:38 d1p4.img

You think it’s ok now ? d1p2.img is bigger than before

Sebastian Roth

Well, sda3=SWAP, ok that’s fine then (should have thought about this earlier). But what changed now??? d1p2.img looks a lot better now!! What is different from capturing last time?

Bcetinkaya

@Sebastian-Roth

Last time, the uploading was faster than now … I didn’t really notice an uploading of the 2nd parition i didn’t try to fog a computer yet … You think it’s time to test this image ?

Sebastian Roth

Well it looks better - as I said. But it’s up to you to give it a try deploying it to another computer and see if it boots up properly afterwards.

Bcetinkaya

@Sebastian-Roth

It works now !!! Thank you very much. thanks to you, I understand “Fog Server” better than before this issue

iPXE boot problem

226

11.7k

17.1k

154.6k