Cannot boot customized Server ISO with updated kernel
Hi guys!
I'm using Cubic version 2021.06-
I'm trying to customize a ubuntu-
It turns out that I cannot boot from the resulting iso, it opens Grub and when I select the Install Ubuntu it freezes.
Can you help?
Thank you in advance!
Jean Marrara
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Cubic Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Jean Marrara
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
How did you upgrade the kernel?
Does it boot/install if you do not upgrade the kernel?
Revision history for this message
|
#2 |
Hi,
I`ve upgraded the Kernel using the commands below (from the chroot/virtual environment).
wget -c https:/
wget -c https:/
wget -c https:/
wget -c https:/
dpkg -i *.deb
Yes, it will boot and start the installer if I do not upgrade the kernel.
Thank you in advance!
Revision history for this message
|
#3 |
Did dpkg automatically update-initramfs ?
If not you may need to do that.
On the Options page, Kernel tab, did you select your newly installed kernel, or you used the default kernel from the original ISO?
This kernel is used for bootstrapping the ISO. You may want to continue to select the original ISO kernel on this tab.
The drawback is that once your ISO boots, it will be running the old kernel in the Live Environment.
However, once you install the OS, the most recently added kernel is used in the newly installed system.
Revision history for this message
|
#4 |
Yes, it updated the initramfs and Linuz and I selected the new kernel on Kernel Tab.
If I select the default kernel from original ISO it works fine.
However, I have this new i225 network interface that I need to enable upon installation/live CD and need new kernel for that.
It seems that when initramfs is updated the live iso init script does not work properly.
Revision history for this message
|
#5 |
I tested this using "xubuntu-
-------
( 1 ) DOWNLOAD KERNELS
-------
In Cubic, I executed the following...
root@cubic:~# mkdir kernels
root@cubic:~# cd kernels
root@cubic:
root@cubic:
root@cubic:
root@cubic:
-------
( 2 ) LIST CURRENT KERNELS
-------
root@cubic:
-rw------- 1 root root 4738430 Jul 9 2020 System.
-rw-r--r-- 1 root root 237773 Jul 9 2020 config-
drwxr-xr-x 2 root root 80 Jul 31 2020 grub
lrwxrwxrwx 1 root root 27 Jul 31 2020 initrd.img -> initrd.
lrwxrwxrwx 1 root root 27 Jul 31 2020 initrd.img.old -> initrd.
-rw-r--r-- 1 root root 182704 Feb 13 2020 memtest86+.bin
-rw-r--r-- 1 root root 184380 Feb 13 2020 memtest86+.elf
-rw-r--r-- 1 root root 184884 Feb 13 2020 memtest86+
lrwxrwxrwx 1 root root 24 Jul 31 2020 vmlinuz -> vmlinuz-
lrwxrwxrwx 1 root root 24 Jul 31 2020 vmlinuz.old -> vmlinuz-
-------
( 3 ) INSTALL NEW KERNEL
-------
root@cubic:
Selecting previously unselected package linux-headers-
(Reading database ... 143400 files and directories currently installed.)
Preparing to unpack linux-headers-
Unpacking linux-headers-
Selecting previously unselected package linux-headers-
Preparing to unpack linux-headers-
Unpacking linux-headers-
Selecting previously unselected package linux-image-
Preparing to unpack linux-image-
Unpacking linux-image-
Selecting previously unselected package linux-modules-
Preparing to unpack linux-modules-
Unpacking linux-modules-
Setting up linux-headers-
Setting up linux-headers-
Setting up linux-image-
I: /boot/vmlinuz.old is now a symlink to vmlinuz-
I: /boot/initrd.
I: /boot/vmlinuz is now a symlink to vmlinuz-
I: /boot/initrd.img is now a symlink to initrd.
Setting up linux-modules-
Processing triggers for linux-image-
/etc/kernel/
update-initramfs: Generating /boot/initrd.
cryptsetup: ERROR: Couldn't resolve device tmpfs
cryptsetup: WARNING: Couldn't determine root device
W: Possible missing firmware /lib/firmware/
W: Possible missing firmware /lib/firmware/
W: Possible missing firmware /lib/firmware/
W: Possible missing firmware /lib/firmware/
-------
( 4 ) LIST NEW INSTALLED KERNELS
-------
root@cubic:
-rw------- 1 root root 5894469 Dec 13 2020 System.
-rw------- 1 root root 4738430 Jul 9 2020 System.
-rw-r--r-- 1 root root 250506 Dec 13 2020 config-
-rw-r--r-- 1 root root 237773 Jul 9 2020 config-
drwxr-xr-x 2 root root 80 Jul 31 2020 grub
lrwxrwxrwx 1 root root 32 Aug 30 16:16 initrd.img -> initrd.
-rw-r--r-- 1 root root 90568833 Aug 30 16:16 initrd.
lrwxrwxrwx 1 root root 32 Aug 30 16:16 initrd.img.old -> initrd.
-rw-r--r-- 1 root root 182704 Feb 13 2020 memtest86+.bin
-rw-r--r-- 1 root root 184380 Feb 13 2020 memtest86+.elf
-rw-r--r-- 1 root root 184884 Feb 13 2020 memtest86+
lrwxrwxrwx 1 root root 29 Aug 30 16:16 vmlinuz -> vmlinuz-
-rw------- 1 root root 14143520 Dec 13 2020 vmlinuz-
lrwxrwxrwx 1 root root 29 Aug 30 16:16 vmlinuz.old -> vmlinuz-
-------
( 5 ) GENERATE CUSTOM ISO
-------
On Cubic's Option page, Kernel tab, I ensured that Kernel Version 5.10.0-051000 was selected.
Then I proceeded to generate the ISO.
-------
( 6 ) TEST ISO
-------
I was able to successfully boot into the generated ISO in VirtualBox.
-------
( 7 ) VERIFY KERNEL
-------
Here is the output after logging into the customized Live ISO...
xubuntu@xubuntu:~$ uname -r
5.10.0-
xubuntu@xubuntu:~$ lsb_release --description
Description: Xubuntu 20.04.1 2021.08.30 LTS customized using Cubic on 2021-08-30 16:04
Revision history for this message
|
#6 |
Hi Cubic PPA,
Tried exact same steps with ubuntu-
However, when I tried the same with ubuntu-
Revision history for this message
|
#7 |
I'll try with the 20.04 server ISO.
May be there is a difference.
Revision history for this message
|
#8 |
Hi all,
I believe I fixed the issue, on ubuntu-
Thank you!
Revision history for this message
|
#9 |
My solution only works for the Ubuntu Server Live Install which comes with the new subiquity installer. It does not work for the ubuntu-
I need to user debian installer because I`m using a preseed file ad subiquty does not accept this type of files.
Can you help?
Revision history for this message
|
#10 |
I thought you were working with Ubuntu 20.04 based on your original question?
Are you trying to customize "ubuntu-
Just so I am clear,
- Ubuntu 18.04 Server uses a debian installer ?
- Ubuntu 20.04 Server uses Sububiquity ?
Revision history for this message
|
#11 |
My understanding is that you want to use ubuntu-
You also want to be able to install kernel 5.10.0-
Let me know if I understand your requirements correctly?
Revision history for this message
|
#12 |
I just downloaded ubuntu-
You were right that casper needs to be installed.
But initramfs-tools does not need to be installed.
I also added the missing i915 firmware modules, although it is not necessary.
I think you should try customizing 18.04.5 server again; it worked for me.
Here are the steps I followed...
=======
apt update
apt install --no-install-
mkdir -p /lib/firmware/i915
cd /lib/firmware/i915
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
wget https:/
mkdir ~/kernels
cd ~/kernels
wget https:/
wget https:/
wget https:/
wget https:/
dpkg -i *.deb
After generating the customized ISO, I installed the OS, and I was able to login and verify the release and kernel version:
$ uname -r
5.10.0-
$ lsb_release --description
Description: Ubuntu-Server 18.04.5 2021.08.31 customized using Cubic on 2021-08-31 22:35
Revision history for this message
|
#13 |
Thank you for the testing it.
I`m trying to customize Ubuntu 18.04 Server with kernel 5.10.0-
The ubuntu-
The ubuntu-
Revision history for this message
|
#14 |
Can you share the download links for both ISOs?
If you share the links, I will download these and see what can be done.
Revision history for this message
|
#16 |
Can you explain what you mean when you say, "ubuntu-
When I look in the /preseed directory of ubuntu-
cli.seed
cloud.seed
hwe-cli.seed
hwe-cloud.seed
hwe-
hwe-
hwe-
ubuntu-
ubuntu-
ubuntu-
Isn't it fair to assume that these files must be used by the installer, if they are present on the ISO?
How does one determine if preseed is supported or not supported?
Revision history for this message
|
#17 |
You're right, the preseed files are still there (on 18.04.5-
Tried the following on a non touched ubuntu-
#kvm -no-reboot -m 1024 -drive file=image.
On Grub, added: file=/cdrom/
It starts the installer, then in the installer checked the Installer version and it says: Ubuntu Server Installer as you can check in the link below
https:/
Also I can check subiquity is running instead of debian-intall (screenshot below):
https:/
Also, preseed was not used during installation at all.
Thank you for all your help!!!!
Revision history for this message
|
#18 |
I understand that you want to customize Ubuntu server with a specific kernel.
You also want a version of Ubuntu that supports preseed, so you can do an automated install.
Unfortunately, newer versions of the Ubuntu server ISO do not allow presseeding.
Would you be willing to consider using cloud-init?
It seems to allow automated installs and customization, just like preseed.
If you could get cloud-init to work like preseed, would that suit your needs?
Revision history for this message
|
#19 |
HI guys, yes cloud-init would work. Sorry for the delay in the response.
Revision history for this message
|
#20 |
Although I am able to install the 5.10 kernel in Cubic, cloud-init keeps overwriting the installed kernel with 5.11.
Cloud-init seems to do an update on its own, and I haven't been able to figure out how to stop that.
Nevertheless, here's some info. May be it can help you or give you some insight...
Download the Ubuntu 21.04 Live Server ISO:
http://
-------
Cubic Options page, Kernel tab
-------
On the Options page, Kernel tab, select
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
5.10.62-051062 Kernel Version
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-------
Cubic Options page, Preseed tab
-------
On the Options page, Preseed tab, add two new cloud-init configuration files.
(1)
Click on the "preseed" folder, and then click the "Create new file" button in the headerbar.
Create a new file named "meta-data".
Leave this file blank.
(2)
Click on the "preseed" folder, and then click the "Create new file" button in the headerbar.
Create a new file named "user-data".
Paste the following into the new "user-data" file:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#cloud-config
autoinstall:
version: 1
# Update the installer?
refresh-
update: no
# interactive-
# - storage
locale: en_US.UTF-8
keyboard:
layout: us
identity:
hostname: ubuntu-server
# The encrypted password is ubuntu
password: "$6$exDY1mhS4KU
username: ubuntu
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-------
Cubic Options page, Boot tab
-------
On the Options page, Boot tab, add the following menuentry above the "Ubuntu Server" menuentry line.
(Notice that we added: autoinstall "ds=nocloud;
Note this is for UEFI. You'll have to make similar changes in other boot config files for booting legacy BIOS.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
menuentry "Install Ubuntu Server (Automated)" {
set gfxpayload=keep
linux /casper/vmlinuz boot=casper autoinstall "ds=nocloud;
initrd /casper/initrd.lz
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Revision history for this message
|
#22 |
Thanks Cubic PPA, that solved my question.
Revision history for this message
|
#23 |
Hi Cubic PPA! How are you?
Would you mind if I reopen this question?
I'm now using Cubic Version 2023.05.83 and trying to customize an Ubuntu 22.04 LTS iso image (https:/
I`m following the instructions you provide in the post #20 in this thread and everything works fine!
However, if I try to update the target image by executing "apt-get dist-upgrade --fix-missing" in step 4, virtual environment, then the autoinstall will not work.
Have you faced this issue before?
Thank you in advance!
Revision history for this message
|
#24 |
Opened a new question https:/