On Thu, Jan 27, 2022 at 5:18 PM Eugene Grosbein <eu...@grosbein.net> wrote:
> 27.01.2022 22:09, Ulrich Spörlein wrote:
> > Or should I bring back a / UFS partition in the front instead, with
> > /usr and /var on ZFS?
>
> I would recommend to create 10GB partition at the beginning of boot drive,
> create distinct ZFS boot pool there for the OS to keep everything
> except of /usr/local, /home and maybe other file systems not belonging to the
> OS.
>
> Use rest of space for second ZFS pool to keep /usr/local, /home etc.
> And you'll never have your problem again.
Thanks everyone, I managed to repurpose the swap partition to a root
UFS partition and
managed to copy everything over. What's puzzling is that I still get
zio_read errors.
It looks like so now:
root@coyote:~# gpart show
=> 40 7814037088 ada0 GPT (3.6T)
40 1024 1 freebsd-boot (512K)
1064 16777216 2 freebsd-ufs [bootme] (8.0G)
16778280 16778200 4 freebsd-swap (8.0G)
33556480 7780478976 3 freebsd-zfs (3.6T)
7814035456 1672 - free - (836K)
and I ran this to replace gptzfsboot with gptboot (or so I thought):
# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
But after rebooting, I get these errors on the console still. Why
would gptboot try to read zfs metadata?
/boot/config: -Dh
Consoles: internal video/keyboard serial port
BIOS drive C: is disk0
zio_read error: 5
zio_read error: 5
zio_read error: 5
zio_read error: 5
ZFS: i/o error - all block copies unavailable
ZFS: failed to read pool tank directory object
BIOS 628kB/523264kB available memory
FreeBSD/x86 bootstrap loader, Revision 1.1
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
/
Loading kernel...
Cheers
Uli
