From owner-freebsd-questions@FreeBSD.ORG Fri Oct 29 14:10:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9ED116A4FB for ; Fri, 29 Oct 2004 14:10:25 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D6DA043D1F for ; Fri, 29 Oct 2004 14:10:24 +0000 (GMT) (envelope-from krylon@gmx.net) Received: (qmail 4285 invoked by uid 65534); 29 Oct 2004 14:10:24 -0000 Received: from i53875AF8.versanet.de (EHLO [192.168.0.13]) (83.135.90.248) by mail.gmx.net (mp008) with SMTP; 29 Oct 2004 16:10:24 +0200 X-Authenticated: #685629 Message-ID: <41824F4F.50608@gmx.net> Date: Fri, 29 Oct 2004 16:10:23 +0200 From: Benjamin Walkenhorst User-Agent: Mozilla Thunderbird 0.7.3 (X11/20041025) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hadi Maleki-Baroogh References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: question.. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 14:10:26 -0000 Hadi Maleki-Baroogh wrote: > my freebsd system tries to start syslogd, panics on ffswrite, and > initiates a boot.. > it looks like it's continually cycling.. > > anyone know what can cause this? Not really. ;-? *Maybe*, just maybe, it is because syslog can't write. Maybe file/folder permissions are wrong, maybe filesystem flags like schg/uchg are active or the filesystem syslog tries to write to is mounted read-only... But there could, of course, be lots of other reasons as well. Maybe your harddisk is broken and the syslog-binary or the log-file or whatever is corrupted. Have you changed anything about the system recently? Try booting into single user mode and do an fsck. I found that if the system crashes too often without being able to do a fsck, at some point your filesystems become wrecked beyond hope for repair (5.2-RELEASE I was using at the time - though I have to note that the crashes were caused by faulty hardware). Also, on another machine, after crashing two times without being able to do a full fsck after the first crash, NetBSD 1.6.2-RC4 had somehow 'forgotten' about the disklabel. (Again, hardware issues) Kind regards, Benjamin