From owner-freebsd-current@freebsd.org Mon Jul 10 21:02:51 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 AA023DB0C88 for ; Mon, 10 Jul 2017 21:02:51 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (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 8088478057 for ; Mon, 10 Jul 2017 21:02:51 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OSW00J004F66R00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Mon, 10 Jul 2017 20:02:43 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1499716963; bh=GgZLkBdY5x4EG9pm9dyv3eP5r7tAEa+BkTpaLGx67oU=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=Iiuo0jRqGM+gsvAVTwYKrdp1qWJ+XYOd+Y5tXwinuKe5japa2rEmnmC+usbmRcSie uWWwHhEFbV3L0edaKVCWdP+1o4xGxdBiMeMHtaLabUDVRMm+ytjD/Y06OsdWySv3Hv eL5Q6BWKzUQ7nXXJGMlPbrtsih51nsc00JqA7tlFFZuqxI2115N06gbe7zxfsJhGbT cDVq6h7YEjUucgnOGl3TKuVIK9DllLAl/+vac1T/8xcAb6Ej4A+JS4MJt5WBJvbq12 l1xlNNCsZLbyECQ/Zhqw+9ebNuP79aubOn9rnEF/T1ncfx1QEHHUJBPoqgZjlUgBAl 5pFZPi5VmjTxw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OSW00KL050ENH00@st13p35im-asmtp002.me.com>; Mon, 10 Jul 2017 20:02:41 +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=18 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707100350 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [SOLVED] [memstick install] auto-zfs error From: Toomas Soome In-reply-to: Date: Mon, 10 Jul 2017 23:02:37 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <88E064A9-D834-418B-BBFA-586104989DB0@me.com> References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> To: Boris Samorodov X-Mailer: Apple Mail (2.3273) 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 21:02:51 -0000 > On 10. juuli 2017, at 22:53, Boris Samorodov wrote: >=20 > 10.07.2017 22:21, Toomas Soome =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>=20 >>> 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 >>=20 >> 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. >=20 > Yep, UFS+GPT works fine here. >=20 > Just for archieves: errors for ZFS + GPT > --- > gptzfsboot: error 128 lba 3907027040 > gptzfsboot: error 128 lba 1 Hm, 128 is 0x80 =3D=3D Disk timeout. So it can be result from the = missing device (bad USB connection or missing floppy drive). What our = INT13 related code is currently missing, is the reset on error calls - = to try to get the IO system back to stable state. Or to be exact - the = reset is not always used. rgds, toomas > gptzfsboot: no zfs pools located, can't boot > --- >=20 > The disk is: > --- > 512 # sectorsize > 2000397852160 # mediasize in bytes (1.8T) > 3907027055 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 3876018 # Cylinders according to firmware. > 16 # Heads according to firmware. > 63 # Sectors according to firmware. > WD-WMAUR0112162 # Disk ident. > Not_Zoned # Zone Mode > --- >=20 > UEFI is not available at the motherboard. >=20 >> 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. >=20 > --=20 > WBR, bsam