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 panic (the kernel's panic. Too late for your > panic, I'm sure). >
I tried booting using -a or -s, but I have no luck. When I use -a it gets to the moment where it asks for the root device but the keyboard is dead, I can't do anything. And when using -s it just hangs with the previous panic message. > > If this doesn't work for you, I'd start by booting off a bsd.rd (USB, > CDROM, network, whatever) and looking around a bit. What does the > fdisk of your physical drive look like? Is your OpenBSD partition > still there? If not, recreate it (hopefully you either used the > defaults or remember what you did). All that really matters is the > starting sector (probably 64 assuming MBR. UEFI is 1024, iirc, but > I'm too lazy to look this up right now. Dammit, no I'm not, yes, > probably 1024, but I'm DEFINITELY not looking to see if that's a > hard number or if there are things that cause it to move around). > > After the fdisk partitions, look at the disklabel in on the physical > drive -- should be one big RAID partition as 'a' and type RAID. > > I looked at the softraid partition and everything seems fine. As I mentioned I see it as a 'a' RAID partition. Then I do a bioctl on it and I can access it and see al the other partitions 'a-j' . I did an fsck -p on all of them and I get no errors. I even mount them to see if everything is ok and I managed to get the work done in '/home', but that is all. When I reboot nothing works. > I am kinda suspicious that the bioctl command you gave was not the > culprit in this situation, but something else in your script. > > Actually in the moment I was not running the script. I was doing some tests and I could no longer access the sd1 which was used by a previous bioctl attempt. So i tried to do a 'bioctl -d', but by mistake instead of sd1 I did it on sd0. All froze and I had to do a hard reset. > As for safeguards...Well, from personal experience recently, I can > *assure* you I understand the first response when something goes > horribly wrong and your finger is the one on the (virtual) trigger > is, "Why wasn't there a safeguard??". I get that, and I bet mine > was a bigger oops than yours. But realistically, there are an > almost unlimited number of ways to hurt yourself, and a much smaller > number of ways to do things right, and often what to person A is > a horrible mistake, person B needs as a way to solve a big problem. > I have often needed to use an OS like OpenBSD to clean up messes in > other OSs because the safeguards in the other OS prevented me from > doing what I needed to do. So yes, I understand, but no, I don't > want a "are you sure?" on every step of everything that could cause > an "event". > > I understand the point and maybe it is ok this way. Actually that is why I am creating this scripts --- to check before doing anything that I am not trying to modify the 'root' disk. > And think how much you just learned about the value of good backups... > > I learned this lesson a long time ago, on my beginner Linux years. Now, is just a reminder. Thank for your answer and help and I appreciate any further hints. > Nick. >
