Date: Mon, 10 Jul 2017 23:02:37 +0300 From: Toomas Soome <tsoome@me.com> To: Boris Samorodov <bsam@passap.ru> Cc: freebsd-current@freebsd.org Subject: Re: [SOLVED] [memstick install] auto-zfs error Message-ID: <88E064A9-D834-418B-BBFA-586104989DB0@me.com> In-Reply-To: <d95bef1b-b8d8-7a81-f47c-c1165afc1bb8@passap.ru> References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <c4ef7a9b-ccce-f060-f8d3-cb3fe6a9d5a7@passap.ru> <eee307df-a0f8-0fa9-9a01-2621f02def55@freebsd.org> <cf07997a-18e7-2d47-3658-c76ef1a15680@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> <d95bef1b-b8d8-7a81-f47c-c1165afc1bb8@passap.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 10. juuli 2017, at 22:53, Boris Samorodov <bsam@passap.ru> 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 <bsam@passap.ru> 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<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE= ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >>>=20 >>>=20 >>>=20 >>> = Features2=3D0xc08e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,P= DCM,SSE4.1,XSAVE,OSXSAVE> >>>=20 >>> AMD Features=3D0x20100800<SYSCALL,NX,LM> >>> AMD Features2=3D0x1<LAHF> >>> 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: <A_M_I_ OEMAPIC > >>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88E064A9-D834-418B-BBFA-586104989DB0>