Dual boot problem

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Dual boot problem

Greg Thomas-2
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$ disklabel sd0

# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST1000LM049-2GH1
duid: f251a360129c9562
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 121601
total sectors: 1953525168
boundstart: 64
boundend: 1953520065
drivedata: 0

16 partitions:
#                size           offset  fstype [fsize bsize   cpg]
  a:          2097152               64  4.2BSD   2048 16384 12960 # /
  b:         33807608          2097216    swap                    # none
  c:       1953525168                0  unused
  d:          8388576         35904832  4.2BSD   2048 16384 12960 # /tmp
  e:         74955232         44293408  4.2BSD   2048 16384 12960 # /var
  f:         12582912        119248640  4.2BSD   2048 16384 12960 # /usr
  g:          2097152        131831552  4.2BSD   2048 16384 12960 #
/usr/X11R6
  h:         41943040        133928704  4.2BSD   2048 16384 12960 #
/usr/local
  i:          4194304        175871744  4.2BSD   2048 16384 12960 # /usr/src
  j:         12582912        180066048  4.2BSD   2048 16384 12960 # /usr/obj
  k:        629145600        192648960  4.2BSD   4096 32768 26062 # /home

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

Since my install is on sd0 I ran the dd command from the FAQ:

dd if=/dev/rsd0a of=openbsd.pbr bs=512 count=1

I moved the PBR to Windows, and ran the bcdedit commands listed in the FAQ plus

bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /set {bootmgr} timeout 12

Thanks for any pointers.  I'm going to re-run the dd command in case I
chose the wrong disk somehow earlier.

Greg

OpenBSD 6.7 (GENERIC.MP) #182: Thu May  7 11:11:58 MDT 2020
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17041059840 (16251MB)
avail mem = 16511991808 (15747MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
bios0: vendor LENOVO version "8DET76WW (1.46 )" date 06/21/2018
bios0: LENOVO 4286CTO
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF!
TCPA SSDT SSDT UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4)
EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2791.35 MHz, 06-2a-07
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.95 MHz, 06-2a-07
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.96 MHz, 06-2a-07
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.95 MHz, 06-2a-07
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf8000000, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus 5 (EXP4)
acpiprt5 at acpi0: bus 13 (EXP5)
acpiprt6 at acpi0: bus 14 (EXP7)
acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2
acpitz0 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpipci0 at acpi0 PCI0: 0x00000000 0x00000011 0x00000001
acpicmos0 at acpi0
tpm0 at acpi0: TPM_ addr 0xfed40000/0x5000, device 0x0000104a rev 0x4e
acpibat0 at acpi0: BAT0 model "45N1025" serial 19711 type LION oem "LGC"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0: version 1.0
"IBM0079" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpidock0 at acpi0: GDCK docked (15)
acpivideo0 at acpi0: VID_
acpivout0 at acpivideo0: LCD0
acpivideo1 at acpi0: VID_
cpu0: using VERW MDS workaround (except on vmm entry)
cpu0: Enhanced SpeedStep 2791 MHz: speeds: 2801, 2800, 2600, 2400,
2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi, SANDYBRIDGE, gen 6
"Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
puc0 at pci0 dev 22 function 3 "Intel 6 Series KT" rev 0x04: ports: 16 com
com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo
com4: probed fifo depth: 0 bytes
em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address
f0:de:f1:d9:f8:47
ehci0 at pci0 dev 26 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 6 Series HD Audio" rev 0x04: msi
azalia0: codecs: Conexant CX20590, Intel/0x2805, using Conexant CX20590
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 6 Series PCIE" rev 0xb4: msi
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 1 "Intel 6 Series PCIE" rev 0xb4: msi
pci2 at ppb1 bus 3
iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6250" rev
0x5e: msi, MIMO 1T2R, MoW, address 64:80:99:5a:ea:8c
ppb2 at pci0 dev 28 function 3 "Intel 6 Series PCIE" rev 0xb4: msi
pci3 at ppb2 bus 5
ppb3 at pci0 dev 28 function 4 "Intel 6 Series PCIE" rev 0xb4: msi
pci4 at ppb3 bus 13
sdhc0 at pci4 dev 0 function 0 "Ricoh 5U823 SD/MMC" rev 0x04: apic 2 int 16
sdhc0: SDHC 3.0, 50 MHz base clock
sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma
ppb4 at pci0 dev 28 function 6 "Intel 6 Series PCIE" rev 0xb4: msi
pci5 at ppb4 bus 14
xhci0 at pci5 dev 0 function 0 "NEC xHCI" rev 0x04: msi, xHCI 0.96
usb1 at xhci0: USB revision 3.0
uhub1 at usb1 configuration 1 interface 0 "NEC xHCI root hub" rev
3.00/1.00 addr 1
ehci1 at pci0 dev 29 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel QM67 LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 6 Series AHCI" rev 0x04: msi, AHCI 1.3
ahci0: port 0: 6.0Gb/s
ahci0: port 1: 6.0Gb/s
ahci0: port 2: 3.0Gb/s
scsibus1 at ahci0: 32 targets
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
ichiic0 at pci0 dev 31 function 3 "Intel 6 Series SMBus" rev 0x04: apic 2 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM PC3-12800 SO-DIMM
spdmem1 at iic0 addr 0x51: 8GB DDR3 SDRAM PC3-12800 SO-DIMM
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.0, 0x1e2b1 0x940300 0x194b40
0xd001a3 0x120c00
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
aps0 at isa0 port 0x1600/31
uhub3 at uhub0 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.00 addr 2
uhub4 at uhub3 port 1 configuration 1 interface 0 "Standard
Microsystems product 0x2514" rev 2.00/0.00 addr 3
ugen0 at uhub3 port 4 "Broadcom Corp Broadcom Bluetooth Device" rev
2.00/7.48 addr 4
uvideo0 at uhub3 port 6 configuration 1 interface 0 "Chicony
Electronics Co., Ltd. Integrated Camera" rev 2.00/8.54 addr 5
video0 at uvideo0
uhub5 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.00 addr 2
ugen1 at uhub5 port 3 "Intel(R) Corporation Intel(R) Centrino(R)
Advanced-N + WiMAX 6250" rev 2.00/0.00 addr 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (f251a360129c9562.a) swap on sd0b dump on sd0b
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
Reply | Threaded
Open this post in threaded view
|

Re: Dual boot problem

Nick Holland
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.

Reply | Threaded
Open this post in threaded view
|

Re: Dual boot problem

Clay Daniels-2
On Sun, Jun 28, 2020 at 11:25 AM Nick Holland <[hidden email]>
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
Reply | Threaded
Open this post in threaded view
|

Re: Dual boot problem

Greg Thomas-2
In reply to this post by Nick Holland
On Sun, Jun 28, 2020 at 9:25 AM Nick Holland <[hidden email]>
wrote:

>
> 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.
>

Rad, thanks Nick!  I'm going to poke around with BCDEasy or whatever that
3rd party software is since it'll be easier to figure out rather than
reading through all the bcdedit documentation.  I swear back in the Windows
ntldr days that I was running Windows and OpenBSD on separate disks so I
think this should be doable with their current boot loader.

Worse comes to worse I'll go with your last suggestion!

Greg
Reply | Threaded
Open this post in threaded view
|

Re: Dual boot problem

Greg Thomas-2
In reply to this post by Clay Daniels-2
On Sun, Jun 28, 2020 at 12:34 PM Clay Daniels <[hidden email]>
wrote:

>
> 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. ;-)
>

Yeah, I'm super fortunate to have found this pretty much unused X220 so I
could just keep the beat up old X220 for Windows.
Reply | Threaded
Open this post in threaded view
|

Re: Dual boot problem

Greg Thomas-2
In reply to this post by Greg Thomas-2
On Sun, Jun 28, 2020 at 1:13 PM Greg Thomas <[hidden email]>
wrote:

> On Sun, Jun 28, 2020 at 9:25 AM Nick Holland <[hidden email]>
> wrote:
>
>>
>> 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.
>>
>
> Rad, thanks Nick!  I'm going to poke around with BCDEasy or whatever that
> 3rd party software is since it'll be easier to figure out rather than
> reading through all the bcdedit documentation.  I swear back in the Windows
> ntldr days that I was running Windows and OpenBSD on separate disks so I
> think this should be doable with their current boot loader.
>
> Worse comes to worse I'll go with your last suggestion!
>

I couldn't find any magic with bcdedit/BCDEasy so I shrunk my Windows
partition, did a minimal install of OpenBSD way out there at the end of
sd2, copied over some of /etc, and it's all good.

nihilanon$ fdisk sd2
Disk: sd2 geometry: 31130/255/63 [500118192 Sectors]
Offset: 0 Signature: 0xAA55
            Starting         Ending         LBA Info:
 #: id      C   H   S -      C   H   S [       start:        size ]
-------------------------------------------------------------------------------
*0: 07      0  32  33 -    191  24  25 [        2048:     3067904 ] NTFS

 1: 07    191  56  58 -  30875 167  12 [     3072000:   492945408 ] NTFS

 2: A6  30875 167  13 -  31130 158   4 [   496017408:     4096000 ] OpenBSD

 3: 00      0   0   0 -      0   0   0 [           0:           0 ] unused


Next up is OpenVPN, and deciding if I should stick with -stable (most
probably) or start trying snapshots again.