Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Aug 2016 06:59:55 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   =?UTF-8?B?W0J1ZyAyMTE3MTVdIFNvbWUgY29tcHV0ZXJzIGNhbiBub3QgYm9vdCDigJMg?= =?UTF-8?B?bm8gZmlsZSBzeXN0ZW0gZm91bmQgKGUuZy4gJ05vbi1TeXN0ZW0gZGlzayBv?= =?UTF-8?B?ciBkaXNrIGVycm9yIOKApicpIOKAkyB3aGVyZSB0aGUgR1BUIGFuZCBwYXJ0?= =?UTF-8?B?aXRpb25zIGFyZSBjcmVhdGVkIGJ5IGdwYXJ0KDgp?=
Message-ID:  <bug-211715-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211715

            Bug ID: 211715
           Summary: Some computers can not boot – no file system found
                    (e.g. 'Non-System disk or disk error …') – where the
                    GPT and partitions are created by gpart(8)
           Product: Base System
           Version: CURRENT
          Hardware: Any
               URL: https://github.com/trueos/pc-sysinstall/issues/3#issue
                    comment-238661284
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: grahamperrin@gmail.com

FreeBSD-based TrueOS Desktop CURRENT installed to an HP EliteBook 8540p
notebook with UEFI enabled. A limited workaround is outlined below. 

Long before this beta, I found the same symptoms but never a workaround with
FreeBSD-based PC-BSD CURRENT installed to some other computers, including but
not limited to an HP EliteBook 8570p. 


Outline
=======

https://github.com/trueos/pc-sysinstall/issues/3#issuecomment-238661284 is
concise –

> If I boot from the installation disk and run the following commands –
> 
> gpart destroy -F ada0
> 
> gpart create -s gpt ada0
> 
> – then boot Parted Magic (from UBCD) and launch Partition Editor, there is again the prompt to fix the GPT.

– and critically, for a disk where the operating system is installed: 

a) without a fix to the GPT, the computer can not find the BSD boot loader

  – more broadly, it can not find the file system 
    that should be used for the UEFI boot; and 

b) immediately after a fix by GParted to the GPT, the loader is found and the
FreeBSD-based OS boots without difficulty. 


Symptom on an HP EliteBook 8540p
================================

> Non-System disk or disk error
> replace and strike any key when ready
> 
> _


Shown by GParted
================

> Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 7 blocks) or continue with the current setting?


Limitations of the workaround
=============================

If GELI encryption is preferred when installing the OS, then (as above) the
computer can not find the file system that includes the boot loader. The fix to
the GPT will allow the loader to be found, however: 

* with the attempt to load, there's an immediate panic. 


Side note
=========

#211702 blocks me from making a comparison with FreeBSD-11.0-BETA4-amd64


Reference
=========

HP EliteBook 8540p Notebook PC – HP EliteBook 8540w Mobile Workstation –
Maintenance and Service Guide
<http://h20565.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=4097214&docLocale=en_GB&docId=emr_na-c03382696>;

-- 
You are receiving this mail because:
You are the assignee for the bug.


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