Open piroman21 opened 3 years ago
What about the latest vtoyboot-1.0.15 ?
On vtoyboot-1.0.15, after updating the kernel, it also does not start.
Did you make a new fresh install ? Please give a photo or a video about how it does not boot.
Yes.
When did you update the kernel? In the virtualbox enviroment or boot in the physical machine by Ventoy?
After update kernel, you have two different kernel? All of the two kernels do not boot?
Can the Fedora boot menu display normal?
From the Ventoy physical machine. After updating, the Fedora menu is not displayed.
Any error or warning message during you update the kernel? any log?
Did you run the vtoyboot.sh of 1.0.15 in the origial VirtualBox enviroment?
Did you create a new VirtualBox VM and make a fresh install of Fedora or you use an old fedora VM ?
Which fedora iso file did you use? How did you update the kernel? Which command did you use? And any other description about the whole process.
I want to reproduce the problem.
VirtualBox 6.1.22 Created a new virtual machine. Enabled EFI. Installed Fedora-Xfce-Live-x86_64-34-1.2.iso https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Spins/x86_64/iso/Fedora-Xfce-Live-x86_64-34-1.2.iso
During installation, I created partitions /boot/efi /boot swap /
[root@fedora ~]# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 vfat FAT32 5449-9CBB 4G 0% /boot/efi ├─sda2 ext4 1.0 416cb822-0929-45bf-8baf-e9cfd192d07d 3,5G 5% /boot ├─sda3 xfs bfb27faa-60a4-4967-8554-55cbd85952ce 33G 13% / └─sda4 swap 1 7c78fd4b-f876-42a6-bb1a-f7f7c4153f12 [SWAP] sr0 zram0 [SWAP]
[root@fedora ~]# mount proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel) devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=960796k,nr_inodes=240199,mode=755,inode64) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=402268k,nr_inodes=819200,mode=755,inode64) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate,memory_recursiveprot) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime,seclabel) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) /dev/sda3 on / type xfs (rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,nosuid,noexec,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22756) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime,seclabel) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel,pagesize=2M) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime,seclabel) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime,seclabel) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel,nr_inodes=409600,inode64) /dev/sda2 on /boot type ext4 (rw,relatime,seclabel) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=201132k,nr_inodes=50283,mode=700,uid=1000,gid=1000,inode64) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=201132k,nr_inodes=50283,mode=700,inode64)
After installing the system, I downloaded and launched vtoyboot-1.0.15 I copied the vdi image to the usb-hdd.
It booted from the disk. Executed dnf update. After updating and rebooting Fedora menu is not displayed. And there is a reboot back to the ventoy menu.
Please try this new vtoyboot release.
!!! Important !!! After you execute dnf update, you need to run vtoyboot.sh again before you reboot the system. vtoyboot-1.0.16.tar.gz
Hi. Fedora 34 does not boot after system kernel upgrade.