Last active 1 hour ago
I tried again with the following custom scheme and it failed.
Tried imaging it without any custom partitioning - success. Going to try setting the custom scheme with MB as suggested (instead of the 20gb I had originally).
Okay, I'll try that now. No, haven't tried without custom sizes - I can try as a troubleshooting step but that would result in a pretty unusable partitioning scheme.
I currently have the custom size set to way bigger then required (its set to 20 gb), but I'll try chaning to it to MB.
Log from my latest deployment attempt, the schema from the upload (that I modified based off my other post), and the export schema I am trying to use.
I get the following error at the end of a deploy log - the system only boots into emergency mode. Any ideas? I wonder if it's related to https://forum.clonedeploy.org/845-error-while-expanding-volume-group-system-nullreferenceexceptio
Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/nvme0n1: 2000409264 sectors, 953.9 GiB Logical sector size: 512 bytes Disk identifier (GUID): 7C0359B6-126B-48C0-BE5D-77C2B2FCFB01 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 2000409230 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 2099199 1024.0 MiB 8300 Linux filesystem 2 2099200 2000409263 952.9 GiB 8E00 Linux LVM
I managed to compare it to the last time you fixed it, and was able to at least get the error to go away. Going to test deploying it and see what happens.
Hello again - I captured another image with custom partitioning like before and I am getting the same error. Can you take a look? Schema attached.
Oh, I found how to have multiple profiles. That probably solves the problem for me. Wish me luck on trying to deploy this monstrosity....
Is it possible to have an image schema that is dynamic depending on the size of the hardware?
I have a reference Linux image that I built on a 20gb HDD VM, and I am modifying the slightly complex partitioning for deployment to larger hard drives.
Is it possible to do something like....
/boot - 1.5 gb static
/home - 35% of total hdd space, or 20gb, whichever is smaller
/var - 15% of total hdd space, or 10gb, whichever is smaller
/ - rest of the available space
If that's not possible, is it possible to have two deployment schemes for the same image? So I could create one for large hard drives with the smaller values, and one based on percentages?
Wanted to circle back and let you know how much I appreciate how quickly you responded.