Issue install 20.04 with autoinstall
Locked
Issue install 20.04 with autoinstall
 
|
I am getting the below issue when installing with autoinstall.
2021-01-20 15:03:14,014 DEBUG subiquitycore.controller.filesystem:171 self.ai_data = {'layout': {'name': 'direct'}} 2021-01-20 15:03:14,015 ERROR root:39 finish: subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: FAIL: 'NoneType' object has no attribute 'grub_device' Below is the log. What do I do with that ??? My config section is easy.. storage: layout: name: direct Thanks, Jerry -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
On Wed, Jan 20, 2021 at 5:20 PM Jerry Geis <[hidden email]>
wrote: > > I am getting the below issue when installing with autoinstall. > > 2021-01-20 15:03:14,014 DEBUG subiquitycore.controller.filesystem:171 self.ai_data = {'layout': {'name': 'direct'}} > 2021-01-20 15:03:14,015 ERROR root:39 finish: subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: FAIL: 'NoneType' object has no attribute 'grub_device' > > Below is the log. > > What do I do with that ??? > > My config section is easy.. > storage: > layout: > name: direct Please post your entire user-data. -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
HI Tom - #cloud-config autoinstall: version: 1 early-commands: - systemctl stop ssh # otherwise packer tries to connect and exceed max attempts network: network: version: 2 ethernets: eth0: dhcp4: yes dhcp-identifier: mac eno1: dhcp4: yes dhcp6: no dhcp-identifier: mac enp1s0: dhcp4: yes dhcp6: no dhcp-identifier: mac apt: preserve_sources_list: false primary: - arches: [amd64] uri: "http://archive.ubuntu.com/ubuntu/" ssh: install-server: yes allow-pw: no identity: hostname: VMImage username: silentm password: $1$xyz$V5reF9l3SpYlSCJ7ebtij0 locale: en_US packages: - build-essential - gdb - nfs-common - network-manager - net-tools user-data: timezone: America/New_York disable_root: false late-commands: - echo Section - late-commands > /target/root/late-commands debconf-selections: | storage: layout: name: direct users: - default - name: silentm passwd: $1$xyz$V5reF9l3SpYlSCJ7ebtij0 shell: /bin/bash lock-passwd: false ssh_pwauth: True chpasswd: { expire: False } sudo: ALL=(ALL) NOPASSWD:ALL groups: users, silentm Jerry On Sat, Jan 23, 2021 at 3:21 PM Tom H <[hidden email]> wrote: On Wed, Jan 20, 2021 at 5:20 PM Jerry Geis <[hidden email]> -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
On Sat, Jan 23, 2021 at 9:33 PM Jerry Geis <[hidden email]>
wrote: > On Sat, Jan 23, 2021 at 3:21 PM Tom H <[hidden email]> wrote: >> >> Please post your entire user-data. > > #cloud-config > autoinstall: > version: 1 > early-commands: > - systemctl stop ssh # otherwise packer tries to connect and exceed max attempts > network: > network: > version: 2 > ethernets: > eth0: > dhcp4: yes > dhcp-identifier: mac > eno1: > dhcp4: yes > dhcp6: no > dhcp-identifier: mac > enp1s0: > dhcp4: yes > dhcp6: no > dhcp-identifier: mac > apt: > preserve_sources_list: false > primary: > - arches: [amd64] > uri: "http://archive.ubuntu.com/ubuntu/" > ssh: > install-server: yes > allow-pw: no > identity: > hostname: VMImage > username: silentm > password: $1$xyz$V5reF9l3SpYlSCJ7ebtij0 > locale: en_US > packages: > - build-essential > - gdb > - nfs-common > - network-manager > - net-tools > user-data: > timezone: America/New_York > disable_root: false > late-commands: > - echo Section - late-commands > /target/root/late-commands > debconf-selections: | > storage: > layout: > name: direct > users: > - default > - name: silentm > passwd: $1$xyz$V5reF9l3SpYlSCJ7ebtij0 > shell: /bin/bash > lock-passwd: false > ssh_pwauth: True > chpasswd: { expire: False } > sudo: ALL=(ALL) NOPASSWD:ALL > groups: users, silentm 1) You shouldn't define "silentm" under "identity" and "users". 2) AFAIK, "users" is supposed to be a subcategory of "user-data". user-data: #cloud-config users: ... -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
On Sun, Jan 24, 2021 at 7:01 PM Tom H <[hidden email]> wrote:
This works (pretty close to your file): #cloud-config autoinstall: version: 1 network: network: version: 2 ethernets: ens3: dhcp4: yes dhcp-identifier: mac apt: preserve_sources_list: false primary: - arches: [amd64] uri: "http://archive.ubuntu.com/ubuntu/" ssh: install-server: yes allow-pw: no identity: hostname: vmimage username: silent password: "hashed_password" locale: en_US packages: - net-tools user-data: #cloud-config timezone: America/New_York storage: layout: name: direct -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
Hi Tom, When I do this : storage: layout: name: direct I get a different error. It says "nontype object has not attribute grub_device" Thanks, Jerry On Sun, Jan 24, 2021 at 2:23 PM Tom H <[hidden email]> wrote: On Sun, Jan 24, 2021 at 7:01 PM Tom H <[hidden email]> wrote: -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
On Sun, Jan 24, 2021 at 8:27 PM Jerry Geis <[hidden email]>
wrote: > > When I do this : > storage: > layout: > name: direct > > I get a different error. It says "nontype object has not > attribute grub_device" I have no idea what it might be. Go to a shell (via the "help" menu), and check the logs. Hopefully there'll be something there. -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
HI Tom, I did do that - All it says is the same. Nothing additional there. I have looked at /var/log files and also the /var/log/installer files. Nothing additional. I have "not" been able to get a "storage" that works. This was the last one I tried : storage: layout: name: direct config: - type: disk id: disk0 match: size: largest - type: partition id: boot-partition device: disk0 size: 512M - type: partition id: root-partition device: disk0 size: -1 This also gives the same error: about the grub_device. I tried adding "grub_device: false" after the type: disk, same error. I tried adding after device: disk0 same error. Thanks for any suggestion. I am at a loss. Jerry On Sun, Jan 24, 2021 at 3:21 PM Tom H <[hidden email]> wrote: On Sun, Jan 24, 2021 at 8:27 PM Jerry Geis <[hidden email]> -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
On Sun, Jan 24, 2021 at 9:31 PM Jerry Geis <[hidden email]>
wrote: > > I have "not" been able to get a "storage" that works. This was the > last one I tried : > storage: > layout: > name: direct > config: > - type: disk > id: disk0 > match: > size: largest > - type: partition > id: boot-partition > device: disk0 > size: 512M > - type: partition > id: root-partition > device: disk0 > size: -1 > > This also gives the same error: about the grub_device. > I tried adding "grub_device: false" after the type: disk, same > error. I tried adding after device: disk0 same error. I'e just tried this and it works for me. Does it work for you? #cloud-config autoinstall: ... storage: version: 1 layout: name: direct grub: install_devices: - disk0 swap: size: 0 config: - id: disk0 type: disk match: size: largest ptable: mbr wipe: superblock - id: disk0-boot type: partition device: disk0 size: 512MB - id: disk0-root type: partition device: disk0 size: -1 - id: disk0-boot-fs type: format volume: disk0-boot fstype: ext4 - id: disk0-root-fs type: format volume: disk0-root fstype: ext4 - id: disk0-boot-mount type: mount device: disk0-boot-fs path: "/boot" - id: disk0-root-mount type: mount device: disk0-root-fs path: "/" ... -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
Hi Tom, Thanks - I tried this - It stops with the same error: AttributeError: 'NoneType' object has no attribute 'grub_device' The VM I'm trying to install on looks like: Disk /dev/sda: 128.8 GB, 128849018880 bytes, 251658240 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x000d8b93 Device Boot Start End Blocks Id System /dev/sda1 * 2048 2099199 1048576 83 Linux /dev/sda2 2099200 251658239 124779520 8e Linux LVM Jerry Jerry On Mon, Jan 25, 2021 at 9:00 AM Tom H <[hidden email]> wrote: On Sun, Jan 24, 2021 at 9:31 PM Jerry Geis <[hidden email]> -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
On Mon, Jan 25, 2021 at 3:28 PM Jerry Geis <[hidden email]>
wrote: > > Thanks - I tried this - It stops with the same error: > > AttributeError: 'NoneType' object has no attribute 'grub_device' > > The VM I'm trying to install on looks like: > > Disk /dev/sda: 128.8 GB, 128849018880 bytes, 251658240 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk label type: dos > Disk identifier: 0x000d8b93 > > Device Boot Start End Blocks Id System > /dev/sda1 * 2048 2099199 1048576 83 Linux > /dev/sda2 2099200 251658239 124779520 8e Linux LVM 1) How are you ending up with an LVM partition? You must be using a different "storage:" section. 2) I ran "fdisk -l" in the VM that I'd created, and it wasn't what I'd requested in the autoinstall file. It seems that you can use storage: layout: or storage: config: and I used both in my user-data. "layout:" that won the day, and all that I had was a biosboot partition and a root partition. This did the right thing: storage: config: - id: disk0 type: disk match: size: largest ptable: gpt grub_device: true wipe: superblock - id: disk0-biosboot type: partition flag: bios_grub device: disk0 size: 1MB - id: disk0-boot type: partition device: disk0 size: 512MB - id: disk0-root type: partition device: disk0 size: -1 - id: disk0-boot-fs type: format volume: disk0-boot fstype: ext4 - id: disk0-root-fs type: format volume: disk0-root fstype: ext4 - id: disk0-boot-mount type: mount device: disk0-boot-fs path: "/boot" - id: disk0-root-mount type: mount device: disk0-root-fs path: "/" -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
On Mon, Jan 25, 2021 at 12:56 PM Tom H <[hidden email]> wrote: On Mon, Jan 25, 2021 at 3:28 PM Jerry Geis <[hidden email]> HI Tom, I am "starting" with a previous linux install. That is what the fdisk is from above. I am editing the /etc/grub.d/40_custom - adding my menu, setting the default /etc/default/grub to run my custom install and of course all my values are set for autoinstall, ds=XXX ip=dhcp url=XXX - this settings seem fine as its downloading my file , and downloading the live-server iso (I see all that on screen and have verified in the installer log). Thanks, Jerry -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
In reply to this post by Jerry Geis
Hi Tom, So - If I use the "standard" storage: layout: name: direct And use the live-server 20.04 CD - and hit F6 and enter my "autoinstall ds=nocloud-net;s=https://XXX/pathToAutoinstall This works - You example storage works also... So that is great. However - what I was trying to do is "remotely" update an OLD linux install and replace with 20.04. so to do that I was trying edit the /etc/grub.d/40_custom and the menu item autoinstall ds=nocloud-net;s=https://XXX/pathToAutoinstall ip=dhcp url=pathToLiveServer set the /etc/default/grub to the id of my 40_custom and run the grub - update for the old system. This boots and starts - but I get that silly grub_device message. What am I not doing correctly to "remotely" update an old linux box. Thanks, Jerry On Sun, Jan 24, 2021 at 3:29 PM Jerry Geis <[hidden email]> wrote:
-- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
Hey there,
Jerry Geis wrote: >However - what I was trying to do is "remotely" update an OLD linux >install and replace with 20.04. >so to do that I was trying edit the /etc/grub.d/40_custom and the >menu item > autoinstall ds=nocloud-net;s=https://XXX/pathToAutoinstall ip=dhcp >url=pathToLiveServer >set the /etc/default/grub to the id of my 40_custom and run the grub >- update for the old system. >This boots and starts - but I get that silly grub_device message. If the old Linux installation is older than Ubuntu 9.10 Karmic Koala, then you might be running into a Grub compatibility issue. Ubuntu switched from Grub to Grub2 in Karmic Koala. -- Little Girl There is no spoon. -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
Thanks. its actually a CentOS 7 system. Used CentOS from 4-7. Now looking at switch to Ubuntu. I tried grub2-mkconfig - got the same result. AttributeError: 'NoneType' object has not attribute 'grub_device' Jerry On Mon, Jan 25, 2021 at 8:33 PM Little Girl <[hidden email]> wrote: Hey there, -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
Hey there,
Jerry Geis wrote: >Thanks. its actually a CentOS 7 system. Used CentOS from 4-7. Now >looking at switch to Ubuntu. >I tried grub2-mkconfig - got the same result. >AttributeError: 'NoneType' object has not attribute 'grub_device' Ah, okay. I'm out of my element with this, but are either of these of any use? https://ubuntu.com/server/docs/install/autoinstall-reference https://askubuntu.com/questions/661512/how-to-remotely-control-which-os-grub-boots -- Little Girl There is no spoon. -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
In reply to this post by Jerry Geis
On Mon, Jan 25, 2021 at 7:14 PM Jerry Geis <[hidden email]> wrote:
> > I am "starting" with a previous linux install. That is what the > fdisk is from above. I am editing the /etc/grub.d/40_custom - > adding my menu, setting the default /etc/default/grub to run my > custom install and of course all my values are set for > autoinstall, ds=XXX ip=dhcp url=XXX - this settings seem fine as > it's downloading my file, and downloading the live-server iso (I > see all that on screen and have verified in the installer log). OK. But, if you're not wiping out your LVM CentOS installation, you'll have to run some pre-installation "lvreduce" and similar commands to install Ubuntu on this disk, whether you're installing manually or installing Ubuntu via autoinstall (or installing another CentOS via kickstart). -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
Re: Issue install 20.04 with autoinstall
|
|
Hi Tom Thanks - I dont have any lvm on CentOS 7. Just partition 1,2, and 3. I dont know what is not making grub not boot. My storage is: storage: version: 1 layout: name: direct grub: install_devices: - disk0 swap: size: 0 config: - id: disk0 type: disk match: size: largest ptable: mbr wipe: superblock - id: disk0-boot Jerry On Fri, Jan 29, 2021 at 10:21 AM Tom H <[hidden email]> wrote: On Mon, Jan 25, 2021 at 7:14 PM Jerry Geis <[hidden email]> wrote: -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
|
|
In reply to this post by Jerry Geis
On Tue, Jan 26, 2021 at 1:33 AM Jerry Geis <[hidden email]>
wrote: > So - If I use the "standard" > > storage: > layout: > name: direct > > And use the live-server 20.04 CD - and hit F6 and enter my > "autoinstall ds=nocloud-net;s=https://XXX/pathToAutoinstall > This works - You example storage works also... So that is great. Good! You're welcome. > However - what I was trying to do is "remotely" update an OLD > linux install and replace with 20.04. so to do that I was trying > edit the /etc/grub.d/40_custom and the menu item autoinstall > ds=nocloud-net;s=https://XXX/pathToAutoinstall ip=dhcp > url=pathToLiveServer set the /etc/default/grub to the id of my > 40_custom and run the grub - update for the old system. This boots > and starts - but I get that silly grub_device message. > > What am I not doing correctly to "remotely" update an old linux > box. As I said in my earlier reply today, you're going to have to run some pre-installation LVM commands in order to create a 2nd LV within the CentOS VG (to keep it simple), and use that LV as Ubuntu's root volume. -- ubuntu-users mailing list [hidden email] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users |
«
Return to ubuntu-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |