| === ch0ps3y is now known as Guest7614 | ||
| === alucardromero8 is now known as alucardromero | ||
| mybalzitch | moving my install to UEFI and different drives seems fun so far | 04:25 |
|---|---|---|
| montjoie | hello I did a pxe 22.04 boot but it ignore all automatedinstall parameters | 11:32 |
| montjoie | I used ip=dhcp autoinstall cloud-config-url=/dev/null url=http://10.1.1.4/jammy/ubuntu-22.04.4-live-server-amd64.iso autoinstall ds=nocloud-net;s=http://10.1.1.4/jammy/ | 11:33 |
| === miceiken7 is now known as miceiken | ||
| === xispita is now known as Guest9170 | ||
| === xispita_ is now known as xispita | ||
| dbungert | montjoie: are your autoinstall parameters under a top-level autoinstall keyword? https://canonical-subiquity.readthedocs-hosted.com/en/latest/tutorial/providing-autoinstall.html#autoinstall-by-way-of-cloud-config | 14:54 |
| === luna is now known as bittin | ||
| === bittin is now known as bittin_ | ||
| === bittin_ is now known as bittin__ | ||
| mybalzitch | argh I hate uefi | 17:13 |
| patdk-lap | why? | 17:15 |
| mybalzitch | because I don't know how to use it properly | 17:16 |
| mybalzitch | I'm moving my install from legacy to uefi, and its not seeing the boot entry and I'm not sure if its because I didn't install grub properly, or if its because I made a / and /boot/efi parition only and they're both in the mdadm | 17:17 |
| mybalzitch | / is ext4 | 17:17 |
| patdk-lap | only part I dislike is fat32 usage really | 17:17 |
| patdk-lap | did you make a efi partition? | 17:18 |
| patdk-lap | install grub efi, have it init the efi partition | 17:18 |
| patdk-lap | then register that boot option in you uefi bios | 17:19 |
| mybalzitch | thats what /boot/efi is | 17:19 |
| mybalzitch | made it fat32 | 17:19 |
| patdk-lap | so you have like, /boot/efi/EFI/ubuntu | 17:19 |
| mybalzitch | yeah | 17:19 |
| patdk-lap | https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition | 17:22 |
| patdk-lap | you might have to select it manually | 17:23 |
| patdk-lap | it really wants to be booted in uefi mode to have all the efi stuff available | 17:23 |
| patdk-lap | I just did this last weekend on this machine, last one I had not using uefi | 17:23 |
| patdk-lap | but the new motherboard wouldn't boot my m.2 drive in legacy mode, only uefi | 17:23 |
| patdk-lap | do make sure you have grub-efi installed and not grub-pc | 17:25 |
| mybalzitch | I will try this, thank you | 17:27 |
| mybalzitch | oh its failing because I have my efi partition nested inside a mdadm apparently | 17:36 |
| patdk-lap | oh ya, you cannot raid it like that | 17:37 |
| mybalzitch | not if I wanna boot off of it! | 17:38 |
| patdk-lap | it has to be raw, you could use mdadm to do this, but mdadm needs a seperate partition or something to track the metadata | 17:38 |
| patdk-lap | sure you can | 17:38 |
| patdk-lap | I do it | 17:38 |
| patdk-lap | you can use a seperate meatadata partition for mdadm, or use the version of mdadm metadata at end of partition | 17:39 |
| patdk-lap | might have to use v1.0 | 17:41 |
| patdk-lap | you are likely using 1.2 or 1.1 that puts it at the start | 17:41 |
| === alucardromero7 is now known as alucardromero | ||
| === ch0ps3y is now known as Guest422 | ||
| === alucardromero1 is now known as alucardromero | ||
| mybalzitch | heyy I totally redid it and it seems to work now | 18:32 |
| === alucardromero1 is now known as alucardromero | ||
| === miceiken4 is now known as miceiken | ||
| === miceiken9 is now known as miceiken | ||
| === miceiken9 is now known as miceiken | ||
| === miceiken1 is now known as miceiken | ||
| === miceiken0 is now known as miceiken | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!