Re: Clarification re: rebuilding softraid mirror

[IL Ka]

Hello,

No, you do not need to reboot. At least this is how it worked for me for
raid 1:

1) bioctl softraid0 said raid degraded
2) I installed new disk (sd2).
3) kenrel reported on console that disk is detected
4) I created MBR using fdisk on it
5) I created disklabel with RAID type on it
6) bioctl -R /dev/sd2a sd0

I suggest you to try it yourself, but not on production system)



On Fri, Apr 27, 2018 at 2:21 AM, Jordan Geoghegan 
wrote:

> Hello,
>
> Sorry for my ignorance, I was hoping someone could clarify for me the
> proper procedure for rebuilding a softraid mirror. The man page/faq says:
>
>
>> Rebuilding a mirror
>>
>> When a drive failure happens, you will replace the failed drive, create
>> the RAID and other disklabel partitions, then rebuild the mirror. Assuming
>> your RAID volume is sd2 and you are replacing the failed device with sd1m,
>> the following commands should work:
>>
>> #*bioctl -R /dev/sd1m sd2*
>> #*reboot*
>>
>> These steps can be performed in either single user mode <
>> https://www.openbsd.org/faq/faq8.html#LostPW> or from the install kernel
>> .
>>
> Does this mean that a RAID rebuild can *only* be performed from single
> user mode or install kernel, or is it possible to rebuild an array while
> the system is in full operation?
>
> To phrase my question a different way:
> Is it possible to hot swap drives and rebuild arrays on the fly, or will
> this bork my system?
>
> Thanks,
> Jordan Geoghegan
>
>

Clarification re: rebuilding softraid mirror

[Jordan Geoghegan]

Hello,

Sorry for my ignorance, I was hoping someone could clarify for me the 
proper procedure for rebuilding a softraid mirror. The man page/faq says:




Rebuilding a mirror

When a drive failure happens, you will replace the failed drive, 
create the RAID and other disklabel partitions, then rebuild the 
mirror. Assuming your RAID volume is sd2 and you are replacing the 
failed device with sd1m, the following commands should work:


#*bioctl -R /dev/sd1m sd2*
#*reboot*

These steps can be performed in either single user mode 
 or from the install 
kernel . 
Does this mean that a RAID rebuild can *only* be performed from single 
user mode or install kernel, or is it possible to rebuild an array while 
the system is in full operation?


To phrase my question a different way:
Is it possible to hot swap drives and rebuild arrays on the fly, or will 
this bork my system?


Thanks,
Jordan Geoghegan

Re: Virtualbox vs latest snapshot

[IL Ka]

Latest snapshot running on 5.2.8 @win7x64 (everything works and seems to be
stable)
Do you use GPT or MBR?
Is it SATA or PATA/IDE?

Can you boot your hda0:/bsd from cd?
Can you boot from CD, mount drive and fsck it?


xx:2$ dmesg
OpenBSD 6.3-current (GENERIC) #13: Thu Apr 26 07:46:22 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1056899072 (1007MB)
avail mem = 1017061376 (969MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries)
bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006
bios0: innotek GmbH VirtualBox
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.51 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,MWAIT,SSSE3,CX16,PCID,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,RDRAND,NXE,RDTSCP,LONG,LAHF,ITSC,FSGSBASE,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: CPU supports MTRRs but not enabled by BIOS
cpu0: apic clock running at 1000MHz
cpu0: mwait min=64, max=64
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
, remapped to apid 1
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpiac0 at acpi0: AC unit online
acpivideo0 at acpi0: GFX0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom removable
wd0 at pciide0 channel 0 drive 1: 
wd0: 128-sector PIO, LBA, 20480MB, 41943040 sectors
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
vga1 at pci0 dev 2 function 0 "InnoTek VirtualBox Graphics Adapter" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 1 int 19,
address 08:00:27:7d:19:91
"InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 not
configured
auich0 at pci0 dev 5 function 0 "Intel 82801AA AC97" rev 0x01: apic 1 int
21, ICH
ac97: codec id 0x83847600 (SigmaTel STAC9700)
audio0 at auich0
ohci0 at pci0 dev 6 function 0 "Apple Intrepid USB" rev 0x00: apic 1 int
22, version 1.0
piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: apic 1 int
23
iic0 at piixpm0
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Apple OHCI root hub" rev
1.00/1.00 addr 1
uhidev0 at uhub0 port 1 configuration 1 interface 0 "VirtualBox USB Tablet"
rev 1.10/1.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 5 buttons, Z and W dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (c157cae92dc08f0c.a) swap on wd0b dump on wd0b
xx:3$


> > Hi! I installed the latest 04.10 snapshot, the install procedure went
> fine, but after reboot the VM stucks at endless boot loop . It prints only
> the "booting hda0:/bsd" line.. before reboot The 04.03 snapshot works fine.
> There is a similar experience for someone with Virtualbox 5.2.8?
>

Re: Virtualbox vs latest snapshot

[Rupert Gallagher]

Try qemu.
Better software.
Better license.

Sent from ProtonMail Mobile

On Tue, Apr 10, 2018 at 10:50, csszep  wrote:

> Hi! I installed the latest 04.10 snapshot, the install procedure went fine, 
> but after reboot the VM stucks at endless boot loop . It prints only the 
> "booting hda0:/bsd" line.. before reboot The 04.03 snapshot works fine. There 
> is a similar experience for someone with Virtualbox 5.2.8?

Re: crash of OpenBSD 6.3 -stable (amd64 MP kernel) - unswapping kills connections

[Infoomatic]

Hi Stuart,

thanks for your input! Actually, I was never really satisfied with the 
stability of ntopng, so this problem of the memory leak does not really 
surprise me. However, when killing the process, which also means freeing swap 
space, I think it is not an expected behaviour that the system does not handle 
any tcp/ip or icmp connections any more until the swap space is fully freed 
(which, in my case when ntopng used 3 out of 4GB swap, lastet for nearly 20 
minutes). IMHO, unswapping a process should not influence network connectivity 
that much.

Regards,
infoomatic


> Gesendet: Donnerstag, 26. April 2018 um 16:10 Uhr
> Von: "Stuart Henderson" 
> An: misc@openbsd.org
> Betreff: Re: crash of OpenBSD 6.3 -stable (amd64 MP kernel) - unswapping 
> kills connections
>
> On 2018-04-26, Infoomatic  wrote:
> > Hi,
> >
> > Today I discovered some interesting details: I guess ntopng has a memory 
> > leak, thus eating all my 4GB RAM and some 3GB swap - this appeared in the 
> > morning, so after all the backups and heavy traffic occured.
> > When I fired up a rcctl stop ntopng the ssh connection stalled. The 
> > firewall could not handle further connections, and established connections 
> > dropped. The system could not answer to ping packets etc.
> > This now also happened on a 2nd machine. After 20 minutes (when I was in a 
> > taxi to the datacenter) I could login again and realized that ntopng was 
> > stopped and swap was freed.
> >
> > I have now disabled ntopng. I kindly ask the devs to take a look at this! 
> > If you need a testsetup for this or if I can do anything, just contact me.
> 
> First off, it's not a big surprise to have a hanging machine if you
> run it out of memory.
> 
> ntopng is not really stable. There is a newer version upstream but it
> crashes very often with certain packet types suggesting bugs in the packet
> parsers.
> 
> If you run ntopng at all, I would recommend you only run it while you
> need to investigate traffic, not leave it running unattended permanently.
> 
> It might also be a good idea to set login.conf limits for it, if you
> start it via the rc.d script you can add an "ntopng" class with say
> datasize=2500M.
> 
> 
> 

Re: ACPI interrupt storm on ThinkPad T480s

[Matthieu Guegan]

Hi,

Just want to add the X1 Carbon Gen 6th to the list. Same problem when 
plug in a thunderbolt device.


Apart from that, the other thing is that S3 (suspend to ram) mode is not 
supported by the BIOS (it has a special S0i3 mode instead which is 
exclusive with the S3 mode).

Re: Return back dhclient lease time displaying after renew an IP address manually

[Daniel Melameth]

On Thu, Apr 26, 2018 at 2:11 PM, Denis  wrote:
> After upgrading 6.2amd64 -> 6.3amd64 there is no lease time info present
> by renewing an IP address using '#sh /etc/netstart if0' command.
>
> Manually run dhclinent shows MAC address of a dhcpd server (very useful)
> but lease time has been deprecated since 6.2 (very useful for different
> dhcp servers lease time determining). Hope this helpful information will
> be returned back in additional to dhcpd server's MAC added in 6.3.

cat /var/db/dhclient.leases.?

Return back dhclient lease time displaying after renew an IP address manually

[Denis]

After upgrading 6.2amd64 -> 6.3amd64 there is no lease time info present
by renewing an IP address using '#sh /etc/netstart if0' command.

Manually run dhclinent shows MAC address of a dhcpd server (very useful)
but lease time has been deprecated since 6.2 (very useful for different
dhcp servers lease time determining). Hope this helpful information will
be returned back in additional to dhcpd server's MAC added in 6.3.

Denis

Re: Plans to port the amdgpu(4) driver? (=to support Radeons made 2014/2015 and after.) Hardware/other donations needed?

[bijan]

On 04/25/18 17:34, mazocomp wrote:

On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:

drivers/gpu/drm/amd in linux has over 1.5 million lines of code.  Which
is multiple times larger than the complete OpenBSD kernel source...


Wow, this driver is fatter than elephant.

Anyway, thank you for updating radeondrm(4), now I can
use my PC with Kaveri APU.


Updating to the latest snapshot and the same (good) results.
the HDMI/VGA outputs are detected and changing the brightness is
working on my Lenovo G50-45 (AMD A8-6410 with AMD Radeon R5
Graphics[1]). Thank you :-)

[1]: http://dmesgd.nycbug.org/index.cgi?do=view=3586

state-policy floating Expectations

[Daniel Melameth]

The man page defines this as "States can match packets on any
interfaces."  I understood this to mean that state created on one
interface would automatically create state, or allow a related match,
on another interface, but this is not the case.  Simple example:

Host A
10.0.0.2

Firewall
10.0.0.1 (hvn0)
10.0.1.1

Host B
10.0.1.2

/etc/pf.conf from the firewall:
block log
pass in on hvn0


With the above, traffic cannot pass from A to B.  With pf disabled on
the firewall, traffic passes.

I expected state to be created from the incoming packet, and a state
entry is, but the state is never complete/established (left as
CLOSED:SYN_SENT) and this does not work, obviously.  So, what's the
expanded definition of floating?  And how does this compare to
if-bound in the example above if it was applied to the pass rule?
I've found related threads from the past, but I'm still confused and
would appreciate a clue stick.

Thanks.

Re: Virtualbox vs latest snapshot

[Adam Thompson]

On 2018-04-12 20:02, Nick Holland wrote:

On 04/12/18 09:47, Consus wrote:

On 08:28 Thu 12 Apr, Nick Holland wrote:

Another "failure mode" of VirtualBox people should be aware of:
I understand through good sources, Oracle monitors the IP addresses 
that
it's downloaded from, and if they can trace it back to a commercial 
IP
(i.e., not a home address), and if they see you download (or update) 
the

"not for unrestricted free use" parts, their lawyers will contact you
and send you a bill...and they really don't care about "for work" or
"not for work related" uses.

I'd really recommend removing this product from your computers.


This won't stand in court. You sources are so high on crack it's not
even funny.


Think about it a moment,
Using my real name, and a public, trackable identity, I just accused a
very big company with lots of lawyers (and they know how to use them!)
of something.  If my facts are not in order, I could be in big trouble.
My facts are in order.

It's not about court.  It's about threatening lots of companies and
hoping a few pay up to avoid the cost of going to court -- which is
considerable, win or lose.

What you believe changes nothing.  Their licenses are complicated, easy
to use wrong, and they seem to care.  I recommend against using their
products for that reason.

Nick.



My tale of Oracle woe:

My company got spanked by Oracle a couple of years ago because one of 
our developers was downloading multiple versions of the RDBMS, trying to 
find a version that would be happy with a binary database file we got 
from a client.
Their License Enforcement dept. (it's part of the Sales division, which 
tells you something...) undertook a sneaky campaign of phoning all our 
staff asking them how they were satisfied with their Oracle products.
They finally audited us, and - not for the products that dev was 
downloading, but for something else entirely - it turned out we were 
accidentally in violation of one of our licenses, as one sentence had 
changed somewhere in the ~20yrs we'd been using it to invalidate our use 
case.
Since it was not intentional, and we were cooperating with them, and we 
are very small (~10 persons, at the time) they ONLY required a top-up 
payment roughly equal to 1 developer's annual salary.
The threat of being sued out of existence, if we didn't cooperate, was 
made explicitly.  We were, in my opinion, deliberately maneuvered into a 
non-compliant position over a period of many years, then subject to a 
"sting" operation, and finally bullied into compliance.


And we also use VirtualBox :-(.  For now.

It's notable that at least in Canada, BSA (MS,Adobe,Sybase,etc.,etc.) 
audits are legal - and are often accompanied by provincial Sheriffs.  
(Not the same thing as a U.S Sheriff, but still a law enforcement 
officer.)  The threat of legal action is NOT just an empty threat.


-Adam

Re: crash of OpenBSD 6.3 -stable (amd64 MP kernel) - unswapping kills connections

[Stuart Henderson]

On 2018-04-26, Infoomatic  wrote:
> Hi,
>
> Today I discovered some interesting details: I guess ntopng has a memory 
> leak, thus eating all my 4GB RAM and some 3GB swap - this appeared in the 
> morning, so after all the backups and heavy traffic occured.
> When I fired up a rcctl stop ntopng the ssh connection stalled. The firewall 
> could not handle further connections, and established connections dropped. 
> The system could not answer to ping packets etc.
> This now also happened on a 2nd machine. After 20 minutes (when I was in a 
> taxi to the datacenter) I could login again and realized that ntopng was 
> stopped and swap was freed.
>
> I have now disabled ntopng. I kindly ask the devs to take a look at this! If 
> you need a testsetup for this or if I can do anything, just contact me.

First off, it's not a big surprise to have a hanging machine if you
run it out of memory.

ntopng is not really stable. There is a newer version upstream but it
crashes very often with certain packet types suggesting bugs in the packet
parsers.

If you run ntopng at all, I would recommend you only run it while you
need to investigate traffic, not leave it running unattended permanently.

It might also be a good idea to set login.conf limits for it, if you
start it via the rc.d script you can add an "ntopng" class with say
datasize=2500M.

Re: crash of OpenBSD 6.3 -stable (amd64 MP kernel) - unswapping kills connections

[Infoomatic]

Hi,

Today I discovered some interesting details: I guess ntopng has a memory leak, 
thus eating all my 4GB RAM and some 3GB swap - this appeared in the morning, so 
after all the backups and heavy traffic occured.
When I fired up a rcctl stop ntopng the ssh connection stalled. The firewall 
could not handle further connections, and established connections dropped. The 
system could not answer to ping packets etc.
This now also happened on a 2nd machine. After 20 minutes (when I was in a taxi 
to the datacenter) I could login again and realized that ntopng was stopped and 
swap was freed.

I have now disabled ntopng. I kindly ask the devs to take a look at this! If 
you need a testsetup for this or if I can do anything, just contact me.

Regards,
infoomatic



> Gesendet: Mittwoch, 25. April 2018 um 15:25 Uhr
> Von: Infoomatic 
> An: misc@openbsd.org, b...@openbsd.org
> Betreff: crash of OpenBSD 6.3 -stable (amd64 MP kernel)
>
> Hi folks,
> 
> Unfortunately this is not a complete bugreport since I could not retrieve 
> relevant information, however [1] is the dmesg.
> I upgraded to the new OpenBSD 6.3 version on monday, however, today it 
> crashed - better: it hung completely. I could not reach it any more via ssh, 
> a ping needed 15 seconds instead of 19ms, and only some packets arrived at 
> the host - but the network was normal.
> The machine runs the standard services from the default install plus httpd 
> and relayd, and also third party software: OpenVPN, scanlogd and ntopng.
> 
> In the sysctl.conf I have set ddb.panic=0.
> 
> When I was physically standing in front of the machine I was expecting to see 
> some messages on the screen, or even ddb, so to get some info for the devs, 
> but this was not the case.
> I plugged in a PS/2 keyboard with an USB-adapter and promptly got on my 
> screen (without the "date hostname" - took this from the log):
> Apr 25 13:28:21 dorie /bsd: uhub0: device problem, disabling port 1
> 
> I tried another USB port and got:
> Apr 25 13:29:34 dorie /bsd: uhub0: device problem, disabling port 10
> 
> The keyboard was not working on the machine, so I grabbed another one. I 
> plugged it in and suddenly the monitor was filled up with messages which kept 
> flooding and did not stop:
> scsi_xfer pool exhausted!
> 
> I then had to reset the machine. 
> 
> I also found suspicious messages in the log at about the time when the 
> machine got irresponsive:
> Apr 25 11:23:00 dorie relayd[31883]: rsae_send_imsg: poll timeout
> Apr 25 11:23:00 dorie relayd[96425]: rsae_send_imsg: poll timeout
> Apr 25 11:23:11 dorie relayd[39081]: rsae_send_imsg: poll timeout
> Apr 25 11:23:16 dorie relayd[96425]: rsae_send_imsg: poll timeout
> Apr 25 11:23:28 dorie relayd[96425]: relay: proc_dispatch: relay 1 got 
> invalid imsg 59 peerid -1 from ca 1
> Apr 25 11:23:34 dorie relayd[31883]: rsae_send_imsg: poll timeout
> Apr 25 11:23:42 dorie relayd[31883]: relay: pipe closed
> Apr 25 11:23:43 dorie relayd[39081]: rsae_send_imsg: imsg_flush: Broken pipe
> Apr 25 11:23:44 dorie relayd[39081]: relay: pipe closed
> 
> Maybe some devs have an idea where to look for a bug. Any tipps how to deal 
> with this matter in the future?
> 
> TIA and regards,
> infoomatic
> 
> 
> [1] 
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 4238319616 (4041MB)
> avail mem = 4102795264 (3912MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xebb80 (74 entries)
> bios0: vendor American Megatrends Inc. version "0801" date 08/20/2014
> bios0: Thomas-Krenn.AG P9D-MV(X) Series
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT SSDT SSDT SSDT SSDT MCFG HPET SSDT SSDT 
> BERT DMAR EINJ ERST HEST
> acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) 
> PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S4) EHC2(S4) 
> XHC_(S4) HDEF(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Xeon(R) CPU E3-1230L v3 @ 1.80GHz, 2594.38 MHz
> 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,SENSOR,ARAT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> acpitimer0: recalibrated TSC frequency 1795841682 Hz
> 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.2.4, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: 

Re: RAID 1 degraded since 6.3 updated

[Mimoza]

Le 26/04/2018 à 14:13, Stuart Henderson a écrit :

I don't know if is important but the faulty HDD have some bad sector.


Oh, if you have bad sectors showing up then you should definitely replace
it and not use it.



You are right … i'll looking for a new HDD.

Re: RAID 1 degraded since 6.3 updated

[Stuart Henderson]

On 2018-04-26, MImoza  wrote:
>
> Hi Stuart,
> Thanks for your help.
>
> Well i downloaded the 6.2 kernel here :
> https://mirrors.ircam.fr/pub/OpenBSD/6.2/i386/
>
> renamed it as bsd_62, copy in / and boot with the following commande :
> > boot bsd_62
>
> And nothing change …
>
> softraid0 at root
> scsibus4 at softraid0: 256 targets
> sd4 at scsibus4 targ 1 lun 0:  SCSI2 0/direct fixed
> sd4: 30098MB, 512 bytes/sector, 61640890 sectors
> softraid0: trying to bring up sd5 degraded
> sd5 at scsibus4 targ 2 lun 0:  SCSI2 0/direct fixed
> sd5: 1907728MB, 512 bytes/sector, 3907028640 sectors

So it doesn't seem like anything introduced in 6.3 then.

> When i try a rebuilding :
>
>   $ bioctl -R /dev/sd2a sd5
> softraid0: rebuild of sd5 started on sd2a
>   $ bioctl sd5
> Volume  Status   Size Device
> softraid0 1 Degraded2000398663680 sd5 RAID1
>0 Offline 2000398663680 1:0.0   noencl 
>1 Online  2000398663680 1:1.0   noencl 
>
>
> I have try with MP kernel too, but with the same result.
> I don't know if is important but the faulty HDD have some bad sector.

Oh, if you have bad sectors showing up then you should definitely replace
it and not use it.

Re: RAID 1 degraded since 6.3 updated

[MImoza]

Le 26/04/2018 à 09:40, Stuart Henderson a écrit :

On 2018-04-25, MImoza  wrote:

I have swapped out hardware (cable, HDD, port), re-created the RAID from
scratch, but at each time the Thosiba HDD is offline at reboot.
I don't think it's hardware incompatibility because with 6.2 everything
was Ok.
I think it's software, because the rebuilding doesn't work at all
without any warning or error.


What happens if you boot a 6.2 kernel? (Just copy it to / and select
it at the boot loader).




Hi Stuart,
Thanks for your help.

Well i downloaded the 6.2 kernel here :
https://mirrors.ircam.fr/pub/OpenBSD/6.2/i386/

renamed it as bsd_62, copy in / and boot with the following commande :
> boot bsd_62

And nothing change …

softraid0 at root
scsibus4 at softraid0: 256 targets
sd4 at scsibus4 targ 1 lun 0:  SCSI2 0/direct fixed
sd4: 30098MB, 512 bytes/sector, 61640890 sectors
softraid0: trying to bring up sd5 degraded
sd5 at scsibus4 targ 2 lun 0:  SCSI2 0/direct fixed
sd5: 1907728MB, 512 bytes/sector, 3907028640 sectors


When i try a rebuilding :

 $ bioctl -R /dev/sd2a sd5
softraid0: rebuild of sd5 started on sd2a
 $ bioctl sd5
Volume  Status   Size Device
softraid0 1 Degraded2000398663680 sd5 RAID1
  0 Offline 2000398663680 1:0.0   noencl 
  1 Online  2000398663680 1:1.0   noencl 


I have try with MP kernel too, but with the same result.
I don't know if is important but the faulty HDD have some bad sector.

Re: NFS keeps crashing

[Rupert Gallagher]

The following patch from Microsoft seems to restore functionality. Will see in 
the following hours. The denial of service remains as a problem on mountd. Will 
get a spare pc asap and check ktrace.

https://support.microsoft.com/en-us/help/4088776/windows-10-update-kb4088776

Re: RAID 1 degraded since 6.3 updated

[Stuart Henderson]

On 2018-04-25, MImoza  wrote:
> I have swapped out hardware (cable, HDD, port), re-created the RAID from 
> scratch, but at each time the Thosiba HDD is offline at reboot.
> I don't think it's hardware incompatibility because with 6.2 everything 
> was Ok.
> I think it's software, because the rebuilding doesn't work at all 
> without any warning or error.

What happens if you boot a 6.2 kernel? (Just copy it to / and select
it at the boot loader).

Re: Plans to port the amdgpu(4) driver? (=to support Radeons made 2014/2015 and after.) Hardware/other donations needed?

[Jonathan Gray]

On Wed, Apr 25, 2018 at 10:49:53AM -0400, Joe Gidi wrote:
> 
> > On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:
> >> drivers/gpu/drm/amd in linux has over 1.5 million lines of code.  Which
> >> is multiple times larger than the complete OpenBSD kernel source...
> 
> Thanks for this update!
> 
> Just to clarify, before I spend a bunch of money on new hardware, should I
> be able to use a Radeon R7 250 to drive a 4k monitor via DisplayPort with
> this updated driver?
> 
> Thanks again,

It appears that 'R7 250' can mean either a cape verde or oland radeon
depending on the model.  Both are GCN parts.

4k 30Hz should be possible with HDMI, 4k 60Hz on HDMI requires HDMI 2.0
Both claim support for displayport 1.2 which should be able to do
4k 60Hz.  HDMI 2.0 seems to only be on later hardware with DCE >= 11
carrizo (not carrizo-l which is mullins), polaris etc.

With the low end radeons displayport is sometimes only available on
oem models of cards sold as options for systems marketed as business
desktops or workstations.

And as mentioned earlier for acceleration you'll currently have to build
a different version of Mesa than what OpenBSD releases/snapshots ship
with.

Re: Wake-on-LAN from suspended state

[Paul de Weerd]

Hi Erling,

On Thu, Apr 26, 2018 at 12:31:27AM +0200, Erling Westenvik wrote:
| In this context, em(4) refers to the OpenBSD driver (man em), not the
| actual physical device. Many em-devices support WoL at BIOS-level and
| machines with such setup will cold boot successfully. Resuming from
| suspend/hibernate is an altogheter different affair. It works partly on
| an em-machine I have. At least for the first zzz/arp cycle.

Hmm?  So you're saying you *can* resume a suspended machine through
WoL to its em(4) interface?

| I'm wondering: are there any OpenBSD drivers that support WoL at all? 

re(4) has this bit:

> The re driver additionally supports Wake on LAN (WoL).  See arp(8)
> and ifconfig(8) for more details.

Maybe other NIC drivers support it too, I didn't check them all.  Just
remembered that Stefan Sperling (stsp@) added it there a looong long
time ago.  Just checked: 7 years ago!

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/share/man/man4/re.4?rev=1.45=text/x-cvsweb-markup

Cheers,

Paul 'WEiRD' de Weerd

-- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+
+++>-]<.>++[<>-]<+.--.[-]
 http://www.weirdnet.nl/ 

Re: Wake-on-LAN from suspended state

[Paul de Weerd]

Hi George,

On Wed, Apr 25, 2018 at 05:33:15PM +0100, geo...@t-t-l.co.uk wrote:
| I see the same apparent lack of support but I've been using wol happily with
| em on both 6.2 and 6.3 i386 ...  I use it to wake up a box shutdown with
| "halt -p".

Yes, as I mentioned in my original mail, that works fine for me too:
when the machine is powered off (as in your case with `halt -p`), I
can wake up the machine just fine with WoL.

| I don't remember doing anything clever and I can't see anything related in
| any config files.

My challenge is waking the machine with WoL after suspending it
through `zzz`.  To that end, as has been pointed out by a few people
on the list, you'd have to put 'wol' in the relevant hostname.if(5)
file (see the ifconfig manpage for details).  But, since the driver
for Intel gigabit network cards (em(4)) doesn't support this option,
it doesn't work.

Cheers,

Paul 'WEiRD' de Weerd

-- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+
+++>-]<.>++[<>-]<+.--.[-]
 http://www.weirdnet.nl/