much ado for nothing... It seems when I yanked the data cable, it
wasn't the disk that got corrupted.
It was the UEFI loader on sdcard that had become corrupted. Not sure
when that had happened. This issue is documented
here (https://github.com/pftf/RPi4/issues/97). I had ended up
formatting the disk unnecessarily. Thanks a ton for pitching in
suggestions.
On Wed, Dec 1, 2021 at 7:30 PM Ian Darwin <ian@darwinsys.com> wrote:
>
> On Wed, Dec 01, 2021 at 01:39:39PM +0530, Sandeep Gupta wrote:
> > Hello,
> > All partitions except for /dev/rsd1c and /dev/rsd1i are clean.
> > For /dev/rsd1c , I get "BAD SUPER BLOCK: MAGIC NUMBER WRONG".
> > For /dev/rsd1i, I get "UNEXPECTED INCONSISTENCY".
>
> If that's the case, you are probably done! You could mount
> your 'a' partition manually on /mnt, look in /mnt/etc/fstab, and
> see which letter partitions belong where; use that info to make
> sure you have "found" all your partitions.
>
> BTW, in addition to scan_ffs in base, there is testdisk in ports,
> which I think does a better job ATM of finding FFS2 filesystems.
>
> As mentioned, DO NOT do anything with 'c' partition (be glad,
> be very glad, that it didn't find anything resembling a superblock
> when fsck'ing 'c'!). It's not a mountable partition but a 'wrapper'
> for the whole disk.
No comments:
Post a Comment