Just want to close the loop. I ended up finding a backup of my mbox on a different machine with the disklabel in the insecurity update (thanks for the tip, Nick). I installed it on the disk and had access to everything except root!
Out of curiosity, I generated a new disklabel for that same disk with disklabel -A and predictably, the offsets and sizes were all correct in that one too. Thank you all for your wisdom and reorienting my week around proper backups. Isaac > To be clear: having overwritten the starting 5GB of sd1c, > but not of the underlying sd0c, you still have the CRYPTO volume on > sd0c which you can attach with bioctl, right? If my ssd is sd0 and my bio(4) managed volume is sd1, then I dd'd over sd1 (all of sd1a, some of swap). On Wed, Sep 27, 2023 at 6:16 PM Stuart Henderson <stu.li...@spacehopper.org> wrote: > > On 2023-09-27, Isaac Meerleo <spritskills...@gmail.com> wrote: > > Thank you all for your replies. I needed to step away from my > > computer last night so I apologize for the terse email. > > sd0 is my physical hard disk with full disk encryption. I wrote a 5gb > > iso over the beginning of sd1c (my softraid volume). I rebooted. I > > installed openbsd on a separate drive, booted it, mounted the > > encrypted volume, and hopelessly ran scan_ffs. > > > > After reading Stuart's advice, I will attempt to reinstall the > > disklabel from scratch. I installed 7.2 on my second disk; the version > > I used to do the initial install. > > When I initially set up my disk, I used the auto partition defaults > > which left me with a 300gb /home directory. Later, I expanded the > > /home partition across the rest of the disk. When I recreate the > > disklabel, should I let it auto partition and then grow the file > > system like before? Or should I just set home to fill the rest of the > > disk? > > Set it to fill the rest of the disk - don't run growfs on it again. > > I would be wanting to mount filesystems read-only and try to copy data > off to another disk, then reinstall on the disk with damaged disklabel > and copy back, rather than relying on the existing filesystems long-term. > >
