Managed to mess up the system encrypted disk. I can no longer boot.

Hello! Please help. I really messed up. I was playing with some script trying to create an encrypted image and accidentally I did bioctl -d sd0 where sd0 is the disk with my OpenBSD install. Of course the system hanged. When I tried to reboot it no longer ask me for my passphrase. It showed only

Re: Managed to mess up the system encrypted disk. I can no longer boot.

mie., 27 ian. 2021, 20:24 a scris: > > Ironically this is the same error I have been getting, and recently > posted about in the thread "Bootloader on USB stick fails with "root > device not found"" ... > I read your thread just now. I will try the -a option. Interesting, but I must mention tha

Re: Managed to mess up the system encrypted disk. I can no longer boot.

On Thu, Jan 28, 2021 at 4:38 AM Nick Holland wrote: > -a at the boot prompt is my thought, too...but the little bit of your > dmesg that you show seems to indicate you are not seeing the encrypted > drive handled by in softraid at all. So I have my concerns this won't > do much but delay the pani

Re: Managed to mess up the system encrypted disk. I can no longer boot.

On Wed, Jan 27, 2021 at 11:12 PM vejetaryenvampir wrote: > I think I was having the same problem when I changed the passphrase > of my disk. I managed to fix it with installboot(8). You can > access the bug report in here: > https://marc.info/?l=openbsd-bugs&m=161075212820257&w=2 > I had the pan

Re: Managed to mess up the system encrypted disk. I can no longer boot.

On Thu, Jan 28, 2021 at 10:27 AM Samarul Meu wrote: > > Thank you so much! You made my day! > So I used FuguIta (6.8 - stable) attached the encrypted partition > (accessible as sd1 now) and 'installboot sd1', reboot and surprise - > everything is working. I still have

Re: Managed to mess up the system encrypted disk. I can no longer boot.

lun., 8 mar. 2021, 15:06 Marcus MERIGHI a scris: > Hello Samarul, > > > > Today I stumbled again on the same error, but in a different situation, > > let's say. > [...] > > 1. attach an encrypted disk (partition) with an OpenBSD installation on > > it, let's say sd1a --- "bioctl -c C -l sd1a sof

Errors after upgrading packages in 6.9

Hello to you all! As I switch to OpenBSD recently this is my first upgrade experience. I upgraded from stable to stable and the system upgrade was a very smooth experience (nothing to be scared of as I expected). My `/etc/installurl` has only one line `https://cdn.openbsd.org/pub/OpenBSD`

Dhcp client configuration in 7.0

Hello to you all! Prior to 7.0 I was using this line in /etc/dhclient.conf supersede domain-name-servers 127.0.0.1; so that I do not get the DNS from the ISP provider. I am using unbound to resolve my queries. With the new changes I can not get the same functionality. I tried to add this in /etc

Re: Dhcp client configuration in 7.0

On Fri, Oct 29, 2021 at 8:30 PM Zé Loff wrote: > This works for me: > > > /etc/hostname.em0: > > inet autoconf > > > /etc/resolv.conf: > > nameserver 127.0.0.1 > > > /etc/dhcpleased.conf: > > interface em0 { > ignore dns > } > > My dhcpleased.conf is similar (interface urt

Re: Dhcp client configuration in 7.0

sâm., 30 oct. 2021, 03:10 Zé Loff a scris: > On Fri, Oct 29, 2021 at 09:57:26PM +0300, Samarul Meu wrote: > > On Fri, Oct 29, 2021 at 8:30 PM Zé Loff wrote: > > > > > This works for me: > > > > > > > > > /etc/hostname.em0: > > >

Re: Dhcp client configuration in 7.0

d help to debug > this with the following: > > * run "route -n monitor" > * empty the dhcpleased.conf: mv /etc/dhcpleased.conf /etc/X.dhcpleased.conf > * cat /etc/resolv.conf, copy the output into an email. > * restart dhcpleased: doas /etc/rc.d/dhcpleased restart > * co

Re: dd: /dev/rsd1c: device not configured

mar., 30 nov. 2021, 15:39 Luca Ferrari a scris: > Hi, > I'm trying to install 7.0 in a virtual box machine using full disk > encryption, following > . I've done it on > real hardware without a problem, but I'm not understanding the error > in the v

Wrong opacity in picom

I am trying to customize my cwm using picom for some tweakings. The problem is when I try to setup opacity for active and inactive windows. This is my relevant config section: inactive-opacity = .5; inactive-opacity-override = false; active-opacity = .9; inactive-dim = 0.0; I am using Xterm, but

Re: Wrong opacity in picom

dum., 26 dec. 2021, 03:05 Erling Westenvik a scris: > On Sat, Dec 25, 2021 at 08:32:28PM +0200, Samarul Meu wrote: > > I am trying to customize my cwm using picom for some tweakings. > > The problem is when I try to setup opacity for active and inactive > windows. > >

Can't generate tags using universal-ctags

I have a bunch of markdown files in which I have tags defined using "#", something like #tagone #tagsomething. In $HOME/.ctags.d/md.ctags I have this --langdef=markdowntags --languages=markdowntags --langmap=markdowntags:.md --kinddef-markdowntags=t,tag,tags --mline-regex-markdowntags=/(^|[[:spac