Date: Mon, 13 Mar 2017 14:14:40 +0100 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Pete French <petefrench@ingresso.co.uk> Cc: stable@freebsd.org Subject: Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0 Message-ID: <20170313141440.7ecf5bc5@fabiankeil.de> In-Reply-To: <E1cnOkS-0000oL-Ia@dilbert.ingresso.co.uk> References: <E1cnOkS-0000oL-Ia@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/XdzvgM+tl/bMTg=SyLhYF3C Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Pete French <petefrench@ingresso.co.uk> wrote: > I have a number of machines in Azure, all booting from ZFS and, until > the weekend, running 10.3 perfectly happily. >=20 > I started upgrading these to 11. The first went fine, the second would > not boot. Looking at the boot diagnistics it is having problems finding > the root pool to mount. I see this is the diagnostic output: >=20 > storvsc0: <Hyper-V IDE Storage Interface> on vmbus0 > Solaris: NOTICE: Cannot find the pool label for 'rpool' > Mounting from zfs:rpool/ROOT/default failed with error 5. > Root mount waiting for: storvsc > (probe0:blkvsc0:0:storvsc1: 0:<Hyper-V IDE Storage > Interface>0): on vmbus0 storvsc scsi_status =3D 2 > (da0:blkvsc0:0:0:0): UNMAPPED > (probe1:blkvsc1:0:1:0): storvsc scsi_status =3D 2 > hvheartbeat0: <Hyper-V Heartbeat> on vmbus0 > da0 at blkvsc0 bus 0 scbus2 target 0 lun 0 >=20 > As you can see, the drive da0 only appears after it has tried, and > failed, to mount the root pool. >=20 > Normally I would just stick in a big 'vfs.mountroot.timeout' but that > variable doesnt not appear to exist under 11 - or at least it doesnt > show up in sysctl. The variable still exists but is ignored when using ZFS. It's a known issue. You could try this patch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882#c3 Manually specifying the root pool should workaround the issue. sysctl(8) does not show the variable as it's only a tunable. This is unrelated to the update. Fabian --Sig_/XdzvgM+tl/bMTg=SyLhYF3C Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCWMabQAAKCRAFiohV/3dU nd/LAKCBAjofhEtrU10g5Szt/rBjCu4MFQCgl63d/r9PNgIX2E4fPi9Dfqg5S0E= =c6iF -----END PGP SIGNATURE----- --Sig_/XdzvgM+tl/bMTg=SyLhYF3C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170313141440.7ecf5bc5>