Re: how to recover a corrupted disk

Den ons 1 dec. 2021 kl 09:12 skrev Sandeep Gupta <gupta.sandeep@gmail.com>:
> I am running OpenBSD 7.0 on RPi4. I accidentally removed the usb
> cable connecting the sata ssd to the RPi4.
> Well OpenBSD froze and upon reboot I got the very comforting
> Synchronous Exception message.
> Thankfully, I have another RPi4 running OpenBSD. I can mount the
> corrupted disk ( did the necessary backups). I did fsck on all the
> partitions.
> All partitions except for /dev/rsd1c and /dev/rsd1i are clean.
> For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG".

The "c" partition is not meant to hold filesystems, it is the device
used to talk to "the whole disk" for fdisk and such tools.

> For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY".

If you had any non-bsd filesystems (like a small MSDOS/FAT partition
for booting/firmware/arm blob stuff), it will end up as sdXi (and
j,k,l, and so on if you have more than one foreign fs), so if that is
the case, then it is not unexpected to see FFS' fsck have issues with
FAT filesystems.

--
May the most significant bit of your life be positive.

Re: libdmx removal incomplete?

On 2021/12/01 02:05, Alexander wrote:
> On 2021/11/30 8:14, Stuart Henderson wrote:
> > On 2021-11-29, Amit Kulkarni <amit.obsd@gmail.com> wrote:
> > > On Sun, Nov 28, 2021 at 5:17 PM Alexander <xan.abo@posteo.org> wrote:
> > >> Just to gauge what to expect from this and whether I did this wrong:
> > >> After configuring /etc/sysclean.ignore I get 3382 files of which 3274
> > >> are in /usr/X11R6/lib/X11/fonts/. Are numbers this large to be expected?
> > >
> > > 3382 files is too large.
> >
> > That seems about right for the removed font variants to me. You can't
> > judge by the number of files, only the filenames.
> >
> > *If* you don't compile your own software from outside ports/packages, the
> > files under /usr listed in sysclean's default output (no -a flag) is good.
> > I do review manually before rm'ing but I have *never* had it suggesT
> > removing something under /usr that is required. Files outside /usr
> > need more care.
> >
> This is probably a stupid question but how do you review them manually?
> I have a couple files that are manpages, that's easy. signify-keys, too.
> There is some sgi stuff, also easy, retirement is known.
> Same goes for switchd-related things.
> But what about the rest? Assuming you don't just know everything about
> those files already, do you find(1)/grep(1) through the source tree and
> commit messages or is there a different way?

I just scan through the filenames quickly and see if I think they're likely
to cause a problem. I'm doing that anyway for the files outside of /usr
and I read source-changes so I know what to expect.