install the sets, install70.img

[Raul Miller]

I am attempting to install openbsd on a maestro evolve iii notebook.

I am using the install70.img from
https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/ written to a usb
drive.

Installation prompts with responses as follows:
boot> (I let this time out)
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? I
Choose your keyboard layout ('?' or 'L' for list) [default]
System hostname? (short form, e.g. 'foo') whatever

Available network interfaces are: vlan0
Which network interface do you wish to configure? (or 'done') [vlan0] done
DNS domain name? (e.g. 'example.com') [my.domain] bogus.invalid
DNS nameservers? (IP address list or 'none') [none]
Password for root account? (will not echo)
Password for root account? (again)
Start sshd(8) by default? [yes] no
Do you want the X Window System to be started by xenodm(1)? [no]
Setup a user? (enter a lower-case loginname, or 'no') [no]

Available disks are: sd0
Which disk is the root disk? ('?' for details) [sd0]
Use (W)hole disk MBR, whole disk (G)pt, (O)penBSD area or (E)dit? [OpenBSD] G
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a]
Location of sets? (disk http nfs or 'done') [http]

So here's my problem:

I was expecting that since I was using install70.img that I would have
an option to install the sets from the usb drive. But I do not see
that option listed here. And, dropping into shell, I do not see
anything that looks like a device file for the usb drive, to mount on
mnt2

Obviously, I am doing something wrong. But, what?

I am not currently prepared to bring up wifi on this machine, to
install the sets from the network. Should that be my only recourse
here?

I opt to use gpt rather than mbr, because this machine is an efi
machine, and I am under the impression that efi wants gpt. I think
this is the right choice, though if I am wrong about that, I would be
interested in hearing the reasoning. But, in any event, it's probably
not the source of this issue.

How should I access the sets which are supposed to be on the install media here?

Thanks,

-- 
Raul

Re: Fsck_ffs seems to have trashed /usr/local

[Nicolai]

On Fri, Feb 11, 2022 at 10:09:25PM +0100, Konrad Sowula wrote:

> to keep things short, rebooting my vps using 'Server restart' in vultr
> control panel trashed my /usr/local directory

The VULTR "Restart Server" option explicitly says

 "Are you sure you want to restart your server?
  This is a hard restart."

So it's like pulling the power cable from a server.  It doesn't issue a
reboot command that safely shuts down the VM and then restarts.

> If anyone has at least a hint of what happened and could guide me
> towards a correct way of handling situations like these in the future 
> I would be much obliged.

Next time, run "reboot" from the command line if you want to reboot.

Like others said, fsck_ffs didn't cause the trouble, it just tried to
help you fix it.

If this was my server I would click "View Console" from the VULTR
dashboard.  If the machine is sitting at a fsck prompt, I would do what
it suggests.  Otherwise if the machine has booted and /usr/local isn't
mounted, then run fsck_ffs on its partition.

It's hard to tell what state your VM is in.  It may be necessary to
create a new VM and rsync your files to the new VM.

Nicolai

Re: dmesg - cpu, smt, core, package

[Mihai Popescu]

Doing a wrap up, how an Intel i5 family cpu is seen by OpenBSD?
The family has 4 cores / 4 threads per package.
If someone can check please, with dmesg and sysctl.

Thanks.

Re: dmesg - cpu, smt, core, package

[Bryan Steele]

pre-Ryzen AMD CPUs did not have SMT, but they had "CMT" or
"clustered multithreading" which is the shared-FPU stuff,
hw.smt=0 disables that too on these CPUs. I believe this
was intentional as this kind of resource sharing between
cores comes with inherent risk-- FPU state can contain
things like AES key data used by AESNI instructions, etc.

-Bryan.