On Sun, Jun 28, 2020 at 11:25 AM Nick Holland <[email protected]> wrote:
> On 2020-06-27 21:50, Greg Thomas wrote: > > Hey folks, I'm trying to avoid buggin y'all, but I'm down to my last two > > tasks, setting up dual boot with Windows 10 and setting up OpenVPN. I'm > > currently trying to troubleshoot "Loading.... ERR M" while using Windows > > BCD. I can boot no problem when selecting my boot drive while starting > up > > my Thinkpad X220. > > > > I installed a couple of weeks ago using pretty much all defaults. > ... > > nihilanon# fdisk sd0 > > Disk: sd0 geometry: 121601/255/63 [1953525168 Sectors] > > Offset: 0 Signature: 0xAA55 > > Starting Ending LBA Info: > > #: id C H S - C H S [ start: size ] > > > ------------------------------------------------------------------------------- > > 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] > unused > > 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] > unused > > 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] > unused > > *3: A6 0 1 2 - 121600 254 63 [ 64: 1953520001 ] > OpenBSD > > I'm not seeing a windows partition here. And it appears your OpenBSD > partition is using the entire disk. Oh. Your computer has three disks > in it...your Windows install is on a second/third disk? I don't think > that is going to work. > > from your dmesg: > sd0 at scsibus1 targ 0 lun 0: <ATA, ST1000LM049-2GH1, SDM2> > naa.5000c500b98a130c > sd0: 953869MB, 512 bytes/sector, 1953525168 sectors, thin > sd1 at scsibus1 targ 1 lun 0: <ATA, M4-CT512M4SSD2, 040H> > naa.500a07510369b769 > sd1: 488386MB, 512 bytes/sector, 1000215216 sectors, thin > sd2 at scsibus1 targ 2 lun 0: <ATA, SAMSUNG SSD PM85, EXT4> > naa.5002538844584d30 > sd2: 244198MB, 512 bytes/sector, 500118192 sectors, thin > > ERR M basically means that biosboot(8), which is "tagged" with the > physical location of /boot(8) on the disk, doesn't see the marker > that indicates that what it is pointing at is actually /boot. The > windows 10 boot loader is pulling from a disk other than sd0, the pbr > is pointing at something "correct" if it were sd0, but the Windows > boot loader is trying to pull it from whatever the new default disk > is. Maybe. > > There may be some bcdedit magic that can say "boot from this other disk" > which might solve your problem, but I have no idea. A lame way of > doing this might be to shrink your Windows partition by 1G, and install > your OpenBSD root partition there, and the rest on sd0. > > Nick. > > I have used Rod Smith's rEFInd boot manager for some time, and started out installing it in a Windows partition's efi boot section, but it also works as a stand alone boot usb to pick up all UEFI installations on the entire computer, either same disk multi-boot or a separate disks on the same machine. Right now I have FreeBSD 13.0 Current on the spinning disk & OpenBSD 6.7 -current on the M2 SSD drive. Bear in mind Refind works only for UEFI, not MBR. If I load NetBSD to the SSD drive as a MBR install, I have to drop down to the BIOS and pick the boot order there. I too need a Windows install, but I have moved it to my older 2014 machine and kept my self-built toy for BSD. I think I need to buy me another SSD to run NetBSD too. ;-) Clay
