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