@Peter, @Janne: Thanks for the infos. Newfs seemed promising but it
seems like the disk is beyond repair :(.
I did newfs -N and got quite a few location of superblocks:
Then I tried
fsck_ffs -b #blockid /dev/rsd1c
No matter which blockid i tried, it always gave the same BAD SUPER
BLOCK: MAGIC NUMBER WRONG.
I guess I would have to wipe it clean from here.
On Wed, Dec 1, 2021 at 2:06 PM Janne Johansson <icepic.dz@gmail.com> wrote:
>
> 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.
No comments:
Post a Comment