Date: Sat, 8 Apr 2017 12:01:00 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> 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: <20170408110100.GB14604@brick> 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
On 0313T1206, Pete French wrote: > I have a number of machines in Azure, all booting from ZFS and, until > the weekend, running 10.3 perfectly happily. > > 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: > > 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 = 2 > (da0:blkvsc0:0:0:0): UNMAPPED > (probe1:blkvsc1:0:1:0): storvsc scsi_status = 2 > hvheartbeat0: <Hyper-V Heartbeat> on vmbus0 > da0 at blkvsc0 bus 0 scbus2 target 0 lun 0 > > As you can see, the drive da0 only appears after it has tried, and failed, > to mount the root pool. Does the same problem still happen with recent 11-STABLE?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170408110100.GB14604>