From owner-freebsd-questions@FreeBSD.ORG Mon Aug 29 08:31:36 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 A04C616A41F for ; Mon, 29 Aug 2005 08:31:36 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from aomailrelay01.atosorigin.es (aomailrelay01.ATOSORIGIN.ES [195.76.254.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2379B43D45 for ; Mon, 29 Aug 2005 08:31:35 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from AOAV02.atosorigin.es ([172.24.0.163]) by aomailrelay01.atosorigin.es (iPlanet Messaging Server 5.2 HotFix 1.09 (built Jan 7 2003)) with ESMTP id for freebsd-questions@freebsd.org; Mon, 29 Aug 2005 10:37:29 +0200 (Romance Daylight Time) Received: from mailmad05.es.int.atosorigin.com ([172.24.0.162]) by AOAV02 with trend_isnt_name_B; Mon, 29 Aug 2005 10:38:41 +0200 Received: from [172.24.8.84] (es-gmbhr1j.es.int.atosorigin.com [172.24.8.84]) by mailmad05.atosorigin.es (iPlanet Messaging Server 5.2 HotFix 1.26 (built Mar 31 2004)) with ESMTPA id for freebsd-questions@freebsd.org; Mon, 29 Aug 2005 10:31:26 +0200 (Romance Daylight Time) Date: Mon, 29 Aug 2005 10:31:25 +0200 From: Erik Norgaard In-reply-to: <20050828085725.K11358@dualman.cableone.net> To: Denny White Message-id: <4312C7DD.2000305@locolomo.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050824) References: <20050828085725.K11358@dualman.cableone.net> Cc: freebsd-questions@freebsd.org Subject: Re: fsck on corrupted / X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 08:31:36 -0000 Denny White wrote: > The problem started with a power outage before I > had the box in question on a ups. I switched it > to the ups and ran fsck and thought all was well. > Then I started having periodic reboots. After the > last one, the system would crash about the time > fsck was checking pathnames. Have tried running > fsck on / from both single user mode and from the > fixit live cd. Same thing, crashes. Any help/ideas > greatly appreciated. If you can, try to boot mounting / read-only, at least you shouldn't get disk errors on that label then. But this may just be your disk degrading from bad to worse untill it's final death :-( Do you get any READ_DMA or WRITE_DMA errors? I remember that there has been a lot of threads regarding disk errors the last month, try searching the archive for hints. For example you should be able to lower throughput using ata_control, this may reduce problems. Cheers, Erik ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus ------------------------------------------------------------------