Thank you for your input and sorry about the delay. I realize now that my question was poorly documented and promise that I will produce ddb report next time if the crash occurs.
Meanwhile, I have managed to safely remove the encrypted partition with $doas bioctl -d sdX. That was all what I was trying to achieve at this point. I believe FAQ https://www.openbsd.org/faq/faq14.html#softraid would benefit if such an explicit line about properly removing/destroying encypted/"ordinary"RAID is added to it. Many thanks, again On Fri, Dec 15, 2017 at 10:30 AM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2017-12-13, soko.tica <soko.t...@gmail.com> wrote: > > I have successfully built an encrypted bootable usb according to the > > instructions https://www.openbsd.org/faq/faq14.html#softraidFDE > > > > After booting successfully several times, the device went to ddb after I > > installed chrome without previously adding xfonts during the install. > > Subsuequent attempts to boot were unsuccessfull. > > > > I have erased partitions by disklabel and fdisk and tried to repeat the > > installation process. However, the encrypted raid device appeared and I > was > > able to unlock it by the same passphrase, so I ceased the installation. > > > > Is it possible to delete the crypto raid properly at this stage? Should I > > tri to rebuild it? > > > > Any advice is appreciated. > > > > Thanks in advance. > > > > You can use dd to write zeroes over the start of the device to overwrite > the partition table and disklabel, I'm not surehow far you have to go > but would expect "dd if=/dev/zero of=/dev/rsdXc bs=1m count=8" to do > the trick (with the correct disk number here ^ obviously). > > No idea why it would have gone to ddb, your report is very lacking in > information! > > >
