From owner-freebsd-fs@freebsd.org Tue Jul 24 01:29:09 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADDF1102F4DB for ; Tue, 24 Jul 2018 01:29:09 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 32A1B76F36 for ; Tue, 24 Jul 2018 01:29:09 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w6O1RkLD094784 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 23 Jul 2018 18:27:46 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6O1RkVg094783 for freebsd-fs@freebsd.org; Mon, 23 Jul 2018 18:27:46 -0700 (PDT) (envelope-from warlock) Date: Mon, 23 Jul 2018 18:27:45 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: CRC32Mounting from zfs:zroot/ROOT/default failed with error 2 Message-ID: <20180724012745.GB75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 01:29:09 -0000 I'm trying to get my RPI3B+ to boot up with a ZFS root. I've seeded the OS with FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180719-r336479.img (and it's predecessors 20180709-r336134 and 20180618-r335317). I've more or less copied the EFI/U-Boot partition over as-is, and that part seems fine. The EFI loader iterates through my partitions, finds the ZFS root (zfs:zroot/ROOT/default), clearly reads the /boot/defaults/loader.conf and downloads the kernel, umodem.ko and zfs.ko so it's obviously able get the data off of there. [/boot/loader.conf] hw.usb.template=3 umodem_load="YES" zfs_load="YES" The kernel boots. That parts looks relatively normal except for this message during the boot: ... Instruction Set Attributes 0 = : unknown file system. ... (It's possible that the error is landing in the middle of the rest of the info dump that after the CPU 0 processor feature dump.) It eventually fails and gives me a mountroot> prompt. It prints out a good- looking vfs.root.mountfrom (=zfs:zroot/ROOT/default) variable. Trying devices like zfs:zoort (wrong) and zfs:zroot/ROOT/default (should be Ok) results in this, much like the kernel startup error: Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file system At the mountroot prompt, I don't see the ZFS partition directly (but mmcsd0s2a is shown). At the loader prompt, lsdev lists zfs:zroot as a zfs device, and "lszfs zroot" shows ROOT (+$MOS, $FREE & $ORIGIN), "lszfs zroot/ROOT" shows default, but I can't get below that. "ls" and "ls /boot" show what you'd expect to see off of the root filetree from zroot/ROOT/default. I literally made the image by creating a UFS version to build the ZFS version, same kernel, so you'd think there wouldn't be any incompatibilities. Any suggestions?