search for: pmbr

Hi, I've been working on making a USB key which is bootable via EFI and BIOS, and so far I've succeeded but only by using GRUB on the MBR. Syslinux installs correctly, but because the USB key can only have one partition and its type is EFI protective, it isn't set to bootable on the MBR partition table and so syslinux (mbr.bin) doesn't boot. I've also tried gptmbr.bin

So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I

Various EFI systems insist that there be no active flag in the pMBR in order to parse the GPT. The only way around this is to also generate a valid MBR - the firmware will then pick that up and use the system partition provided there. In order to deal with other EFI "sanity" checks, the partition type for the non-EFI partitions is set to 0 to skip the fir...

.... I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice. If I use the usb stick I installed from, I can select the boot device, and actually boot from it, so there doesn't seem to be anything wrong with the SSD. I tried: kg-vm2# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 bootcode written to ada0 in case there was something wrong with the bootcode, but I still get the message "ERROR: No boot disk has been detected or the disk has failed." gpart shows this: root@kg-vm2# gpart show ada0 => 34 250069613 ada0 GPT (119G)...

Hi, I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm getting: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool klawisz gptzfsboot: failed to mount default pool klawisz Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM, 400 GB of local storage with SCSI Controller type: Default (lsi). I'm not sure what I did to

> On Mon, Feb 25, 2019 at 11:54 PM Simon Matter via CentOS > <centos at centos.org> > wrote: > >> > >> > What makes you think this has *anything* to do with systemd? Bitching >> > about systemd every time you hit a problem isn't helpful. Don't. >> >> If it's not systemd, who else does it? Can you elaborate, please? >> >

...d /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" /dev/vda2: UUID="OR1eUA-1hhb-PCff-qybQ-rLt4-JuTN-EcWX61" TYPE="LVM2_member" /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660" PTTYPE="PMBR" /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" TYPE="xfs" /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" TYPE="swap" # cat /etc/fstab # # /etc/fstab # Created by anaconda on Thu Dec 8 13:40:06 2016 # # Acc...

...UID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" > /dev/vda2: UUID="OR1eUA-1hhb-PCff-qybQ-rLt4-JuTN-EcWX61" TYPE="LVM2_member" > /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660" > PTTYPE="PMBR" > /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" > TYPE="xfs" > /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" > TYPE="swap" > > # cat /etc/fstab > # > # /etc/fstab > # Created by an...

Gordon Messmer wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart --type=lvm > > A couple of things to consider: > * The documentation for

Hello, I'm struggling to make a cloned CentOS 7 VM (under KVM) to work. The VM was cloned using mondorestore. Restore appears successful but the VM won't boot; see: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png I booted with CentOS 7 disk in troubleshooting mode (where the virtual disk was automatically mounted without issues) and I tried to repair:

Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful

Hi all, A recent thread inspired me to try getting a proper serial console working on a Supermicro X9SCL motherboard with IPMI. However I find that while I see loader messages and the getty I enabled after boot I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so..