#343 parted gives error while starting backup

[Saige Losli]

I have a scripted backup that I've been using for a few years now. The actual backup command looks like this:

/usr/sbin/ocs-sr -batch -q2 -j2 -z1p -i 4096 -scs -p reboot savedisk autoname sda

I'm trying to run that command on a new laptop. It's about 1 year old Samsung model NP750QUB. The script launches automatically, and when I saw the screen here is what it says:

Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Warning: failed to translate partition name
Getting /dev/sda1 info...
Getting /dev/sda2 info...
Getting /dev/sda3 info...
Getting /dev/sda4 info...
Getting /dev/sda5 info...
Getting /dev/sda6 info...
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Saving block devices info in /home/partimag/9cebe8d0cd86-2020-04-28-0300-img/blkdev.list...
Saving block devices attributes in /home/partimag/9cebe8d0cd86-2020-04-28-0300-img/blkdev.list...
Checking the integrity of partition table in the disk /dev/sda...
/usr/share/drbl/sbin/ocs-functions: line 2984: 8527 Aborted                  parted -s $disk_file pr
int &> $dsk_chk_tmp
The partition table in this disk is illegal/invalid: /dev/sda
It's not supported by parted. Parted is used in Clonezilla to parse the filesystem in the partition
table. This partition table is detected as WRONG by parted!
The error messages from parted are:
*****************************************************.
realloc(): invalid next size
*****************************************************.
If you continue, something strange might happen (E.g. dd is used, not partimage or ntfsclone, to sav
Are you sure you want to continue? (y/N)?

I have tried both "Y" and "N" answers to the continuation question. "N" simply quits Clonezilla and a reboot takes place. "Y" proceeds and appears to actually back up the machine. But I am afraid to test it.

[Saige Losli]

What can I do to avoid this error and successfully backup?

[Steven Shiau]

Which version of Clonezilla live did you use? Could you please give the latest one a try? Either 2.6.6-15 or 20200428-focal:
https://clonezilla.org/downloads.php

Steven

[Saige Losli]

I'm on Alternative eaon

Yes, I can give it a try.

[Saige Losli]

I have now tried it with 20200428-focal, and the results are almost the same. This time, instead of "line 2984: 8527 Aborted", it says "line 2984: 8434 Aborted".

If it is helpful, here I transcribe a screenshot that I was able to take when I was physically with the machine (I was able to start Clonezilla in its user-guided mode, and selected a command prompt to type a couple commands I hope would be helpful):

user@debian:~$ sudo parted /dev/sda 'print'
Model: ATA SAMSUNG MZNLN256 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

realloc(): invalid next size
Aborted
user@debian:~$ sudo fdisk /dev/sda

Welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sda: 238.49GB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG MZNLN256
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A377064E-8D8B-47BB-AF7F-D4E5F0B40A47

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    534527    532480   260M EFI System
/dev/sda2     534528    567295     32768    16M Microsoft reserved
/dev/sda3     567296 469823488 469256193 223.8G Microsoft basic data
/dev/sda4  469823489 471564289   1740801   850M Windows recovery environment
/dev/sda5  471564290 498020354  26456065  12.6G Windows recovery environment
/dev/sda6  498020355 500117507   2097153     1G Windows recovery environment

So what could be the cause of the message: "The partition table in this disk is illegal/invalid" resulting from the "realloc()" call in parted?

Are there additional diagnoses that I can do to help?

[Steven Shiau]

I googled and found this issue was asked on different forum two years ago:
https://bug-parted.gnu.narkive.com/7cW2mSfD/bug-29051-error-in-parted-realloc-invalid-next-size
" It appears that you have some non printing characters in your partition names." -> Is this your case?

Steven

[Saige Losli]

I was worried about something like that. That's why I printed the
partition table in my last posting. I don't see any "non-printing"
characters in the partition names, but then again, how would one know?
It is the original partition table from the factory.

[Steven Shiau]

Maybe you can use sfdisk, blkid or parted to dump the file system info to a file, then use binary editor to check that file?

Steven