From owner-freebsd-fs@freebsd.org Fri Jul 27 03:20:17 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 5D140105F22A for ; Fri, 27 Jul 2018 03:20:17 +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 E561D81E18 for ; Fri, 27 Jul 2018 03:20:16 +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 w6R3J0kO054322 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 26 Jul 2018 20:19:00 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w6R3IxOJ054321 for freebsd-fs@freebsd.org; Thu, 26 Jul 2018 20:18:59 -0700 (PDT) (envelope-from warlock) Date: Thu, 26 Jul 2018 20:18:59 -0700 From: John Kennedy To: freebsd-fs@freebsd.org Subject: Re: Mounting from zfs:zroot/ROOT/default failed with error 2 (and 6) Message-ID: <20180727031859.GD75644@phouka1.phouka.net> References: <20180724012745.GB75644@phouka1.phouka.net> <3596ef16-da50-b26c-b7fd-724ca020cba2@FreeBSD.org> <20180726043937.GC75644@phouka1.phouka.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180726043937.GC75644@phouka1.phouka.net> 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: Fri, 27 Jul 2018 03:20:17 -0000 First off, subject change. I've become convinced that what I'm seeing is two error messages being mashed together: [Normal RPI3B+ kernel output ... CPU 0: ARM Cortex-A53 r0p4 affinity: 0 Instruction Set Attributes 0 = Instruction Set Attributes 1 = <0> ... ... and the messages + error: Trying to mount root from zfs:zrasp/ROOT/default []... Mounting from zfs:zroot/ROOT/default failed with error 2 Digging out that error gets a lot more hits, although typically years old. As I said, if I comment out zfs_enable="YES" and zfs_load="YES" and boot into My UFS partition, I can see that the extra modules that get loaded using ZFS are zfs.ko and opensolaris.ko, even though there are other dependencies: [strings -a < opensolaris.ko | grep _depend_on_] _opensolaris_depend_on_kernel [strings -a < zfs.ko | grep _depend_on_] _zfsctrl_depend_on_acl_nfs4 _zfsctrl_depend_on_kernel _zfsctrl_depend_on_krpc _zfsctrl_depend_on_opensolaris _zfs_depend_on_kernel _zfs_zvol_depend_on_kernel _zfs_vdev_depend_on_kernel If I add opensolaris, sort of progress. Root mount waiting for: usbus0 Mounting from zfs:zroot/ROOT/default failed with error 6; retrying for 3 more seconds Mounting from zfs:zroot/ROOT/default failed with error 6 Not only that, it looks like it gets me in a non-writing mode: ZFS WARNING: Unable to open diskid/DISK-73180AA8s2 for writing (error=1). Adding in these two didn't seem to make any difference at all (didn't see a load *.ko message): acl_nfs4_load="YES" krpc_load="YES" For what it's worth: [usbconfig list] ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (98mA) -> Standard Microsystems Corp. USB 2.0 Hub? That's presumably my entire BSD space, including UFS which hangs booting (well, I waited over 10 minutes stayed at "Tryint to mount root" message). If I power cycle, interrupt the loader, unload everything and just load the kernel I can get into the UFS partition just fine from the mountroot> prompt. If I start up with "boot -v", I see some new messages: GEOM_PART: partition 1 on (mmcsd0, MBR) is not aligned to 4194304 bytes GEOM_PART: partition 1 on (diskid/DISK-73180AAB, MBR) is not aligned to 4194304 bytes Those alternate about 5 times inbetween the second-by-second "error 6" countdown. I'm going to rebuild it with that partition aligned and see what happens.