When i last installed OpenBSD on a mirror raid, i failed because i had
not created the special file for the new softraid(4) device.  A short
notice would have saved me from some headaches.  So i wrote this patch.

I know there's already a paragraph, at the beginning of that section, on
manually creating /dev entries (which i did).  But, depending on how
many disks are attached on the machine, the device file used for the
softraid device may have not be included among those you have manually
created.

In my case, i created sd0, sd1, and sd2.  The first two were the chunks
for the softraid, and sd2 was (or so i thought) for the softraid itself.
But sd2 was actually an extra disk i forgot about; and there was also
the installation media as sd3; making sd4 the softraid device.  At the
time of zeroing its MBR, the device was not configured, which made dd(1)
fail; and the MAKEDEV command was past the console screen for me to
figure out i had not created it.  It took me almost an hour to figure
this out.

-- 
Lucas de Sena

diff /usr/share/doc/www
path + /usr/share/doc/www
commit - cc2b58cd232efe0f10a698cf8a92796f9690d4b2
blob - cacdc0ceff609c0264bf5e8695023d705bd8d414
file + faq/faq14.html
--- faq/faq14.html
+++ faq/faq14.html
@@ -615,7 +615,9 @@ a master boot record and disklabel, zeroing the first 
 highly recommended.
 Be <b>very careful</b> with this command; issuing it on the wrong device
 could lead to a very bad day.
-This assumes that the new softraid device was created as <code>sd2</code>.
+This assumes that the new softraid device was created as <code>sd2</code>,
+and the special file for <code>sd2</code> have been created by
+<a href="https://man.openbsd.org/MAKEDEV">MAKEDEV(8)</a>.
 
 <pre class="cmdbox">
 # <b>dd if=/dev/zero of=/dev/rsd2c bs=1m count=1</b>