Thank you for the quick reply, Otto. I overlooked that option, which is
kind of funny, I know it's saved my butt before. Anyway, I tried using
alternate superblocks, several of them (picked at random from various spots
within the ones named by newfs -N), and fsck is still dying with the same
On Mon, Feb 10, 2014 at 2:38 PM, Damon Getsman damo.g...@gmail.com wrote:
I have been able to mount the filesystem read-only. I'm not sure what else
to do at this point. I feel like I'm overlooking something really obvious
and foolish, but I can't quite put my finger on it. Anybody have any
I have an OpenBSD Virtual Machine (v.5.4) that, unfortunately, got shut
down improperly the other day. This machine had a mounted partition
/dev/rwd0j, which disklabel is reporting as a fstype of 4.2BSD (fsize 2048,
bsize 16384, cgp 1). The partition is completely full with an encrypted
On Sun, Feb 09, 2014 at 11:14:08PM -0600, Damon Getsman wrote:
I have an OpenBSD Virtual Machine (v.5.4) that, unfortunately, got shut
down improperly the other day. This machine had a mounted partition
/dev/rwd0j, which disklabel is reporting as a fstype of 4.2BSD (fsize 2048,
bsize 16384,
4 matches
Mail list logo
