[00:00] you hacked something so there is only simple-boot [00:00] looks like you changed install.py [00:00] change it back to what it originally was [00:00] i changed block_meta.py [00:00] okay change whatever python you changed back to the original [00:00] now that you are using the partitioning_command you shouldn't need those hacks [00:01] done [00:01] it also looks like it is not running what you put in curtin_userdata for some reason [00:01] it did because it hit what i told it to run [00:01] but go ahead and give it another go [00:01] okay [00:02] does it need to be in that weird looking array [00:02] or can i just run commands in there? [00:02] 10_doshit: ['curtin', 'block-meta', 'simple-boot'] [00:02] that thing [00:02] paste your file [00:03] https://paste.tinyw.in/index.php/view/84388124 [00:04] ok this is gonna blow your mind... [00:05] https://paste.tinyw.in/index.php/view/5593153 [00:06] so the simple-boot bit didnt work... BUT my 50G partition did ger created [00:06] im willing to bet though that when i login for the first time, im going to see 1 2.7T root filesystem [00:07] yup! [00:08] https://paste.tinyw.in/index.php/view/63284151 [00:08] its like whatever was done in that curtin session did not *actually* write the partition table [00:09] so the simple-boot part...is architecture dependent [00:09] I forgot that part [00:09] aka amd64 [00:09] yeah it only happens for arm64 [00:09] stupid I know, but that is how it is setup currently [00:09] so that is why it looks like that wasn't run [00:09] well im using amd64 [00:09] amd64 == x86_64 [00:09] amd64 != arm64 [00:10] ohhhh arm64! [00:10] ;) [00:10] sorry [00:10] no worries [00:10] see my other pastes? [00:10] yeah give me a couple minutes...trying to eat dinner with the wife [00:11] I think you are on the right track [00:11] basically what is happening is simple is being run...but why you are not getting the partition you think...I will have to look more at the pastes [00:27] onicrom, you sure you are booting into the correct node? [00:27] cause yeah....I am scratching my head [00:28] logging in I mean [00:29] ive been looking at these guys so much [00:29] its possible [00:29] i will confirm in a oment [00:30] i was dinner, i had burgers :) [00:32] ci-info: | eth0 | True | 10.211.25.216 | 255.255.255.0 | 78:45:c4:f4:65:56 | [00:32] ok its working again but i added some more stuff [00:33] so what was the issue? [00:33] sgdisk -Z "$target" [00:33] sgdisk -og "$target" [00:33] sgdisk -p "$target" [00:33] then lket the hardcoded sizes go [00:33] and run sgdisk -v "$target" [00:34] -Z blow away, -og recreate [00:34] -v verify [00:34] lket=let [00:35] i also added: [00:35] paritioning_commands: 10_wipeshit: curtin wipe --quick --all-unused-disks [00:38] I think your wipeshit was what probably helped [00:38] no idea what the issue was but i thought id blow it out of the water wiping the partition(s)/table [00:39] where is defined that only arm64 will work btw? [00:39] block_meta.py [00:39] machine.platform logic [00:40] is that as simple as changing it? [00:41] yeap :) [00:41] 'amd64' instead of aarch64 [00:41] yeah if you do that it will give you a separate boot partition [00:41] make sure to check for other instances of aarch64 though [00:42] i only found that in all of curtina [00:42] and the hooks [00:42] ./commands/curthooks.py: if machine.startswith('armv7') or machine.startswith('aarch64'): [00:44] ok sir fingers crossed! [00:48] do you know if /boot is meant to be the first parition [00:48] because it looks like whatever just happened it went to /dev/sda1 for / [00:48] and ran out of space :) [00:50] dont think the simple-boot is being done [00:55] nope [00:55] echo "i am running $0 with $@" [00:55] i am running /curtin/helpers/partition with /dev/sda [00:56] i am running /curtin/helpers/install-grub with /tmp/tmpYXa48u/target /dev/sda [00:57] ok that is interesting [00:58] the only thing i just changed was boot=true to boot=false inside common [00:58] and now my / is one giant 2.7T filesystem again [01:02] onicrom, you are doing something! lol [01:02] I know simple boot works as is for arm64 [01:03] you need to open a python terminal on the node architecture if possible [01:04] sorry whats that mean? [01:04] I suspect that your architecture, at least from python is not what you expect [01:04] so do this [01:04] login into one of your nodes [01:04] $ python [01:04] >>> import platform [01:04] >>> print platform.machine() [01:04] and see what it tells you [01:05] x86_64 [01:05] let me execute on the server itself [01:06] same thing [01:06] oh [01:06] im an idiot me thinks [01:07] *facepalm* [01:07] i put amd64 [01:07] haha [01:07] ;) [01:07] ive been screwing with this since yeterday [01:08] forgive my bug eyes [01:08] no worries, I understand [01:08] I have to run [01:08] email me when you get it working...cause you are super close [01:08] you have been a very big help [01:08] thank you so much [01:09] no problem [04:01] anybody have any luck with maas on an HP c7000? === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away [22:32] is there a channel for setup help?