From owner-freebsd-questions Mon Dec 17 8:29:59 2001 Delivered-To: freebsd-questions@freebsd.org Received: from grlu5117.cnet.navy.mil (grlu5117.cnet.navy.Mil [160.127.129.23]) by hub.freebsd.org (Postfix) with ESMTP id 8D39037B41B for ; Mon, 17 Dec 2001 08:29:55 -0800 (PST) Received: from penx68322m1.cnet.navy.mil (pens0394.cnet.navy.Mil [160.125.210.190]) by grlu5117.cnet.navy.mil (8.9.3 (PHNE_18546)/8.9.3) with ESMTP id KAA07716; Mon, 17 Dec 2001 10:29:50 -0600 (CST) Received: by pens0394.cnet.navy.Mil with Internet Mail Service (5.5.2653.19) id ; Mon, 17 Dec 2001 10:33:34 -0600 Message-ID: From: "Burt, Randall -CONT(DYN)" To: "'Stan Brown'" , freebsd-questions@FreeBSD.ORG Subject: RE: 2bd request, help with older softupdates filesystem Date: Mon, 17 Dec 2001 10:33:34 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, I'm new to this, so forgive. You might try putting the drive in the freezer for about 30 minutes or so. It sounds crazy, but I read that this has allowed some folks around 10 minutes of up time on a failing disk. This assumes, of course, that the disk itself is the problem. -----Original Message----- From: Stan Brown [mailto:stanb@panix.com] Sent: Monday, December 17, 2001 9:34 AM To: freebsd-questions@FreeBSD.ORG Subject: 2bd request, help with older softupdates filesystem I posted this yesterday, but go no replies. Sorry for the repost, but I really neeed some advice here. I have a machien that has been runing for a long time with a large quantity of data on it (It's a webserver). It's running 3.4 STABLE (yes I know I should have updateetd). It crashed, and on the way up when it tried to run fsck on the /var partition (IDE drive) it failed. I went inot single user and tries to run: fsck -y /dev//wd0s1e I got a buch of correctinos, nut it finally stoped with. fsck: Cannot find inode 252 What can I do to get this system up long enough to get the data off of it? Is it likely this is a genuine disk problem, or is it possible this is a softupdates problem? This partiton BTW is /var, so I'm hoping the /usr partiton, where the data is is recoverable! -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin 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