I physically removed the SSD mSATA disk, and re-inserted it.
Then I started the install procedure again, and partitioned it, and disklabeled
it.
It is now working, wanting to install the sets.
So apparently, I had some type of hardware failure.
On Friday, February 26, 2021, 10:09:14 PM
Another 6.8 install failure.
What specifically does "disklabel: DIOCWDINFO: Device busy" mean at the end of
disklabel???
Does it mean I have hardware failure???
When I let OpenBSD 6.8 partition the disk and use the default disklabel, I get:
Available disks are: sd0 sd1.
Which disk is the root
This does not look normal to me:
PcEngines2# ls -Fla /
total 12564133706863018
drwxr-xr-x 11 root wheel 512 Oct 5 00:17 ./
drwxr-xr-x 11 root wheel 512 Oct 5 00:17 ../
-rw-r--r-- 1 root wheel 1480 Oct 5 00:17 .profile
lrwxr-xr-x 1 root wheel 11 Oct 5 00:17 autoinsb
drwxr-xr-x 2 root wheel 512
Thanks again. Here is the sha256 of bsd.rd:
106 King$ sha256sum bsd.rd
9fb54e358cbc716b86acff277af176d534a039257c81b802bdc74c93ca48adf3 bsd.rd
47 PcEngines1# sha256 bsd.rd
SHA256 (bsd.rd) =
9fb54e358cbc716b86acff277af176d534a039257c81b802bdc74c93ca48adf3
On Friday, February 26, 2021,
Thanks again Theo.
> WARNING: / was not properly unmounted
That is true for the disk in that system.
But I booted from the 6.8 bsd.rd via PXE.
On Friday, February 26, 2021, 09:21:21 PM EST, Theo de Raadt
wrote:
Kenneth Hendrickson wrote:
> Thanks Theo.
>
> Here is what
Thanks Theo.
Here is what happened beforehand:
Welcome to the OpenBSD/amd64 6.8 installation program.
WARNING: / was not properly unmounted
Starting non-interactive mode in 5 seconds...
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? i
At any prompt except password prompts you can escape to a
After making the filesystems, I get error messages:
sd0> p
OpenBSD area: 125033958-250067790; size: 125033832; free: 28
#size offset fstype [fsize bsize cpg]
a: 2104480133435904 4.2BSD 2048 16384 1 # /
b: 8401932125033958
Kenneth Hendrickson wrote:
> Thanks again Theo.
>
> > WARNING: / was not properly unmounted
>
> That is true for the disk in that system.
You don't understand the OpenBSD installed. That / is the root filesystem
of the install-tool fileysystem inside the bsd.rd
It is corrupt. Someone wrote
Kenneth Hendrickson wrote:
> Thanks Theo.
>
> Here is what happened beforehand:
>
> Welcome to the OpenBSD/amd64 6.8 installation program.
> WARNING: / was not properly unmounted
I have no idea what is going on here, but this never happens with
an OpenBSD install image. The mr.fs
Kenneth Hendrickson wrote:
...
> No label changes.
> newfs: /dev/rsd0a is mounted on /mnt
^^^
Well you had that partition mounted, probably with a different disklabel
and sizes, so it was not newfs'd.
You did something manual earlier. You didn't show that which created
the problem.
Hello,
symptoms like this:
chromium plays video with audio (youtube)
mostly after pause, it loses audio.
while this happen it could show spinner,
but sometimes it can play video no problem, but no audio.
dmesg:
OpenBSD 6.9-beta (GENERIC.MP) #346: Fri Feb 19 23:56:21 MST 2021
Hello everyone!
I've been trying to use kqueue for the last couple of day but I keep
having an issue with EVFILT_TIMER filter. (I'm running Openbsd
-current)
Right now, I'm trying to do the following:
1) Initilialize a timer event @ 200ms, periodically.
2) Inside the main event loop => If this
On 2021-02-26, Michael W. Lucas wrote:
> Hi,
>
> Should LibreSSL and OpenSSL be strictly command line compatible?
>
> The reason I ask is: using OpenSSL, I can use openssl s_client to
> connect to a site like so:
>
> $ openssl s_client -crlf www:443
>
> LibreSSL requires I add the -connect
>
> $
Hi,
Should LibreSSL and OpenSSL be strictly command line compatible?
The reason I ask is: using OpenSSL, I can use openssl s_client to
connect to a site like so:
$ openssl s_client -crlf www:443
LibreSSL requires I add the -connect
$ openssl s_client -crlf -connect www:443
Thanks,
==ml
--
On 2021-02-26, Daniel Jakots wrote:
> On Fri, 26 Feb 2021 11:53:40 +0100 (CET), Rachel Roch
> wrote:
>
>> Let's say I'm running "pkg_add -u" on a OpenBSD-based router with
>> multiple interfaces.
>>
>> What determines the source IP ?
>
> On -current there is
> route [-T rtable] sourceaddr
On Fri, Feb 26, 2021 at 3:58 AM Stuart Henderson
wrote:
> On 2021-02-26, Sven F. wrote:
> > On Thu, Feb 25, 2021 at 8:38 PM Steven Shockley
> > wrote:
> >>
> >> I can try it, but I don't think it'll help in my case:
>
> It's worth trying anyway I think.
>
> > Can the patch sys/net/pf.c r1.1096
Remco writes:
> I've never used this myself, so this is just an idea, Maybe setting up
> a routing domain and running pkg_add using route(8)'s "exec" command
> will do the job ?
Yup. route -T exec works well.
I use it for one my home servers that serves stuff out over a Wireguard
tunnel.
Hi
Let's say I'm running "pkg_add -u" on a OpenBSD-based router with multiple
interfaces.
What determines the source IP ?
Building on that, there is no "source interface" flag for pkg_add like there is
for ping and certain others. Is there a way for me to configure a default
interface for
On 26-02-2021 11:53, Rachel Roch wrote:
Hi
Let's say I'm running "pkg_add -u" on a OpenBSD-based router with multiple
interfaces.
What determines the source IP ?
Building on that, there is no "source interface" flag for pkg_add like there is
for ping and certain others. Is there a way for
On Fri, 26 Feb 2021 11:53:40 +0100 (CET), Rachel Roch
wrote:
> Let's say I'm running "pkg_add -u" on a OpenBSD-based router with
> multiple interfaces.
>
> What determines the source IP ?
On -current there is
route [-T rtable] sourceaddr [-inet|-inet6] [address]
route [-T rtable]
On Fri, Feb 26, 2021 at 11:53:40AM +0100, Rachel Roch wrote:
> Hi
>
> Let's say I'm running "pkg_add -u" on a OpenBSD-based router with
> multiple interfaces.
>
> What determines the source IP ?
I'd say the routing table.
> Building on that, there is no "source interface" flag for pkg_add
Hi,
pkg_add uses the $PKG_PATH environment variable to determine which source to
use for packages, eg:
wolf:fred ~: env |grep -i pkg
PKG_PATH=https://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/
The interface used will be determined by the boxes routing table, so to specify
an
I've bought few of these nics some months ago. I suspect OpenBSD re
driver needs some adjustments and I could send one of them to an
interested developer.
P.S. I'm getting watchdog timeouts in some hard to reproduce fashion.
And I'm way below the
capability to fix it myself and it seems that
On 2021-02-26, Sven F. wrote:
> On Thu, Feb 25, 2021 at 8:38 PM Steven Shockley
> wrote:
>>
>> I can try it, but I don't think it'll help in my case:
It's worth trying anyway I think.
> Can the patch sys/net/pf.c r1.1096 be applied on 6.8 ?
> or does it need some others files to be changed as
Hi!
Latest snapshot works. Thx.
OpenBSD 6.9-beta (GENERIC.MP) #360: Thu Feb 25 11:53:45 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
ifconfig veb0
veb0: flags=8802
index 8 llprio 3
groups: veb
Addresses (max cache: 100, timeout: 240):
On 26.2.2021. 9:00, csszep wrote:
> Hi!
>
> I miss something , or veb(4) ifconfig bits not yet commited ?
>
> OpenBSD 6.9-beta (GENERIC.MP) #358: Wed Feb 24 17:11:53 MST 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
>
> ifconfig veb0 create
> ifconfig:
Hi!
I miss something , or veb(4) ifconfig bits not yet commited ?
OpenBSD 6.9-beta (GENERIC.MP) #358: Wed Feb 24 17:11:53 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
ifconfig veb0 create
ifconfig: SIOCIFCREATE: Invalid argument
Hrvoje Popovski ezt
27 matches
Mail list logo
