Re: two recent snapshot installer problems

> On 7. märts 2017, at 21:05, Michael W. Lucas <mwlucas_at_michaelwlucas.com> wrote:
> 
> Hi,
> 
> I want to open a bug report on this, but have no idea how to gather
> useful info.
> 
> Attempting to install
> FreeBSD-12.0-CURRENT-amd64-20170301-r314495-memstick.img onto an
> eight-drive iX system. This machine previously ran -current, but the
> OS has been sadly used by book testing and I decided to do a clean
> install.
> 
> Used the Guided ZFS install, no networking, no extra users, default
> security. 
> 
> I want a two-way mirror for the base install, and the BIOS didn't
> provide serial numbers for each disk, so I wound up doing multiple
> installs, thinking that once I installed to the disk that the BIOS
> expected to be a boot disk, it'd find the pool and boot.
> 
> Each of the four installs failed to boot, giving me:
> 
> gptzfsboot: error 1 lba 32
> error 1
> gptzfsboot: error 1 lba 4294967288
> gptzfsboot: error 1 lba 1
> gptzfsboot: No ZFS pools located, can't boot


The messages are from low level disk IO, INT13.

        if (V86_CY(v86.efl)) {
                printf("%s: error %u lba %u\n",
                    BOOTPROG, v86.eax >> 8 & 0xff, lba);
                return (-1);
        }

So the error 1 is:

01h	Invalid Command

Which means the INT13 AX=0x4200  is not supported by this BIOS. So, the question is, does your HBA is set in bios to IDE or AHCI mode? Changing that  may make an difference, also usual suggestion - check for bios update, and if the host supports it, check the uefi boot… Of course, the fact that it did run fbsd before, points towards bios settings change...

the invalid command from INT13 extended read is by itself quite odd, but there is also possible another reason - if by any reason somehow the memory buffer for this call is from memory above 640k and so the invalid memory area was provided…

rgds,
toomas


> 
> Old disklabels? gpart -F destroy da0 through ada3. and
> reinstall. Nope.
> 
> In frustration I did an eight-disk mirror install. Got the same
> message.
> 
> Fine, I'll install to the Intel RAID satadom. It's a raid config, but
> it'll get me a working system. Select a ZFS stripe on raid/r0.
> 
> gpart: arg0 'raid/r0': Invalid argument
> 
> Mirror on the individual satadom drives?
> 
> Same boot message.
> 
> Any suggestions on how to gather debugging info for this?
> 
> Thanks,
> ==ml
> 
> 
> -- 
> Michael W. Lucas    Twitter _at_mwlauthor 
> nonfiction: https://www.michaelwlucas.com/
> fiction: https://www.michaelwarrenlucas.com/
> blog: http://blather.michaelwlucas.com/
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"