Re: Installer buggy (Re: OpenBSD on VMware ESXi)

2019-05-23 Thread Roderick



Thanks, Jan, thanks Otto for the personal mail.

Yes, the problem is sure that. I will se with the provider.

When I changed the fdisk partition (first writes), they were not written,
but the disklabel. When I did not, but changed the disklabel, then the
disklabel was not changed. I hope enough dmesg is written before KARL!!!

Rodrigo



Re: Installer buggy (Re: OpenBSD on VMware ESXi)

2019-05-23 Thread Jan Vlach


> On Thu, 23 May 2019, Jan Vlach wrote:
> 
> > IIRC, pvscsi used to eat up first write to the paravirtual storage
> > device with VMware. Not sure what's the current situation as I tend to
> > use LSI Logic SAS.
> 
> I do not understand very much, but yes, something is being eaten up.
> 
> The fsck I mentioned before was not effective, I landed with a system
> with ro mounted root system. It was impossible to do anything reasonable
> with it.
> 
> pci3 at ppb2 bus 3
> vmwpvs0 at pci3 dev 0 function 0 "VMware PVSCSI" rev 0x02: apic 1 int 18
^^
https://marc.info/?l=openbsd-misc=144899602327183=2

I think you're seeing this. Change the Storage adapter in VMware to LSI
Logic SAS or ask your VM provider to do this for you.

JV



Re: Installer buggy (Re: OpenBSD on VMware ESXi)

2019-05-23 Thread Roderick



On Thu, 23 May 2019, Jan Vlach wrote:


IIRC, pvscsi used to eat up first write to the paravirtual storage
device with VMware. Not sure what's the current situation as I tend to
use LSI Logic SAS.


I do not understand very much, but yes, something is being eaten up.

The fsck I mentioned before was not effective, I landed with a system
with ro mounted root system. It was impossible to do anything reasonable
with it.

I booted bsd.rd and did fsck /dev/rsd0a: tice!!!
The first one did not mark it as clean.

And now, I boot, but do not get a compleete /var/run/dmesg.boot for
Tom Smyth. Below is all what I get.

It seems, it was not the installer. :)

Any idea how to continue? How to get the ESXi version?

Thanks
Rodrigo






v 0x00
vga1: aperture needed
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02
pci2 at ppb1 bus 2
ahci0 at pci2 dev 0 function 0 "VMware AHCI" rev 0x00: apic 1 int 18, AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus0 at ahci0: 32 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable
ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01
pci3 at ppb2 bus 3
vmwpvs0 at pci3 dev 0 function 0 "VMware PVSCSI" rev 0x02: apic 1 int 18
scsibus1 at vmwpvs0: 16 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI4 0/direct fixed 
naa.6000c290fd42ddbb45acd19e285b95bf
sd0: 20480MB, 512 bytes/sector, 41943040 sectors
ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 "VMware PCIE" rev 0x01
pci8 at ppb7 bus 8
ppb8 at pci0 dev 21 function 6 "VMware PCIE" rev 0x01
pci9 at ppb8 bus 9
ppb9 at pci0 dev 21 function 7 "VMware PCIE" rev 0x01
pci10 at ppb9 bus 10
ppb10 at pci0 dev 22 function 0 "VMware PCIE" rev 0x01
pci11 at ppb10 bus 11
vmx0 at pci11 dev 0 function 0 "VMware VMXNET3" rev 0x01: apic 1 int 19, 
address 00:50:56:0a:ad:be
ppb11 at pci0 dev 22 function 1 "VMware PCIE" rev 0x01
pci12 at ppb11 bus 12
ppb12 at pci0 dev 22 function 2 "VMware PCIE" rev 0x01
pci13 at ppb12 bus 13
ppb13 at pci0 dev 22 function 3 "VMware PCIE" rev 0x01
pci14 at ppb13 bus 14
ppb14 at pci0 dev 22 function 4 "VMware PCIE" rev 0x01
pci15 at ppb14 bus 15
ppb15 at pci0 dev 22 function 5 "VMware PCIE" rev 0x01
pci16 at ppb15 bus 16
ppb16 at pci0 dev 22 function 6 "VMware PCIE" rev 0x01
pci17 at ppb16 bus 17
ppb17 at pci0 dev 22 function 7 "VMware PCIE" rev 0x01
pci18 at ppb17 bus 18
ppb18 at pci0 dev 23 function 0 "VMware PCIE" rev 0x01
pci19 at ppb18 bus 19
ppb19 at pci0 dev 23 function 1 "VMware PCIE" rev 0x01
pci20 at ppb19 bus 20
ppb20 at pci0 dev 23 function 2 "VMware PCIE" rev 0x01
pci21 at ppb20 bus 21
ppb21 at pci0 dev 23 function 3 "VMware PCIE" rev 0x01
pci22 at ppb21 bus 22
ppb22 at pci0 dev 23 function 4 "VMware PCIE" rev 0x01
pci23 at ppb22 bus 23
ppb23 at pci0 dev 23 function 5 "VMware PCIE" rev 0x01
pci24 at ppb23 bus 24
ppb24 at pci0 dev 23 function 6 "VMware PCIE" rev 0x01
pci25 at ppb24 bus 25
ppb25 at pci0 dev 23 function 7 "VMware PCIE" rev 0x01
pci26 at ppb25 bus 26
ppb26 at pci0 dev 24 function 0 "VMware PCIE" rev 0x01
pci27 at ppb26 bus 27
ppb27 at pci0 dev 24 function 1 "VMware PCIE" rev 0x01
pci28 at ppb27 bus 28
ppb28 at pci0 dev 24 function 2 "VMware PCIE" rev 0x01
pci29 at ppb28 bus 29
ppb29 at pci0 dev 24 function 3 "VMware PCIE" rev 0x01
pci30 at ppb29 bus 30
ppb30 at pci0 dev 24 function 4 "VMware PCIE" rev 0x01
pci31 at ppb30 bus 31
ppb31 at pci0 dev 24 function 5 "VMware PCIE" rev 0x01
pci32 at ppb31 bus 32
ppb32 at pci0 dev 24 function 6 "VMware PCIE" rev 0x01
pci33 at ppb32 bus 33
ppb33 at pci0 dev 24 function 7 "VMware PCIE" rev 0x01
pci34 at ppb33 bus 34
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, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
softraid0 at root
scsibus2 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
syncing disks... done
rebooting...
OpenBSD 6.4 (GENERIC) #926: Thu Oct 11 13:43:06 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem  = 536227840 (511MB)
avail mem = 511414272 (487MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 09/19/18, BIOS32 rev. 0 @ 0xfd780, SMBIOS rev. 2.7 @ 
0xe0010 (620 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 09/19/2018
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) 
S16F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3) 
PE50(S3) S1F0(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits

Re: Installer buggy (Re: OpenBSD on VMware ESXi)

2019-05-23 Thread Jan Vlach
Hi Rodrigo,

IIRC, pvscsi used to eat up first write to the paravirtual storage
device with VMware. Not sure what's the current situation as I tend to
use LSI Logic SAS.

Also, the first eaten-up write would explain why you're still seeing
Linux partitions instead of OpenBSD.


# fdisk sd0
Disk: sd0   geometry: 14593/255/63 [234441648 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 -  14592 254  63 [  64:   234436481 ]
OpenBSD

jvl

P.S. Description or even screenshots would help to know where you got
stuck.



Re: Installer buggy (Re: OpenBSD on VMware ESXi)

2019-05-23 Thread Roderick



Some more details about my experience. Excuseme that I dont take
fotos of the screen and just describe, with the data y wrote down.

As I wrote, yesterday my instalation did not work. Today morning
I began to inspect with the shell of cd65.iso the partitions.

fdisk gave me  41943040 sectors divided as follows:

  startsize
0*  2048 997376  Linux files
1 999424   40943616  Linux LVM

disklabel gave me the sizes I typed:

a   409600   0   4.2BSD
b  1048576   409600  swap
c 41943040   0
e 40484864  1458176  4.2BSD

you see there the offset zero, no MBR. That is why the system did not
boot. I went to the shell and did "fdisk -iy sd0". Now I have a partition
3 with the whole, 64 till 41942976. I started the installer and
got an installation, as described, only with the automatic set values.

The server hoster offers two kinds of shutting down the system by
clicking on their web plattform: software and hardware. If I restart
with "hardware", the system does not go up anymore, unless I reinstall
the whole system. I though the hoster spoiled my disk because it
writes in the first 2048 sectors. I went to install again, but with
an offset of 2048 in the OpenBSD fdisk partition: no way, the installer
ignores my settings.

Rodrigo