#369 Drive auto-rename doesn't occur in Server Lite

[Zevgeny Chernikov]

Hi, I have an image that was taken from a drive named "xda". I want to deploy the image to a PC which has drives named "nvme0n".

If I use Clonezilla live in local mode, this works fine, the restore process automatically handles the different drive name.

However, if I am mass-deploying with Server Lite (bittorrent mode), the PXE booted clients fail to restore the image, complaining that the drive name is different.

Can we please add the auto-rename process to Server Lite? Even if there's a restriction like all clients must have the same hardware, that's fine since I imagine many deployments would be to identical hardware.

[Steven Shiau]

You can first convert the image to the name you want, then do the massive deployment:
https://drbl.org/management/techrpt.php?c=cnvt-ocs-dev&t=To%20change%20the%20device%20name%20in%20saved%20clonezilla%20image

Steven

[Zevgeny Chernikov]

Thanks for the reply. Sorry for the delay, I finally got around to trying this again.
When I run the command to change the filenames, the command runs without error, and the filenames are changed. However, when I try to use the renamed image in Clonezilla, the image does not appear in the list of available images in my folder. Did I do something wrong?

[Steven Shiau]

How did you run the command? If the converted image is listed in /home/partimag/, definitely it should be listed in the Clonezilla TUI.

Steven

[Zevgeny Chernikov]

Hi, here's the steps that I did:

1. Source image is on a samba share.
2. Start clonezilla in clonezilla live mode.
3. Device-Image, Samba, DHCP.
4. Choose Beginner mode. Verify image shows up on the list.
5. Cancel and exit to command line.
6. Verify that /home/partimag contains the image files.
7. Run command "sudo cnvt-ocs-dev -d /home/partimag 2022-05-06-W10-Public-Dell7060-V04 xvda nvme0n1"
8. Command runs without errors. Verify that files are renamed in the folder.
9. Start clonezilla again and do steps 1-3
10. Choose Beginner Mode.
11. Converted image is no longer on the GUI list.
12. Exit to command line. Do "ls /home/partimag". The image folder is still present.

When Clonezilla is searching /home/partimag for images, what is it looking for? I created a folder by hand with some random files as a test, and that doesn't show up on the GUI list either, so it obviously only displays "valid" image folders according to some criteria.

[Steven Shiau]

Which version of Clonezilla live did you use?
BTW, if you can, please run:
find /home/partimag -print

Then post the results. Thanks.

Steven

[Zevgeny Chernikov]

Sorry for the delay, thanks for your time. I'm using: clonezilla-live-20211116-impish-amd64.iso

Here is the output of find /home/partimag -print. I only have 1 image folder in this folder. This is the result after I have run the conversion to nvme0n1.

/home/partimag
/home/partimag/2022-04-26-W10-rename-test
/home/partimag/2022-04-26-W10-rename-test/clonezilla-img
/home/partimag/2022-04-26-W10-rename-test/efi-nvram.dat
/home/partimag/2022-04-26-W10-rename-test/Info-dmi.txt
/home/partimag/2022-04-26-W10-rename-test/Info-img-id.txt
/home/partimag/2022-04-26-W10-rename-test/Info-lshw.txt
/home/partimag/2022-04-26-W10-rename-test/Info-lspci.txt
/home/partimag/2022-04-26-W10-rename-test/Info-OS-prober.txt
/home/partimag/2022-04-26-W10-rename-test/Info-packages.txt
/home/partimag/2022-04-26-W10-rename-test/Info-saved-by-cmd.txt
/home/partimag/2022-04-26-W10-rename-test/Info-smart.txt
/home/partimag/2022-04-26-W10-rename-test/nvme0n1-chs.sf
/home/partimag/2022-04-26-W10-rename-test/nvme0n1-gpt-1st
/home/partimag/2022-04-26-W10-rename-test/nvme0n1-gpt-2nd
/home/partimag/2022-04-26-W10-rename-test/nvme0n1-gpt.gdisk
/home/partimag/2022-04-26-W10-rename-test/nvme0n1-gpt.sgdisk
/home/partimag/2022-04-26-W10-rename-test/nvme0n1-mbr
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p1.vfat-ptcl-img.gz.aa
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p2.dd-ptcl-img.gz.aa
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p3.ntfs-ptcl-img.gz.aa
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p3.ntfs-ptcl-img.gz.ab
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p4.ntfs-ptcl-img.gz.aa
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p5.ntfs-ptcl-img.gz.aa
/home/partimag/2022-04-26-W10-rename-test/nvme0n1p5.ntfs-ptcl-img.gz.ab
/home/partimag/2022-04-26-W10-rename-test/device_name_converted.info

[Steven Shiau]

A normal, complete Clonezilla image should contain files "disk" and "parts" in the image directory, something like:
https://clonezilla.org/fine-print-live-doc.php?path=clonezilla-live/doc/02_Restore_disk_image
No idea why yours does not have that. It should be there, even it's converted by cnvt-ocs-dev.

Steven

[Zevgeny Chernikov]

Hmm, that's odd. Is there any additional logging or debug info that I can turn on, for the conversion command?

(Alternatively, could you please consider my original suggestion of implementing auto-rename for the mass deployment modes?)

Is cnvt-ocs-dev the same command that is used during auto-rename when deploying to a single PC? Because I haven't had any problems deploying to a single PC and getting it auto-converted.

[Steven Shiau]

It's shown on the screen... So if you are familiar with "screen" or "tmux", you can try to catch the output messages on the screen.
What is the files list in your original image dir?
"(Alternatively, could you please consider my original suggestion of implementing auto-rename for the mass deployment modes?)" -> Will think about it.
"Is cnvt-ocs-dev the same command that is used during auto-rename when deploying to a single PC?" -> Yes.

Steven