Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Nov 2016 02:43:08 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-amd64@FreeBSD.org
Subject:   [Bug 214375] RAIDZ pool with cheksum=skein fails to execute loader.efi from boot1.efi on UEFI system
Message-ID:  <bug-214375-6@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214375

            Bug ID: 214375
           Summary: RAIDZ pool with cheksum=3Dskein fails to execute
                    loader.efi from boot1.efi on UEFI system
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: lstewart@FreeBSD.org
                CC: freebsd-amd64@FreeBSD.org
                CC: freebsd-amd64@FreeBSD.org

I tested with FreeBSD-CURRENT snapshot
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/12.0/Fre=
eBSD-12.0-CURRENT-amd64-20161021-r307747-memstick.img.xz

Installing boot1.efifat into the EFI partition and creating a single RAIDZ =
pool
to boot from fails to boot when "-O checksum=3Dskein" is included in the zp=
ool
creation step, but boots fine when that option is omitted i.e. default chec=
ksum
algorithm is used.

Symptoms observed are that boot1 sees my pool (prints my pool name after "f=
ound
the following pools" message) but hangs where it should have run loader.efi,
and the only way to recover is a hard reset. Same result after every boot.

tsoome@ appears to have reproduced the problem and a likely fix is up for
review at https://reviews.freebsd.org/D8487 which I will be testing shortly,
but he requested that a bug report be filed.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214375-6>