Error 19

H

Hello

Tried disable acpi= hostres
Tried switching usb from 3.0 port to 2.0
1) I think the solution is to do something like using labels instead of device name in fstab. But I haven't installed the system yet, and trying to install it.

2) For example, linux distributions provide a .iso file, so why does freebsd gives both .iso and .img files? why does the handbook say use .img for usb even though .iso would work the same?

3) Also I downloaded the dvd .iso file as i use ventoy (one usb can hold multiple different distribution images, rather than only one). does .img file would also work in this scenario or only .iso.

Thank you!


IMG 20260331 214406 338
 
Hello said:
3) Also I downloaded the dvd .iso file as i use ventoy (one usb can hold multiple different distribution images, rather than only one). does .img file would also work in this scenario or only .iso.
Click to expand...
I dd'd a FreeBSD 14 release to USB and it worked fine (straight dd/no Ventoy); I was confused on that too initially but iirc in an announcement page it mentioned that could be done for non-memstick images
 
Hello said:
Tried disable acpi
Click to expand...
That option should probably be removed. It doesn't change anything, modern systems don't even work without ACPI.

Hello said:
so why does freebsd gives both .iso and .img files?
Click to expand...
They are set up differently. A CD/DVD image (ISO) is read-only, in order for the system to properly boot it has to have some way of writing temp files for example. The CD image is set up specifically for that situation. The ".img" is a plain "harddisk" type setup, i.e. it assumes it has a writable filesystem.

Hello said:
why does the handbook say use .img for usb even though .iso would work the same?
Click to expand...
Older systems aren't capable of booting an ISO image from a USB stick. And because an ISO is inherently read-only they do not work the same, although it may appear that way.
 
What is the benefit of writable filesystem? Does it mean it is a portable system with persistent storage (os on the same usb)?
Is there a live bootable media/gui for freebsd?

And how can I solve my main issue?

Thank you :)
 
Hello said:
3) as i use ventoy (one usb can hold multiple different distribution images, rather than only one). does .img file would also work in this scenario or only .iso.
Click to expand...
According to the Ventoy website, FreeBSD-15.0-RELEASE-amd64-disc1.iso | -bootonly.iso are listed as supported.

Have you installed the latest available Ventoy version?

Regarding .img files: What is Ventoy
With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly.
Click to expand...
Also, forum member fmc000 confirmed, FreeBSD (15.0-STABLE in his case) .img images are bootable from Ventoy:

https://forums.freebsd.org/threads/installing-15-0-using-ventoy-does-not-work.100559/post-730012 .
 
T-Daemon said:
According to the Ventoy website, FreeBSD-15.0-RELEASE-amd64-disc1.iso | -bootonly.iso are listed as supported.

Have you installed the latest available Ventoy version?

Regarding .img files: What is Ventoy

Also, forum member fmc000 confirmed, FreeBSD (15.0-STABLE in his case) .img images are bootable from Ventoy:

https://forums.freebsd.org/threads/installing-15-0-using-ventoy-does-not-work.100559/post-730012 .
Click to expand...
Thanks for your answer! I dont think I am using the latest version, but I dont think that is the problem. I found people having this same problem more than a decade ago.
 
Hello said:
Thanks for your answer! I dont think I am using the latest version, but I dont think that is the problem. I found people having this same problem more than a decade ago.
Click to expand...
Lol. Seriously... These posts are from a decade ago are and that's your reference?

Try without Ventoy. This software is known to fail with each new version of FreeBSD.
 
You must log in or register to reply here.
Back
Top