search

ventoy / Ventoy

A new bootable USB solution.
https://www.ventoy.net
GNU General Public License v3.0
63.27k stars 4.11k forks source link

trying to boot latest archlinux results in emergency mode. #124

Open Abh15h3k opened 4 years ago

Abh15h3k commented 4 years ago

when booting into the archiso it sits at "Waiting 30 seconds for device /dev/disk/by-label/ARCHLINUX..." and then gives the rootfs shell.

now if i'm doing this without memdisk. i can just mount the exfat partition and mount the iso to /run/archiso/bootmount. How do i do the same workaround when using memdisk?

ventoy commented 4 years ago

Please give detail about the Ventoy version? Legacy BIOS or UEFI? archiso name? I tested archlinux-2020.05.01-x86_64.iso in my laptop (legacy+UEFI) and it worked fine. When you drop into the shell, please run cat /ventoy/log and send me the log, thank you.

Abh15h3k commented 4 years ago

Ventoy Version: 1.0.0.9 UEFI iso: archlinux-2020.04.01-x86_64.iso

there is no /ventoy when i press F1 to enable memdisk and select the iso.

ventoy_memdisk_boot

EDIT: same issue with archlinux-2020.05.01-x86_64.iso

Abh15h3k commented 4 years ago

I've updated to 1.0.10-1 and same issue.

Just to clarify here are the steps im following

  1. yay -S ventoy (currently 1.0.10-1)
  2. sudo ventoy -i /dev/sdc (Sandisk Ultrafit 64GB USB3)
  3. sudo mount /dev/sdc1 /mnt
  4. sudo cp archlinux-2020.05.01-x86_64.iso /mnt/
  5. sync && sudo umount /mnt
  6. boot in to the usb drive on a laptop (behaves the same on a desktop as well).
  7. Press F1 to enable memdisk (the iso selection area just flashes black once)
  8. select archlinux-2020.05.01-x86_64.iso.
  9. Then i get the interactive prompt.
ventoy commented 4 years ago

Hi, F1 memdisk mode is only for Live system. So archlinux-2020.05.01-x86_64.iso can not use memdisk mode.

"Waiting 30 seconds for device /dev/disk/by-label/ARCHLINUX..." This error still exist when you use normal boot (without F1) ?

Abh15h3k commented 4 years ago

Hi, F1 memdisk mode is only for Live system. So archlinux-2020.05.01-x86_64.iso can not use memdisk mode.

Oh ok

"Waiting 30 seconds for device /dev/disk/by-label/ARCHLINUX..." This error still exist when you use normal boot (without F1) ?

normal boot is working

But i just tried to boot linux mint ( which has a live system ) and i get this WhatsApp Image 2020-05-19 at 18 03 09

Abh15h3k commented 4 years ago

"Waiting 30 seconds for device /dev/disk/by-label/ARCHLINUX..." This error still exist when you use normal boot (without F1) ?

Ok so right now this a lucky draw. sometimes im thrown into the emergency shell or sometimes it boots properly. when i am thrown into the emergency shell i just have to symlink /dev/dm-0 to /dev/disk/by-label/ARCHLINUX.... and press ctrl+d and it continues booting. Here's the log for this situation Note: the log is of when i tried booting artix (fork of arch) but same behavior in arch as well.

============== VENTOY =================
271 blocks
5724 blocks
kenel version=Linux version 5.5.3-artix1-1 (linux@artixlinux) (gcc version 9.2.1 20200130 (Artix Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Wed, 12 Feb 2020 14:04:08 +0000
kenel cmdline=BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC label=ARTIX_202002
=====ventoy_unpack_initramfs: #/initrd001 0 3037 /initrd001_tmp#
vtx=3037 cat
6096 blocks
=====ventoy_unpack_initramfs: #/initrd002 0 FD37 /initrd002_tmp#
vtx=FD37 xzcat
420114 blocks
terminate with all zero data file
Now hand over to ventoy.sh
#### install vtoytool #####
try /ventoy/tool/vtoytool/00/ ...
vtoytool_64 OK
use vtoy_fuse_iso_64
use unsquashfs_64
use unsquashfs_64
kernel version
Linux version 5.5.3-artix1-1 (linux@artixlinux) (gcc version 9.2.1 20200130 (Artix Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Wed, 12 Feb 2020 14:04:08 +0000
OS=###arch###
use mount_handler ...
######### /ventoy/hook/arch/ventoy-disk.sh  ############
wait_for_usb_disk_ready /dev/sdd ...
wait_for_usb_disk_ready /dev/sdd finish
create_ventoy_device_mapper /dev/sdd --readonly
dmsetup avaliable in system /sbin/dmsetup
device-mapper module check success
==== create ventoy device mapper success ====
no need to replace block device
vstollen commented 4 years ago

Same problem for me with ventoy version 1.0.09 and archlinux-2020.05.01-x86_64.iso.

dirks commented 4 years ago
  1. Power on or Reboot
  2. F12 to get boot selection menu and selecting usb stick or boot after prioritizing usb stick in boot sequence via EFI Settings
  3. Select arch iso entry from ventoy menu
  4. Select Arch Efi CD boot entry from Arch boot menu
  5. Arch starts to boot but as reported above 
    "Waiting 30 seconds for device /dev/disk/by-label/ARCHLINUX...

Different from the original report, I can not mount the exfat partition in the interactive prompt, because the filesystem exfat is unknown.

Abh15h3k commented 4 years ago
  • Ventoy 1.0.11 and 1.0.12 (upgraded)
  • ISO Arch 2020.06.01 and 2020.05.01 (sha1 checked)
  • EFI Boot
  • Dell E7440, Efi Version A17 and A28
  1. Power on or Reboot
  2. F12 to get boot selection menu and selecting usb stick or boot after prioritizing usb stick in boot sequence via EFI Settings
  3. Select arch iso entry from ventoy menu
  4. Select Arch Efi CD boot entry from Arch boot menu
  5. Arch starts to boot but as reported above 
    "Waiting 30 seconds for device /dev/disk/by-label/ARCHLINUX...

Different from the original report, I can not mount the exfat partition in the interactive prompt, because the filesystem exfat is unknown.

Follow these steps

mkdir /mnt
mount /dev/sdX2 /mnt  # mount the fat32 partition
modprobe fuse
mkdir /isos
/mnt/tools/...64 /dev/sdX1 /isos
ventoy commented 4 years ago

Please make a try with Ventoy-1.0.13.

Abh15h3k commented 4 years ago

sorry for the late reply.

with the latest ARCHLINUX iso and ventoy (1.0.14-2) i still get dropped into emergency shell. there is no "/ventoy" for getting the log.

with ARTIXLINUX iso and ventoy (1.0.14-2) i again get dropped into the emergency shell. but i get the "/ventoy" so here's the log for that

============== VENTOY =================
310 blocks
5724 blocks
kenel version=Linux version 5.5.3-artix1-1 (linux@artixlinux) (gcc version 9.2.1 20200130 (Artix Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Wed, 12 Feb 2020 14:04:08 +0000
kenel cmdline=BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC label=ARTIX_202002
remove whole sbin directory
=====ventoy_unpack_initramfs: #/initrd001 0 3037 /initrd001_tmp#
vtx=3037 cat
6096 blocks
=====ventoy_unpack_initramfs: #/initrd002 0 FD37 /initrd002_tmp#
vtx=FD37 xzcat
420114 blocks
terminate with all zero data file
Now hand over to ventoy.sh
#### install vtoytool #####
try /ventoy/tool/vtoytool/00/ ...
vtoytool_64 OK
use vtoy_fuse_iso_64
use unsquashfs_64
use unsquashfs_64
kernel version
Linux version 5.5.3-artix1-1 (linux@artixlinux) (gcc version 9.2.1 20200130 (Artix Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Wed, 12 Feb 2020 14:04:08 +0000
OS=###arch###
use mount_handler ...
######### /ventoy/hook/arch/ventoy-disk.sh  ############
wait_for_usb_disk_ready unknown ...
wait_for_usb_disk_ready unknown ...
wait_for_usb_disk_ready /dev/sda ...
wait_for_usb_disk_ready /dev/sda finish
create_ventoy_device_mapper /dev/sda --readonly
dmsetup avaliable in system /sbin/dmsetup
device-mapper module check success
==== create ventoy device mapper success ====
no need to replace block device
ventoy commented 4 years ago

What about the latest release?

CrustyB commented 4 years ago

Came here via search. 1.0.28 and Arch ISO archlinux-2020.11.01-x86_64.iso. Drops to emergency shell. No persistence, no memdisk, using efi boot. For reference, Manjaro works just fine.

ventoy commented 4 years ago

Came here via search. 1.0.28 and Arch ISO archlinux-2020.11.01-x86_64.iso. Drops to emergency shell. No persistence, no memdisk, using efi boot. For reference, Manjaro works just fine.

I test archlinux-2020.11.01-x86_64.iso with Ventoy-1.0.28 in UEFI mode (on a VirtualMachine) and it works fine. When you dropped into the emergency shell please run two commands and give me the photo about the output.

cat /ventoy/log
blkid
Karrq commented 3 years ago

This is still having issues at of May 15 2021...

I tried to boot the latest (may 1) archiso via memdisk with ventoy but I got dropped in the emergency shell with the same problem.

I am booting in UEFI mode, tried both with and without secureboot but didn't make a difference. memdiskfind in the hook seems to not return anything, thus the memdisk hook doesn't do anything.

There's no /ventoy folder to search for the log, and blkid just returns the system's disks + the efi ventoy partition and the ventoy exfat partition

alteriks commented 3 years ago

I've recently stumbled upon the problem with booting Archlinux in UEFI mode. I've tried to make Arch ISO with ZFS enabled kernel using mkarchiso tool. It seems that Ventoy during can only boot whenever kernel is named vmlinuz-linux and initramfs is named initramfs-linux.img. After installing zfs-linux-lts package in Archlinux it comes with /boot/vmlinuz-linux-lts and /boot/initramfs-linux-lts.img respectively.

Booting this kernel in CSM/Legacy BIOS mode using syslinux is fine boot UEFI mode gave me a headache, until I found a workaround on SamLukeYes repo - https://github.com/SamLukeYes/archiso-surface/blob/main/airootfs/etc/pacman.d/hooks/linux-dummy.hook I've adapted it to my use-case, so I can use Ventoy with my custom iso file. But maybe we can make Ventoy less picky about file names.

ventoy commented 3 years ago

I've recently stumbled upon the problem with booting Archlinux in UEFI mode. I've tried to make Arch ISO with ZFS enabled kernel using mkarchiso tool. It seems that Ventoy during can only boot whenever kernel is named vmlinuz-linux and initramfs is named initramfs-linux.img. After installing zfs-linux-lts package in Archlinux it comes with /boot/vmlinuz-linux-lts and /boot/initramfs-linux-lts.img respectively.

Booting this kernel in CSM/Legacy BIOS mode using syslinux is fine boot UEFI mode gave me a headache, until I found a workaround on SamLukeYes repo - https://github.com/SamLukeYes/archiso-surface/blob/main/airootfs/etc/pacman.d/hooks/linux-dummy.hook I've adapted it to my use-case, so I can use Ventoy with my custom iso file. But maybe we can make Ventoy less picky about file names.

Please give your original custom iso for test.

Take archlinux-2020.10.01-x86_64.iso for example. There are two files with the same name as follows:

/arch/boot/x86_64/initramfs-linux.img
/EFI/archiso/efiboot.img/arch/boot/x86_64/initramfs-linux.img

What's your situation?

alteriks commented 3 years ago

@ventoy sorry about delay. You can check my building steps in my repo: https://github.com/alteriks/mkarchiso_zfs

ISO file is located on my googledrive: https://drive.google.com/drive/folders/1mxYpSikYOW7W4harSoSxrFd7KtDE-sTH