From owner-freebsd-current@freebsd.org Mon Jul 10 22:15:30 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 1A0BCDB1E87 for ; Mon, 10 Jul 2017 22:15:30 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward1o.cmail.yandex.net (forward1o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::2a1]) (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 B0B5C7A0E5 for ; Mon, 10 Jul 2017 22:15:29 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [5.45.198.129]) by forward1o.cmail.yandex.net (Yandex) with ESMTP id 6B63A21320; Tue, 11 Jul 2017 01:15:16 +0300 (MSK) Received: from smtp4j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp4j.mail.yandex.net (Yandex) with ESMTP id ECD45324112A; Tue, 11 Jul 2017 01:15:15 +0300 (MSK) Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id yV5WBh9lgF-FEXqm9DV; Tue, 11 Jul 2017 01:15:14 +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=1499724914; bh=+hivCvijFdGFYMjyQeH55uEz6ITBKltrn4Gf1wkKSQI=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=YB6BvAJ9eF8Q/wivklCgyYK51NK5qKiJjmeoc3vgkB5tKy7H04ro1nTnvTQWMUuPh VBcNMb0YxpyaOnYs2qWyGnSl5RfTROo6gh2y47Ccee1eLthzQDssifM3GTqzLRQGdB lQAD5bDhuBHFQIGo+Q+JrautEk6bRiGJ1soQWZUQ= Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [SOLVED] [memstick install] auto-zfs error To: Toomas Soome Cc: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> <88E064A9-D834-418B-BBFA-586104989DB0@me.com> From: Boris Samorodov Message-ID: Date: Tue, 11 Jul 2017 01:15:14 +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: <88E064A9-D834-418B-BBFA-586104989DB0@me.com> 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 22:15:30 -0000 10.07.2017 23:02, Toomas Soome пишет: > >> On 10. juuli 2017, at 22:53, 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 > > Hm, 128 is 0x80 == 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. Actually, it's the same SATA cable/disk which works for UFS/ZFS. > rgds, > toomas > >> 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. >> -- WBR, bsam