ZPOOL create ZFS create How to use Disk Partitions in Single DISK ZFS setup

ZPOOL create    ZFS create  How to use Disk Partitions in Single DISK ZFS setup 

URLs to Read. For you to gain understanding.  Takes time to Learn well

:

https://blog.programster.org/zfs-create-disk-pools   Good easy explanation of ZFS

https://somedudesays.com/2021/08/the-basic-guide-to-working-with-zfs/   Good examples of RAIDZ setup

 https://github.com/yuriskinfo/cheat-sheets/blob/master/cheat-sheets/FreeBSD-cheat-sheet.adoc  FreeBSD gpart cheat sheet

https://github.com/danboid/creating-ZFS-disks-under-Linux/blob/master/README.md   Single disk Linux ZFS

https://unix.stackexchange.com/questions/672151/create-zfs-partition-on-existing-drive   Create ZFS Partition on existing disk  like  /dev/sda3 

https://serverfault.com/questions/596812/setup-zfs-on-freebsd-from-bsd-rescue  ZFS on FreeBSD bsd-rescue  OHV

https://docs.oracle.com/cd/E19253-01/819-5461/gaynr/index.html  Create a ZFS root pool  Oracle Docs on ZFS Zettabyte File System

https://illumos.org/books/zfs-admin/gavwq.html#gazud  Illumous ZFS manual examples

https://openzfs.github.io/openzfs-docs/man/8/zfs-create.8.html  OpenZFS docs

https://github.com/openzfs/zfs/issues OpenZFS Issues web page

https://github.com/openzfs/zfs  OpenZFS  Readme.md file

https://openzfs.github.io/openzfs-docs/Getting%20Started/index.html  Get Started

  

What I want to do with my ZFS disk system.  I am using UEFI GPT, two partitions one for root /dev/sda5, one larger for home /dev/sda6 .   Boot from the ESP EFI FAT32 /EFI/freebsd/bootx64aa.efi  into the ZFS file system on a Raspberry Pi 4B with 8 gigabytes of dram memory.  I want 50 -80 GB for the root "/"  disk space.   I want 130-180 GB for the home "/home"  "/usr/ports" "/usr/home" "/usr/src"   "/home" is symbolic link to "/usr/home" 

  I am using rEFInd EFI app to select which operating system to boot on the Raspberry Pi.  I would like to boot  PuppyLinux Raspup 32bit, POP!_OS ARM64, Manjaro ARM64,  and other test arm64 OS like Raspberry Pi OS.

 

forums.freebsd.org 

https://www.reddit.com/r/freebsd/comments/v4b5oj/freebsd_on_zfs_on_raspberry_pi/ Reddit ZFS setup on FreeBSD for Raspberry Pi.

https://www.reddit.com/r/freebsd/comments/rzh6xh/comment/hrv68l2/  base tutorial

https://github.com/freebsd/freebsd-src/blob/main/usr.sbin/bsdinstall/scripts/zfsboot bsdinstall scripts for zfsboot

https://lists.freebsd.org/archives/freebsd-arm/  FreeBSD arm mailing list subscribe

Creating a tiny new GhostBSD package for sharing with others

 Creating a tiny new GhostBSD / FreeBSD package for sharing with others, GURUs Generate_User_Report_for_Upload

 Here is an example of creating a FreeBSD style package, read some URLs

http://lastsummer.de/creating-custom-packages-on-freebsd/#:~:text=The%20last%20step%20uses%20pkg-create%288%29%20to%20build%20a,to%20use%20the%20package%20archive%20file%20with%20pkg-add%288%29.  This has very good steps to follow,

 

Insert this file to start your journey.  Copy and paste into tmp_stage.sh ;  chmod u+x tmp_stage.sh ;  sh ./tmp_stage.sh

 

 

#!/bin/sh

STAGEDIR=/tmp/stage
rm -rf ${STAGEDIR}
mkdir -p ${STAGEDIR}

cat >> ${STAGEDIR}/+PRE_DEINSTALL <<EOF
# careful here, this may clobber your system
echo "Resetting root shell"
pw usermod -n root -s /bin/csh
EOF

cat >> ${STAGEDIR}/+POST_INSTALL <<EOF
# careful here, this may clobber your system
echo "Registering root shell"
pw usermod -n root -s /bin/sh
EOF

https://github.com/freebsd/pkg  Github has some good reading too.

 

https://stackoverflow.com/questions/4602977/freebsd-pkg-create-how-to Kind of Sparse as an example.  May be of future use

https://www.tecmint.com/pkg-command-examples-to-manage-packages-in-freebsd/  23 examples of using pkg command

https://forums.freebsd.org/threads/where-does-make-package-put-the-pkg-file.73535/  Helpful example of creating a package   "pkg help create"

https://forums.freebsd.org/threads/creating-a-pkg-with-pkg-create.88358/  FreeBSD forum post that I followed and put a link to this blog.

https://forums.freebsd.org/threads/freebsd-install-rtorrent-and-rutorrent-on-lighttpd-full-guide.85230/

https://docs.freebsd.org/en/books/porters-handbook/plist/#plist-keywords  Yes the learning curve is too damned steep to accomplish a very simple task of creating a binary package from these 7 files:

    ./share/applications/generate_user_report.desktop #Desktop application file
    ./lib/guru/Makefile #Makefile
    ./lib/guru/README.md #Standard Readme file written in MarkDown language
    ./lib/guru/Report_fred-ghostbsd-pc1_2020-04-05_example.txt #Example Report.txt File created from User_Report.sh file
    ./lib/guru/User_Report.py #Python script file to create the GUI interface with a couple buttons
    ./lib/guru/User_Report.sh #Shell Script file
    ./lib/guru/applets-screenshooter.png #Icon file

No creation of these files from a Makefile is needed.  I included a sample Makefile.

Freebsd pkg #manifest
Best simple use of "pkg create" tool Best description on the web
Packaging setup, usage, and explanation
How to make a binary package, using FreeBSD tools
Quick Porting example from Porters Handbook

https://forums.freebsd.org/threads/creating-a-pkg-with-pkg-create.88358/#post-602161 Pat Maddox March 2023 help with pkg creation
Section 3.2..2 porting pkg plist

Rice your PC to a Red Ferrari GhostBSD in 10 minutes flat!

Rice your PC to a Red Ferrari GhostBSD in 10 minutes flat!  

Enhance your PC from a Ford Festiva to a Red Ferrari.  

Test drive Ghostbsd.org/download  "latest" version in 10 minutes flat!    

 

This could be the most fun-to-drive Ferrari ever made

https://www.afr.com/life-and-luxury/cars-bikes-and-boats/why-you-ll-probably-buy-the-568-300-ferrari-296-gtb-20221128-p5c1rh#:~:text=The%20296%20is%20a%20car,%2Dto%2Ddrive%20Ferrari%20ever.

Fun to drive Yellow Ferrari 296 GTB:

Small but beautiful, the $568,300 petrol-electric 296 GTB is a triumph of design, super fast and may become as legendary as the fabled Dino.

Now that you are excited about an expensive car, lets go to the other end of price spectrum to nearly FREE and pull ourselves up out of the PC computer Windows(TM) Hole by our BOOTstraps ,  into a RICED RED gleaming fast GhostBSD operating system test drive in 10 minutes!   You do have 10 minutes to spare, correct?

https://ventoy.net/en/index.html  Here download and create a USB flash drive with Ventoy applications.   https://ventoy.net/en/doc_start.html  Windows and Linux users

Place  GhostBSD.org/download  "latest" February 2, 2023 version and a copy of a puppy linux image, too.   on the Ventoy USB flash drive

PuppyLinux.com  

https://distro.ibiblio.org/puppylinux/puppy-fossa/fossapup64-9.5.iso

 

Now Boot from Ventoy USB Flash drive and select GhostBSD image to boot in your 4GB of dram memory the "live image".   No need to install first.  The GhostBSD.ISO image is copied into dram and run from dram memory.   After booting GhostBSD, pull the USB flash drive out from the computer.  It is not needed anymore.

Use the NetworkMgr  to connect via ethernet or via wifi.

 

pkg install  hw-probe

 

hw-probe -all -uploade    Create an entry to bsd-hardware.info  see an inventory of your computer and what BSD  device drivers exist for your PC hardware.

When you do wish to install to hard drive or ssd,  click on the GBI app icon. GhostBSD Installer and answer some questions.

 

 

Tools to write image or .ISO file to a USB Flash drive:

Balena Etcher tool for Windows or Linux

Here at balena we have thousands of users working through our getting started process and until recently we were embarassed about the steps that involved flashing an SD card. There was a separate track for each Mac/Windows/Linux and several manual and error-prone steps along the way.

To our surprise there was nothing out there that fit our needs. So we built Etcher, an SD card flasher app that is simple for end users, extensible for developers, and works on any platform.

Rufus tool to write .ISO images

Create bootable USB drives the easy way

Rufus is a utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc.

It can be especially useful for cases where:

• you need to create USB installation media from bootable ISOs (Windows, Linux, UEFI, etc.)
• you need to work on a system that doesn't have an OS installed
• you need to flash a BIOS or other firmware from DOS
• you want to run a low-level utility

Despite its small size, Rufus provides everything you need!

https://sourceforge.net/projects/win32diskimager/  

Win32DiskImager open source tool to write .ISO files to USB Flash drive or microSD card

This program is designed to write a raw disk image to a removable device or backup a removable device to a raw image file. It is very useful for embedded development, namely Arm development projects (Android, Ubuntu on Arm, etc). Anyone is free to branch and modify this program. Patches are always welcome.

This release is for Windows 7/8.1/10. It will should also work on Windows Server 2008/2012/2016 (although not tested by the developmers). For Windows XP/Vista, please use v0.9 (in the files archive).

Can't Format USB Drive in Windows 10 BRITEC09 6 minute video

119,672 views Sep 8, 2021 Windows 10

119,672 views • Sep 8, 2021 • Windows 10

So you want to know how to fix "Windows Was Unable to Complete the Formatting of USB Pen Drive" this is a common error and I will show you how to fix and resolve the USB Flash Drive problem. Now there is many reasons you can't format USB Drive in Windows 10 or Windows 11. It can be related to a faulty USB drive, Malware or the USB drive is RAW or Corrupt. I will show you step by step guide of solving the USB problem.

Video to use Diskpart command line tool to clean misformatted USB flash drive stick

58,053 views Apr 9, 2017

Hi there, i am kabir hossain from shortcutbd. today i want to show you how you can fix/ recover your unallocated space from your HDD Drive or repair Unallocated USB Drive.

Trouble shooting FreeBSD Installation problems

Write a blog post about troubleshooting FreeBSD installation

Introduction:

FreeBSD is a powerful and reliable operating system that is widely used in servers and other critical systems. However, like any other software, it can sometimes be prone to issues during installation. In this blog post, we will discuss some common problems that you might encounter while installing FreeBSD and how to troubleshoot them.

Problem 1: Boot error

One of the most common problems that users face while installing FreeBSD is a boot error. This can be caused by a number of reasons, including a faulty installation media, a hardware issue, or a misconfigured BIOS.

To troubleshoot this problem, the first thing you should do is to check the integrity of the installation media. You can do this by running the "md5" command on the installation ISO file and comparing the output with the official checksum. If the checksum does not match, it means that the installation media is corrupt and you need to download a new ISO file.

If the checksum matches and you are still facing a boot error, it could be due to a hardware issue or a misconfigured BIOS. In this case, you should try booting from the installation media using a different computer or on a different hardware platform. If the problem persists, it could be due to a misconfigured BIOS, in which case you should try resetting the BIOS to its default settings.

Problem 2: Kernel panic

Another common problem that you might encounter during the installation of FreeBSD is a kernel panic. This can be caused by a number of reasons, including a faulty hardware component or a problem with the installation media.

To troubleshoot this problem, you should first try booting the installation media on a different computer or on a different hardware platform. If the problem persists, it could be due to a faulty hardware component, in which case you should try replacing the suspect component.

If the problem is not caused by hardware, it could be due to a problem with the installation media. In this case, you should try downloading a new ISO file and creating a new installation media.

Problem 3: "No bootable device" error

If you see the "No bootable device" error while trying to install FreeBSD, it could be due to a misconfigured BIOS or a problem with the installation media.

 

Introduction:

FreeBSD is a powerful and reliable operating system that is widely used in servers and other critical systems. However, like any other software, it can sometimes be prone to issues during installation. In this blog post, we will discuss some common problems that you might encounter while installing FreeBSD and how to troubleshoot them.

Problem 1: Boot error

One of the most common problems that users face while installing FreeBSD is a boot error. This can be caused by a number of reasons, including a faulty installation media, a hardware issue, or a misconfigured BIOS.

To troubleshoot this problem, the first thing you should do is to check the integrity of the installation media. You can do this by running the "md5" command on the installation ISO file and comparing the output with the official checksum. If the checksum does not match, it means that the installation media is corrupt and you need to download a new ISO file.

If the checksum matches and you are still facing a boot error, it could be due to a hardware issue or a misconfigured BIOS. In this case, you should try booting from the installation media using a different computer or on a different hardware platform. If the problem persists, it could be due to a misconfigured BIOS, in which case you should try resetting the BIOS to its default settings.

Problem 2: Kernel panic

Another common problem that you might encounter during the installation of FreeBSD is a kernel panic. This can be caused by a number of reasons, including a faulty hardware component or a problem with the installation media.

To troubleshoot this problem, you should first try booting the installation media on a different computer or on a different hardware platform. If the problem persists, it could be due to a faulty hardware component, in which case you should try replacing the suspect component.

If the problem is not caused by hardware, it could be due to a problem with the installation media. In this case, you should try downloading a new ISO file and creating a new installation media.

Problem 3: "No bootable device" error

If you see the "No bootable device" error while trying to install FreeBSD, it could be due to a misconfigured BIOS or a problem with the installation media.

To troubleshoot this problem, you should first check the BIOS settings and make sure that the boot order is correctly configured. The installation media should be set as the first boot device.

If the boot order is correctly configured and you are still facing the "No bootable device" error, it could be due to a problem with the installation media. In this case, you should try creating a new installation media using a different USB drive or DVD.

Conclusion:

Installing FreeBSD can sometimes be challenging, especially if you encounter problems during the process. However, by following the troubleshooting steps discussed in this blog post, you should be able to resolve most issues and successfully install the operating system.

Suyimazu, Gaming with Steam on GhostBSD / FreeBSD Final FOSDEM2022 Feb6 ...

https://codeberg.org/Alexander88207/Suyimazu   Here is the code and place to share bugs.  Thank Alexander Vereeken for scratching his own itch to play Windows Games on FreeBSD.  Suyimazu uses WINE and WineTricks to accomplish this task.

ghostbsd.com/download  Look for "Latest"  version of GhostBSD  22.02.05  as of 22.02.06

http://download.us.ghostbsd.org/development/amd64/latest/  USA Mirror, Norway, France, South Africa, Canada

Use  Administration --> Software Station  search "Suyimazu"  Install  software

Try out your Windows Game software on GhostBSD / FreeBSD 

Raspberry Pi 4B with 8 gigs,   Vilros.com     

Fred.Suyimazu@theGalacticZoo.com  GhostBSD, Suyimazu installed onto a Sandisc Extreme SSD 1TB, 1050 MB per second transfer speed.  Shipped to you.

Please comment below, on how Suyimazu works on your games.

Suyimazu, Gaming with Steam on GhostBSD / FreeBSD Final FOSDEM2022 Feb6 ...

GhostBSD, Glabel an external 240GB SSD USB 3.0 drive paritions installed with ghostbsd

Glabel, gpart, geom, or How to label GPT, GPTID partitions with out a /dev/da1p3 drive name. 

First, can you read between the lines from a manual pages that INFER a similar naming/numbering scheme exists that you can try out, yet there is not ONE example to guide you.  EXAMPLE:

mount -t zfs    /dev/da1p2  /mnt/bsd 

gpart show

=>       34  468877245  ada0  GPT  (224G)

         34       4062        - free -  (2.0M)

       4096     614400     1  efi  (300M)

     618496  449799648     2  linux-data  (214G)

  450418144          7        - free -  (3.5K)

  450418151   18454920     3  freebsd-swap  (8.8G)

  468873071       4208        - free -  (2.1M)

=>       40  468862048  diskid/DISK-333457EBD0F2  GPT  (224G)

         40     532480                         1  efi  (260M)

     532520  459218944                         2  freebsd-zfs  (219G)

  459751464    9099264                         3  freebsd-swap  (4.3G)

  468850728      11360       

gpart status

                      Name  Status  Components

                    ada0p1      OK  ada0

                    ada0p2      OK  ada0

                    ada0p3      OK  ada0

diskid/DISK-333457EBD0F2p1      OK  diskid/DISK-333457EBD0F2

diskid/DISK-333457EBD0F2p2      OK  diskid/DISK-333457EBD0F2

diskid/DISK-333457EBD0F2p3      OK  diskid/DISK-333457EBD0F2

gpart show -l

=>       34  468877245  ada0  GPT  (224G)

         34       4062        - free -  (2.0M)

       4096     614400     1  (null)  (300M)

     618496  449799648     2  (null)  (214G)

  450418144          7        - free -  (3.5K)

  450418151   18454920     3  swap-internal-disk  (8.8G)

  468873071       4208        - free -  (2.1M)

=>       40  468862048  diskid/DISK-333457EBD0F2  GPT  (224G)

         40     532480                         1  (null)  (260M)

     532520  459218944                         2  (null)  (219G)

  459751464    9099264                         3  (null)  (4.3G)

  468850728      11360                            - free -  (5.5M)

Some of these  label names are carried over from the 'file label' name and not the given 'glabel' name in the listings above.

https://www.ithands-on.com/2020/10/freebsd-101-disk-labels.html   BEST WEB PAGE about glabel

https://people.freebsd.org/~trhodes/doc/handbook/geom-glabel.html

https://people.freebsd.org/~rodrigc/doc/handbook/geom-glabel.html

https://flylib.com/books/en/3.326.1.183/1/

Use a GPT /dev/diskid  name to select the "drive"  not /dev/da1p2

sudo glabel  label -v  swap_unirex_244g /dev/diskid/DISK-333457EBD0F2p3

Metadata value stored on /dev/diskid/DISK-333457EBD0F2p3.

Done.

sudo swapctl -A

swapctl: adding /dev/gpt/swap-unirex-224 as swap device

whoami

fred

# use sudo to execute privileged root commands 

glabel  label  -v swap_unirex_244g   /dev/diskid/DISK-333457EBD0F2p3

glabel  label  -v bootfs_unirex_244g   /dev/diskid/DISK-333457EBD0F2p1

##  The next one only works when the filesystem unmounted! and NOT in USE

umount /dev/diskid/DISK-333457EBD0F2p2

mkdir  /mnt/bsdp2

glabel  label  -v rootfs_unirex_244g   /dev/diskid/DISK-333457EBD0F2p2

mount -t zfs  /dev/diskid/DISK-333457EBD0F2p2  /mnt/DISK-333457EBD0F2p2

/etc/fstab

fred@fred-pc ~> cat /etc/fstab

# Device Mountpoint FStype OptionsDump Pass

# diskid/DISK-333457EBD0F2p3  801fd8c2-7926-11ec-b6e6-0021ccd45dec

# /dev/gptid/801fd8c2-7926-11ec-b6e6-0021ccd45dec

# /dev/label/swap0 none swap sw 0 0

# /dev/label/swap-unirex-224 none    swap sw 0  0

/dev/gpt/swap-unirex-224     none    swap sw 0  0

procfs /proc procfs rw 00

linprocfs /compat/linux/proc linprocfs rw 00

tmpfs /compat/linux/dev/shm tmpfs rw,mode=1777 0 0

linsysfs /compat/linux/sys linsysfs rw 0 0

fdesc /dev/fd fdescfs rw 0 0

fred@fred-pc ~> 

I get confused about which label goes with which partition.  So here are commands to use for finding information.

gpart status

gpart show

gpart show -l

gpart list

glabel list

# use the following command to see what labels are used with which devices.

ls -l  /dev/gpt /dev/gptid  /dev/diskid /dev/label  

# URL links to more information about glabel  and gpart commands

https://www.freebsd.org/cgi/man.cgi?glabel(8)

https://www.freebsd.org/cgi/man.cgi?gpart(8)

https://www.freebsd.org/cgi/man.cgi?query=swapinfo&apropos=0&sektion=0&manpath=FreeBSD+13.0-RELEASE+and+Ports&format=html

https://nanxiao.gitbooks.io/freebsd-101-hacks/content/posts/display-swap-space-utilization.html

https://klarasystems.com/articles/exploring-swap-on-freebsd/

glabel  label -v rootfs_unirex_244g   /dev/diskid/DISK-333457EBD0F2p2

So the answer is to  Glabel your GPT UUID external USB 3.0 SSD drive,   Next use that as the first or 2nd line in the /etc/fstab file to name your SWAP Partition

/dev/label/swap-unirex-224  none    swap  sw 0   0

/dev/gpt/swap-unirex-224     none    swap  sw 0   0

swapon -aL   to  turn the swap on for all swap partitions listed in the file /etc/fstab

swapinfo  -m    will tell you how much of your swap space is used in megabytes.

swapinfo -m

Device          1M-blocks     Used    Avail Capacity

/dev/gpt/swap-unirex-224      4443      578     3864    13%

swapinfo -h in Human readable sizes

swapinfo -h

Device              Size     Used    Avail Capacity

/dev/gpt/swap-unirex-224     4.3G     578M     3.8G    13%

Tools to check Free Memory available and How much SWAP memory is used

    freebsd-command-to-get-ram-information/

https://unix.stackexchange.com/questions/349890/reliably-determine-free-memory-in-bsd

https://forums.freebsd.org/threads/free-command-perl-script-for-freebsd.299/

https://stackoverflow.com/questions/4093786/what-is-equivalent-of-linuxs-free-command-on-freebsd-v8-1

https://www.skynats.com/blog/duf-disk-usage-free-utility-for-linux-bsd-macos-windows/

freecolor  -t   Is another useful tool that prints on the command line in colors red,grey, and green, a fuel gauge style  examples:  freecolor -o  ; freecolor -om;  freecolor -mt

swapctl  -l   Is another method to display your swap space memory usage 

free

freebsd-memory.sh

whereis free

free: /usr/local/bin/free

ls -l /usr/local/bin/fr*

-rwxr-xr-x  1 fred  fred    6756 Jan 21 22:00 /usr/local/bin/free

-rwxr-xr-x  1 fred  fred    5461 Jan 21 22:01 /usr/local/bin/freebsd-memory.sh

-rwxr-xr-x  1 root  wheel  11008 Apr 29 06:21 /usr/local/bin/freecolor

-rwxr-xr-x  1 root  wheel  22280 Apr 28 11:33 /usr/local/bin/fribidi

-r-xr-xr-x  1 root  wheel    269 Apr 28 11:33 /usr/local/bin/fribidi-config

 whereis freecolor

freecolor: /usr/local/bin/freecolor /usr/local/man/man1/freecolor.1.gz /usr/ports/sysutils/freecolor

 

fred@fred-pc ~> ls -l  /dev/gpt /dev/gptid  /dev/diskid /dev/label

ls: /dev/label: No such file or directory

/dev/diskid:

total 0

crw-r-----  1 root  operator  0xa2 Jan 29 14:36 DISK-333457EBD0F2

crw-r-----  1 root  operator  0xa8 Jan 29 14:36 DISK-333457EBD0F2p1

crw-r-----  1 root  operator  0xa9 Jan 29 14:36 DISK-333457EBD0F2p2

crw-r-----  1 root  operator  0xae Jan 29 14:36 DISK-333457EBD0F2p3

/dev/gpt:

total 0

crw-r-----  1 root  operator  0x95 Jan 29 14:36 swap-internal-disk

/dev/gptid:

total 0

crw-r-----  1 root  operator  0x97 Jan 29 14:36 873d142e-6117-de4f-bd8c-3075b666793f

crw-r-----  1 root  operator  0x91 Jan 29 14:36 d53c24c9-8a7e-7b44-97f0-97311087d9fa

 glabel list

Geom name: ada0p1

Providers:

1. Name: gptid/d53c24c9-8a7e-7b44-97f0-97311087d9fa

   Mediasize: 314572800 (300M)

   Sectorsize: 512

   Stripesize: 0

   Stripeoffset: 2097152

   Mode: r0w0e0

   secoffset: 0

   offset: 0

   seclength: 614400

   length: 314572800

   index: 0

Consumers:

1. Name: ada0p1

   Mediasize: 314572800 (300M)

   Sectorsize: 512

   Stripesize: 0

   Stripeoffset: 2097152

   Mode: r0w0e0

Geom name: ada0p3

Providers:

1. Name: gpt/swap-internal-disk

   Mediasize: 9448919040 (8.8G)

   Sectorsize: 512

   Stripesize: 0

   Stripeoffset: 230614093312

   Mode: r0w0e0

   secoffset: 0

   offset: 0

   seclength: 18454920

   length: 9448919040

   index: 0

Consumers:

1. Name: ada0p3

   Mediasize: 9448919040 (8.8G)

   Sectorsize: 512

   Stripesize: 0

   Stripeoffset: 230614093312

   Mode: r0w0e0

Geom name: ada0p3

Providers:

1. Name: gptid/873d142e-6117-de4f-bd8c-3075b666793f

   Mediasize: 9448919040 (8.8G)

   Sectorsize: 512

   Stripesize: 0

   Stripeoffset: 230614093312

   Mode: r0w0e0

   secoffset: 0

   offset: 0

   seclength: 18454920

   length: 9448919040

   index: 0

Consumers:

1. Name: ada0p3

   Mediasize: 9448919040 (8.8G)

   Sectorsize: 512

   Stripesize: 0

   Stripeoffset: 230614093312

   Mode: r0w0e0

Geom name: da0

Providers:

1. Name: diskid/DISK-333457EBD0F2

   Mediasize: 240057409536 (224G)

   Sectorsize: 512

   Stripesize: 4096

   Stripeoffset: 0

   Mode: r1w1e2

   secoffset: 0

   offset: 0

   seclength: 468862128

   length: 240057409536

   index: 0

Consumers:

1. Name: da0

   Mediasize: 240057409536 (224G)

   Sectorsize: 512

   Stripesize: 4096

   Stripeoffset: 0

   Mode: r1w1e3

Geom name: cd0

Providers:

1. Name: iso9660/PC_GHS

   Mediasize: 100734976 (96M)

   Sectorsize: 2048

   Mode: r0w0e0

   secoffset: 0

   offset: 0

   seclength: 196748

   length: 100734976

   index: 0

Consumers:

1. Name: cd0

   Mediasize: 100734976 (96M)

   Sectorsize: 2048

   Mode: r0w0e0

glabel label  -v swap-unirex-224G  /dev/diskid/DISK-333457EBD0F2p3

glabel: Can't store metadata on /dev/diskid/DISK-333457EBD0F2p3: Permission denied.

fred@fred-pc ~ [1]> sudo glabel label  -v swap-unirex-224G  /dev/diskid/DISK-333457EBD0F2p3

Password:

Metadata value stored on /dev/diskid/DISK-333457EBD0F2p3.

Done.

sudo glabel label  -v bootfs-unirex-224G  /dev/diskid/DISK-333457EBD0F2p1

Metadata value stored on /dev/diskid/DISK-333457EBD0F2p1.

Done.

gpart show -l

=>       34  468877245  ada0  GPT  (224G)

         34       4062        - free -  (2.0M)

       4096     614400     1  (null)  (300M)

     618496  449799648     2  (null)  (214G)

  450418144          7        - free -  (3.5K)

  450418151   18454920     3  swap-internal-disk  (8.8G)

  468873071       4208        - free -  (2.1M)

=>       40  468862048  diskid/DISK-333457EBD0F2  GPT  (224G)

         40     532480                         1  (null)  (260M)

     532520  459218944                         2  (null)  (219G)

  459751464    9099264                         3  (null)  (4.3G)

  468850728      11360                            - free -  (5.5M)

fred@fred-pc ~ [1]> sudo mount -t fat32 /dev/diskid/DISK-333457EBD0F2p1  /mnt/bsd_fat32

mount: /dev/diskid/DISK-333457EBD0F2p1: Operation not supported by device

fred@fred-pc ~ [1]> ls /dev/glabel

ls: /dev/glabel: No such file or directory

fred@fred-pc ~ [1]> ls /dev/label

bootfs-unirex-2 swap-unirex-224

fred@fred-pc ~> ls -l /dev/label

total 0

crw-r-----  1 root  operator  0x1ff Jan 30 00:21 bootfs-unirex-2

crw-r-----  1 root  operator  0x1fc Jan 30 00:21 swap-unirex-224

fred@fred-pc ~> sudo mount -t fat32 /dev/label/bootfs-unirex-2  /mnt/bsd_fat32

mount: /dev/label/bootfs-unirex-2: Operation not supported by device

fred@fred-pc ~ [1]> sudo mount -t fat32 /dev/label/bootfs-unirex-2224g  /mnt/bsd_fat32

mount: /dev/label/bootfs-unirex-2224g: Operation not supported by device

fred@fred-pc ~ [1]> su root

Password:

root@fred-pc:/home/fred # mount -t fat32 /dev/label/bootfs-unirex-2 /mnt/bsd_fat32

mount: /dev/label/bootfs-unirex-2: Operation not supported by device

root@fred-pc:/home/fred # 

root@fred-pc:/home/fred # ls /mnt  /dev/label /dev/gpt /dev/gptid /dev/diskid 

/dev/diskid:

DISK-333457EBD0F2 DISK-333457EBD0F2p2

DISK-333457EBD0F2p1 DISK-333457EBD0F2p3

/dev/gpt:

swap-internal-disk

/dev/gptid:

7d0e6dcf-7926-11ec-b6e6-0021ccd45dec

801fd8c2-7926-11ec-b6e6-0021ccd45dec

873d142e-6117-de4f-bd8c-3075b666793f

d53c24c9-8a7e-7b44-97f0-97311087d9fa

/dev/label:

bootfs-unirex-2 swap-unirex-224

/mnt:

bsd_fat32 swap_space

root@fred-pc:/home/fred #