Last active 6 months ago
A bit more feedback. Got an image that does deploy. The main change was to modify the partitions manually, and make the last one to be 1 physical sector less than the disk boundary shown by partition tools. I also made it ext4 (rather than xfs), but I suspect the fs type is not relevant.
PS. I installed "Server with GUI" (selected in the pre-installation screen).
Yes, the download I used was from a warwick (UK) mirror only 3 days ago, and it installs OK, no problems. Thank you very much for your help!
Did that, still no luck.
Without the Exact Disk Match setting it threw the exact error as before (ERR signature...).
With the Exact Disk Match set, it now shows "Couldn't dynamically create partition layout.".
Tried again, on a new build, with the Create Partition method set to Dynamic, and Force Dynamic Partition for Exact Disk Match ticked. Same error.
Yes, we did. Had several iterations since, but will try again right now and let you know!
Thanks, that makes sense...
One of the later set of logs attached.
Using Clonedeploy on WIndows, cloning a Centos 7.5 box with 8 partitions (xfs) on a 1T hard disk.
When uploading the image we get script error, repeated for each partition:
/bin/lie_global_functions: line 17 <3604> Terminated
lie_reporter 63 partclone (wd: /)
However, the process seems to complete successfully. On deployment of that image, we get a different error:
/bin/lie_deploy: line 164: [: : integer expression expected
ERR signature for logical partition invalid: read 0x3DCC , but should be 0xAA55..., and it bombs out at that point.
Tried the 'dynamic' options in settings, no difference. Isn't AA55 a 'magic' MBR number? BTW, when rebuilt the image to 7 partitions, the deployment fails on it too (i.e. always on the last partition).
Great hint. Installed Chromium and can now log in... Thanks!
I have a clean, default install of Ubuntu 18.04 (beta). Apart from adjusting repository to bionic, and applying systemctl instead of service a couple of times, the instructions worked smoothly. The database creation step took longer than I expected, but complete without errors (not even the error at line 1929).
All services (apache2, mysql, smbd, tftpd-hpa) show status OK.
CloneDeploy Web Interface loads OK. Entered Username: clonedeploy, and at this point the Password field refuses to accept a value. The string Password persists and doesn't allow me to overtype or wipe it out. Unsurprisingly, when Log In is pressed at this point, I get a message below: Incorrect Username Or Password.