Ventoy puts me into mountroot

I have tried FreeBSD's memstick .img file on Ventoy and it always has the /dev/ufs/FreeBSD_Install device fail. Anyone know why this happens? I am using the latest Ventoy version (1.1.17)
IMG_0228.jpg
 
I did that and it worked. Thank you! Why don't memstick .img files work well in Ventoy?
I've not used Ventoy so all this is speculation.
if you do the file command on the memstick .img it looks like it has 2 partitions a DOS/MBR boot partition and a "data section".
same file command on an ISO tells you it 9660 CD-ROM filesystem data with a DOS/MBR boot sector.

Perhaps these differences are why. Ventoy sees the 9660 format, sees that it is bootable and starts grabbing what it needs after that. The memstick format, maybe Ventoy sees the 2 partitions and is just grabbing the first partition instead of partition 2.

I have no idea, just speculations. I've always just used dd to write the memstick image directly to the USB device.
 
Ventoy is very nice to use since you can just use 1 USB stick for potentially all your images. Added a new iso/img is just a simple copy to the Ventoy partition. It really saves a lot of pain constantly dd'ing the stick especially cause most USB sticks are slow as snail to write to; or at least the cheap ones I like to use 😆
 
but dd is native on freebsd
I'm not sure how it has any relevance here. Ventoy is not some software that is running on top of FreeBSD or any OS for that matter. It's a boot loader kind of like GRUB. The comparison to dd doesn't make sense because dd isn't a boot loader and does not in any way interact with your BIOS/EFI the way Ventoy does.
 
I'm not sure how it has any relevance here. Ventoy is not some software that is running on top of FreeBSD or any OS for that matter. It's a boot loader kind of like GRUB. The comparison to dd doesn't make sense because dd isn't a boot loader and does not in any way interact with your BIOS/EFI the way Ventoy does.
But ventoy must be written to a USB device, at least the parts that act as a bootloader, currently it looks like there is only a Linux version and a Windows version. The rest of the "ventoy instally" has userland tools that are used to update the existing "ventoy usb thing".

The totality is what I'm talking about. You have a USB device, you copy ventoy boot bits to it, then you use other tools to add images to that usb device.

I'm saying using dd to push the entire image to the usb device is native.
 
But ventoy must be written to a USB device, at least the parts that act as a bootloader, currently it looks like there is only a Linux version and a Windows version. The rest of the "ventoy instally" has userland tools that are used to update the existing "ventoy usb thing".

The totality is what I'm talking about. You have a USB device, you copy ventoy boot bits to it, then you use other tools to add images to that usb device.

I'm saying using dd to push the entire image to the usb device is native.
It's just a one-time deal and you don't even need Windows or Linux for it. They provide a standalone live-cd for you to set that up the first time if you prefer to do so, though using Windows or Linux is more convenient. Once you do that one-time setup, you can just use `cp` `rsync` or even a GUI file manager to transfer ISO's to the partition instead of using `dd` and nuking your USB stick everytime you want to boot something different. It's a small price to pay for that flexibility, really.
 
in order for Ventoy to work it needs to load a module (geom_ventoy). that is needed so it can simulate a disk/partition out of a file. If the module does not load (wrong version or whatever) you'll get the mountroot> stuff. Try a 15.0 image if 15.1 does not work

PS I never used ventoy, this is just my understanding of how it works
 
I have tried FreeBSD's memstick .img file on Ventoy and it always has the /dev/ufs/FreeBSD_Install device fail. Anyone know why this happens? I am using the latest Ventoy version (1.1.17)
I think if I remember correctly, the 15.0 ISO file worked for me. Try that instead of using the img file.
 
Why Ventoy? Why not just follow the instructions in the handbook ? Choosing an image and a dd to a USB stick is easier
Ventoy can handle a bunch of different images at once and you generally just need to copy the relevant images to the disk.

DD to a USB stick is only easier if you're just wanting 1 image. If you just one image, then Ventoy isn't really intended for you anyways.
 
hedwards

Yes, but the question isn't about its usefulness.
I used to use it for Linux distributions.
For FreeBSD, I prefer the native FreeBSD approach from start to finish:
ISO > USB drive > installation or maintenance.
 
hedwards

Yes, but the question isn't about its usefulness.
I used to use it for Linux distributions.
For FreeBSD, I prefer the native FreeBSD approach from start to finish:
ISO > USB drive > installation or maintenance.
That's an entirely different thing, isn't it? It's what I used when I wanted to install FreeBSD 15.0 from scratch, but I think that the release had been out for a while at that point.

I wouldn't personally recommend other methods as ventoy and iventoy will happily also allow you to have isos on there that can help clean up the mess or manage the drives for things where the installer won't.
 
Maybe it didn't work because our dvd / img files aren't 'hybrid'.

Many Linux .isos you can dd to a memory stick and they also function. The FreeBSD .img files are pure image files which ventoy possibly doesn't support.
 
Maybe it didn't work because our dvd / img files aren't 'hybrid'.

Many Linux .isos you can dd to a memory stick and they also function. The FreeBSD .img files are pure image files which ventoy possibly doesn't support.
It's not clear to me what's involved with that, but 15.0 is the last FreeBSD release that is currently listed as tested. Possibly, the easiest thing to do with ventoy is either wait for 15.1 support to be fixed and working or install 15.0 and upgrade from there.
 
hedwards
To access my system I have: An Nvme SSD in an external "sabrent" enclosure that I connect to my PCs I have a perfectly functional and comfortable external FreeBSD boot with a graphical environment
 
Back
Top