Date: Sun, 30 Jan 2022 03:06:18 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: Ulrich =?ISO-2022-JP?B?U3AbJEIiLhsoQnJsZWlu?= <uqs@freebsd.org> Cc: Eugene Grosbein <eugen@grosbein.net>, freebsd-stable@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: gptzfsboot can't boot from 4TB SSD Message-ID: <20220130030618.dd46cf514f98cdfa6caa1ad4@dec.sakura.ne.jp> In-Reply-To: <CAJ9axoQPCxiAMRn4BxCfnVMj4ggbumwyGg3schKg78=fmK%2B8pQ@mail.gmail.com> References: <YfKkr%2BmC6rMrRlF9@acme.spoerlein.net> <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> <CAJ9axoRneWhE61k-o0xTH04wyLQnoeNwD6Y2myR0vnvD1Q01Vg@mail.gmail.com> <f321250d-2d27-b1ea-9525-0b4aaf80d05d@grosbein.net> <CAJ9axoQPCxiAMRn4BxCfnVMj4ggbumwyGg3schKg78=fmK%2B8pQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Jan 2022 13:24:06 +0100 Ulrich Sp〓rlein <uqs@freebsd.org> wrote: > On Thu, Jan 27, 2022 at 5:18 PM Eugene Grosbein <eugen@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 > > Do you still have vfs.root.mountfrom="zfs:your/tank/dataset" line in /boot/loader.conf on UFS? And/or having /boot.config (or /boot/config) having configuration touching your ZFS pool? If so, and the partition position problem is really the root cause, it can cause loader to look for your ZFS root pool and fail. (/boot/zfsloader is used instead of /boot/loader.) Comment it out and let /etc/rc.d/zpool to import your now-non-root pool. If (and only if) the import fails, possibly you need to delete everything you moved to UFS from ZFS to avoid collision. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220130030618.dd46cf514f98cdfa6caa1ad4>