Questions and support problems dealing directly with the FreeBSD Operating System.
Post Reply
Zar Marco
Posts: 8
Joined: Sat Feb 17, 2018 8:54 pm


Post by Zar Marco »

Hi and sorry for another noob question. I have a multiboot with zfs.

This is my situation:

Code: Select all

zar_marco@ghostgram ~> gpart  show

=>        40  1953525095  nvd0  GPT  (932G)

          40        2008        - free -  (1.0M)

        2048     1048576     1  efi  (512M)

     1050624  1952473088     2  solaris-root  (931G)

  1953523712        1423        - free -  (712K)

=>        40  1953525095  diskid/DISK-2140JY447104  GPT  (932G)

          40        2008                            - free -  (1.0M)

        2048     1048576                         1  efi  (512M)

     1050624  1952473088                         2  solaris-root  (931G)

  1953523712        1423                            - free -  (712K)

=>        40  2000409184  nvd1  GPT  (954G)

          40      532480     1  efi  (260M)

      532520  1994960896     2  freebsd-zfs  (951G)

  1995493416     3866584        - free -  (1.8G)

  1999360000     1048576     3  ms-basic-data  (512M)

  2000408576         648        - free -  (324K)

where nvd0p1 is linux efi, nvd0p2 contain datasets for linux and freebsd (rpool), nvd1p1 is ghostbsd efi, nvd1p2 dataset of ghost (zroot) and nvd1p3 in my idea is freebsd efi.

In the first time freebsd efi was contain in linux efi, but I had some problems with hostid and I couldn't boot linux.

So I had think to create a new efi partition for freebsd.

This is output of zpool:

Code: Select all

zar_marco@ghostgram ~> zpool list -v


rpool                          928G   179G   749G        -         -     2%    19%  1.00x    ONLINE  -

  diskid/DISK-2140JY447104p2   931G   179G   749G        -         -     2%  19.2%      -    ONLINE

zroot                          944G  10.5G   933G        -         -     0%     1%  1.00x    ONLINE  -

  nvd1p2                       951G  10.5G   933G        -         -     0%  1.11%      -    ONLINE

and zfs list:

Code: Select all

zar_marco@ghostgram ~> zfs list -t filesystem | grep rpool

rpool                                179G   721G       96K  none

rpool/arch                          29.1G   721G       96K  none

rpool/arch-gnome                    31.3G   721G       96K  none

rpool/arch-gnome/home               18.9G   721G     18.7G  legacy

rpool/arch-gnome/root               12.3G   721G     12.0G  /

rpool/arch/home                     17.6G   721G     17.3G  legacy

rpool/arch/root                     11.5G   721G     11.1G  /

rpool/condivise                     95.9G   721G     95.9G  /condivise

rpool/freebsd                       12.1G   721G       96K  none

rpool/freebsd/root                  10.1G   721G     9.71G  /mnt/freebsd

rpool/freebsd/tmp                     96K   721G       96K  none

rpool/freebsd/usr                   2.05G   721G       96K  none

rpool/freebsd/usr/home               580M   721G      369M  legacy

rpool/freebsd/usr/ports              757M   721G      757M  none

rpool/freebsd/usr/src                760M   721G      760M  none

rpool/freebsd/var                    576K   721G       96K  none

rpool/freebsd/var/audit               96K   721G       96K  none

rpool/freebsd/var/crash               96K   721G       96K  none

rpool/freebsd/var/log                 96K   721G       96K  none

rpool/freebsd/var/mail                96K   721G       96K  none

rpool/freebsd/var/tmp                 96K   721G       96K  none

rpool/void                          10.3G   721G       96K  none

rpool/void/home                     3.28G   721G     3.00G  legacy

rpool/void/root                     7.05G   721G     6.83G  /

zar_marco@ghostgram ~> zfs list -t filesystem | grep zroot

zroot                               10.5G   904G       96K  legacy

zroot/ROOT                          10.2G   904G       96K  legacy

zroot/ROOT/backup-2022-12-03-03-53     8K   904G     7.39G  /

zroot/ROOT/default                  10.2G   904G     8.24G  /

zroot/tmp                            184K   904G      184K  /tmp

zroot/usr                            320M   904G       96K  /usr

zroot/usr/home                       319M   904G      319M  /usr/home

zroot/usr/ports                       96K   904G       96K  /usr/ports

zroot/usr/src                         96K   904G       96K  /usr/src

zroot/var                            484K   904G       96K  /var

zroot/var/audit                       96K   904G       96K  /var/audit

zroot/var/crash                       96K   904G       96K  /var/crash

zroot/var/mail                       100K   904G      100K  /var/mail

zroot/var/tmp                         96K   904G       96K  /var/tmp

this is /boot/efi of freebsd:

Code: Select all

zar_marco@ghostgram ~> ls /mnt/freebsd/boot/efi/

BOOT/    freebsd/

zar_marco@ghostgram ~> ls /mnt/freebsd/boot/efi/BOOT/


BOOTX64.efi is a copy of /boot/loader.efi of freebsd

Now if I boot, always booted ghostbsd

Can I fixed this? I don,t know how reinstall freebsd bootloader
Posts: 11
Joined: Sun Dec 16, 2018 1:35 am

Re: multiboot

Post by vimanuelt »

GhostBSD expects to be the only operating system on a bare metal system. GhostBSD practices the keep it simple philosophy.

While rEFInd is available for end users to install, it is really up to the end user to know how to use it correctly. is a good resource for those that want to experiment with booting multiple operating systems on a single system.

Here are some alternatives to the rEFInd (multiboot) option.

(1) [Hypervisor] Use a hypervisor if you want to run multiple operating systems. With a hypervisor it is possible to run both operating systems at the same time instead of just one operating system at a time. You'll be able to access files on both running operating systems.

(2) [Physical swap] If you do not like using a hypervisor, then having two hard disk drives is an option. You can simply swap out the hard disk drive that you need. It will reduce the amount of wear on the hard disk drive and help to prevent loss of two operating systems at the same time. :) The downside is that you have to swap out hard disk drives to access a file that you want.

(3) [BIOS HDD selection] Yet another option on newer systems that have more than one hard disk drive is to rely on firmware (BIOS) for HDD/OS selection. You can simply boot the hard drive with the OS that you need. (Popular option on gaming systems). The downside is that you have to reboot into another HDD/OS if you need a file on the other HDD/OS. However, this is not always the case.

(4) [Multiple computers] Use two computers. Install different operating systems on each.

Hope this helps.
Post Reply