can't launch into the installer

I got this strange logs when I launch the live cd using ventoy
14 Replies
...KhofeKat?
...KhofeKat?OP4d ago
No description
wolfyreload
wolfyreload4d ago
Might be worth comparing the hashes/checksums of the ISO that you copied onto the USB vs the expected one on the website If it doesn't match you'll need to download the ISO agian. I did a short video on how to do the checksums, https://youtu.be/wUDbMJtR1sM
...KhofeKat?
...KhofeKat?OP3d ago
Okay
...KhofeKat?
...KhofeKat?OP3d ago
It match
No description
...KhofeKat?
...KhofeKat?OP3d ago
No description
...KhofeKat?
...KhofeKat?OP3d ago
This might also help to debugging, it stuck here for like 2-5 mins then proceed into this one [Refer to reply] Also happens when using fedora kinonite Seriously what is going on @@ I fixed it, appararently you have to switch your ventoy usb from auto to HDD in the bios to work (for me)
HikariKnight
HikariKnight3d ago
those usb errors, if you keep getting them and the boot hangs on it in the future, it usually is a usb hub or some usb device is messing up, i would suggest unplugging it and keeping it disconnected overnight (dont have an ETA on how long this will take as it varies depending on which caps and how many the device has) to fully discharge the caps, that usually fixes those issues.
...KhofeKat?
...KhofeKat?OP3d ago
Oh... now that you mentioned it, i plug a usb hub Well noted for future So thanks for the info
HikariKnight
HikariKnight3d ago
yw since i dont have an ETA for how long it takes to drain the caps i just use "overnight" as a catch all as that will be long enough if you unplug, wait lets say 2 hours and its not enough and you re-plug, you just wasted 2 hours and reset the draining progress :clueless: so better just do overnight when you dont use the hub for a long time and that will be enough for all the caps in any usb device
...KhofeKat?
...KhofeKat?OP3d ago
Ahh I see, thanks for the precautions, for my futureself so he wouldnt be pissed :dispair: I know this is out of my topic of the question mount: nofail: unknown filesystem type '0'. dmesg(1) may have more information after failed mount system call. But I got this issue xd After following the auto mount guide
HikariKnight
HikariKnight3d ago
your fstab is wrong please paste it in here within ``` text here ```
...KhofeKat?
...KhofeKat?OP3d ago
UUID=b25c2be1-de30-4b7f-8058-5a8a170c7e05 / btrfs subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
UUID=ef680bd9-6f3e-4741-b5db-1d23297cecf1 /boot ext4 defaults 1 2
UUID=F49B-80FE /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=b25c2be1-de30-4b7f-8058-5a8a170c7e05 /home btrfs subvol=home,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
UUID=b25c2be1-de30-4b7f-8058-5a8a170c7e05 /var btrfs subvol=var,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
ext4 nofail 0 0 0 0
UUID=8cf6826a-4eec-4565-8ec4-5a47f30220a1 /var/mnt/ext4 ext4 defaults,noatime,errors=remount-ro,nofail,rw,users,exec
UUID=b25c2be1-de30-4b7f-8058-5a8a170c7e05 / btrfs subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
UUID=ef680bd9-6f3e-4741-b5db-1d23297cecf1 /boot ext4 defaults 1 2
UUID=F49B-80FE /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=b25c2be1-de30-4b7f-8058-5a8a170c7e05 /home btrfs subvol=home,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
UUID=b25c2be1-de30-4b7f-8058-5a8a170c7e05 /var btrfs subvol=var,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
ext4 nofail 0 0 0 0
UUID=8cf6826a-4eec-4565-8ec4-5a47f30220a1 /var/mnt/ext4 ext4 defaults,noatime,errors=remount-ro,nofail,rw,users,exec
HikariKnight
HikariKnight3d ago
ext4 nofail 0 0 0 0 this line is wrong remove it
...KhofeKat?
...KhofeKat?OP3d ago
Ah yes that fixes it How in the world it get there?! Anyway thanks once again!

Did you find this page helpful?