Discovering File System Corruption
ceri at submonkey.net
Wed Jan 11 06:22:45 PST 2006
On 10 Jan 2006, at 14:26, Bret Walker wrote:
> I have a 6.0-RELEASE-p1 box with a GENERIC kerbnel that I'm having
> trouble with.
> I recently reconstituted the machine from being a 5.4 box. I didn't
> upgrade, I reinstalled.
> When I was trying to install tripwire, kept getting this message:
> "./bin/i386-unknown-freebsd_r/siggen missing. Build did not complete
> *** Error code 1"
> I CVSupped a few times, even deleting the tripwire directory
> and letting CVSup re-add it. I finally fixed the problem by copying
> missing file from another box.
> The maintainer of the the port wrote to me:
> " The missing files were missing from the distfile extraction, not
> the port.
> The distfile failed to extract properly. That indicates that either
> failed (unlikely) or that you have some kind of filesystem problem.
> have a problem much more serious than a mere port that failed to
> I have run fsck in single user mode many times, each time coming
> back clean.
> I ran fsck -f -p, to make sure I wasn't having any problems like
> this (
> msg04802.html ).
> How can I determine what is going on? Do I have filesystem corruption,
> or is something else going on?
Try to extract the distfile that you downloaded and see if it is
corrupted or incomplete.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20060111/81cc75c5/PGP.bin
More information about the freebsd-questions