Installing FreeBSD

D

Deleted member 85076

Guest
I get this message (booted in multi-user mode.)

Code: 
Loader variables:
vfs.root.mountfrom=zfs:zroot/ROOT/default

Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using <fstype>
      and with the specified (optional) option list.
      
      eg. ufs:/dev/da0s1a
          zfs:zroot/ROOT/default
          cd9660:/dev/cd0 ro
            (which is equivqlent to: mount -t cd9660 -o ro /dev/cd0 /)
  ?                List valid disk boot devices
  .                Yield 1 second (for background tasks)
  <empty line>     Abort manual input
 
Now it says Invalid signature detected
Disabled Secure boot solved this!
IMG_0241.jpeg

Think the Ports tree is definately recommended here
IMG_0242.jpeg

You could create a partition here and this is DOS Partitioning is always recommended
IMG_0243.jpeg

Although on my device it says no free space available!
IMG_0244.jpeg

Quirky!
IMG_0245.jpeg

FreeBSD!
 
WIFI cards might take more time to configure -- any chance you can use an Ethernet wire to a router or similar?

Also - what version of FreeBSD are you installing? At the moment assuming 15.x?

Installing UFS is fine - I actually install (either ZFS or UFS) depending on the system I am building.

Sorry you are having issues !
 
balanga said:
There's no problem installing on a thumb drive. I have done so many times, and it is very useful to have a backup system if/when needed.
Click to expand...
It makes me think the /etc/fstab is incorrect. If you (UFS) install from memstick 1 to memstick 2 as supposed harddrive, it uses the current device number. Next boot without the install memstick makes it device 1. You have to manually change it in the installer shell before rebooting to prevent this device load prompt.
I don't know if this is relevant with a ZFS root system, though. Does it even read fstab?
 
I cannot understand why UEFI boot is a problem.
I believe, at some point, BIOS boots need to stop supporting Root on ZFS boots if more read-incompatible features are implemented and activated by default on creation of new pools. This is because the toooooooooo strict limitation in size of boot codes for legacy BIOS boots.

UEFI boot (or future replacements?) is the way to go.
Just Secure Boot alone is toxic for non-Windows environments.
 
MG said:
It makes me think the /etc/fstab is incorrect. If you (UFS) install from memstick 1 to memstick 2 as supposed harddrive, it uses the current device number. Next boot without the install memstick makes it device 1. You have to manually change it in the installer shell before rebooting to prevent this device load prompt.
I don't know if this is relevant with a ZFS root system, though. Does it even read fstab?
Click to expand...
You don't actually need fstab to boot. You will end up with mountroot prompt where you can manually enter something like

ufs:/dev/da1p2 or somesuch. I always select GPT as the partitioning because I can never remember BSD slices.

You just need to practice a few times to get the hang of things. A USB installation is easily replaceable.
 
balanga said:
You don't actually need fstab to boot. You will end up with mountroot prompt where you can manually enter something like

ufs:/dev/da1p2 or somesuch. I always select GPT as the partitioning because I can never remember BSD slices.

You just need to practice a few times to get the hang of things. A USB installation is easily replaceable.
Click to expand...
Not doing anything else for years. I have no rolled out FreeBSD system installation.
In my opinion this mountroot prompt is only the result of incomplete boot-configuation. It's an unforseen situation, but a PC already has a device order set. If it doesn't work, just state the problem. It's kind of silly to be unable to find a bootdevice but still be able to detect and generate a list of possible devices that could work anyway. If you reboot a remote compuiter and it gets in this prompt, you locked yourself out for no acceptable reason.
Does an interactive pre-kernel environment have to be so limited?
 
MG said:
Not doing anything else for years. I have no rolled out FreeBSD system installation.
In my opinion this mountroot prompt is only the result of incomplete boot-configuation. It's an unforseen situation, but a PC already has a device order set. If it doesn't work, just state the problem. It's kind of silly to be unable to find a bootdevice but still be able to detect and generate a list of possible devices that could work anyway. If you reboot a remote compuiter and it gets in this prompt, you locked yourself out for no acceptable reason.
Does an interactive pre-kernel environment have to be so limited?
Click to expand...
I'm talking about a temporary boot solution.

With something like Ventoy, I can boot FreeBSD from an ISO and once booted I can create a new (small) partition on the available free space left after installing and can install FreeBSD on it by simply extracting the base and kernel tar files.

With an amended ventoy grub file (F6 from Ventoy) I can boot from that partion, but will encounter a mountroot prompt from which I should be able to boot a fresh FreeBSD and with minimal effort you can access the internet and configure your system however you want it.

Remember this is only a temporary solution.
 
You must log in or register to reply here.
Back
Top