Date: Thu, 16 Apr 2015 01:33:17 +1000 From: Yudi V <yudi.tux@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: mountroot prompt with error2, when trying to boot from a single drive in a 2-way mirror Message-ID: <CACo--mte5c8ER-V6hqcZmvsmU2gPtCwMgSsFH29HLrcrLG-yjg@mail.gmail.com> In-Reply-To: <05238e5a.6156fafe@fabiankeil.de> References: <CACo--mtMq=pLA-n5B2yPGftdUVa0aR6Pox5mRitMLguPXRto0g@mail.gmail.com> <552D135F.9010907@FreeBSD.org> <CACo--muDpFszfQZzGe7%2BvuBc1Y9QQ0u-fgoHCM1kOUny2u5yOg@mail.gmail.com> <05238e5a.6156fafe@fabiankeil.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Fabian, First, what is the recommended image hosting site. I don't think your conclusion is right. If you had a look at the console messages, it looks like the vdev is created but destroyed due to guid mismatch. I will repost the images once I know what service to use. Thanks! Yudi On 4/15/15, Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > yudi v <yudi.tux@gmail.com> wrote: > >> It's not the BIOS settings, I checked. It picks up the other HDD in the >> mirror and goes through the boot code and then it fails at booting into >> zfs >> root pool. >> The error is: >> >> *Trying to mount root from zfs:osysPool/ROOT/default []... >> *> >> >> * Mounting from zfs:osysPool/ROOT/default failed with error 6.* >> >> it is something to do with the guid mismatch for ada2p3 and ada3p3, not >> sure why it's even trying to compare them as they are the two partitions >> in >> the mirror. >> Please see the below images for the relevant console messages. >> screen1: >> https://drive.google.com/file/d/1Q-F-8kF-Nevn5ijvFXLNuvtJOuRn7ztO2Q/view?usp=sharing >> screen2: >> https://drive.google.com/file/d/1ZGseshS0Uk0cc6Gli_-tywHNXO7sLQ_aVw/view?usp=sharing > > Please note that these resources aren't accessible without allowing > presumably non-free JavaScript from untrustworthy (YMMV) sources. > >> Is anything amiss in the above label info for these two drives? >> I have used these two drives before for testing and reinstalled the os >> and >> recreated the pools. >> Any suggestions on how to fix this. > > The problem could be the result of a known race condition that will prevent > the system from booting if the kernel looks for the root pool before its > vdevs are available. The less disks there are, the "better" the chances > that > ZFS "wins" the race. > > The vfs.mountroot.timeout is ignored for ZFS so the kernel only tries once. > For details and a patch to change this see: > https://lists.freebsd.org/pipermail/freebsd-fs/2015-March/020997.html > > As a workaround you can add a UFS root file system on a disk that > doesn't actually exist to vfs.root.mountfrom. It should be the first > one so you don't hit the spa_namespace_lock deadlock reported in: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198563 > > Fabian > -- Kind regards, Yudi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACo--mte5c8ER-V6hqcZmvsmU2gPtCwMgSsFH29HLrcrLG-yjg>