Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Manjaro LxQt failed
#1
Hello,
I'm trying to boot "manjaro-lxqt-20.0-minimal-200423-linux56.iso" on a HP8570p in BIOS mode with "ventoy 1.0.9"
I can select the iso and I got the manjaro screen.
Then I just pressed enter to start the manjaro live cd. After a while I got this message:

Code:
ERROR: '/dev/disk/by-label/MANJARO_LXQTM_200' device did not show up after 30seconds
Falling back to interactive prompt

Using the same USB-Stick at a "ASROCK J4105M" the system starts in UEFI mode and everything works as expected.

Henning
Reply
#2
Same error with 1.0.10 Sad
Reply
#3
I got the same problem on a different distro. I have a solution that should work for all distributions.


Ventoy creates a "virtual" disk for us with the ISOs contents on it under the name /dev/dm-0. So to get the system to boot we can just make a link with the name that the system is expecting that points to /dev/dm-0.
After the device times out you should type:
Code:
ln /dev/dm-0 /dev/disk/by-label/MANJARO_LXQTM_200
exit

It should mount the disk and boot fine after exiting  Smile
I hope this fixes your problem.
Reply
#4
What about ventoy-1.0.13?
Reply
#5
Just installed Ventoy 1.0.13.
But the problem hasn't changed.

After timeout I'm at the Monjaro? console [rootfs]#
Tried to do a link like described before. But no device /dev/dm-0

By the way.
The iso label of the iso is set as parm in grub: misolabel=MANJARO_LXQTM_200
Reply
#6
At least in Linux Mint, Ventoy link the filesystem.squashfs file in /dev/loop0, so try:
Code:
ln /dev/loop0 /dev/disk/by-label/MANJARO_LXQTM_200
Reply
#7
Hello,

no luck so far...
Since I get only a blank screen during boot I tried to get more messages ...

In Manjaor Boot Screen I simply press E 
   

Then I have removed the "quiet" option
   

At the next prompt I did the link as described before 
   

Sad

Henning
Reply
#8
When dropped into the rootfs shell, please run 2 commands:

blkid
cat /ventoy/log
Reply
#9
@longpanda
First of all. Thank you for ventoy and your premium support.
 

When booting in MemDisk mode I did not find the ventoy log. But output of blkid is same as when in normal mode (checked with diff)

Here is the output of blkid:
sda is the SSD in my HP-8570p Laptop with Windows 10 and Manjaro already installed 
sdb is the ventoy test stick with sdb1 changed to fat32 yesterday (but same effect with exfat)
Code:
/dev/sda1: LABEL="System-reserviert" BLOCK_SIZE="512" UUID="01D448597B22E280" TYPE="ntfs" PARTUUID="5b954906-01"
/dev/sda2: LABEL="Win10 System" BLOCK_SIZE="512" UUID="01D4485ABCF3D560" TYPE="ntfs" PARTUUID="5b954906-02"
/dev/sda3: UUID="1744b255-a6c2-40fa-84b8-5454064d17f9" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="5b954906-03"
/dev/sda5: UUID="0505199f-1536-4e5d-8ed6-09babc064d2a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="5b954906-05"
/dev/sdb1: UUID="8ED5-3E05" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f12f02ae-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="VTOYEFI" LABEL="VTOYEFI" UUID="4437-4B71" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f12f02ae-02"

Here the log:
Code:
============== VENTOY =================
300 blocks
5724 blocks
kenel version=Linux version 5.6.6-1-MANJARO (builduser@development) (gcc version 9.3.0 (Arch Linux 9.3.0-1)) #1 SMP PREEMPT Tue Apr 21 07:46:00 UTC 2020
kenel cmdline=BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=de_DE keytable=de tz=UTC driver=free nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 misobasedir=manjaro misolabel=MANJARO_LXQTM_200 systemd.show_status=1
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
440000 blocks
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.6.6-1-MANJARO (builduser@development) (gcc version 9.3.0 (Arch Linux 9.3.0-1)) #1 SMP PREEMPT Tue Apr 21 07:46:00 UTC 2020
OS=###manjaro###
Copy dm-disk rule file
Here use notify ...
... start inotifyd listen /ventoy/hook/manjaro/ventoy-inotifyd-hook.sh ...
##### INOTIFYD: /dev/fuse is created ...
##### INOTIFYD: /dev/cuse is created ...
##### INOTIFYD: /dev/btrfs-control is created ...
##### INOTIFYD: /dev/loop-control is created ...
##### INOTIFYD: /dev/net is created ...
##### INOTIFYD: /dev/ppp is created ...
##### INOTIFYD: /dev/mapper is created ...
##### INOTIFYD: /dev/userio is created ...
##### INOTIFYD: /dev/rfkill is created ...
##### INOTIFYD: /dev/core is created ...
##### INOTIFYD: /dev/fd is created ...
##### INOTIFYD: /dev/stdin is created ...
##### INOTIFYD: /dev/stdout is created ...
##### INOTIFYD: /dev/stderr is created ...
##### INOTIFYD: /dev/char is created ...
##### INOTIFYD: /dev/loop0 is created ...
##### INOTIFYD: /dev/loop1 is created ...
##### INOTIFYD: /dev/loop2 is created ...
##### INOTIFYD: /dev/loop3 is created ...
##### INOTIFYD: /dev/loop4 is created ...
##### INOTIFYD: /dev/loop5 is created ...
##### INOTIFYD: /dev/loop6 is created ...
##### INOTIFYD: /dev/loop7 is created ...
##### INOTIFYD: /dev/block is created ...
##### INOTIFYD: /dev/rtc is created ...
##### INOTIFYD: /dev/bus is created ...
##### INOTIFYD: /dev/disk is created ...
##### INOTIFYD: /dev/sr0 is created ...
##### INOTIFYD: /dev/dri is created ...
##### INOTIFYD: /dev/ptp0 is created ...
##### INOTIFYD: /dev/cdrom is created ...
##### INOTIFYD: /dev/fw0 is created ...
##### INOTIFYD: /dev/drm_dp_aux0 is created ...
##### INOTIFYD: /dev/drm_dp_aux1 is created ...
##### INOTIFYD: /dev/drm_dp_aux2 is created ...
##### INOTIFYD: /dev/cdc-wdm0 is created ...
##### INOTIFYD: /dev/cdc-wdm1 is created ...
##### INOTIFYD: /dev/cdc-wdm2 is created ...
##### INOTIFYD: /dev/usb is created ...
##### INOTIFYD: /dev/hidraw0 is created ...
##### INOTIFYD: /dev/fb0 is created ...
##### INOTIFYD: /dev/sdb is created ...
##### INOTIFYD: /dev/sdb1 is created ...
##### INOTIFYD: /dev/sdb2 is created ...
Reply


Forum Jump:


Users browsing this thread: 7 Guest(s)