d1.partitions
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 280064, type=7, bootable
/dev/sda2 : start= 282112, size= 976491008, type=7
d1.minimun.partitions
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 58102, type=7, bootable
/dev/sda2 : start= 282112, size= 976491008, type=7
d1.fixed_size_partitions
:2
I have two sizes of disks (250gb ssd and 500gb) on my clients.
Time ago when I prepared the image on the 500gb drives and restored on the 250gb disks I was not able to receive the clone image created on big drives to the small drives…
I use “1 drive resize” option . I am not sure, but I remember that the problem was not happening since a revision that solved this.
But now the problem has returned!. I have tried partclone +gzip later partclone+ zstd and the problem remains.
When I clone the client I receive from partclone the message :
If I prepare the image on a 250 disk, the problem (off course)dissapears. the empty sizes of the drives are enough to work (the image size is 150 gb uncompressed and 79gb compressed on the server)
Maybe the -c option was out and has returned?
tested in unicast deploy task and same problem and message
yes I have (in the same network )the 1.2.0 production server, but is a complete server with their storage node. The problem happens on my test server with only three clients. There is no connection between both servers.
I have the same problem and message.
I have only one node, one server and one group. And the multicast works ok if I first create a session and later join the computers to it in the ipxe menu.
I have RC15 and ubuntu 16.04
Sorry to all
The clients get the IP from the isc-dhcpd-server on the fog server . I don’t know why was this service running. Removing that software solved the problem.
We have three dhcp servers. They have different clients over the network . All them provide a static IP to a given MAC. Our macs are stored on a shared database. We have a monitored network so we think we don’t have rogue DHCP servers.
We have a suspect. Is possible that some of the clients kernel linux are using avahi or something similar to get the IP?
Hello
I have fog 1.20 on a ubuntu 14.04 server . My organization provides a dhcp server with static ip for every mac. So I only provide the tftpd server to the clients. I have the default installation for this on the server. The clients are using the official published kernel 3.19.3 Tom Elliot usb x86 x64.
My problem is:
“Sometimes” a client gets an IP by himself using the one owned by other computer. In my organization this is a “big crime”. The reason (I think)for this can be in the client kernel but I don’t know sure .
My network administrator send me messages like:
The computer client.xxx.xxx.xxx with the mac xx:xx:xx:xx:xx:xx and the IP xxx.xxx.xxx.xxx is using the IP address yyy.yyy.yyy.yyy owned by veryimportantpc.yyy.yyy.yyy and the mac yy:yy:yy:yy:yy:yy
But most of the time everything works fine. I receive two or three messages a day…
Is there a easy solution for this?