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

2021-03-08 Thread Samarul Meu
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

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

2021-03-08 Thread Marcus MERIGHI
Hello Samarul, samarul@gmail.com (Samarul Meu), 2021.03.08 (Mon) 10:46 (CET): > 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',

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

2021-03-08 Thread Samarul Meu
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 no idea why detaching the so

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

2021-01-29 Thread tetrahedra
On Thu, Jan 28, 2021 at 10:27:47AM +0200, 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 no idea why detaching the sof

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

2021-01-28 Thread Samarul Meu
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.

2021-01-27 Thread Samarul Meu
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.

2021-01-27 Thread Nick Holland
On 1/27/21 1:45 PM, Samarul Meu wrote: 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.

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

2021-01-27 Thread tetrahedra
On Wed, Jan 27, 2021 at 05:50:07PM +0200, Samarul Meu wrote: After searching online I discovered this: boot sr0a:/bsd. Now it asks for my Passphrase and it starts booting but then it hangs softraid0 at root scsibus2 at softraid0: 256 targets panic: root device (3312a...) not found Stopped at db

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

2021-01-27 Thread vejetaryenvampir
Samarul Meu wrote: > It showed only this: > > open(hd0a:/etc/boot.conf): Invalid argument > boot> > cannot open hd0a:/etc/random.seed: Invalid argument > booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > failed(22). will try /bsd > > After searching online I discovered this: boot sr0a:/bsd

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

2021-01-27 Thread Erling Westenvik
On Wed, Jan 27, 2021 at 05:50:07PM +0200, Samarul Meu wrote: > 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

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

2021-01-27 Thread Samarul Meu
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.

2021-01-27 Thread Ashton Fagg
Color me surprised...I can't say I've ever tried it to know. Still, rm is a little different to something that's talking directly to a device. On Wed, 27 Jan 2021 at 12:33, Daniel Jakots wrote: > > On Wed, 27 Jan 2021 11:31:13 -0500, Ashton Fagg > wrote: > > > Do you want "rm -rf /" to hold you

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

2021-01-27 Thread Daniel Jakots
On Wed, 27 Jan 2021 11:31:13 -0500, Ashton Fagg wrote: > Do you want "rm -rf /" to hold your hand also? As a matter of fact, it does :) https://github.com/openbsd/src/commit/c11d908c7069eb03d103482ce1d0227f3d47b349

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

2021-01-27 Thread Ashton Fagg
Pressed send too early. It is also worth pointing out that I'm fairly sure every *nix has similar ways to blow your arms and legs off. There's nothing special about OpenBSD or bioctl in that sense. On Wed, 27 Jan 2021 at 11:31, Ashton Fagg wrote: > > On Wed, 27 Jan 2021 at 10:55, Samarul Meu wr

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

2021-01-27 Thread Ashton Fagg
On Wed, 27 Jan 2021 at 10:55, Samarul Meu wrote: > > I am a little puzzled that there is no failsafe mechanism for commands like > bioctl or fdisk on the already mounted disk. For me the obvious think was > that the system complains when trying bioctl -d sd0. To be fair, bioctl talks to block I/O

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

2021-01-27 Thread Samarul Meu
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