We have been using DRBL/Clonezilla for deploying Windows Images on about 50 PCs for a number of years now, and mostly it did what we wanted. Unfortunately, a new Machine of type Lenovo Think Station P360 refuses the procedure of saving a disk to the DRBL server. The client boots to the point where it offers "Clonezilla: save disk nvme0n1 as image 2023-03-29-14-img". After that, it says
"Enter Clonezilla... Loading Linux Kernel vmlinuz-pxe...
Loading initial ramdisk initrd-pxe.img... [ 28,43MiB 100% 4,02 MiB/s]".
Then suddenly it shows
"[0.121265] ACPI Error: Method parse/execution failed _SB.PC00.PEG0.STA, AE", followed by a bunch of similar ACPI error messages.
Are there any ideas what this means? In the past, we have been able to clone sda drives as well as nvme drives.
Regards
Joachim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Steven,
thanks you very much for your quick reaction - and sorry for my very delayed one :-)
Meanwhile I found that I can do he cloning from a USB disk using Clonezilla alone. It will show the ACPI error messages as before but - surprise! - still boot (from USB) and do the job. This tells me that the issue does not lie within Clonezilla and not in ACPI settings but rather in the DRBL boot process. In the attached screenshots you will see that the boot hangs after "mounting /proc file system". I cannot get beyond that point.
Apart from that I have tried to run Clonezilla live in DRBL and to use the lite server following your howto, but I must confess that I have not been able to get that running.
"Apart from that I have tried to run Clonezilla live in DRBL and to use the lite server following your howto, but I must confess that I have not been able to get that running." -> What were the issues you encountered? It should be easier than DRBL (Clonezilla SE).
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Meanwhile I gave Clonezilla SE another try and ran in in server mode providing its own DHCP service. Unfortunately, the clients did not get an IP address assigned from that DHCP. Maybe there is a conflict between the Clonezilla SE machine's IP (automatically set to 192.168.169.250) and the fact that our network uses 192.168.0.x addresses. Would it help to set the Clonezilla SE machine's own IP to something like 192.168.0.x, and if so, how do I do that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, I have no DHCP service running in my network except for the one that comes with DRBL. Instead I use static IP addresses.
What I wanted to say in my last post is that I am not sure if our network switch will distribute addresses like 192.168.169. , since the switch itself has 192.168.0*.1 .
Do you see a problem here? Again: Would it help to set the Clonezilla SE machine's IP to something like 192.168.0.x, and if so, how can I do that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Meanwhile I managed to get Clonezilla light in server mode to provide DHCP. My old PCs are now able to boot Clonezilla Live via PXE and to start the restore disk procedure (btw.: save disk is not supported, right?), but not so the new P360 machines. They seem to hang just like they do with my normal DRBL server. The network interface in these machines is INTEL I219-LM. Can you tell me wether this interface is supported by DRBL?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today's approach using the latest version of clonezilla live (20230713-mantic) seems to have been successful in terms of restoring an image file to a disk in lite server mode. Am I right that the lite server only supports restore disk, but not save disk? At least I could not find such an option there.
- Btw: Will this version of Clonezilla be available for the full DRBL/Clonezilla harddisk installation?
Joachim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Am I right that the lite server only supports restore disk, but not save disk?" -> Yes.
However, you can either boot Clonezilla live on the machine you want to save, or PXE boot on the machine you want to save in the mode "interactive-client": https://clonezilla.org/clonezilla-live/doc/11_lite_server/images/ocs-08-5-massive-deployment.png
Then mount the image repository and save the image.
"Will this version of Clonezilla be available for the full DRBL/Clonezilla harddisk installation?" -> Please refer to this doc: https://drbl.org/installation/
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems like this time I've been successful! I integrated the downloaded mantic release of clonezilla to the drbl server using the drbl4imp command and
drbl -sl -i /home/.../Downloads/clonezilla-live-20230721-mantic-amd64.iso.
Today I don't have the time to run the save disk procedure to its completion, but anyhow it starts to write the image as desired.
Thanks a lot for your support
Joachim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have been using DRBL/Clonezilla for deploying Windows Images on about 50 PCs for a number of years now, and mostly it did what we wanted. Unfortunately, a new Machine of type Lenovo Think Station P360 refuses the procedure of saving a disk to the DRBL server. The client boots to the point where it offers "Clonezilla: save disk nvme0n1 as image 2023-03-29-14-img". After that, it says
"Enter Clonezilla... Loading Linux Kernel vmlinuz-pxe...
Loading initial ramdisk initrd-pxe.img... [ 28,43MiB 100% 4,02 MiB/s]".
Then suddenly it shows
"[0.121265] ACPI Error: Method parse/execution failed _SB.PC00.PEG0.STA, AE", followed by a bunch of similar ACPI error messages.
Are there any ideas what this means? In the past, we have been able to clone sda drives as well as nvme drives.
Regards
Joachim
Not sure. If you can take a photo about the messages on the screen of client machine, it might help.
BTW, maybe you can try this method:
https://clonezilla.org/clonezilla-SE/use_clonezilla_live_in_drbl.php
By using different versions of Clonezilla live, it might have different results. Especially you can try alternative release, i.e., Ubuntu-based one.
In addition, you can try Clonezilla lite server:
https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/11_lite_server
Steven
Dear Steven,
thanks you very much for your quick reaction - and sorry for my very delayed one :-)
Meanwhile I found that I can do he cloning from a USB disk using Clonezilla alone. It will show the ACPI error messages as before but - surprise! - still boot (from USB) and do the job. This tells me that the issue does not lie within Clonezilla and not in ACPI settings but rather in the DRBL boot process. In the attached screenshots you will see that the boot hangs after "mounting /proc file system". I cannot get beyond that point.
Apart from that I have tried to run Clonezilla live in DRBL and to use the lite server following your howto, but I must confess that I have not been able to get that running.
Best regards
Joachim
"Apart from that I have tried to run Clonezilla live in DRBL and to use the lite server following your howto, but I must confess that I have not been able to get that running." -> What were the issues you encountered? It should be easier than DRBL (Clonezilla SE).
Steven
Meanwhile I gave Clonezilla SE another try and ran in in server mode providing its own DHCP service. Unfortunately, the clients did not get an IP address assigned from that DHCP. Maybe there is a conflict between the Clonezilla SE machine's IP (automatically set to 192.168.169.250) and the fact that our network uses 192.168.0.x addresses. Would it help to set the Clonezilla SE machine's own IP to something like 192.168.0.x, and if so, how do I do that?
So did you mean you have two DHCP services exiting in the same LAN? If so, please check this:
https://drbl.org/fine-print.php?path=./faq/2_System/37_coexist_with_existing_dhcp.faq#37_coexist_with_existing_dhcp.faq
Steven
No, I have no DHCP service running in my network except for the one that comes with DRBL. Instead I use static IP addresses.
What I wanted to say in my last post is that I am not sure if our network switch will distribute addresses like 192.168.169. , since the switch itself has 192.168.0*.1 .
Do you see a problem here? Again: Would it help to set the Clonezilla SE machine's IP to something like 192.168.0.x, and if so, how can I do that?
Not sure how you configure your Clonezilla SE. Maybe you can run:
drbl-bug-report
Then post the generated file so that we know more info?
Thanks.
Steven
Meanwhile I managed to get Clonezilla light in server mode to provide DHCP. My old PCs are now able to boot Clonezilla Live via PXE and to start the restore disk procedure (btw.: save disk is not supported, right?), but not so the new P360 machines. They seem to hang just like they do with my normal DRBL server. The network interface in these machines is INTEL I219-LM. Can you tell me wether this interface is supported by DRBL?
Here comes the bug report from my DRBL server:
-------CUT BEGIN HERE--------------------------------------------
Description of problem:
How reproducible:
Steps to Reproduce:
Actual results:
Expected results:
Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):
OS version: LinuxMint 19.2
Server arch: x86_64
Server CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
Server memory size: 1522924 kB
Server Kernel version: 4.15.0-54-generic
Installed DRBL-related packages: drbl-5.2.10-drbl1 clonezilla-5.4.6-drbl1 partclone-0.3.23-drbl-1 mkpxeinitrd-net-2.5.6-drbl1 ipxe-1.0.0+git-20180124.fbe8c52d-0ubuntu2.2 partimage-0.6.9-6build1 ntfsprogs-<none> gzip-1.6-5ubuntu1.2 bzip2-1.0.6-8.1ubuntu0.2 lzop-1.03-4 pigz-2.4-1 pbzip2-1.1.9-1build1 udpcast-20120424-2 syslinux-3:6.03+dfsg1-2
Client kernel version: 5.4.0-147-generic
Client kernel arch: x86_64
NICs with private IP address in server: enp4s0
Private IP address in server: 192.168.0.222
Total client no: 19
Client IP address: 192.168.0.50 192.168.0.51 192.168.0.52 192.168.0.53 192.168.0.54 192.168.0.55 192.168.0.56 192.168.0.57 192.168.0.58 192.168.0.59 192.168.0.60 192.168.0.61 192.168.0.62 192.168.0.63 192.168.0.64 192.168.0.65 192.168.0.66 192.168.0.67 192.168.0.68
===
-------CUT END HERE----------------------------------------------</none>
So maybe you can use alternative Clonezilla live to run the lite server? It contains non-free firmware, and maybe your network interface needs that?
Steven
Today's approach using the latest version of clonezilla live (20230713-mantic) seems to have been successful in terms of restoring an image file to a disk in lite server mode. Am I right that the lite server only supports restore disk, but not save disk? At least I could not find such an option there.
- Btw: Will this version of Clonezilla be available for the full DRBL/Clonezilla harddisk installation?
Joachim
"Am I right that the lite server only supports restore disk, but not save disk?" -> Yes.
However, you can either boot Clonezilla live on the machine you want to save, or PXE boot on the machine you want to save in the mode "interactive-client":
https://clonezilla.org/clonezilla-live/doc/11_lite_server/images/ocs-08-5-massive-deployment.png
Then mount the image repository and save the image.
"Will this version of Clonezilla be available for the full DRBL/Clonezilla harddisk installation?" -> Please refer to this doc:
https://drbl.org/installation/
Steven
It seems like this time I've been successful! I integrated the downloaded mantic release of clonezilla to the drbl server using the drbl4imp command and
drbl -sl -i /home/.../Downloads/clonezilla-live-20230721-mantic-amd64.iso.
Today I don't have the time to run the save disk procedure to its completion, but anyhow it starts to write the image as desired.
Thanks a lot for your support
Joachim