> On Aug 3, 2020, at 9:54 AM, sven falempin <sven.falem...@gmail.com> wrote:
>
> Hello
>
> I saw a similar issue in the mailing list around decembre 2019,
> following an electrical problem softraid doesn't bring devices ups
>
>
> # ls /dev/sd??
> /dev/sd0a /dev/sd0g /dev/sd0m /dev/sd1c /dev/sd1i /dev/sd1o /dev/sd2e
> /dev/sd2k
> /dev/sd0b /dev/sd0h /dev/sd0n /dev/sd1d /dev/sd1j /dev/sd1p /dev/sd2f
> /dev/sd2l
> /dev/sd0c /dev/sd0i /dev/sd0o /dev/sd1e /dev/sd1k /dev/sd2a /dev/sd2g
> /dev/sd2m
> /dev/sd0d /dev/sd0j /dev/sd0p /dev/sd1f /dev/sd1l /dev/sd2b /dev/sd2h
> /dev/sd2n
> /dev/sd0e /dev/sd0k /dev/sd1a /dev/sd1g /dev/sd1m /dev/sd2c /dev/sd2i
> /dev/sd2o
> /dev/sd0f /dev/sd0l /dev/sd1b /dev/sd1h /dev/sd1n /dev/sd2d /dev/sd2j
> /dev/sd2p
> # dmesg | grep 6.7
> OpenBSD 6.7 (RAMDISK_CD) #177: Thu May 7 11:19:02 MDT 2020
> # dmesg | grep sd
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
> sd0 at scsibus1 targ 0 lun 0: <ATA, QEMU HARDDISK, 2.1.>
> t10.ATA_QEMU_HARDDISK_Q
> M00005_
> sd0: 1907729MB, 512 bytes/sector, 3907029168 sectors, thin
> sd1 at scsibus1 targ 1 lun 0: <ATA, QEMU HARDDISK, 2.1.>
> t10.ATA_QEMU_HARDDISK_Q
> M00007_
> sd1: 1907729MB, 512 bytes/sector, 3907029168 sectors, thin
> wskbd0 at pckbd0: console keyboard, using wsdisplay1
> softraid0: trying to bring up sd2 degraded
> softraid0: sd2 was not shutdown properly
> softraid0: sd2 is offline, will not be brought online
> # bioctl -d sd2
> bioctl: Can't locate sd2 device via /dev/bio
> #
>
> I suspect a missing devices in /dev ( but it seems i have the required one )
> and MAKEDEV all of course did a `uid 0 on /: out of inodes`
>
> I have backups but i ' d like to fix the issue !
Hi Sven,
The device sd2 wasn’t attached by softraid, your /dev/bio is fine. This can
happen if softraid fails to find all component disks or the metadata on one or
more components does not match expectations (newer metadata seen on other
disks). Make sure all of the component disks are working. If that is not the
issue, you may need to re-run the command that you used to create the array and
include -C force. Be very careful doing this, I suggest running the command
once without -C force to ensure it found all the components and fails to bring
the array up due to the same error message you got (attempt to bring up
degraded).
If you’re not careful, you can blow out the whole array.
-Brian
>
> --
> --
> ---------------------------------------------------------------------------------------------------------------------
> Knowing is not enough; we must apply. Willing is not enough; we must do
