Date: Wed, 25 Feb 1998 14:22:56 +1030 From: Greg Lehey <grog@lemis.com> To: Grimm <grimm@shell.pgonline.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Recovering from disaster... Message-ID: <19980225142256.26908@freebie.lemis.com> In-Reply-To: <Pine.BSI.3.95.980224193809.11429A-100000@shell.pgonline.com>; from Grimm on Tue, Feb 24, 1998 at 07:38:50PM -0800 References: <Pine.BSI.3.95.980224193809.11429A-100000@shell.pgonline.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 February 1998 at 19:38:50 -0800, Grimm wrote: > I installed some new RAM today, without realizing that it wasn't > non-parity (and leaving on the parity check in the CMOS) and FreeBSD, on > bootup, panicked with the inevitable parity error. > > Now, when I try to boot up, what happens is that the kernel tells me that > /, /usr and /var weren't unmounted properly, and that it can't fix them, > (Error in Superblock, IIRC) and reboots automatically. > > Booting into single-user mode doesn't help much either. I can't mount > /usr, for instance. I'm scared to use fsck, because it trashed my drive > under similar circumstances before. If you don't use fsck, you don't recover the file systems. Period. I don't know of fsck trashing file systems (though I won't pretend it can't happen). Typically, if you have a trashed file system after fsck, it was trashed before. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980225142256.26908>