In my classroon，50 computers need to be maintained which have same hardware and with Win10 system.Each one has two hard disks.
Disk A(win10) is 512GB SSD,the other one disk B is 1TB harddrive.
When use clonezilla-live-3.1.0-22-amd64 lite-server mode(ramdisk,bt) on a model computer, choose the beginner to run disk to disk。
The disk number is always different everytime reboot the computer and boot from clonezilla.
Sometime disk A as sdb and disk B as sda,and sometimes the results are exactly the opposite.
The same problem also occurs on the client machine,which causes the system deployment work is wrong.
The data from diskA on model machine is copied to disk B on client machine,that the space on client's diskB is only 512GB used,and the rest space become blank space cannot work in Win10.Then client machines always boot failure.
What should I do to solve this problem？
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a tough issue since Linux kernel now only assigns the device name in the first-come-first- serve mechanism for the sda/sdb/sdc devices...
We will try to have some workarounds about this.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@robin,
In this discussion: https://sourceforge.net/p/clonezilla/discussion/Open_discussion/thread/4584356b80/
it's possible you can add boot parameter to force the scsi device shown in the order, i.e., by adding
scsi_mod.disable_async_probing=ahci
or more, like
scsi_mod.disable_async_probing=ahci,ata_piix,mptsas
This actually depends on the SCSI device you have.
In the Clonezilla lite server, you can add that in
/tftpboot/nbi_img/grub/grub.cfg
and
/tftpboot/nbi_img/pxelinux.cfg/default
to control the clients.
Not sure if it will 100% work or not. In the previous discussion, Rob mentioned he succeeded 5 times, but then fail. Not sure if he tested on the same machine or different one.
Maybe you can give it a try?
If it works, we can try to add that boot parameter in Clonezilla.
Hello,
In my classroon，50 computers need to be maintained which have same hardware and with Win10 system.Each one has two hard disks.
Disk A(win10) is 512GB SSD,the other one disk B is 1TB harddrive.
When use clonezilla-live-3.1.0-22-amd64 lite-server mode(ramdisk,bt) on a model computer, choose the beginner to run disk to disk。
The disk number is always different everytime reboot the computer and boot from clonezilla.
Sometime disk A as sdb and disk B as sda,and sometimes the results are exactly the opposite.
The same problem also occurs on the client machine,which causes the system deployment work is wrong.
The data from diskA on model machine is copied to disk B on client machine,that the space on client's diskB is only 512GB used,and the rest space become blank space cannot work in Win10.Then client machines always boot failure.
What should I do to solve this problem？
Thank you.
This is a tough issue since Linux kernel now only assigns the device name in the first-come-first- serve mechanism for the sda/sdb/sdc devices...
We will try to have some workarounds about this.
Steven
@robin,
In this discussion:
https://sourceforge.net/p/clonezilla/discussion/Open_discussion/thread/4584356b80/
it's possible you can add boot parameter to force the scsi device shown in the order, i.e., by adding
scsi_mod.disable_async_probing=ahci
or more, like
scsi_mod.disable_async_probing=ahci,ata_piix,mptsas
This actually depends on the SCSI device you have.
In the Clonezilla lite server, you can add that in
/tftpboot/nbi_img/grub/grub.cfg
and
/tftpboot/nbi_img/pxelinux.cfg/default
to control the clients.
Not sure if it will 100% work or not. In the previous discussion, Rob mentioned he succeeded 5 times, but then fail. Not sure if he tested on the same machine or different one.
Maybe you can give it a try?
If it works, we can try to add that boot parameter in Clonezilla.
Ref: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/index.html#jsc-SLE-11117
Steven
Last edit: Steven Shiau 2023-10-07
@steven_shiau
Ok, thanks for the tip. Actually I'm not very good at Linux and grub, but I'll try to do it and give you feedback.
Robin