The install process fails with the error: Unable to find target partition "nvme0n1p1", despite the fact that the subsequent partition list includes the "nvme0n1" disk.
I'm sorry I can't believe that info didn't make it into the original report. We're running into this problem with Clonezilla Live 20161010-xenial. I will try yakkety after the weekend, but I don't imagine they have wildly divergant kernels (if that indeed is the problem here)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, in that case, the issue is not related to the Linux kernel I believe. could you please show me the results of the following in the Clonezilla live environment when you have that errors:
1. sudo -i
2. df -ah
3. cat /proc/partitions
4. parted -s /dev/nvme0n1 print
Please show the reuslts of 2, 3 and 4.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Everything looks normal. This is weird.
Could you please do it again, then:
1. Take a photo about the whole messages on the screen then post it.
2. Post the log file /var/log/clonezilla.log, too.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is bizarre. When you asked me to re-run the test and take pictures last night, the installation worked perfectly. I chalked it up to gremlins and went to bed, only to try again twice this morning (in a row) and it worked again! I ran it a third time this morning, and got the same error. Sounds like some sort of race condition, or timing issue?
Attached are the image and log file you requested.
Maybe something triggered that... Could you try to test it again (and then several times) by entering the expert mode, and do not select the option "-j2"?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still think maybe it's related to the Linux kernel since you have found that sometimes it happens, sometimes it's not. Besides, it's related to the kernel detecting the partitions.
Could you please give Clonezilla live 20161017-yakkety a try? Please test it many times, all with -j2 enabled (by default). :D
The version comes with Linux kernel 4.8 so the results might be different.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks like the yakkety version is working! I've managed to install it 7 times in a row successfully. I am running into an error with the installer though. After everything is done installing, it drops me into a shell instead of showing me the final ncurses dialog to reboot. The log shows:
"ocs-live-restore" finished.
Check /var/log/clonezilla.log for more details.
The next step: true
user@yakkety:~$
So I have to manually reboot from there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Steven,
Yeah the issue I mentioned happened every time in the 7 attempts I made yesterday to install. I think we can safely say the original issue has been resolved by using the yakkety build, however the UI bug is still an issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is weird... Somehow for Clonezilla live 20161024-yakkety-amd64 I just can not reproduce the issue you mentioned here. Since the issue is not reproduced here, I have no idea how to fix it.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
RESOLVED: Samsung SSD NVME has a controller model name with spaces = "Samsung SSD 950 PRO 512GB_S2GMNCAH106976X"
When constucting in prep-ocsroot:
HARDDEVS=' nvme0n1p1 16G_ext4(In_Samsung_SSD_950_PRO_512GB_)_Samsung SSD 950 PRO 512GB_S2GMNCAH106976X ...'
the spaces remain scrambling the lines of the menu:
whiptail --backtitle 'NCHC Free Software Labs, Taiwan' --title 'Clonezilla - Opensource Clone System (OCS) | Mode: ' --menu 'Now we need to mount a device as /home/partimag (Clonezilla image(s) repository) so that we can read or save the image in /home/partimag.\n///NOTE/// You should NOT mount the partition you want to backup as /home/partimag\nThe partition name is the device name in GNU/Linux. The first partition in the first disk is "hda1" or "sda1", the 2nd partition in the first disk is "hda2" or "sda2", the first partition in the second disk is "hdb1" or "sdb1"... If the system you want to save is MS windows, normally C: is hda1 (for PATA) or sda1 (for PATA, SATA or SCSI), and D: could be hda2 (or sda2), hda5 (or sda5)...' 0 0 10 nvme0n1p1 '16G_ext4(In_Samsung_SSD_950_PRO_512GB_)_Samsung' SSD 950 PRO 512GB_S2GMNCAH106976X nvme0n1p2 '16G_ext4(In_Samsung_SSD_950_PRO_512GB_)_Samsung' SSD 950 PRO 512GB_S2GMNCAH106976X nvme0n1p3
and when we choose except the first line, clonezilla fail.
So I made a correction in /usr/share/drbl/sbin/ocs-functions of clonezilla-live-2.5.0-7-amd64.iso with editCZCDsquashfs.sh script:
line 3966 was:
serialno="$(LC_ALL=C udevadm info -q env -n /dev/${dsk_} | grep ID_SERIAL= | sed -e 's/ID_SERIAL=//g')"
and I put:
serialno="$(LC_ALL=C udevadm info -q env -n /dev/${dsk_} | grep ID_SERIAL= | sed -e 's/ID_SERIAL=//g' | tr ' ' '_')"
The tr converts spaces to _ and there is no more scramble and clonezilla works well.
I think it would correct some bugs as “Box” is an unknown partition device* errors.
Hope this help a little...
PiM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
#!/bin/shexec tail -n +3 $0# This file provides an easy way to add custom menu entries. Simply type the# menu entries you want to add after this comment. Be careful not to change# the 'exec tail' line above.#CLONEZILLA http://clonezilla.org/livehd.php#you can use only the Clonezilal live iso file in grub2 (Thanks to the patches files from grml).#For example, put clonezilla-live-2.5.0-5-i686.iso in dir /dev/nvme0n1p1,#then make the grub2 custom menu (/etc/grub.d/56_clonezilla) like:##================================================
menuentry 'Clonezilla live 2.5.0-7-amd64' --class debian --class gnu-linux --class gnu --class os {setisofile="/clonezilla-live-2.5.0-7-amd64.iso"
loopback loop (hd0,1)$isofile
linux (loop)/live/vmlinuz boot=live union=overlay username=user config components quiet noswap nolocales edd=on nomodeset nodmraid ocs_live_run=\"ocs-live-general\"ocs_live_extra_param=\"\" keyboard-layouts=ocs_live_batch=\"no\"locales=vga=788ip=frommedia nosplash toram=filesystem.squashfs findiso=$isofile
initrd (loop)/live/initrd.img
}##================================================#Then run "update-grub2" to update your grub2 config.#then: grub-install /dev/nvme0n1
HAve a good time,
PiM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Which version of Clonezilla live did you use?
Have you tried testing Clonezilla live, like 2.4.9-7 or 20161010-yakkety?
Steven
I'm sorry I can't believe that info didn't make it into the original report. We're running into this problem with Clonezilla Live 20161010-xenial. I will try yakkety after the weekend, but I don't imagine they have wildly divergant kernels (if that indeed is the problem here)
OK, in that case, the issue is not related to the Linux kernel I believe. could you please show me the results of the following in the Clonezilla live environment when you have that errors:
1. sudo -i
2. df -ah
3. cat /proc/partitions
4. parted -s /dev/nvme0n1 print
Please show the reuslts of 2, 3 and 4.
Thanks.
Steven
Apologies for the delay, attached are the results of each of those commands.
Everything looks normal. This is weird.
Could you please do it again, then:
1. Take a photo about the whole messages on the screen then post it.
2. Post the log file /var/log/clonezilla.log, too.
Thanks.
Steven
Hi Steven,
This is bizarre. When you asked me to re-run the test and take pictures last night, the installation worked perfectly. I chalked it up to gremlins and went to bed, only to try again twice this morning (in a row) and it worked again! I ran it a third time this morning, and got the same error. Sounds like some sort of race condition, or timing issue?
Attached are the image and log file you requested.
Last edit: Matt Broadstone 2016-10-19
Maybe something triggered that... Could you try to test it again (and then several times) by entering the expert mode, and do not select the option "-j2"?
Steven
Steven,
Removing the
-j2option did stop the error from occurring, however when booting the machine it halts atGRUBwith a blinking cursor.I still think maybe it's related to the Linux kernel since you have found that sometimes it happens, sometimes it's not. Besides, it's related to the kernel detecting the partitions.
Could you please give Clonezilla live 20161017-yakkety a try? Please test it many times, all with -j2 enabled (by default). :D
The version comes with Linux kernel 4.8 so the results might be different.
Steven
Steven,
It looks like the yakkety version is working! I've managed to install it 7 times in a row successfully. I am running into an error with the installer though. After everything is done installing, it drops me into a shell instead of showing me the final ncurses dialog to reboot. The log shows:
"ocs-live-restore" finished.
Check /var/log/clonezilla.log for more details.
The next step: true
user@yakkety:~$
So I have to manually reboot from there.
OK, cool.
The new issue you mentioned is minor. If it can be reproduced many times, let me know.
Steven
Steven,
Yeah the issue I mentioned happened every time in the 7 attempts I made yesterday to install. I think we can safely say the original issue has been resolved by using the yakkety build, however the UI bug is still an issue.
This is weird... Somehow for Clonezilla live 20161024-yakkety-amd64 I just can not reproduce the issue you mentioned here. Since the issue is not reproduced here, I have no idea how to fix it.
Steven
RESOLVED: Samsung SSD NVME has a controller model name with spaces = "Samsung SSD 950 PRO 512GB_S2GMNCAH106976X"
When constucting in prep-ocsroot:
the spaces remain scrambling the lines of the menu:
and when we choose except the first line, clonezilla fail.
So I made a correction in /usr/share/drbl/sbin/ocs-functions of clonezilla-live-2.5.0-7-amd64.iso with editCZCDsquashfs.sh script:
line 3966 was:
and I put:
The tr converts spaces to _ and there is no more scramble and clonezilla works well.
I think it would correct some bugs as “Box” is an unknown partition device* errors.
Hope this help a little...
PiM
@Matt: I have also a Samsung 950 Pro and clonezilla works fine with a GPT partition table and a small BIOS_boot partition.
I put the iso on the first partition and added a /etc/grub.d/56_clonezilla:
HAve a good time,
PiM
Thanks. Will apply the patch you have mentioned in the next Clonezilla live.
Steven