From owner-freebsd-questions@FreeBSD.ORG Thu Mar 3 03:29:32 2005 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 6831916A4CE for ; Thu, 3 Mar 2005 03:29:32 +0000 (GMT) Received: from shell.reiteration.net (82-34-179-228.cable.ubr01.sout.blueyonder.co.uk [82.34.179.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBBC243D55 for ; Thu, 3 Mar 2005 03:29:31 +0000 (GMT) (envelope-from lists@reiteration.net) Received: from [127.0.0.1] (helo=reiteration.net) by shell.reiteration.net with esmtp (Exim 4.44 (FreeBSD)) id 1D6h4e-000N8o-D9 for freebsd-questions@freebsd.org; Thu, 03 Mar 2005 03:32:28 +0000 From: "John" To: freebsd-questions@freebsd.org Date: Thu, 3 Mar 2005 03:32:25 +0000 Message-Id: <20050303031238.M39321@reiteration.net> X-Mailer: Open WebMail 2.50 20050106 X-OriginatingIP: 192.168.1.7 (jfm) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: lists@reiteration.net X-SA-Exim-Scanned: No (on shell.reiteration.net); SAEximRunCond expanded to false Subject: correcting hard errors on IDE drive 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: Thu, 03 Mar 2005 03:29:32 -0000 Hello list The system giving these errors is in a data centre. I got mailed this in my daily system log: > ad0s1f: hard error reading fsbn 266219 (ad0s1 bn 266219; cn 16 tn 145 sn 44) status=59 error=40 > ad0s1f: hard error reading fsbn 110559243 of 266214-266233 (ad0s1 bn 110559243; cn 6881 tn 253 sn 39) status=59 error=40 > ad0s1f: hard error reading fsbn 266219 (ad0s1 bn 266219; cn 16 tn 145 sn 44) status=59 error=40 > ad0s1f: hard error reading fsbn 110559231 of 266208-266221 (ad0s1 bn 110559231; cn 6881 tn 253 sn 27) status=59 error=40 This is an IDE drive, btw. that's all there was. I know I need to run fsck on that partition, the problem is I need to do it remotely, and that partition is in fact /var/log so there's a lot of processes writing to it. I can stop the various daemons running on the server and restart them if need be. The question is, how can I remain at an interactive root login whilst taking the system down to a level so I can umount /var/log without having to visit the datacentre? I don't think the system will come up in a state where I can ssh into it if I just uncomment /var/log in /etc/fstab -- lists@reiteration.net