From owner-freebsd-current@freebsd.org Mon Jul 10 23:06:22 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 B38F2DB2EC7 for ; Mon, 10 Jul 2017 23:06:22 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward5h.cmail.yandex.net (forward5h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 585367B8AA for ; Mon, 10 Jul 2017 23:06:22 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b6:7]) by forward5h.cmail.yandex.net (Yandex) with ESMTP id 37D3220FE4; Tue, 11 Jul 2017 02:06:18 +0300 (MSK) Received: from smtp2p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2p.mail.yandex.net (Yandex) with ESMTP id 6C4AF1A8003B; Tue, 11 Jul 2017 02:06:16 +0300 (MSK) Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ffG7OZaxgz-6Gsegs3Z; Tue, 11 Jul 2017 02:06:16 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1499727976; bh=A6NIZY09iuxh2X2Qncgmrfj0c/rEE2fHGGp3w3NCgSA=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=O2HQEoijv2S9GdkQTw/pYwPZIxsZTB3Z/SCYlOnmBg5qgz4jbCt2MTVKfzVW5QS0R b+xpGnhTdzWCSs6t3zvRISNBGDRMoruqpnZzQ7IlEaASDFG4/LyotfWRhcr6u+ocF9 5cem1aAPRQfAOoXvggq2cBoKnYdhAbIIl57vwams= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0,1 0 Subject: Re: [SOLVED] [memstick install] auto-zfs error To: Ronald Klop , Toomas Soome Cc: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> From: Boris Samorodov Message-ID: <277f7ce9-f939-0878-f954-4924596b6421@passap.ru> Date: Tue, 11 Jul 2017 02:06:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit 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 23:06:22 -0000 10.07.2017 23:58, Ronald Klop пишет: > On Mon, 10 Jul 2017 21:53:11 +0200, Boris Samorodov wrote: > >> 10.07.2017 22:21, Toomas Soome пишет: >>> >>>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>>> >>>> 10.07.2017 21:05, Allan Jude пишет: >>>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>>>> Hi All, >>>>>>> >>>>>>> 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..." >>>>>>> >>>>>>> Is it a known error / should I give more (precise) errors? >>>>>>> >>>>>>> I tried two recent images with the same result: >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>>>> >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>>>>> >>>>>> >>>>>> It turned out GPT and zfs are not usable at this machine. >>>>>> MBR / ZFS works fine. >>>>>> >>>>>> I'll stick with that. >>>>> >>>>> What type of machine is it? >>>> >>>> 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="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >>>> >>>> >>>> Features=0xbfebfbff >>>> >>>> >>>> >>>> >>>> Features2=0xc08e3bd >>>> >>>> >>>> AMD Features=0x20100800 >>>> AMD Features2=0x1 >>>> VT-x: HLT,PAUSE >>>> TSC: P-state invariant, performance statistics >>>> real memory = 4294967296 (4096 MB) >>>> avail memory = 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) >>>> --- >>>> >>>> -- >>>> 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. >> >> Yep, UFS+GPT works fine here. >> >> Just for archieves: errors for ZFS + GPT >> --- >> gptzfsboot: error 128 lba 3907027040 >> gptzfsboot: error 128 lba 1 >> gptzfsboot: no zfs pools located, can't boot >> --- >> >> 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 >> --- >> >> UEFI is not available at the motherboard. >> >>> Namely, what I have found is that in some systems the INT13 ah=08 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. >> > > This looks similar to: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > Please add your information if you think it is the same issue. Or try > the workaround and see if it helps. Yes, the problem seems to be the same. A comment is added. Thank you for the link. -- WBR, bsam