From owner-freebsd-current@freebsd.org Mon Jul 10 20:21:17 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD065DB047B for ; Mon, 10 Jul 2017 20:21:17 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B20C076F55 for ; Mon, 10 Jul 2017 20:21:17 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OSW004002K4ND00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Jul 2017 19:21:11 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1499714471; bh=vD6+i0hGVs3Mn0kWGBYuG1cduCxPEAbTG3fCTgUEcOA=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=wHXGmp8552mFXmL5VyUrkcOmaG0BzXHuS0UkTPiA6t4Ays17ckI9bz1gMTgKMaP4a pV8bz7JZGDmy3hPrHMtbBj8MO9WcVSLfdXM1Y7g9RNrobl0pn5d40hCfOwyc4bD1gN nIcOZpPFwej3+gPyCvwmgRxmevrYZ+rQzSBA4e2uv7vp+ifVtyZ49RGpfBi90IDi9u l0KsKIrPQZtPo/dc7J2nY5p9+aoiefUXetEAnt+ZTchMRBdmUv9T6g7BNwVye1gSRi snXG1Br4XAyEvyb74GNNcjt7Qmc93sZ53RazdBr5CFo20+wsyeorP+9/SkqRrBQwLr zjsNRFkCLLCIw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OSW001PM338LE50@st13p35im-asmtp001.me.com>; Mon, 10 Jul 2017 19:21:11 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-10_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=52 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707100340 From: Toomas Soome Message-id: <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [SOLVED] [memstick install] auto-zfs error Date: Mon, 10 Jul 2017 22:21:08 +0300 In-reply-to: Cc: freebsd-current@freebsd.org To: Boris Samorodov References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 20:21:18 -0000 > On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >=20 > 10.07.2017 21:05, Allan Jude =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> On 2017-07-09 14:40, Boris Samorodov wrote: >>> 08.07.2017 18:56, Boris Samorodov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> Hi All, >>>>=20 >>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>> installation memstick.img. Auto-UFS (GPT) installs fine and the = system >>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>> At the very beginning it gives something like "gpt sector XXXX = error, >>>> gpt sector 1 error, can't find zroot..." >>>>=20 >>>> Is it a known error / should I give more (precise) errors? >>>>=20 >>>> I tried two recent images with the same result: >>>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-C= URRENT-amd64-20170703-r320599-memstick.img >>>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-C= URRENT-amd64-20170626-r320360-memstick.img >>>=20 >>> It turned out GPT and zfs are not usable at this machine. >>> MBR / ZFS works fine. >>>=20 >>> I'll stick with that. >>=20 >> What type of machine is it? >=20 > It's a PC circa 2009 with MB ASUS P5QL/EPU: > --- > CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz > K8-class CPU) > Origin=3D"GenuineIntel" Id=3D0x1067a Family=3D0x6 Model=3D0x17 = Stepping=3D10 >=20 >=20 > = Features=3D0xbfebfbff >=20 >=20 >=20 > = Features2=3D0xc08e3bd >=20 > AMD Features=3D0x20100800 > AMD Features2=3D0x1 > VT-x: HLT,PAUSE > TSC: P-state invariant, performance statistics > real memory =3D 4294967296 (4096 MB) > avail memory =3D 3324891136 (3170 MB) > Event timer "LAPIC" quality 100 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > --- >=20 > --=20 > WBR, bsam Of course it really can not be that the BIOS has something against = combination of GPT+ZFS, but this combination may trigger some sort of = bug/misbehavior. I have seen some pretty weird issues and have work in = process to have a bit more fool proof approach, but I haven't had time = yet to finalize it properly. Namely, what I have found is that in some systems the INT13 ah=3D08 can = result with unexpected results - error from command reported or disk = count not reported etc - something not really expected. It also may have = to do about what other devices are there. And also if the system has = plain BIOS or BIOS emulated on UEFI. rgds, toomas