On Sun, 10 Aug 2014, Eric L. Camachat wrote: > ---------------------------------------------------------------------------- > /usr/local/libexec/ppf_verify: pgp command failed > > gpg: Signature made Sun Aug 10 16:49:09 2014 MDT > gpg: using DSA key 0x49F050BB7A0EC18C > gpg: Can't check signature: No public key > ---------------------------------------------------------------------------- > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 08/09/2014 10:32, Mehmet Erol Sanliturk wrote: >> >> the installed systems are not bootable , and the last sentence on the >> screen is the following : >> >> >> No bootable device -- insert boot disk and press any key >> > > If you installed into GPT partitions like this: > $ gpart show ada0 > => 34 488397101 ada0 GPT (233G) > 34 1038 1 freebsd-boot (519K) > 1072 455081984 2 freebsd-ufs (217G) > 455083056 33314079 3 freebsd-swap (16G) > > Try to make GPT in MBR as bootable (active) partition: > $ fdisk -s /dev/ada0 > /dev/ada0: 484521 cyl 16 hd 63 sec > Part Start Size Type Flags > 1: 1 488397167 0xee 0x80 > $ fdisk -p /dev/ada0 > # /dev/ada0 > g c484521 h16 s63 > p 1 0xee 1 488397167 > a 1 > > This is an known issue on HP laptops. The simpler version is gpart set -a active ada0 There are multiple possible issues. This one is due to strict compliance with the GPT standard. Another problem is when a BIOS system does weird things based on an MBR partition type. Some Lenovo systems do that. When that is the problem, using MBR partitioning rather than the PMBR from GPT can work.Received on Sun Aug 10 2014 - 21:59:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:51 UTC