I'm a total Clonezilla newbie having a problem using a Clonezilla auto-recovery USB that I created. I followed the guide, and created a CentOS 5.9 recovery USB stick. I tested it out, and it successfully recovered the disk. Just for thoroughness, after verifying the recovered drive worked fine, I attempted to boot from the USB stick again, and it refused to boot! The device was being skipped, even though it was listed as the first device in BIOS. I removed all drives to see if I could at least get to the splash screen, and was met with the "Reboot and Select Proper Boot Device" message you see when there is no bootable disk present.
I put the auto-recovery USB back into the computer that I used to format and copy the image onto it from, and performed a diff of what was on the USB and the contents of the original zip file. This revealed that a hidden directory named .disk had been deleted when I used the auto-recovery USB!
I copied the .disk directory from the source zip back to the USB, booted it up, and it worked fine again!
After repeated testing, it seems that the .disk folder doesn't get deleted every time, but after a few uses, eventually it WILL be deleted. I'm going to perform a few recoveries using the "Run from RAM" option and see if that prevents it from happening.
I was hoping someone here could shed some light on what might be happening.
Last edit: Corey Z 2013-08-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
New information: I had been choosing to boot from the device in BIOS, but it looks like the correct choice was to boot from UEFI. BIOS presented two options, [UEFI: Kingston...] and [Kingston...]. I guess the format of the auto-recovery zip file requires it to be booted via the UEFI option?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Both of BIOS and uEFI should work for Clonezilla live.
The key point is, you have to make sure your OS is booted from BIOS or uEFI.
I suggest to set only one mode in your BIOS setting, either legacy (BIOS) or EFI.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm a total Clonezilla newbie having a problem using a Clonezilla auto-recovery USB that I created. I followed the guide, and created a CentOS 5.9 recovery USB stick. I tested it out, and it successfully recovered the disk. Just for thoroughness, after verifying the recovered drive worked fine, I attempted to boot from the USB stick again, and it refused to boot! The device was being skipped, even though it was listed as the first device in BIOS. I removed all drives to see if I could at least get to the splash screen, and was met with the "Reboot and Select Proper Boot Device" message you see when there is no bootable disk present.
I put the auto-recovery USB back into the computer that I used to format and copy the image onto it from, and performed a diff of what was on the USB and the contents of the original zip file. This revealed that a hidden directory named .disk had been deleted when I used the auto-recovery USB!
I copied the .disk directory from the source zip back to the USB, booted it up, and it worked fine again!
After repeated testing, it seems that the .disk folder doesn't get deleted every time, but after a few uses, eventually it WILL be deleted. I'm going to perform a few recoveries using the "Run from RAM" option and see if that prevents it from happening.
I was hoping someone here could shed some light on what might be happening.
Last edit: Corey Z 2013-08-22
New information: I had been choosing to boot from the device in BIOS, but it looks like the correct choice was to boot from UEFI. BIOS presented two options, [UEFI: Kingston...] and [Kingston...]. I guess the format of the auto-recovery zip file requires it to be booted via the UEFI option?
Both of BIOS and uEFI should work for Clonezilla live.
The key point is, you have to make sure your OS is booted from BIOS or uEFI.
I suggest to set only one mode in your BIOS setting, either legacy (BIOS) or EFI.
Steven.