Recovery from disk+fs crash

[Eric Anderson]

Robin Elfrink said:
> Eric Anderson wrote:
>
>>>root@:~# fsck /dev/da0s1f
>>>** /dev/da0s1f (NO WRITE)
>>>cannot alloc 18446744067446403432 bytes for inphead
>
>
>> Have you tried using fsck_ffs and specifying an alternate superblock?
>> (say 160)
>
> Yes:
>
> root@:~# fsck_ffs -b 160 /dev/da0s1f
> Alternate super block location: 160
> ** /dev/da0s1f (NO WRITE)
> cannot alloc 18446744067446403432 bytes for inphead
>
> Same error. Something is so badly wrong that fsck wants to allocate a
> very big amount of memory.
>
> I more or less have given up on the illusion of getting data back (that
> shows 'em, not letting me have a proper backup system), but still it's
> annoying not knowing what is going on and how to fix it.
>
>
> Robin
>


You could go in with fsdb and fix the parts manually, but it wouldn't be
simple.  You might also try a 'preen' first - not sure if that will do
anything different.  Also - this fs is not currently mounted at all,
right?


Eric


-- 
-------------------------------------------------------------
Eric Anderson    anderson at centtech.com    Centaur Technology
You have my continuous partial attention
-------------------------------------------------------------