Search Results for: gpart create

gpart backup | gpart restore does not alway give you exact replication

Today I was setting up some drives for testing. I did this manually: root@r730-04:~ # gpart create -s gpt da2 da2 created root@r730-04:~ # gpart add -t efi -s 260M -a 4k da2 da2p1 added root@r730-04:~ # gpart add -t freebsd-swap -s 8G -a 4k da2 da2p2 added root@r730-04:~ # gpart add -t freebsd-zfs -a 4k da2 da2p3 added root@r730-04:~ # gpart show da2 => 40 62533216 da2 GPT (30G) 40 532480 1 […]

gpart backup | gpart restore does not alway give you exact replication Read More »

Copying everything off a zpool, destroying it, creating a new one, and copying everything back

I have a problem with a zpool. To be clear, this really isn’t a problem. I’m not aware of any I/O throttling etc. It is just something I would like to change. [18:26 r720-02 dvl ~] % zpool status data01 pool: data01 state: ONLINE status: One or more devices are configured to use a non-native block size. Expect reduced performance. action: Replace affected devices with devices that support the configured block size, or

Copying everything off a zpool, destroying it, creating a new one, and copying everything back Read More »

creating a raidz2 from 8x 4TB devices – here. we. go.

It’s time. Time to create the 8x 4T raidz2 zpool. These are the devices: disks=”nda0 nda1 nda2 nda3 nda5 nda8 da12 da13″ In this post: FreeBSD 14.3 Check for existing partitions Using the list above: [18:15 r730-01 dvl ~] % gpart show | grep -E “nda0|nda1|nda2|nda3|nda5|nda8|da12|da13” => 40 7814037088 nda5 GPT (3.6T) => 34 7814037101 nda8 GPT (3.6T) Note I could not do this command because it fails at the first error: [18:05

creating a raidz2 from 8x 4TB devices – here. we. go. Read More »

Making room to creating a raidz2 from 8x 4TB devices – here. we. go.

It’s time. Time to create the 8x 4T raidz2 zpool. That doesn’t happen in this post, hopefully the next one. But first, I have to move some stuff around, to free up all the 4TB devices. The host has 4 devices (NVMe) and I moved in two more, 4TB SSDs. From /var/log/messages: Dec 9 00:24:29 r730-01 kernel: mrsas0: System PD created target ID: 0xc Dec 9 00:24:29 r730-01 kernel: mrsas0: System PD created

Making room to creating a raidz2 from 8x 4TB devices – here. we. go. Read More »

prod – moving to a SATADOM based zpool (zroot) using zfs snapshot and send | recv

In this post, I’m moving my zroot zpool from larger devices to smaller devices. Why? Well, the smaller devices happen to attach directly to the main board of my server, albeit with some slight modification to a fan cowl. There have been several recent posts regarding this topic. I tried a different zpool approach, where I added new devices to the zpool and removed the old devices. That worked. It wasn’t ideal for

prod – moving to a SATADOM based zpool (zroot) using zfs snapshot and send | recv Read More »

Test run – moving to a SATADOM based zpool (zroot) using zfs snapshot and send | recv

Yesterday I managed to move a zroot zpool from larger drives to smaller drives using snapshot, send, recv. Today, I’m doing the same thing. Yet, what is different? using serial numbers in some partition labels moving to SATADOM This really is a dry-run for when I do this on my production host, r730-01 – apart from the whole moving-to-smaller-drives part. host ssh keys NOTE: not shown in this post are messages like this:

Test run – moving to a SATADOM based zpool (zroot) using zfs snapshot and send | recv Read More »

Test run – moving to a smaller zpool (zroot) using zfs snapshot and send | recv

Today, I’m going to try a test run of moving a zroot into a smaller zpool. Over the past few posts, I’ve tested moving to smaller zpools using zfs remove. That’s not what I want to do with my zpool – mostly because it does not leave you with a functioning original zpool. I’m following https://www.hagen-bauer.de/2025/08/zfs-migration-to-smaller-disk.html and I particularly like their use of labels on each partition. In this post: FreeBSe 14.3 mfsbsd-14.2-RELEASE-amd64

Test run – moving to a smaller zpool (zroot) using zfs snapshot and send | recv Read More »

Moving a zpool to smaller drives with UEFI #ZFS #FreeBSD

This is another in the series of shrinking zpools. In this test, I’m repeating the previous test, only with UEFI, not BIOS, boot partitions. Partitioning root@r730-04:/home/dvl # gpart create -s gpt mfisyspd0 mfisyspd0 created root@r730-04:/home/dvl # gpart create -s gpt mfisyspd1 mfisyspd1 created root@r730-04:/home/dvl # gpart create -s gpt mfisyspd2 mfisyspd2 created root@r730-04:/home/dvl # gpart create -s gpt mfisyspd3 mfisyspd3 created root@r730-04:/home/dvl # gpart add -t efi -s 260M -a 4k mfisyspd0 mfisyspd0p1

Moving a zpool to smaller drives with UEFI #ZFS #FreeBSD Read More »

Moving a zpool to smaller drives #ZFS #FreeBSD

After succeeding with whole drives and with partitioned drives, I’m ready to try with more complex partitions. This is a repeat of the failed attempt a few days ago. Parition creation The partitions are created Create the schema: root@r730-04:/home/dvl # gpart create -s gpt /dev/mfisyspd0 mfisyspd0 created root@r730-04:/home/dvl # gpart create -s gpt /dev/mfisyspd1 mfisyspd1 created root@r730-04:/home/dvl # gpart create -s gpt /dev/mfisyspd2 mfisyspd2 created root@r730-04:/home/dvl # gpart create -s gpt /dev/mfisyspd3 mfisyspd3

Moving a zpool to smaller drives #ZFS #FreeBSD Read More »

Let’s try shrinking a whole-disk zpool

After yesterday’s failure to shrink a parition-based zpool. After reading this post, you want also want to read this other successful post. You will recall that expedition ended with: dvl@r730-04:~ $ zpool add zroot mirror /dev/da2p3 /dev/da3p3 cannot use ‘/dev/da2p3′: must be a block device or regular file Today, I’m going to try the same thing with whole disks, just to see if that works. You might also want to read Moving a

Let’s try shrinking a whole-disk zpool Read More »

Scroll to Top