From owner-freebsd-questions Tue Dec 14 4:10: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from kens.com (kens.com [129.250.30.40]) by hub.freebsd.org (Postfix) with ESMTP id 4C9AF14E3A for ; Tue, 14 Dec 1999 04:09:55 -0800 (PST) (envelope-from rsocha@kens.com) Received: (from rsocha@localhost) by kens.com (8.9.3/8.9.3-mod-for-majordomo) id HAA25055 for freebsd-questions@freebsd.org; Tue, 14 Dec 1999 07:09:53 -0500 (EST) Date: Tue, 14 Dec 1999 07:09:52 -0500 From: "Robin S . Socha" To: freebsd-questions@freebsd.org Subject: fsck fails - inode not found Message-ID: <19991214070952.A25001@kens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all, I wish I could have lurked longer than 3 days, but... I'm running FreeBSD 3.1-RELEASE (Intel Pentium, IDE - stock hardware) on our company mailserver. I tried updating to 3.3 this morning via cvsup. The server crashed for no apparent reason. fsck bails out during its Connectivity Check, saying "inode 90459... not found". The partition can be mounted and I've managed to make a backup of the few files I've already altered. However, I'm loath to reinstalling the entire machine. Does fsck's error message ring any kind of bell for anyone? Thanks in advance, Robin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message