Date: Fri, 28 Jul 2017 12:55:15 +0200 From: =?UTF-8?B?R29yYW4gVGVwxaFpxIc=?= <purpleritza@gmail.com> To: FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: ZFS fails with error 6 on upgrade to 11.1 Message-ID: <CADLW%2Bu2ov_z3mWOy8dMu-QtwxuP60ryszsi5VCUNk7mpdTOmZw@mail.gmail.com> In-Reply-To: <87o9s57cj0.fsf@domain.invalid> References: <87shhiao5h.fsf@domain.invalid> <alpine.BSF.2.21.1707270810250.53090@mail.fig.ol.no> <87r2x1o9eu.fsf@domain.invalid> <87o9s57cj0.fsf@domain.invalid>
next in thread | previous in thread | raw e-mail | index | archive | help
Just from top of my head, you mentioned that pool is created in Arch? Is your pool upgraded? Maybe the difference in zpool features between FreeBSD and ZoL is the culprit. Try booting your OS or livecd like mfsBSD to import pool to alternate root and running 'zpool upgrade ssd', maybe that'll do the trick. I don't know anything about Linux ZFS system but I'd expect them t be incompatible afterall. Good luck On Jul 28, 2017 12:15 AM, "Sebastian Schwarz" <seschwar@gmail.com> wrote: > On 2017-07-27, Sebastian Schwarz wrote: > > On 2017-07-27, Trond Endrest=C3=B8l wrote: > >> Off the top of my head I would ensure zfs.ko is loaded at boot time, > >> by adding zfs_load=3D"YES" to /boot/loader.conf within the > >> ssd/ROOT/freebsd11.1.0 filesystem. > > > > zfs_load=3D"YES" is already present in loader.conf. > > And the module does get loaded during boot, as indicated by the > following output during the boot: > > > ZFS filesystem version: 5 > > ZFS storage pool version: features support (5000) > > And the hard drives themselves are detected as well. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLW%2Bu2ov_z3mWOy8dMu-QtwxuP60ryszsi5VCUNk7mpdTOmZw>