10.07.2017 23:02, Toomas Soome пишет: > >> On 10. juuli 2017, at 22:53, Boris Samorodov <b...@passap.ru> wrote: >> >> 10.07.2017 22:21, Toomas Soome пишет: >>> >>>> On 10. juuli 2017, at 21:24, Boris Samorodov <b...@passap.ru> 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<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> >>>> >>>> >>>> >>>> Features2=0xc08e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,OSXSAVE> >>>> >>>> AMD Features=0x20100800<SYSCALL,NX,LM> >>>> AMD Features2=0x1<LAHF> >>>> 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: <A_M_I_ OEMAPIC > >>>> 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 _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
