Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Dec 2001 16:37:08 +0100
From:      "Anthony Atkielski" <anthony@freebie.atkielski.com>
To:        <questions@FreeBSD.ORG>, <syjef@hal-pc.org>
Subject:   Re: Help with a rash of panics
Message-ID:  <01e101c184b5$31a63e10$0a00000a@atkielski.com>
References:  <200112141525.JAA26408@mail.hal-pc.org>

next in thread | previous in thread | raw e-mail | index | archive | help
From your description, it appears that the only thing that changed between
the time before you got the panics and the time after was your physical
moving of the system.  Therefore it is logical to assume that you have a
hardware problem.  You can rebuild your disk structure from your most recent
backups and see if the problem goes away (which it might, if the hardware
problem was temporary and has now gone away).  If the problem persists, you
probably will have to replace some hardware, most likely the disk drives,
since they the most sensitive to movement.  You'll want to take a full
backup before the hardware replacement and then restore everything from
scratch afterwards.

If you changed something in software at the same time, then software might
still be the problem.  But software doesn't change by itself, so if it
worked before, it should continue working now, and if it stops working,
hardware is the immediate suspect.

----- Original Message -----
From: <syjef@hal-pc.org>
To: <questions@FreeBSD.ORG>
Sent: Friday, December 14, 2001 16:25
Subject: Help with a rash of panics


> I will give the short version of the story.  If anyone thinks the long
version
> will be helpful, I will see what all I can give you.
>
> I recently moved to a new house, and when I first tried to bring my system
(a
> Pentium III, Asus MB, a Western Digital HD as primary master and Samsung
and
> primary slave) I was met with several messages scrolling by referring to
inode
> problems.  This happened during the automatic checks while the filesystems
were
> being mounted. The system had been shutdown correctly prior to being
moved.  At
> this time I was running 4.4-(STABLE?).  From that point in time I have
received
> kernel panic after kernel panic, probably 95% of the time they have been
ufs
> related, the other 5% have pretty well been invalid page faults.  The
Western
> Digital HD checks out under their data lifeguard tools.  I have no
diagnostic
> tools for the Samsung.
>
> Having lost enough data through these repeated panics I went out and
bought the
> most recent copy of FreeBSD I could find, which was 4.3.  I have finally
gotten
> that installed, but I did not newfs my root filesystem.  The problem
persists.
> Today I received a panic that I hope will shed some light on this.  I was
> trying to dump my root filesystem and in the process received the
following
> message:
>
> /: bad dir ino 14338 at offset 2252: mangled entry
> panic: ufs_dirbad: bad dir
>
> I think the first line resembles the messages I would see scroll
occassionally
> while the system was booting.  Does this message mean anything to anyone?
> Thanks so much for the
> help.
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01e101c184b5$31a63e10$0a00000a>